Update README.md

2026-07-16 20:43:33 +00:00
parent 9d6ca48404
commit f083742850
1 changed files with 72 additions and 13 deletions
@@ -1,20 +1,79 @@
 # geolocal.io

-AI-native infrastructure for local business discovery, storytelling, visuals, and booking via MCP. Powers the long tail of independent SMBs ignored by big platforms.
+> AI-native infrastructure for local business discovery, storytelling, visuals, and booking via MCP. Powers the long tail of independent SMBs ignored by big platforms.

-## Repository Structure (ASCII Site Map)
+## What Is This?

-```
+`geolocal.io` makes local service businesses discoverable, bookable, and payable in the agentic AI economy.
+
+We do this by:
+
+- **Hosting a multi-tenant MCP server** that exposes rich, structured business data (story, visuals, services, pricing, availability) to any AI agent.
+- **Providing a simple JSON pointer** (`/.well-known/mcp-server`) that any business can add to their website to connect to our hosted MCP server—no coding required.
+- **Enabling a complete transaction loop** by integrating with Cal.com for booking and Stripe for payment capture.
+- **Building a partner-first distribution engine** by working through agencies, SEO consultants, and Chambers of Commerce who already serve these businesses.
+- **Creating a self-reinforcing data network** where AI agents provide verification and competitive intelligence data through our "related businesses" handshake.
+
+We are not a destination site. We are an invisible, critical layer of infrastructure that powers the agentic economy's discovery of local businesses.
+
+## The Problem We Solve
+
+- **45% of consumers** now use AI tools to find local businesses—up from just **6% one year earlier**.
+- **ChatGPT recommends just 1.2% of local businesses**, according to SOCi's 2026 Local Visibility Index.
+- **AI is now the third most-used business discovery channel**, behind only Google and Facebook.
+
+The major platforms (Google, Yelp, OpenAI) are building MCP infrastructure to serve their own data. They are **not** building infrastructure to serve the businesses themselves. We bridge that gap.
+
+## Quick Start
+
+### For Partners (Agencies, SEO Consultants, Chambers)
+
+1. Read the **[Partner & Channel Strategy](./docs/gtm/partner-channel-strategy.md)** to understand the opportunity.
+2. Review the **[Partner One-Pager](./docs/gtm/partner-one-pager.md)** for a concise sell-sheet.
+3. Contact us to get started.
+
+### For Investors
+
+1. Read the **[North Star](./NORTH_STAR.md)** document for our vision and principles.
+2. Review the **[Market Data & Analysis](./docs/investors/market-data-analysis.md)** for the opportunity size.
+3. Explore the **[Business & Financial Model](./docs/investors/business-financial-model.md)** and **[Competitive Moats & Risks](./docs/investors/competitive-moats-risks.md)** for our defensible position.
+
+### For Developers & Engineers
+
+1. Read the **[Product & Technical Roadmap](./docs/engineering/product-technical-roadmap.md)** for our phased implementation plan.
+2. Review the **[MCP Server Architecture](./docs/engineering/mcp-server-architecture.md)** for technical details.
+3. Check the **[Deployment Guide](./docs/engineering/deployment-guide.md)** for setup instructions.
+
+## Repository Structure
 geolocal-io/
-├── NORTH_STAR.md          ← Single source of truth for vision & principles
-├── README.md              ← This file (you are here)
+├── NORTH_STAR.md # Single source of truth for vision & principles
+├── README.md # This file
 ├── docs/
-│   ├── investors/         ← Pitch narrative, market, financials, moat
-│   ├── legal/             ← Risks, IP, data flows, compliance notes
-│   ├── engineering/       ← Architecture, MCP design, MVP scope, data model
-│   ├── gtm/               ← Partner (agency/CoC) outreach, onboarding, pricing, playbooks
-│   └── early-thinking/    ← Raw conversation history and initial explorations
-└── (future: code/, assets/, etc.)
-```
+│ ├── investors/ # Pitch narrative, market, financials, moat
+│ ├── legal/ # Risks, IP, data flows, compliance notes
+│ ├── engineering/ # Architecture, MCP design, MVP scope, data model
+│ ├── gtm/ # Partner (agency/CoC) outreach, onboarding, pricing, playbooks
+│ └── early-thinking/ # Raw conversation history and initial explorations
+└── (future: code/, assets/)
+
+
+## The North Star
+
+Everything we build must follow a single principle: **make it dead simple for a partner to deploy an MCP endpoint for a local business, and make that endpoint compelling enough that AI agents prefer it.**
+
+Our North Star document defines the "what," "why," "what if," and "when" with clarity and conviction. It anchors all product decisions, fundraising conversations, and go-to-market execution.
+
+## Status
+
+| Area | Status |
+| :--- | :--- |
+| **Strategy & Vision** | ✅ Complete |
+| **Market Data & Analysis** | ✅ Complete |
+| **Competitive Intelligence** | ✅ Complete |
+| **Business & Financial Model** | ✅ Complete |
+| **Product & Technical Roadmap** | ✅ Complete |
+| **GTM Strategy** | ✅ Complete |
+| **Legal & Compliance** | ⬜ In progress |
+| **Code / Implementation** | ⬜ Not started |
+

-Start with **NORTH_STAR.md**. Pick the audience folder that matches who you're preparing for. Everything must trace back to the North Star.