ADR-0001: GEO plus an MCP agentic layer as the core differentiator

• Status: Accepted
• Date: 2026-07-30 (recorded; decision predates this, see ../source/JSGlobtech_GEO_Agency_Playbook.pdf authored 2026-07-27)
• Deciders: Junaid Siddiqui (owner)
• Related: ../strategy/positioning.md, ../integrations/mcp-server.md, ADR-0002, ADR-0003, ADR-0007

Context

Search demand is shifting from traditional engines to LLMs (ChatGPT, Gemini, Perplexity). A business absent from generated answers loses demand it cannot see or measure. Traditional SEO optimises for humans clicking links, which does not make a business legible to a generative engine.

The available positions for a small Dubai agency entering this space:

1. Content-only GEO — rewrite copy and add schema. Low barrier, and exactly what legacy marketing agencies are already pivoting to. Easily commoditised.
2. Visibility plus an action layer — publish machine-readable facts and expose real tools an AI can invoke, so the engine can act on the business's behalf inside the chat.
3. Pure custom AI engineering — no GEO narrative, just build what clients ask for. Harder to market, no repeatable story.

JSGlobtech is a software engineering shop, not a marketing agency, which makes option 2 the position it can defend and competitors cannot easily copy.

Decision

Position the offer as two layers, and lead with the second:

• Visibility layer (GEO) — structured, machine-readable facts so engines cite and factualise the business accurately.
• Agentic Action Layer (MCP) — a remote Model Context Protocol server exposing real tools, so the engine can capture leads and trigger workflows rather than merely mention the client.

The action layer is the differentiator. Marketing agencies cannot ship it; it is engineering work.

Consequences

• Positive:
  • Defensible against content-only competitors, and it plays to existing engineering capability.
  • The value proposition is demonstrable rather than asserted — the endpoint is live and can be run in front of a prospect (ADR-0007).
  • Creates a natural upsell ladder: visibility first, action second, custom integrations third.
• Trade-offs / costs:
  • Requires MCP infrastructure per client, so delivery is heavier and hosting becomes an ongoing obligation.
  • MCP is young; specs and client behaviour still shift, so maintenance is non-trivial.
  • Explaining "agentic action" to non-technical buyers needs deliberate framing (../sales/pitch-script.md reduces it to "digital receptionist").
• Follow-ups:
  • Playbook §1 claims booking and reservation processing; only lead capture exists. Either build them or stop claiming them (../integrations/mcp-server.md).
  • Reconcile the "GEO agency" framing with the site's "development agency" framing — ADR-0005.