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

docs: Phase A repo structure — archive, product, kebab-case

Browse Source 
- Move copilot history and CSV to docs/archive/
- Add docs/product/ (SSP, intermediate, genre packs) and engineering/adrs/
- Rename all spaced/special-char doc paths to kebab-case
- Nest competitive GTM under docs/gtm/competitive/
- Point README and NORTH_STAR at CANONICAL_STRATEGY
- Leave code/ unchanged for later monorepo Phase B
This commit is contained in:
VPS admin
2026-07-18 05:23:39 +00:00
parent 36853f3bab
commit 3f9c86f823
32 changed files with 250 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gtm/competitive/README.md
+8
View File
@@ -0,0 +1,8 @@
# Competitive
| Doc | Purpose |
|-----|---------|
| [intelligence.md](./intelligence.md) | Competitor landscape |
| [moats-and-risks.md](./moats-and-risks.md) | Moats and risks |
Parent index: [../README.md](../README.md).
docs/gtm/competitive/intelligence.md
+232
View File
@@ -0,0 +1,232 @@
# Competitive Intelligence Dossier
## 1. The Competitive Landscape: Market Positioning Map
The competitive landscape for local business AI discovery is fragmented across three distinct layers. This map illustrates where each player operates and your position relative to them.
| Layer | Players | Your Position |
| :--- | :--- | :--- |
| **Consumer-Facing MCP Data Providers** | Yelp, Google (via MCP integrations) | **Downstream** — they provide data to AI agents; you enable businesses to be the data source |
| **AI Visibility & Marketing Platforms** | Pie, Mainstreet, VibeAds | **Adjacent** — they help businesses optimize for AI discovery; you provide the infrastructure that makes AI discovery native |
| **Data Extraction / Lead Gen Infrastructure** | Apify scrapers, Google Local MCP, Yelp scrapers | **Complementary** — you're not scraping; you're building the source of truth for AI |
*Source: Competitive analysis based on available market data [citation:1][citation:4][citation:7]*
## 2. Consumer-Facing MCP Data Providers
These platforms expose their own data to AI agents via MCP servers. They are **not** building infrastructure for businesses to host their own MCP endpoints—they are selling access to their datasets.
### 2.1 Yelp
Yelp has aggressively positioned itself as the data provider of choice for AI-driven local discovery, leveraging its proprietary dataset and a multi-tiered paid API model.
#### MCP Offering
- Official `yelp-mcp` server on GitHub, exposing tools for natural language business search, details, reviews, photos, menus, and conversational restaurant reservations [citation:1][citation:10]
- Tools include: `search_businesses`, `get_business`, `get_reviews`, `search_by_phone`, `count_businesses` [citation:1]
- Allows AI agents to not just search but **transact** (reservations available on request) [citation:10]
#### Strategic Position
- **Data moat:** 330 million+ reviews, a proprietary dataset that would be extremely expensive and time-consuming to replicate [citation:1]
- **Distribution:** Licensing deals with OpenAI, Meta.ai, Bing, Amazon Alexa [citation:10]
- **Revenue model:** Charging developers for API access, and licensing data to major AI platforms [citation:10]
#### Pricing Model
Yelp's Fusion AI API is priced at a premium, targeting developers and enterprises that need reliable, structured data [citation:1][citation:10].
| Tier | Cost | Daily Calls | Features |
| :--- | :--- | :--- | :--- |
| Starter | $7.99/1000 calls | 300 | Basic search, business details |
| Plus | $9.99/1000 calls | 500 | + Reviews endpoint |
| Enterprise | $14.99/1000 calls | More | + Review Highlights |
| AI API License | $25/1000 calls | 1,000 minimum | Full premium access, conversational reservations |
*Source: Yelp Fusion MCP Server documentation [citation:1][citation:10]*
#### Regulatory Vulnerability
- Yelp is heavily dependent on Google for distribution and has filed extensive regulatory complaints documenting Google's self-preferencing behavior in search results [citation:12]
- This dependency exposes Yelp to the same algorithmic and regulatory risks that have affected other local platforms
### 2.2 Google (via MCP Infrastructure)
Google's MCP integration is less visible but arguably more powerful because it controls the primary data source for local discovery: Google Business Profile.
#### MCP Reach
- Google Local MCP servers allow AI clients to query Google Local data directly [citation:7]
- Community-built servers (e.g., `google-local-mcp`, `google-maps-mcp-server`) provide tools for search, lead generation, and business validation [citation:7][citation:11]
#### Strategic Position
- **Integration advantage:** Google's MCP integrations are built on top of Google's own search infrastructure [citation:7]
- **Regulatory pressure:** Google is under regulatory scrutiny globally for self-preferencing behavior in local search [citation:12]
- **Data advantage:** Google Business Profile remains the authoritative source for local business data—if your GBP data is inconsistent, you are **invisible to voice assistants and AI** [citation:12]
## 3. AI Visibility & Marketing Platforms
These platforms help businesses **optimize their existing presence** for AI discovery. They don't provide MCP infrastructure—they help businesses show up in AI results.
### 3.1 Pie (Direct Competitor)
Pie is the most direct competitor to `geolocal.io` in terms of *go-to-market*. However, their **technical approach is fundamentally different** from your MCP infrastructure play.
#### Core Product
Pie is a growth platform for local businesses with three products [citation:4]:
| Product | Function |
| :--- | :--- |
| **AI Search** | Optimizes business visibility in AI search (ChatGPT, Claude, Perplexity) |
| **Growth** | Manages customer acquisition across Google Maps, Yelp, Nextdoor |
| **Front Desk** | AI receptionist that answers calls, takes bookings, and responds to questions 24/7 |
#### Strategic Position
- **Funding:** $23.7M total ($19.5M Series A led by Lightspeed Venture Partners) [citation:4]
- **Leadership:** Founded by former Square and Toast operators [citation:4]
- **Distribution:** Thousands of businesses; embedded partnerships with vertical platforms (e.g., auto-repair system Tekmetric) [citation:4]
- **Pricing:** Undercuts agencies—one reported example was ~$359/month (vs. $2,500-$5,000/month for agencies) [citation:4]
#### Why Pie Is Different From You
| Aspect | Pie | Your `geolocal.io` |
| :--- | :--- | :--- |
| **Core offering** | AI-driven **marketing and lead generation** platform | **MCP infrastructure** that makes businesses native to AI |
| **Business model** | Subscription-based growth marketing tool | Infrastructure platform + partner distribution |
| **Technical approach** | Optimizes existing signals (GBP, website, Yelp) | Exposes business data **directly to AI agents** via MCP |
| **Value prop** | "We get you found in AI search" | "You become a direct, interactive source of truth for AI" |
*Source: Pie's own communications [citation:4]*
### 3.2 Mainstreet
Mainstreet is an autonomous AI agent for Google Business Profile management.
#### Core Product
Autonomous agent that [citation:3]:
- Replies to reviews in the business's voice
- Publishes weekly Google Posts automatically
- Tracks local map-pack rank across a 5x5 grid
- Monitors top 3 competitors weekly
#### MCP Offering
Exposes three free tools via `@mainstreet/mcp` [citation:3]:
| Tool | Function |
| :--- | :--- |
| `lookup_business` | Returns GBP snapshot: rating, review count, category, address, hours, reviews |
| `check_local_rank` | Returns local map-pack rank for a keyword + top 3 competitors |
| `request_audit` | Triggers a free 5-minute PDF audit |
#### Strategic Position
- **Niche focus:** Reputation management, not infrastructure
- **Pricing:** $99/month (single location); $199/month (multi-location) [citation:3]
- **Distribution:** Direct-to-business, targeting independent small business owners
- **Key insight:** Mainstreet helps businesses *look good* to AI, but doesn't make them *natively discoverable* via MCP
### 3.3 VibeAds
VibeAds is a Google Ads optimization MCP server specifically tuned for local service businesses.
#### Core Product
MCP server that lets AI query Google Ads data for local service businesses [citation:2]:
- Account Health Score (0-100) across 6 dimensions
- Search term waste detection
- 35+ diagnostic rules
- Local-service-first tuning for plumbers, HVAC, electricians, roofers, and 33 more categories
#### Strategic Position
- **Niche focus:** Paid ad optimization, not discovery
- **MCP approach:** Provides diagnostic tools for AI agents to analyze advertising performance
- **Relevance:** Validates the need for local-service-specific MCP tuning
## 4. Data Extraction & Lead Generation Infrastructure
These platforms provide MCP servers that extract local business data from other platforms. They are **complementary** to your model, as you are building the source of truth rather than extracting it.
### 4.1 Apify Ecosystem
Apify hosts a marketplace of MCP servers for extracting business data from Yelp, Google Maps, and Chambers of Commerce.
| Tool | Function | Pricing |
| :--- | :--- | :--- |
| Local Business Directory Extractor (single page) | Extract schema.org data from a business page [citation:5] | Usage-based |
| Local Business Contact Finder | Scrape Google Maps/Yelp for contact details [citation:9] | From $5.00/1,000 results |
| Yelp Business API | Extract Yelp listings by keyword/location [citation:15] | From $0.50/1,000 items |
| Local Business Lead Generator | Extract Google Local Services data [citation:14] | $3.00/1,000 businesses |
#### Why Apify Is Not a Competitor
- Apify's MCP servers are for **extracting** data, not **enabling** businesses
- They help generate leads, not build AI-native business presences
- They are a **data extraction layer**, not an **infrastructure layer**
### 4.2 Google Local MCP Servers
Several community-built MCP servers allow AI agents to query Google Local data directly.
| Server | Function |
| :--- | :--- |
| `google-local-mcp` | Search Google Local for businesses; returns name, address, phone, hours, rating, review count, website, category [citation:7] |
| `@nexgendata/google-maps-mcp-server` | Search local businesses, generate leads, validate emails [citation:11] |
#### Why They Are Not Competitors
- These servers **extract** Google's data; they don't help businesses own their data
- They are lead generation tools, not AI-native business enablement
## 5. Competitive Landscape Summary
| Competitor | Layer | Core Offering | Direct Threat? |
| :--- | :--- | :--- | :--- |
| **Yelp** | Data Provider | MCP access to Yelp's data (paid API) | **Yes** — if Yelp offers hosted MCP endpoints for businesses, this is a direct competitive move |
| **Google** | Infrastructure | Google Local MCP servers extracting GBP data | **Yes** — Google could integrate MCP discovery into GBP directly |
| **Pie** | Marketing Platform | AI-driven growth platform (GEO, marketing automation) | **Yes** — competition for agency/business attention, but different technical approach |
| **Mainstreet** | Reputation Management | GBP review and post automation | **No** — adjacent: reputation vs. infrastructure |
| **VibeAds** | Ad Optimization | Google Ads diagnostics for local businesses | **No** — niche focus on paid ads |
| **Apify** | Data Extraction | Scrapers and MCP servers for lead generation | **No** — complementary: data extraction vs. data source enablement |
| **Google Local MCPs** | Data Extraction | Search and lead generation from Google data | **No** — complementary: extraction vs. enablement |
## 6. The Defensible Position
Your `geolocal.io` model is the only player building **infrastructure for businesses to own their AI presence**, rather than selling access to their data or optimizing their existing signals. This positions you as:
1. **Not dependent on Yelp/Google's data** — you enable businesses to be the source of truth
2. **Not competing with agencies** — you work through them as a partner channel
3. **Not scraping** — you give businesses a direct voice in the agentic economy
The competitive risk is that Yelp or Google could offer hosted MCP endpoints for businesses, but this would require them to pivot from their current "landlord" model to an "infrastructure" model—a significant strategic shift.
## 7. Strategic Positioning Statement
> *"Yelp and Google control the data. Pie optimizes your visibility in their data. `geolocal.io` lets you become the data source."*
## 8. References
| # | Source | URL |
|---|--------|-----|
| [1] | Yelp Fusion MCP Server (official) | <https://github.com/Yelp/yelp-mcp> |
| [2] | VibeAds MCP Server (official) | <https://github.com/vibeads/mcp> |
| [3] | Mainstreet MCP (`@mainstreet/mcp`) | <https://www.npmjs.com/package/@mainstreet/mcp> |
| [4] | Pie raises $23.7M Series A (Lightspeed) | <https://www.morningstar.com/news/business-wire/20260630636582/pie-raises-237m-to-bring-ai-powered-growth-to-main-street-businesses> |
| [5] | Apify MCP Server (generic wrapper for any Apify actor) | <https://github.com/apify/apify-mcp-server> |
| [6] | The Next Web — "Pie raises $19.5M" (pre-Series A) | <https://thenextweb.com/news/pie-19-5m-ai-search-main-street-businesses> |
| [7] | Google Local MCP Server (community) | <https://github.com/johnisanerd/google-local-mcp> |
| [9] | Compass — Crawler Google Places (Apify) | <https://apify.com/compass/crawler-google-places> |
| [10] | Yelp Data Licensing Pricing | <https://business.yelp.com/data/resources/pricing/> |
| [11] | nexgendata Google Maps MCP Server (Apify) | <https://apify.com/nexgendata/google-maps-mcp-server> |
| [12] | "Your Google Business Profile Is a Lie and AI Knows It" (Medium) | <https://medium.com/@carlo.cuman/your-google-business-profile-is-a-lie-and-ai-knows-it-5228fd8a4d11> |
| [14] | Apify — Lead Generation Use Case | <https://apify.com/use-cases/lead-generation> |
| [15] | Yelp Business API (Apify — epctex) | <https://apify.com/epctex/yelp-business-api> |
docs/gtm/competitive/moats-and-risks.md
+234
View File
@@ -0,0 +1,234 @@
# Competitive Moats & Risks
## 0. Relationship to the Competitive Intelligence Dossier
This document is the strategic companion to the **[Competitive intelligence](./intelligence.md)** dossier, which profiles the key players in the local business AI discovery space (Yelp, Google, Pie, Mainstreet, Apify, and others). This analysis assumes familiarity with that landscape and focuses on:
1. **Our defensible positions:** What makes `geolocal.io` hard to replicate
2. **The unseen strength:** Why first-mover advantage and critical mass are the real moats
3. **Key risks:** What could derail us and how to mitigate them
4. **The acceleration strategy:** How to win before incumbents can react
Together, these documents provide a complete view of the competitive landscape and our path to victory.
## 1. The Central Strategic Question
`geolocal.io` is building a platform to make local businesses discoverable in agentic AI by exposing public business data through a customer-facing MCP endpoint. The data we expose is information the business already shares on their website, Google Business Profile, and other public channels.
This means the risk profile is fundamentally different from an enterprise MCP deployment. We are not connecting to internal systems, employee emails, or proprietary corporate data. We are simply making structured, machine-readable versions of already-public information.
**The central question:** Can we build a defensible business before incumbents (Yelp, Google) or nimble competitors (Pie, Mainstreet) replicate our model or render it obsolete?
---
## 2. The Unseen Strength: First-Mover Advantage & Critical Mass
### 2.1 Why First-Mover Advantage Matters Here
In the agentic AI economy, **being first is not just about brand awareness—it's about training the AI itself.**
AI agents are not static. They learn, adapt, and build "muscle memory" based on the data sources they encounter most frequently and reliably. A business that is already discoverable through `geolocal.io` when an AI agent first learns to search for local services is more likely to be recommended than a business that appears later.
This is a form of **AI-native brand equity.** The AI agent has a relationship with the data source. It knows the structure, the reliability, and the value of the information it receives.
| Stage | What Happens | Why It Matters |
| :--- | :--- | :--- |
| **Early** | `geolocal.io` is the first MCP endpoint AI agents encounter for a given region or category | The AI learns that `geolocal.io` is a reliable source of local business data |
| **Mid** | AI agents begin to **prefer** `geolocal.io` endpoints over scraped or unverified sources | The platform becomes the "default" for local discovery |
| **Late** | AI agents actively **expect** `geolocal.io` data and may treat its absence as a negative signal | Competitors cannot easily displace `geolocal.io` because it's baked into the AI's "muscle memory" |
### 2.2 Critical Mass: The Self-Reinforcing Flywheel
Critical mass is not just a nice-to-have; it is the **engine of the model.** The value of `geolocal.io` grows exponentially with the number of businesses on the platform:
- More businesses → more MCP endpoints → more data for AI agents
- More data → better "related businesses" recommendations → more value for each business
- More value → more agencies want to partner → more businesses join
- More businesses → more telemetry data → better insights → more value for agencies and businesses
**This is the flywheel.** And it only works if we achieve critical mass before competitors do.
### 2.3 The "Pioneer" Moat
The phrase *"pioneers get the arrows, settlers get the land"* applies here—but with a twist. In the agentic AI economy, **settlers get the data, and data is the land.**
| Competitor | What They'd Have to Do | Why It's Harder for Them |
| :--- | :--- | :--- |
| **Yelp** | Convince businesses that a Yelp-hosted MCP is better than an independent one | Yelp is a landlord, not a partner. Businesses are wary of platform lock-in. |
| **Google** | Integrate MCP into GBP without triggering antitrust concerns | Regulatory scrutiny makes bold moves difficult. |
| **Pie / Mainstreet** | Build MCP infrastructure from scratch and compete for agencies | They are marketing platforms, not infrastructure providers. They'd need to pivot their core offering. |
| **Startup** | Build a similar platform and attract partners and businesses | They are entering a market where `geolocal.io` already has a partner network, data, and AI agent preference. |
The first mover who achieves critical mass creates a moat that is not just about technology, but about **relationships, data, and AI agent muscle memory.**
---
## 3. The Moats: What Makes `geolocal.io` Hard to Replicate
### 3.1 The Network Effect Moat
The value of `geolocal.io` increases as more businesses join the platform. This creates the self-reinforcing flywheel described above.
**Why this matters:** Yelp and Google have network effects too, but they are built around *their* platform, not the businesses themselves. `geolocal.io` gives businesses an independent, portable presence that they control—and that's a different kind of network effect that incumbents would struggle to replicate.
### 3.2 The Partner Ecosystem Moat
Our partner-first model creates a distribution advantage:
- Agencies, SEO consultants, and Chambers trust and use the platform
- They have invested time in learning the product and onboarding their clients
- Switching costs are high—they would have to retrain and migrate all their clients
**Why this matters:** This is a classic "switching cost" moat. Once an agency has a significant number of clients set up on `geolocal.io`, moving to a competitor is painful and time-consuming.
### 3.3 The Simplicity Moat
`geolocal.io` solves the "son-in-law" problem—the business owner who doesn't know how to code and doesn't want to learn. The technical implementation is dead simple:
- Add a single JSON file to the business website
- No coding, no server management, no security audits
- The entire technical burden is handled by `geolocal.io`
**Why this matters:** Competitors who try to replicate this will need to offer the same level of simplicity, which is harder than it sounds. Pie and Mainstreet are marketing platforms, not infrastructure. They don't offer a direct MCP endpoint. Yelp and Google could, but they would need to build the same level of simplicity and partner-friendly pricing.
### 3.4 The Telemetry Moat
Every MCP interaction generates data that no one else has:
- Which AI platforms are recommending which businesses
- Which queries trigger which recommendations
- Which businesses are converting discovery to bookings
- Real-time demand signals by category and region
**Why this matters:** This is a proprietary dataset that cannot be replicated without running the same infrastructure. Over time, this data becomes the "source of truth" for agentic local discovery—a powerful asset for licensing and analytics.
### 3.5 The "Acting in Good Faith" Moat
In a world where AI agents are trained to avoid risky or unverified sources, being a reliable, well-maintained data source is a defensible advantage:
- `geolocal.io` is a single, trusted endpoint that AI agents can rely on
- It doesn't use scraping, dubious third-party packages, or uncontrolled code
- It's simple enough that business owners can trust it
**Why this matters:** AI agents will prefer stable, trustworthy sources over the chaos of scraping and community-built servers. This is the "Yelp of the agentic era" dynamic: trust at scale.
### 3.6 First-Mover Advantage at Scale
The combination of early entry, partner network growth, and telemetry accumulation creates a **pioneer's shield**:
- **AI agents learn to trust `geolocal.io` data** because they encounter it consistently and reliably
- **Agencies standardize on `geolocal.io`** because it's the first and easiest platform they tried
- **Businesses get value from the platform** because AI agents are already recommending them
- **Competitors face a higher barrier to entry** because they must overcome the network effect and AI agent preference
---
## 4. The Risks: What Could Derail `geolocal.io`
### 4.1 Yelp Offers a Hosted MCP Endpoint
**The risk:** Yelp decides to offer a similar service—a hosted MCP endpoint for businesses, combined with their superior data (330M+ reviews).
**Why it matters:** Yelp has the data, the relationships, and the brand awareness. If they offer a free or low-cost hosted MCP, it could significantly undercut our value proposition.
**Mitigation:**
- Focus on the businesses Yelp ignores (the 98.8% with few reviews)
- Emphasize the independence of our platform—businesses own their data, not Yelp
- Build the partner ecosystem faster than Yelp can launch
### 4.2 Google Integrates MCP Discovery Directly into GBP
**The risk:** Google adds native MCP support to Google Business Profile, making the JSON pointer obsolete for businesses already on GBP.
**Why it matters:** Google controls the primary source of local business data. If they make MCP discoverability a native feature, the independent market for MCP hosting shrinks significantly.
**Mitigation:**
- Build a solution that works alongside Google, not as a replacement
- Focus on services and experiences that Google doesn't cover well (ticketed activities, tours, local events)
- Provide superior booking and deposit capture that Google's basic MCP might not support
### 4.3 The JSON Pointer Becomes a Security or Trust Issue
**The risk:** AI agents (or the platforms that power them) start to distrust or ignore MCP endpoints hosted by third-party providers like `geolocal.io`.
**Why it matters:** If AI providers see third-party MCP endpoints as a spam or brand-reputation risk, they could restrict or deprioritize them.
**Mitigation:**
- Build a pristine reputation: well-maintained, secure, and lightweight endpoints
- Position `geolocal.io` as the trusted intermediary rather than an unknown server
- Build direct relationships with AI providers who want reliable local business data
### 4.4 Consumer Behavior Shifts Away from Agentic AI
**The risk:** AI adoption plateaus or declines, and consumer preference shifts back to traditional search.
**Why it matters:** The entire `geolocal.io` thesis rests on the assumption that agentic AI is the future of discovery. If this proves wrong, the market evaporates.
**Mitigation:**
- This risk is low—the adoption data (45% of consumers using AI for local searches) is too strong to ignore
- If AI adoption plateaus, `geolocal.io` still provides value as a structured data source for traditional search
### 4.5 Pie or Mainstreet Extend Their Offerings to MCP Hosting
**The risk:** Pie or Mainstreet, which already have business relationships and marketing platforms, add MCP hosting as a feature.
**Why it matters:** They have existing distribution and brand awareness. Their customers trust them. They could undercut our pricing or bundle MCP hosting with existing services.
**Mitigation:**
- Build the partner ecosystem faster; agencies are less likely to switch if they're already using `geolocal.io`
- Focus on the simplicity and independence of our platform—Pie and Mainstreet are marketing platforms, not infrastructure providers
### 4.6 The MCP Standard Becomes Obsolete or Fragments
**The risk:** MCP is replaced by a competing standard, or multiple incompatible versions fragment the market.
**Why it matters:** Our entire infrastructure is built on MCP. If the standard shifts, we would need to adapt or be left behind.
**Mitigation:**
- Build at the highest level of abstraction possible—don't lock into a single implementation
- Monitor MCP governance (now under the Linux Foundation) and participate in standard-setting
- Build a flexible architecture that can adapt to new protocols
---
## 5. The Most Likely Competitive Scenario
Yelp, Google, and Pie are all building versions of this capability. The most likely outcome is a fragmented market where:
| Player | Strength | Weakness | Position |
| :--- | :--- | :--- | :--- |
| **Yelp** | Massive data, direct AI licenses | Landlord model, not infrastructure | Will offer a paid, Yelp-centric MCP |
| **Google** | GBP ownership, search dominance | Regulatory pressure, self-preferencing | Will integrate MCP into GBP but may face antitrust scrutiny |
| **Pie** | Marketing platform, agency relationships | Not building MCP infrastructure | May add MCP as a feature, but not core |
| **`geolocal.io`** | Independence, simplicity, partner-friendly | Smaller brand, less data | Will serve the businesses incumbents ignore |
This is a **defensible niche**—serving the long tail of local businesses that Yelp and Google don't serve well, through a partner ecosystem that values simplicity and independence.
---
## 6. The Moat-by-Acceleration Strategy
Our competitive advantage is not in building a better MCP server. It's in moving faster than incumbents can react and achieving critical mass before they can replicate our model:
| Priority | Action | Why It Matters |
| :--- | :--- | :--- |
| **1. Partner network** | Recruit agencies and Chambers aggressively | Distribution is the hardest part; partners solve it |
| **2. Simplicity** | Make onboarding frictionless | Yelp and Google are complex; simplicity is our advantage |
| **3. Telemetry** | Capture and monetize data | Competitors can't replicate the dataset |
| **4. Trust** | Build a pristine reputation | AI agents will prefer trusted sources |
**The window of opportunity is 12-18 months.** If we can build a significant partner network and telemetry asset in that time, we create a moat that competitors will struggle to cross.
---
## 7. Risk Assessment Summary
| Risk | Probability | Impact | Mitigation |
| :--- | :--- | :--- | :--- |
| Yelp offers hosted MCP | High | High | Focus on ignored businesses; build partner ecosystem |
| Google integrates MCP into GBP | High | Medium | Build complementary solution; focus on services Google ignores |
| JSON pointer becomes distrusted | Medium | High | Build pristine reputation; position as trusted intermediary |
| Consumer behavior shifts | Low | High | The adoption data is strong; diversify into structured data |
| Pie/Mainstreet add MCP hosting | Medium | Medium | Build partner ecosystem first; focus on infrastructure vs. marketing |
| MCP standard fragments | Low | Medium | Build flexible architecture; monitor governance |