Ty
3bd59b6d2b
- Fix all broken links in root README (partner-channel-strategy → Ideal Customer Profile, etc.) - Add code/ directory to repo structure tree - Update status table: Legal ✅, MCP Server ✅ MVP - Rewrite section READMEs with actual file inventories: docs/engineering/, docs/gtm/, docs/investors/, docs/legal/
88 lines
4.6 KiB
Markdown
88 lines
4.6 KiB
Markdown
# 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.
|
|
|
|
## 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 **[Ideal Customer Profile](./docs/gtm/Ideal%20Customer%20Profile.md)** to understand who we target.
|
|
2. Review the **[Channel Strategy](./docs/gtm/ChannelStrategy.md)** and **[Sales and Marketing](./docs/gtm/Sales%20and%20marketing.md)** for the playbook.
|
|
3. Use the **[Partner One-Pager](./docs/gtm/Partner%20One-Pager.md)** as your sell-sheet.
|
|
|
|
### 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%20Data%20&%20Analysis.md)** for the opportunity size.
|
|
3. Explore the **[Business and Financial Model](./docs/investors/Business%20and%20financial%20model.md)** and **[Competitive Moats & Risks](./docs/gtm/Competitive%20moats%20and%20risks.md)** for our defensible position.
|
|
|
|
### For Developers & Engineers
|
|
|
|
1. Read the **[Technical Roadmap](./docs/engineering/technical%20roadmap.md)** for our phased implementation plan.
|
|
2. Explore the **[code/](./code/)** directory for the MCP server implementation.
|
|
3. See **[package.json](./code/package.json)** for dependencies and scripts.
|
|
|
|
## Repository Structure
|
|
|
|
```
|
|
geolocal-io/
|
|
├── NORTH_STAR.md # Single source of truth for vision & principles
|
|
├── README.md # This file
|
|
├── code/ # MCP server implementation (TypeScript)
|
|
│ ├── src/
|
|
│ │ ├── index.ts # Server entry point (stdio transport)
|
|
│ │ ├── mcp-server.ts # Tool registration (5 MCP tools)
|
|
│ │ ├── config.ts # Environment configuration
|
|
│ │ ├── manifest-generator.ts # /.well-known/mcp-server JSON
|
|
│ │ ├── db/ # PostgreSQL schema + seed data
|
|
│ │ ├── tools/ # get_business_info, get_hours, etc.
|
|
│ │ └── routes/ # Multi-tenant gateway
|
|
│ ├── package.json
|
|
│ ├── tsconfig.json
|
|
│ ├── Dockerfile
|
|
│ └── railway.json
|
|
└── docs/
|
|
├── investors/ # Market data, financial model
|
|
├── gtm/ # ICP, channel strategy, partner one-pager
|
|
├── engineering/ # Technical roadmap
|
|
├── legal/ # Data flow, partnership agreement, IP notes
|
|
└── early-thinking/ # Raw conversation history and initial explorations
|
|
```
|
|
|
|
## 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** | ✅ Complete |
|
|
| **MCP Server (code/)** | ✅ MVP — 5 tools, TypeScript, Railway-ready |
|
|
|
|
|