Ty_Tech/geolocal-io
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: expand scope to local retail alongside services

Browse Source 
- Strategy §1a: brick-and-mortar services + local retail in scope
- Pure online e-com remains out (Shopify lane)
- ICP, NORTH_STAR, README, product docs aligned
- Add UC-03 general store (toothbrush / chicken strips case)
This commit is contained in:
VPS admin
2026-07-18 06:08:08 +00:00
parent 9478aaa22e
commit 4d04a4a65a
8 changed files with 257 additions and 100 deletions
Download Patch File Download Diff File Expand all files Collapse all files
NORTH_STAR.md
+8 -8
View File
@@ -4,17 +4,17 @@
## What Is It?
geolocal.io is the infrastructure that makes local service businesses discoverable, bookable, and transactable inside the agentic AI economy.
geolocal.io is the infrastructure that makes **local businesses** — services and local retail with real-world presence — discoverable, understandable, and actionable inside the agentic AI economy.
Here's what we actually do:
- Host a multi-tenant MCP server that gives AI agents structured access to a business's story, services, pricing, visuals, and real-time availability.
- Give businesses a dead-simple JSON file they drop on their website at `/.well-known/mcp-server`. That's it. No coding. No servers to manage. It points to us.
- Handle the full booking and payment loop through Cal.com and Stripe.
- Sell through agencies, SEO consultants, and Chambers of Commerce—people who already have the trust of business owners.
- Build a feedback loop where AI agents help us verify and correct business data in exchange for useful tools like "related businesses."
- Host a multi-tenant MCP server that gives AI agents structured access to a business's story, hours, services or assortment signals, specialties, visuals, and the right next step (book, visit, pick up).
- Give businesses a dead-simple pointer on their website (well-known or multi-path). No coding. No servers for them to manage. It points to us.
- Orchestrate booking and payment partners where those paths apply — we do not rebuild Calendly or Shopify.
- Sell through self-serve, agencies, SEO consultants, tourism boards, and Chambers — people who already have the trust of business owners.
- Build feedback and quality loops so helpfulness improves over time, including removing bad endpoints when they hurt trust.
We are not a destination site. We don't compete with Yelp or Google for user attention. We're the invisible layer that makes the long tail of local businesses actually work in the AI era.
We are not a destination site. We don't compete with Yelp or Google for user attention. We're the invisible layer that makes the long tail of local businesses actually work in the AI era — the garage **and** the general store.
---
@@ -92,7 +92,7 @@ This document is a short compass. The full operating strategy is:
**[docs/strategy/CANONICAL_STRATEGY.md](./docs/strategy/CANONICAL_STRATEGY.md)** (final draft)
Product map: [docs/product/](./docs/product/).
Use cases: [UC-01](./docs/product/use-cases/uc-01-endpoint-auto-repair.md), [UC-02](./docs/product/use-cases/uc-02-intermediate-tourism-board.md).
Use cases: [UC-01](./docs/product/use-cases/uc-01-endpoint-auto-repair.md), [UC-02](./docs/product/use-cases/uc-02-intermediate-tourism-board.md), [UC-03](./docs/product/use-cases/uc-03-local-retail-general-store.md).
Historical exploration: [docs/archive/](./docs/archive/).
Near-term execution: ship Priority 0 platform (HTTP MCP, ingestion, first genre pack, portal spine, real endpoints) and open one destination pilot conversation — without confusing the portal for the whole company.
README.md
+6 -4
View File
@@ -1,23 +1,25 @@
# geolocal.io
AI-native infrastructure for local business discovery, storytelling, visuals, and booking via MCP. Powers the long tail of independent service businesses that big platforms do not serve cleanly in the agent era.
AI-native infrastructure for local business discovery via MCP. Powers the long tail of independent brick-and-mortar — services **and** local retail — that big platforms do not serve cleanly in the agent era.
## Start here
1. **[Canonical Strategy](./docs/strategy/CANONICAL_STRATEGY.md)** — operating truth (final draft)
2. **[North Star](./NORTH_STAR.md)** — short compass
3. **[Product overview](./docs/product/overview.md)** — platform vs activation
4. **[Use cases](./docs/product/use-cases/)** — UC-01 endpoint, UC-02 tourism intermediate
4. **[Use cases](./docs/product/use-cases/)** — UC-01 services, UC-02 tourism, UC-03 local retail
## What this is
geolocal.io makes local service businesses discoverable, bookable, and measurable inside AI assistants by:
geolocal.io makes **local businesses** discoverable and actionable inside AI assistants by:
- Hosting a **multi-tenant MCP** agents can call for structured business truth
- Giving businesses a **simple pointer** on their own site (no servers for them to run)
- Providing a **Self-Service Portal** so owners can see and test how AI understands them
- Working with **tourism boards, chambers, and partners** for distribution
- Integrating **Cal.com** and **Stripe** for booking and payment — we orchestrate, we do not rebuild those categories
- Integrating booking, payment, and later inventory partners where those paths apply — we orchestrate, we do not rebuild Shopify or Calendly
Scope includes **local services and local retail** with real presence (see strategy §1a). Pure online e-commerce is out of scope.
We are not a consumer destination site. We are infrastructure.
docs/gtm/ideal-customer-profile.md
+48 -37
View File
@@ -1,69 +1,80 @@
# ICP Definition – geolocal.io
> **Single source of truth.** All investor, GTM, and engineering docs must reference this file for persona details.
> Last updated: 2026-07-16
> **Single source of truth for who we sell to.** Aligns with [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) §1a.
> Last updated: 2026-07-18
---
## Primary ICP (Tier 1 – "The Perfect Fit")
## Primary ICP (Tier 1 – best fit)
| Attribute | Description |
|-----------|-------------|
| **Business type** | Independent, locally-owned SMBs with physical presence or local service radius. |
| **Typical verticals** | Wellness (yoga, pilates, massage), personal care (salons, barbers), home services (cleaning, landscaping, handymen), boutique retail (florists, bike shops, bakeries). |
| **Employees** | 1–10 (solo-preneurs to micro-teams). |
| **Revenue** | $50k–$500k annual gross revenue. |
| **Tech maturity** | Has a website (even a simple one) but no dedicated head of marketing or IT. Uses at least 1 booking tool (e.g., Cal.com, Squarespace Scheduling, Vagaro) or POS that supports appointments. |
| **Pain point** | Loses walk-in / phone-in leads to AI assistants (Siri, ChatGPT, Alexa) that cannot find or book them; feels invisible in voice/search results. |
| **Motivation** | Wants to be "found" by AI without learning new software. Willing to pay if it delivers 3–5 new bookings/month. |
| **Business type** | Independent, locally owned SMBs with a **physical location** or clear local service radius. Includes **services and local retail**. |
| **Typical verticals** | **Services:** wellness, personal care, home services, auto repair, tourism activities. **Local retail:** general stores, hardware, pharmacies, gift/outfitter shops, specialty food. **Hybrid:** bike shops, marinas, bakeries that sell and serve. |
| **Employees** | 1–15 (solo operators to small teams). |
| **Revenue** | Roughly $50k–$1M annual gross (directional, not a hard gate). |
| **Tech maturity** | Has some web presence (even thin). May use booking tools, POS, or neither. No dedicated AI/engineering team. |
| **Pain point** | AI assistants cannot reliably describe them, recommend them, or complete a next step (book, visit, buy/pickup). They lose the “named recommendation” moment. |
| **Motivation** | Want AI to tell the truth about what they do or carry — without learning a new craft stack. Will pay if it drives visits, calls, bookings, or sales. |
**Illustrative retail case:** A general store in Athol, Idaho should be able to make ChatGPT-class assistants answer: we carry toothbrushes; the chicken strips are a local favorite; here are hours and how to get here — from the store’s own structured truth, not a guess.
---
## Secondary ICP (Tier 2 – "The Enterprise-Lite")
## Secondary ICP (Tier 2)
| Attribute | Description |
|-----------|-------------|
| **Business type** | Regional franchises or multi-location SMBs (5–20 locations). |
| **Typical verticals** | Dental clinics, auto repair chains, tutoring centers. |
| **Tech maturity** | Has a central CRM or scheduling API; needs a bulk implementation. |
| **Motivation** | Wants to standardise AI-discovery across all locations with minimal custom dev. |
| **Business type** | Multi-location local brands or regional operators (a handful to ~20 locations). |
| **Typical verticals** | Multi-site auto, dental, tutoring, small retail chains with local stores. |
| **Motivation** | Standardize AI-readiness across locations with light ops burden. |
---
## Common attributes across all ICPs
## Intermediate ICP (distribution, not the end SMB)
- **Booking-dependent:** Must take appointments or reservations online.
- **Payment-ready:** Accepts credit cards (Stripe, Square, or PayPal) – required for the transaction loop.
- **Google Maps presence:** Has a Google Business Profile (needed to verify physical location).
- **Decision-maker:** Owner or store manager (not a corporate procurement department).
- **Budget signal:** Currently spends >$100/mo on at least one marketing channel (Meta ads, Google Ads, or SEO tool).
| Attribute | Description |
|-----------|-------------|
| **Type** | Tourism boards, visitor bureaus, chambers of commerce. |
| **Job** | Fund and aggregate member AI-readiness; improve destination helpfulness. |
| **See** | [UC-02](../product/use-cases/uc-02-intermediate-tourism-board.md) |
---
## Buying signals we look for
## Shared fit signals
1. Mentions "not showing up in ChatGPT" or "Alexa can't find us."
2. Currently uses a paper/phone booking system alongside a digital one.
3. Has asked their agency/SEO consultant about "AI search optimisation."
4. Churn risk with current booking software (complains about cost or complexity).
- Place-based: consumers ask about them with a location in mind
- Owner or store manager can decide (not only enterprise procurement)
- Willing to put a small discovery pointer on a site or landing page
- Some path to value: appointments **or** walk-in/pickup/retail demand **or** both
- Often already spending something on ads, SEO, or web help (not mandatory)
---
## Buying signals
1. “ChatGPT / AI doesn’t know we exist” or recommends a competitor
2. Phone and foot traffic still matter; online presence is weak or outdated
3. Agency or chamber asking about AI search / AI visitor experience
4. Tourism or main-street context where “what’s here / what do they have” is the job
---
## Anti-ICP (do not target)
- E-commerce only (no physical/local service).
- Enterprise with >100 locations and dedicated engineering teams (they will build internally).
- Pure B2B SaaS or products sold via distributors (no direct consumer booking).
- Businesses that do not accept online payments.
- **Pure e-commerce** with no meaningful local footprint (Shopify’s world)
- Enterprise with large dedicated engineering teams building their own agent stack
- Pure B2B with no consumer or visitor discovery motion
- National marketplaces and travel packagers (Airbnb/Kayak class) as primary customers
Note: “Does not take online appointments” is **not** automatic anti-ICP. Many strong retail fits will not be booking-led.
---
## How to use this definition
## How to use this file
- **GTM teams:** Use the buying signals for lead scoring and partner briefs.
- **Engineering:** Use the tech-maturity attributes to scope the `.well-known` setup and default data model.
- **Investor docs:** Reference this as the "target wedge" – 1.2% of 33M US SMBs = our initial TAM.
- **GTM:** lead scoring and partner briefs
- **Product/engineering:** genre packs and data model must support services **and** local retail primitives
- **Investors:** wedge is long-tail **local** businesses, not “appointments SaaS only”
---
*Any updates to ICP must be made here first, then propagated to derivative docs.*
*Update this file first when ICP changes, then propagate.*
docs/product/genre-packs.md
+8 -7
View File
@@ -1,22 +1,23 @@
# Genre packs
Generic business fields are scaffolding. Durable differentiation is **genre-specific primitives** — structured tools and schemas that match how a vertical actually works.
Generic business fields are scaffolding. Durable differentiation is **genre-specific primitives**.
## Planned early packs
## Planned packs
- Auto repair (see [UC-01](./use-cases/uc-01-endpoint-auto-repair.md))
- Beauty
- Home services
- Tourism activity (especially with destination pilots / [UC-02](./use-cases/uc-02-intermediate-tourism-board.md))
- Tourism activity ([UC-02](./use-cases/uc-02-intermediate-tourism-board.md) context)
- **Local retail / general store** (see [UC-03](./use-cases/uc-03-local-retail-general-store.md)) — assortment signals, house specialties, hours, visit path
## Why this matters
Assistants evaluate helpfulness partly by whether the business answers the *right* questions for its category. “Do you work on Korean transmissions?” is not the same shape as “Do you have a sunset charter tomorrow for six?”
Assistants evaluate helpfulness by whether the business answers the *right* questions for its category. “Do you work on Korean transmissions?” is not the same shape as “Do you have a toothbrush?” or “Are the chicken strips still a thing?”
## Repo note (future)
## Sequencing
Genre packs will live under top-level `genres/` in a later monorepo phase. Product intent and use-case contracts stay here first.
Services packs may ship first for pilot speed. Retail is **in scope**, not a strategy exception.
## Detail source
[Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (genre-specific primitives).
[Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) §1a and genre primitives.
docs/product/overview.md
+10 -15
View File
@@ -1,13 +1,13 @@
# Product overview
geolocal.io is **AI-readiness infrastructure** for local services. Assistants call structured endpoints. Businesses own their presence. Intermediates and partners help distribution. Booking and payments are orchestrated through specialists, not rebuilt here.
geolocal.io is **AI-readiness infrastructure** for **local businesses** with real-world presence — services **and** local retail. Assistants call structured endpoints. Businesses own their presence. Intermediates and partners help distribution. Booking, payment, and inventory systems are orchestrated through specialists where needed; we do not rebuild Shopify for pure online stores.
## Platform vs activation
| Layer | Responsibility |
|-------|----------------|
| **Platform** | Multi-tenant MCP, multi-path discovery pointers, ingestion/content sync, genre packs, telemetry, quality enforcement (including quarantine/decommission), intermediate aggregation |
| **Activation** | Self-Service Portal and assisted onboarding so ordinary operators can turn the platform on |
| **Platform** | Multi-tenant MCP, discovery attachment, ingestion/content sync, genre packs (services + retail), telemetry, quality enforcement, intermediate aggregation |
| **Activation** | Self-Service Portal and assisted onboarding |
| **Distribution** | Tourism boards, chambers, agencies |
The portal is how Model 1 scales. It is not the product definition of the company.
@@ -17,23 +17,18 @@ The portal is how Model 1 scales. It is not the product definition of the compan
| Surface | Audience | Status |
|---------|----------|--------|
| MCP gateway | AI agents | MVP in `code/` (stdio); HTTP is Priority 0 |
| Genre packs | Vertical structure for agents + owners | Specified; auto pack first via UC-01 |
| Self-Service Portal | SMB owners / delegates | Specified in strategy + [ssp.md](./ssp.md); not built |
| Intermediate MCP + board tools | Tourism boards / chambers | Specified via UC-02; not built |
| Genre packs | Vertical structure for agents + owners | Services + retail in strategy; auto pack first via UC-01; retail via UC-03 |
| Self-Service Portal | SMB owners / delegates | Specified; not built |
| Intermediate MCP + board tools | Tourism boards / chambers | UC-02; not built |
| Partner flows | Agencies / local web | Distribution; after core attach |
## Canonical use cases
- [UC-01 Endpoint — auto repair](./use-cases/uc-01-endpoint-auto-repair.md)
- [UC-02 Intermediate — tourism board](./use-cases/uc-02-intermediate-tourism-board.md)
- [UC-03 Endpoint — local retail / general store](./use-cases/uc-03-local-retail-general-store.md)
## Where we sit in the assistant journey
## Scope reminder
We barely try to own pure discovery SEO. We are primary for evaluation, selection, and complementary fulfillment, and second chair for interpretation and feedback. Detail: [Canonical Strategy §5](../strategy/CANONICAL_STRATEGY.md).
## Related
- [genre-packs.md](./genre-packs.md)
- [ssp.md](./ssp.md)
- [intermediate.md](./intermediate.md)
- Engineering priorities in the strategy, roadmap under `docs/engineering/`
In: brick-and-mortar and local presence (garage **and** general store).
Out: pure online commerce with no local footprint. Detail: [Canonical Strategy §1a](../strategy/CANONICAL_STRATEGY.md).
docs/product/use-cases/README.md
+1
View File
@@ -6,6 +6,7 @@ Canonical use cases for product, engineering, and GTM. These are operating specs
|----|------|-------|--------|
| [UC-01](./uc-01-endpoint-auto-repair.md) | Endpoint activation — independent auto repair | Model 1 | Spec |
| [UC-02](./uc-02-intermediate-tourism-board.md) | Intermediate activation — destination tourism board | Model 2 | Spec |
| [UC-03](./uc-03-local-retail-general-store.md) | Endpoint activation — local retail / general store | Model 1 | Spec |
## How to write more of these
docs/product/use-cases/uc-03-local-retail-general-store.md
+114
View File
@@ -0,0 +1,114 @@
# UC-03 — Endpoint activation: local retail (general store)
**Status:** Spec
**Business model:** Model 1 — Endpoint enablement
**Primary surface:** Platform MCP + Self-Service Portal
**Priority:** In vision and ICP from day one; implementation may follow first service pack, not exclude retail from strategy
---
## 1. Problem
A small local retailer (example: a general store in Athol, Idaho) is easy for a human neighbor to understand and hard for an AI assistant to represent honestly. The store’s website, if it exists, is thin. Reviews may mention chicken strips once in 2019. Nothing structured says they carry basic toiletries, what the house specialties are, or when to come by.
When a traveler or local asks ChatGPT whether that store has a toothbrush or is worth stopping for food, the assistant either guesses, recommends a chain, or stays vague. The store never sees the miss.
---
## 2. Desired outcome
The operator can publish structured local truth so an assistant can answer, with grounding in the store’s own data:
- Yes — they typically carry everyday items like toothbrushes
- Yes — chicken strips (or another house specialty) are a known reason to stop
- Hours, location, and visit/pickup expectations
- Optional: limited “ask us” path if inventory is uncertain
This is **not** full real-time warehouse inventory for v1 unless the store already has a feed. Honest “we carry / house specialty / hours” beats fake precision.
---
## 3. Actors
| Actor | Role |
|-------|------|
| Owner / operator | Maintains what the store wants AI to say |
| Consumer | Asks an assistant a place-based retail question |
| AI assistant | External engine calling the MCP |
| geolocal platform | Hosted MCP, portal, ingestion, telemetry |
---
## 4. Preconditions
- Physical store location
- Ability to publish a discovery pointer (own site or simple landing page)
- Operator can list categories, flagship items, and specialties in plain language
- Optional later: POS/inventory integration for confirmed stock
---
## 5. Main success scenario
1. Operator signs up and chooses **local retail / general store** genre.
2. Portal scrapes any existing site and reflects gaps.
3. Operator enters or confirms: hours, categories carried, flagship items, house specialties, parking/visit notes.
4. Simulation shows an assistant answering “toothbrush?” and “what’s good here?” using that structured truth.
5. Pointer installed and preflight passes.
6. Live endpoint serves tools such as business info, hours, assortment/specialty summary, visit path.
7. Reports show what people (via agents) asked — including misses (“asked for propane; not listed”).
---
## 6. Alternate and exception paths
| ID | Case | Behavior |
|----|------|----------|
| A1 | No inventory system | Use “typically carry” categories and curated specialties; never claim live stock |
| A2 | Hybrid sell + service | Combine retail primitives with service/booking tools (e.g. bike shop) |
| E1 | Operator claims infinite stock for everything | Preflight/quality warnings; quality policy may quarantine misleading endpoints |
| E2 | Pure online shop, no storefront | Out of ICP; route away |
---
## 7. Minimum MCP / genre contract (retail v1)
- Identity, location, hours
- Categories typically carried
- Flagship items / house specialties (named, short descriptions)
- Visit guidance (walk-in, pickup window if any)
- Optional phone/contact
- Explicit inventory confidence level: curated list vs live feed
---
## 8. Success metrics
- Preflight pass with at least hours + one specialty or category set
- Simulation answers a “do you have X?” and a “what’s special?” question without hallucination from empty fields
- Weekly report shows retail-shaped intents (carry, hours, food specialty), not only appointment intents
---
## 9. Out of scope for UC-03 v1
- Full Shopify replacement or cart/checkout
- Guaranteed real-time stock without a feed
- Marketplace shopping across many stores in one consumer app
---
## 10. Dependencies
- Retail genre pack v1
- Portal genre branch for retail
- UC-01 platform mechanics (pointer, preflight, reports)
- Strategy §1a scope (local retail in ICP)
---
## 11. Open questions
1. How much assortment is enough for go-live (categories only vs item list)?
2. When do we integrate POS for true stock?
3. How do we prevent spammy “we have everything” profiles?
docs/strategy/CANONICAL_STRATEGY.md
+62 -29
View File
@@ -1,6 +1,6 @@
# geolocal.io — Canonical Strategy
**Status:** Final draft (2026-07-18; revised same day to restore full strategic depth)
**Status:** Final draft (2026-07-18; revised same day for strategic depth and local-retail scope)
**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.
This is an operating strategy, not a product brochure. The Self-Service Portal matters, but it is one activation surface. The company is the platform underneath.
@@ -9,11 +9,40 @@ This is an operating strategy, not a product brochure. The Self-Service Portal m
## 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 an assistant for a plumber, a transmission shop, a fishing charter, or a place to rent bikes.
geolocal.io is the infrastructure that lets **local businesses** show up properly inside the AI era — discoverable, understandable, and actionable when someone asks an assistant for a plumber, a transmission shop, a fishing charter, a place to rent bikes, **or the general store that still has the toothbrush they forgot and the chicken strips worth driving for.**
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 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 not trying to replace Shopify for pure online merchants.
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.
We are the layer underneath for **brick-and-mortar and local presence** — services *and* local retail. AI agents call us. Businesses own their presence. Tourism boards, chambers, and agencies help distribute it. In plain terms: Shopify made agent-ready commerce easy for online stores; we make agent-ready presence easy for the long tail of real-world local businesses that do not live inside a Shopify-class stack.
---
## 1a. Who is in scope (and who is not)
The original exploration called out service businesses as the pain that is easiest to see. That was emphasis, not a hard wall. The North Star was aimed at **local businesses**, not “appointments only.”
### In scope
Businesses with a **real local footprint** that consumers ask AI about in place-based ways:
| Kind | Examples | What “helpful” often means |
|------|----------|----------------------------|
| **Local services** | Auto repair, salon, home services, charters, clinics | Specialization, hours, booking path, pricing signals |
| **Local retail** | General store, hardware, pharmacy, gift shop, outfitter | “Do you have X?”, what’s in stock or typically carried, specialties/food, hours, directions, pickup |
| **Hybrid** | Bike shop that rents and sells, marina store, bakery with catering | Both inventory-ish answers *and* services/booking |
The Athol, Idaho general store is a fair test case: an assistant should be able to say, with confidence rooted in the store’s own structured truth, that they carry toothbrushes and that the chicken strips are a known local draw — not invent it from a stale review scrape.
### Out of scope (for now)
- **Pure online commerce** with no meaningful local presence — that is Shopify Storefront MCP territory and peers
- National pure-play marketplaces (Amazon, large pure e-com brands building their own agent stacks)
- Trying to win Airbnb/Kayak-class lodging and travel packaging
- Becoming a consumer shopping destination site
### Sequencing, not exclusion
Early genre packs and pilots can still **lead with services and tourism** (clear booking path, destination wedge). Local retail is **in the product vision and ICP from day one**. Retail primitives (assortment, “we carry,” specialties, hours) are a first-class genre family, not a later afterthought that contradicts the strategy.
---
@@ -29,11 +58,11 @@ What matters operationally is the shape of the answer. AI does not hand you a pa
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 but still far below traditional Google local 3-pack visibility. Locations that do get recommended tend to look trustworthy — high ratings, complete profiles, consistent signals.
Traditional local SEO still matters. It is no longer enough. Businesses need a machine-readable, up-to-date, bookable expression of who they are.
Traditional local SEO still matters. It is no longer enough. Businesses need a machine-readable, up-to-date expression of who they are — and, when it applies, how to book, buy, pick up, or walk in.
### The long tail is last again
Service-oriented local businesses are poorly positioned for this shift. The pattern rhymes with the early web: platforms and structured commerce move first; independent brick-and-mortar catches up late, if at all. Airline, hotel, rental-car, and large e-commerce players are already investing in agent-ready experiences. Bob’s Garage is not.
Independent brick-and-mortar — **services and local retail** — is poorly positioned for this shift. The pattern rhymes with the early web: platforms and structured commerce move first; the general store, the garage, and the charter captain catch up late, if at all. Airlines, hotels, rental-car players, and Shopify-class merchants are already investing in agent-ready experiences. Athol’s general store and Bob’s Garage are not.
---
@@ -77,9 +106,9 @@ Relevance gets you considered. Helpfulness is why an assistant comes back. Helpf
## 4. North Star
Make AI give the most relevant and helpful recommendation for a local service need — and then fulfill it.
Make AI give the most relevant and helpful recommendation for a **local** need — and then help fulfill it when fulfillment applies (book, reserve, pick up, walk in with the right expectation).
We stay focused on local service businesses. We are not trying to boil the ocean of all commerce.
We stay focused on **local businesses with real-world presence**. We are not trying to boil the ocean of all global e-commerce.
---
@@ -109,15 +138,17 @@ Think of AI-first consumption as seven stages:
If we drift into “we are an SEO company” or “we are a booking company,” we lose the plot.
### What “as-built” looks like for SMBs in 2026
### What “as-built” looks like for local SMBs in 2026
When engines judge helpfulness, three dependency areas keep showing up:
1. **Website** — can a machine understand what this business does?
1. **Website / public content** — can a machine understand what this business does or sells?
2. **Communication** — can a customer or agent complete a conversation path?
3. **Booking and payments** — can the job actually get scheduled and paid?
3. **Transaction path** — booking, reservation, payment, pickup, or clear walk-in expectation
Some vendors in those lanes will grow their own MCPs (scheduling tools, salon platforms, POS systems). That is fine and expected. Those MCPs are usually **scenario-specific** — book a slot, take an order. They do not solve long-tail story, genre depth, destination aggregation, or a neutral business-owned presence that works across assistants. We complement them.
For a salon, that third path may be appointments. For a general store, it may be “yes we carry that,” hours, and “come get it before six.” Both are local fulfillment. Neither requires us to become Shopify.
Some vendors in those lanes will grow their own MCPs (scheduling tools, salon platforms, POS systems, big e-com platforms). That is fine and expected. Scenario-specific tools do not replace a neutral, business-owned local presence that works across assistants for the long tail.
---
@@ -149,13 +180,13 @@ Once enough endpoints and intermediates exist, the network itself becomes valuab
### Platform first
What we actually sell is **AI-readiness infrastructure for local services**:
What we actually sell is **AI-readiness infrastructure for local businesses** (services and local retail with real presence):
1. **Hosted multi-tenant MCP** — structured tools agents call for story, services, hours, specialization, booking path, related businesses, and genre-specific detail.
1. **Hosted multi-tenant MCP** — structured tools agents call for story, hours, services or assortment signals, specialties, booking or visit path, related businesses, and genre-specific detail.
2. **Discovery attachment on the business domain** — not a single magic path only. Industry precedent is already multi-location and extensible (`/mcp`, commerce-style paths, AI context paths, well-known files). Those locations can point **off-domain** to hosted infrastructure such as geolocal. That extensibility is what makes “easy for Bob’s daughter” possible.
3. **Ingestion and content sync** — a strong channel from the business’s public content into the MCP. Garbage in, garbage out. If the source site cannot support helpful answers, the portal and reports have to say so.
4. **Genre packs** — vertical primitives. A salon MCP is not identical to a phone-repair MCP, even if some tools overlap.
5. **Orchestration of fulfillment partners** — Cal.com (and peers) for booking, Stripe (and peers) for payment. We integrate; we do not rebuild those categories.
4. **Genre packs** — vertical primitives. A salon MCP is not identical to a phone-repair MCP, and neither is identical to a general store that needs “do you carry X?” and house specialties.
5. **Orchestration of fulfillment partners** — Cal.com (and peers) where booking applies; Stripe/Square (and peers) where payment applies; inventory or POS hooks later where retail truth lives. We integrate; we do not rebuild those categories.
6. **Telemetry and owner insight** — not vanity dashboards. Concrete helpfulness feedback: what agents asked, where they bounced, how the business compares to category peers, what to change.
7. **Quality enforcement** — including the right to **decommission** chronically harmful endpoints. Bad data does not only hurt one customer; it taxes the trust of the whole network with AI engines.
8. **Intermediate surfaces** — destination and chamber MCPs plus operator dashboards.
@@ -177,13 +208,14 @@ Generic “get business info” is scaffolding. Durable differentiation is genre
- Beauty: services, duration, stylist context
- Home services: service radius, emergency vs scheduled, estimate vs fixed price
- Tourism activities: seasonality, capacity, weather sensitivity
- **Local retail / general store:** categories carried, flagship items or house specialties, “typically in stock” vs confirmed inventory when available, hours, pickup/walk-in guidance
- Intermediates: member directory and category routing
Roadmaps ship **genre packs**, not only generic endpoints.
Roadmaps ship **genre packs**, not only generic endpoints. Services packs may ship first for pilot speed; retail packs are in-scope product, not a strategy exception.
### 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.
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. We are not trying to out-Shopify Shopify for pure online stores. Stay complementary to those platforms; own the long tail of **local** businesses they do not serve cleanly for AI agents.
Upstream SEO/GEO checklists and partner referrals exist so businesses can *be found*. That work is enablement, not our core product category.
@@ -221,20 +253,21 @@ That last step is uncomfortable and necessary. Model 3 depends on it.
### Category
AI-readiness infrastructure for local services — or, shorter, agentic local commerce infrastructure.
AI-readiness infrastructure for **local businesses** — or, shorter, agentic local commerce infrastructure.
### Analogies that help
- **Shopify Storefront MCP for local services** — usually the clearest one-liner
- **Stripe for AI discovery and booking presence** — infrastructure, not another consumer app
- **Service registry for the long tail** — 2028 language when talking to platforms and sophisticated partners
- **Shopify Storefront MCP, but for local brick-and-mortar** — clear for technical audiences; includes local retail without claiming we replace Shopify
- **Stripe for AI discovery and local presence** — infrastructure, not another consumer app
- **Service and local-retail registry for the long tail** — 2028 language when talking to platforms and sophisticated partners
### 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.
- **Business owner (services):** Make every AI assistant understand and book your business.
- **Business owner (retail):** Make sure AI can tell people what you actually carry and why you’re worth the stop.
- **Tourism board:** Turn lodging-tax dollars into AI-discoverable local experiences and businesses 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.
- **Investor:** A neutral MCP layer for the vast majority of local businesses AI currently skips, distributed through self-serve and municipal partners.
### Language to avoid
@@ -257,9 +290,9 @@ Motion:
3. Fund it with tourism marketing budgets, innovation RFPs, or visitor-experience framing.
4. Give members free or discounted endpoints during the pilot, then convert to paid.
### Parallel motion: self-service small businesses
### Parallel motion: self-service local businesses
While intermediates mature, sell direct into high-intent verticals — auto repair, beauty, home services — and tourism activities when a destination pilot needs them.
While intermediates mature, sell direct into high-intent verticals — auto repair, beauty, home services, tourism activities when a destination pilot needs them — **and** local retail where the “do you have it / what’s special here” job is obvious.
### Partners as distribution
@@ -440,9 +473,9 @@ If two documents disagree, resolve it on purpose.
## 18. Closing
The company worth building is the platform: multi-tenant MCP, genre systems, ingestion, quality, intermediate upgrade path, and eventually a service graph. The Self-Service Portal is how ordinary businesses turn that platform on. Tourism boards are how we attach many endpoints at once. Trust and decommissioning are how we stay preferred by machines that only name one or two winners.
The company worth building is the platform: multi-tenant MCP, genre systems (services **and** local retail), ingestion, quality, intermediate upgrade path, and eventually a service-and-place graph. The Self-Service Portal is how ordinary businesses turn that platform on. Tourism boards are how we attach many endpoints at once. Trust and decommissioning are how we stay preferred by machines that only name one or two winners.
Market conditions support urgency without requiring panic. Consumers are using AI for local discovery. Recommendation is highly selective. Large platforms are MCP-enabling *their* layers. The long tail of local services still lacks a neutral on-ramp.
Market conditions support urgency without requiring panic. Consumers are using AI for local discovery. Recommendation is highly selective. Large platforms are MCP-enabling *their* layers. The long tail of local businesses — the garage **and** the general store — still lacks a neutral on-ramp.
Freeze strategy. Realign docs. Ship the platform. Activate with the portal. Scale through intermediates. Protect trust like it is the product — because for AI engines, it is.