# geolocal.io — Canonical Strategy **Status:** Draft operating strategy (2026-07-18) **Role:** The document the team plans, builds, and sells against. When other docs disagree with this one, update them — or update this one deliberately. Do not leave the conflict hanging. --- ## 1. What we are geolocal.io is the infrastructure that lets local service businesses show up properly inside the AI era — discoverable, understandable, bookable, and measurable when someone asks ChatGPT, Claude, Gemini, or the next assistant for a plumber, a transmission shop, a fishing charter, or a place to rent bikes. We are not building another place for consumers to browse. We are not selling business owners a chatbot for their website. We are not trying to replace Yelp or Google as destinations people open on purpose. We are the layer underneath. AI agents call us. Businesses own their presence. Tourism boards, chambers, and agencies help distribute it. In plain terms: we want to be for local services what Shopify’s Storefront MCP became for online stores — a simple, standard way for any AI to talk to a real business and complete the job. --- ## 2. Why this has to exist ### Consumers already changed behavior A large and growing share of people now ask AI tools for local recommendations. BrightLocal’s 2026 consumer research puts that figure around 45%, with ChatGPT as the most common tool people name. Earlier surveys used different wording and showed much smaller numbers (around 6% in some 2025 reporting), so we should treat the leap as real without pretending every percentage point is apples-to-apples in investor decks. What matters operationally is the shape of the answer. AI does not hand you a page of blue links. It names one, two, or three businesses. If you are not one of those names, you do not exist in that moment. Practitioners talking about this on the open web describe the same thing: local discovery is collapsing into a shortlist of recommendations, not a results page. ### AI is extremely selective about who it recommends SOCi’s 2026 Local Visibility Index looked at roughly 350,000 locations across more than 2,700 multi-location brands. In that sample, ChatGPT recommended only about 1.2% of brand locations. Gemini and Perplexity were higher (around 11% and 7%) but still far below traditional Google local 3-pack visibility (around 36%). Locations that do get recommended tend to look trustworthy — ChatGPT’s picks averaged about 4.3 stars. Other local SEO research has also found that AI systems lean hard on listings and review sources. Yelp, for example, shows up frequently as a cited source in local answers. That is good news for platforms that already own data. It is bad news for the independent shop whose only online presence is a dusty website and a half-maintained Google listing. Traditional local SEO still matters. It is no longer enough. Businesses need a machine-readable, up-to-date, bookable expression of who they are. ### The big platforms are building for themselves This is the structural opening. Shopify has already shipped Storefront MCP on merchant domains so agents can search catalogs, manage carts, and move toward checkout without scraping a site. Yelp has published an official MCP path into its own Fusion AI data. Google is wiring MCP into Maps grounding and Merchant tooling and has partnered on open commerce protocols. Cal.com already exposes a serious booking MCP — create, reschedule, cancel, availability — so scheduling is not a greenfield problem. What none of them are building is a neutral, business-owned on-ramp for the long tail of local services: Bob’s Garage, the surf shop, the charter captain, the salon, the tourism board that wants its members to be helpful to visitors’ AI assistants. Incumbents protect their platforms and their datasets. We build the missing infrastructure for everyone else. --- ## 3. North Star Make AI give the most relevant and helpful recommendation for a local service need — and then fulfill it. Relevance gets you on the shortlist. Helpfulness is why the assistant comes back next time. Helpfulness means clear services, real specialization, honest pricing signals, real availability, a clean booking path, trust cues, and a track record of successful outcomes. When an AI finds a path that works repeatedly, it prefers that path. Our job is to make geolocal-backed businesses the path of least resistance for helpfulness. We stay focused on local service businesses. We are not trying to boil the ocean of all commerce. --- ## 4. Four business models (keep them distinct) This company is not one product with one customer. It is four stacked models that reinforce each other. Earlier planning materials mostly described the first one. That is part of why the project felt fractured. All four stay in view. ### Model 1 — Endpoint enablement Individual small businesses attach to geolocal. They get a hosted multi-tenant MCP, a tiny pointer on their own website, a self-service portal, diagnostics, and ongoing reports. This is day-zero product. ### Model 2 — Intermediate enablement Tourism boards, chambers of commerce, and visitor bureaus become discovery nodes. They get an aggregating MCP for a destination or membership set, tools to onboard members, and a story they can take to leadership about visitor experience and economic development. This is our primary go-to-market wedge for scale. ### Model 3 — Industry trust layer Over time, quality norms, genre standards, and decommissioning of bad data make geolocal a surface AI systems learn to prefer. This is not a year-one revenue line so much as the strategic prize of doing Models 1 and 2 well. ### Model 4 — Service graph Once enough endpoints and intermediates exist, the network itself becomes valuable: related businesses, specialties, demand patterns, competitive context. Think of an AI-native successor to the old local directory graphs — not a consumer portal, but infrastructure and data products built on real usage. **Operating rule:** Every product decision should name which model it serves. We do not build Model 4 features before Models 1 and 2 are real. --- ## 5. What we actually sell ### The offer We sell AI-readiness infrastructure for local services. In practice that means: 1. **A hosted multi-tenant MCP** that agents can call for structured business truth — story, services, hours, booking path, related businesses, and later genre-specific detail. 2. **A dead-simple discovery pointer** on the business’s own site (for example a well-known path or JSON file) that points at us. No servers for Bob’s daughter to manage. Pattern-wise, this is the same idea as Shopify putting MCP on the merchant domain while hosting the hard parts. 3. **A Self-Service Portal** — the real product experience for owners (described below). 4. **Orchestration, not reinvention.** Cal.com for booking. Stripe for payments. We integrate; we do not rebuild their categories. 5. **Telemetry and optimization reports** — how often agents hit you, what they asked for, where your site or data failed, and what demand looks like in your area. 6. **Surfaces for partners and intermediates** — agencies, SEO consultants, tourism boards, chambers. ### The Self-Service Portal For a typical small business, the portal is how the product clicks. They come to geolocal.io and describe the business. The experience adapts to the genre — automotive feels different from a surf shop or a charter. We scrape their existing site and show them what the system already sees. Then we put a phone-and-chat style simulation in front of them: an assistant recommending their shop, listing real services, and finding a Thursday-at-three slot for the job they actually do. That is the aha moment. They are not buying abstract “AI optimization.” They are watching pre-qualified, in-scope, calendar-aligned demand show up. To make that real, they install a tiny pointer on their site. We walk them through a preflight test in the browser against their live MCP. If the assistant cannot see services, hours, or specialty, they fix content or portal data before going live. We also give upstream guidance (how to get found in the first place — Google Business Profile, consistent NAP, plain-text city and service language, FAQs) and downstream guidance (how to keep the MCP helpful). If they need website help, we can introduce a partner. After launch, they get regular reports on interactions, intents, and local demand. One line we will not blur: **we are not selling them a chatbot for their customers.** The chat UI inside the portal is a test harness so the owner can see how *external* assistants will interpret the business. That distinction matters for product, pricing, and sales language. ### Genre-specific primitives A generic “get business info” tool is fine for scaffolding. The durable product is genre systems — structured fields and tools that match how a category actually works. - Auto: makes and models, specialties, emergency flags - Beauty: services, duration, stylist context - Home services: service radius, emergency vs scheduled, estimate vs fixed price - Tourism activities: seasonality, capacity, weather sensitivity - Intermediates: member directory and category routing for a destination or chamber Roadmaps should ship **genre packs**, not only generic endpoints. ### What we will not build in the near term We are not a consumer destination app. We are not competing with Calendly, Cal.com, or Square as booking engines. We are not competing with Stripe or Square as payment rails. We are not replacing Google Business Profile. We are not building a Yelp-style review network. We are not trying to out-Kayak Kayak or out-Airbnb Airbnb. Stay complementary to travel platforms; own the local service long tail they do not serve cleanly for AI agents. --- ## 6. How we talk about ourselves ### Category AI-readiness infrastructure for local services — or, when you need a shorter phrase, agentic local commerce infrastructure. ### Analogies that help - **Shopify Storefront MCP for local services** — usually the clearest one-liner for technical and product people. - **Stripe for AI discovery and booking presence** — useful when you need “infrastructure, not another app UI.” - **Twilio for local service tools** — agents call a contract; the business does not rebuild a stack. ### Messaging that works - **Business owner:** Make every AI assistant understand and book your business. - **Tourism board:** Turn lodging-tax dollars into AI-discoverable local experiences your members own. - **Agency or partner:** Add AI-readiness as a productized line — not another chatbot retainer. - **Investor:** A neutral MCP layer for the vast majority of local services AI currently skips, distributed through self-serve and municipal partners. ### Language to avoid Do not call this an AI chatbot for the website. Do not claim we replace Google or Yelp. Do not position primarily as “an SEO tool with AI features,” even though discovery guidance is part of the portal. Category is infrastructure. --- ## 7. Go-to-market ### Primary wedge: tourism and destination intermediates Hotel and lodging taxes create promotion budgets that destinations are often required to spend. Boards and visitor organizations frequently struggle to spend that money well, and many run open calls for ideas. One intermediate relationship can bring dozens or hundreds of member endpoints online at once. Travel is also an area where AI referral behavior has been growing quickly in industry reporting. The brochure rack in the hotel lobby is the analog world proving the job to be done; geolocal is the AI-native version of that job. Motion: 1. Choose one or two destination markets for a real pilot. 2. Sell a board-level pilot: destination MCP, member onboarding through the portal, and a simple dashboard of member hits and category demand. 3. Fund it with tourism marketing budgets, innovation RFPs, or “AI visitor experience” framing — whatever matches how that board already buys. 4. Give members free or discounted endpoints during the pilot, then convert to paid. ### Parallel motion: self-service small businesses While intermediates mature, we also sell direct. First genre packs should be high-intent local services — auto repair, beauty, home services — and tourism activities when a destination pilot needs them. Pricing direction for self-serve (infrastructure framing, not chatbot usage): | Tier | Monthly | Intent | |------|---------|--------| | Starter | about $49 | Endpoint, portal test experience, monthly report, basic diagnostics | | Core | about $129 (anchor) | Full MCP, live preflight, weekly reports, local demand insights, partner access | | Pro | about $249 | Multi-site, deeper telemetry, competitor signals, priority support | Position above DIY chat widgets and below enterprise multi-location AI visibility platforms. Tourism board deals use separate pilot or enterprise pricing, not the SMB price list. ### Partners as distribution, not the product Agencies, SEO shops, and local web people matter. They are how hard websites get fixed and how busy owners get onboarded. They are not the center of the product story. The portal offers self-serve or “talk to a partner.” Commission and wholesale terms come after we have real attach volume — roughly after the first fifty to a hundred endpoints. ### Where we will not lead We do not lead with national multi-location brand AI visibility (that is a different buyer and a different set of competitors). We do not lead with pure e-commerce (Shopify already owns that MCP story). We do not lead with pure B2B or non-local use cases. --- ## 8. Competitive posture ### How the vacuum gets filled — and our answer | Actor | Likely path | Our response | |-------|-------------|--------------| | Yelp | Become a default AI source of local truth via MCP and data licensing | Offer business-owned truth and a booking path the business controls; stay complementary when agents need owner data Yelp cannot provide | | Google | Maps, Merchant, and open commerce protocols | Stay complementary; help owners with Business Profile hygiene; do not fight Maps for consumer UI | | Shopify | Keep expanding agentic commerce | Copy the good patterns (merchant-domain discovery, hosted complexity); do not compete for e-commerce | | Cal.com, Square, Vagaro | Booking and ops MCPs | Integrate deeply; own discovery, genre, intermediates, and graph | | AI visibility SaaS for big multi-location brands | Measure and optimize enterprise footprints | Different customer; we own long-tail endpoints and destination distribution | | Local agencies | Manual “get recommended by AI” retainers | Make them partners; productize what they cannot scale alone | ### Moats, in the order we earn them 1. Endpoint density in specific geos and genres 2. Genre primitive quality that AI systems prefer because it is more helpful 3. Telemetry flywheel — demand signals improve recommendations, which attract more attach 4. Intermediate contracts that lock distribution 5. Trust and quality enforcement — freshness, decommissioning, reliability Compared with older local graphs that depended on social check-ins, our freshness comes from the real service economy: availability, bookings, content updates, and agent interactions that do not dry up unless local commerce dries up. --- ## 9. What success looks like ### First 90 days - Public multi-tenant MCP over HTTP (stdio alone is not a product agents on the open internet can use) - Self-Service Portal MVP: onboard, scrape reflection, simulation, pointer install, preflight - About 100 live endpoints - One tourism or destination pilot at LOI or live pilot stage - One or two genre packs - Booking path via Cal.com (link first is acceptable; deeper API or MCP orchestration next) - First dollars of ARR, even if small — proof someone will pay ### By 180 days - About 1,000 endpoints - Three genres - Related-businesses handshake in production - Several intermediate dashboards active - Telemetry good enough for real owner reports ### By 360 days - About 10,000 endpoints - Several major chamber or tourism partnerships - Early anonymized demand or data product in beta or market - Case studies showing that, in pilot geos, assistants prefer geolocal-backed paths These are planning bars, not financial covenants. Adjust with evidence; do not quietly abandon them. --- ## 10. Product and technical priorities User stories and distribution come before elegant architecture theater. **Priority 0 — prove Model 1** 1. HTTP MCP transport 2. Multi-tenant routing by business slug or domain 3. Portal spine: signup → scrape → simulation → pointer → preflight 4. Manifest / well-known generator 5. Seed genres and real pilot businesses 6. Cal.com path (redirect first, deeper integration next) **Priority 1 — prove Model 2** 7. Intermediate (tourism) MCP and member aggregation 8. Board dashboard for members, hits, and categories 9. Pilot paperwork and data agreements **Priority 2 — feed Models 3 and 4** 10. Telemetry pipeline and owner reports 11. Related businesses tool and quality rules 12. More genre packs 13. Partner marketplace **Explicitly later:** full white-label everywhere, heavy OAuth before we need it, a public developer platform, a full data-as-a-service product, and CMS plugins until attach volume demands them. --- ## 11. Risks we take seriously **Yelp or Google become “good enough.”** We counter with business-owned data, booking completion, genre depth, intermediate distribution, and a clear owner-control story. **Small businesses will not care until bookings prove ROI.** The portal’s live simulation, tourism-funded pilots, demand reports, and partner-assisted installs exist to close that gap. **MCP and discovery conventions will keep moving.** Follow patterns the industry already recognizes (merchant-domain discovery, well-known locations, multi-path fallbacks). Do not invent a private religion. **Market statistics get oversold in the pitch.** Cite sources carefully. Distinguish multi-location brand studies from the entire SMB universe. Prefer honesty over hype; the opportunity is large enough without exaggeration. **Scope creeps into chatbots or consumer marketplaces.** Weekly check: are we still infrastructure? If the answer is fuzzy, cut scope. **Engineering builds tools nobody can activate.** No new MCP tool without a portal path that shows an owner why it matters. **Tourism procurement is slow.** Run self-serve SMB in parallel. Prefer short pilot contracts over perfect enterprise RFPs for the first win. --- ## 12. How we keep the docs honest | Document | Job | |----------|-----| | `docs/geolocal-copilot-conversation.md` | Historical exploration archive — useful context, not the operating manual | | **`docs/strategy/CANONICAL_STRATEGY.md` (this file)** | **Operating strategy the team rallies around** | | `NORTH_STAR.md` | Short compass; must stay consistent with this file | | `docs/gtm/*` | Execution detail for channels and sales; must describe this company, not a different one | | `docs/investors/*` | External packaging of this strategy | | `docs/engineering/*` | Build plan for the priorities above | | `code/` | Implementation of Priority 0 | If two documents disagree, either this file changes on purpose or the other document changes. Silence is how the project fractures again. --- ## 13. Near-term leadership decisions 1. Adopt this document as the single operating strategy (or mark specific sections for revision). 2. Rewrite `NORTH_STAR.md` so it reflects four models, the tourism wedge, and the Self-Service Portal — not a partner-dashboard-only story. 3. Mark stale any GTM material that collapses the company into one model or one channel. 4. Lock a short list of destination pilots and the first genre pack. 5. Treat Core ~$129 as the pricing anchor for experiments; do not block launch on perfect price discovery. 6. Charter engineering for a 30-day sprint: HTTP MCP, portal spine, and about ten real pilot endpoints — not more strategy prose. 7. Stand up lightweight legal: tourism pilot data terms, business terms of service, and basic telemetry privacy. Full data-product legal can wait. --- ## 14. Closing The version of this company that is worth building is the ambitious one: endpoint infrastructure, intermediate distribution, a trust layer AI systems learn to prefer, and eventually a service graph that compounds. The thin version — “a partner dashboard that spits out an MCP file” — is easier to write down and much easier for someone else to crush. Market conditions in 2026 support urgency without requiring panic. Consumers are using AI for local discovery. Recommendation is highly selective. Shopify, Yelp, Google, and Cal.com all prove that MCP is real — and each protects its own layer. The long tail of local services still lacks a neutral on-ramp. Our job as a funded planning team is to freeze a clear strategy, realign the docs, and execute the portal plus tourism pilot path until that vacuum starts filling under our name. --- ## Research notes Key external reference points used while drafting this strategy: - BrightLocal local consumer research (2026) on AI use for business recommendations - SOCi 2026 Local Visibility Index and related coverage on recommendation selectivity - Shopify Storefront MCP and agentic commerce materials - Yelp Fusion AI MCP (public repository and product pages) - Google Maps grounding and Merchant MCP materials - Cal.com MCP documentation for booking lifecycle tools - Public discussion of AI local discovery and agentic commerce Re-verify statistics before every external pitch. Prefer primary sources over secondary rewrites when the number matters.