Ty
1e66fe135a
Replace stale timeline targets with Ty's direction: prime the pump through a Chamber of Commerce or Tourism Board partnership, use member businesses as the first customer segment, and make the conversational SSP the compelling wow experience that wins returning customers. Old milestones assumed a form-wizard portal and endpoint counts (100, 1000, 10000) that predated the conversational SSP pivot and the refined MVP scope. New milestones track distribution-first activation through board trust, then prove the loop, then scale. Signed-off-by: Ty <tybala@outlook.com> Co-authored-by: Ty <tybala@outlook.com>
geolocal.io
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
- Canonical Strategy — operating truth (final draft)
- North Star — short compass
- Product overview — platform vs activation
- Use cases — UC-01 services, UC-02 tourism, UC-03 local retail
What this is
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 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.
Who should read what
Partners (agencies, SEO, chambers)
Investors
Engineering
- Canonical Strategy priorities
- Technical roadmap
- code/ — MCP MVP (TypeScript)
- ADRs
Repository map (Phase A)
geolocal-io/
├── NORTH_STAR.md
├── README.md
├── code/ # MCP server MVP (later → apps/mcp-gateway)
└── docs/
├── strategy/ # CANONICAL_STRATEGY.md (operating truth)
├── product/ # SSP, intermediate, genre packs
├── gtm/ # channels, sales, competitive/
├── investors/
├── engineering/ # roadmap + adrs/
├── legal/
└── archive/ # historical exploration only
Later monorepo phases add apps/, packages/, genres/, and infra/ without changing the docs contract above.
Status
| Area | Status |
|---|---|
| Canonical strategy | Final draft |
| Market / GTM / legal docs | Present (some GTM still pre-strategy framing) |
| Product docs | Scaffolded |
MCP server (code/) |
MVP — 5 tools, TypeScript, Railway-ready |
| Self-Service Portal | Specified; not built |
| HTTP multi-tenant gateway | Priority 0 |
Doc governance
If a document conflicts with docs/strategy/CANONICAL_STRATEGY.md, fix the conflict on purpose. Historical exploration lives in docs/archive/, not in operating GTM.