porbot
162 lines
8.3 KiB
Markdown
162 lines
8.3 KiB
Markdown
# geolocal.io — Business Plan (working draft)
|
||
|
||
**Branch:** `planning-rev2`
|
||
**Status:** In progress — conversation checkpoint, not final
|
||
**Purpose:** One durable place for the clean plan. Existing docs on `main` are raw material; this file is what we iterate.
|
||
|
||
**How we work this file**
|
||
- Checkpoint here after every few solid decisions (or when a phrase must not be lost).
|
||
- Prefer revising this over spawning parallel strategy docs.
|
||
- Mark unknowns as open questions. Do not invent market numbers here.
|
||
- Nothing is locked until Ty says so. Checkpoint working directions; revise freely as the conversation matures.
|
||
|
||
---
|
||
|
||
## 1. North star (wording still open)
|
||
|
||
**Intent (stable):** Enable local businesses to be discovered and recommended by AI assistants.
|
||
|
||
Still wordsmithing the exact sentence. The job does not change while the phrasing does.
|
||
|
||
---
|
||
|
||
## 2. What the company is
|
||
|
||
Infrastructure — not a consumer destination.
|
||
|
||
- Host structured business truth so AI assistants can discover, understand, and recommend local businesses (services and local retail with real-world presence).
|
||
- Give the business a simple way to point at that truth (no servers for them to run).
|
||
- Orchestrate booking / payment / related partners where needed; do not rebuild Calendly or Shopify.
|
||
- Stay invisible to end consumers; win by being useful to agents and trustworthy to owners.
|
||
|
||
**Not:** another Yelp/Google for human browsing attention.
|
||
|
||
---
|
||
|
||
## 3. Who we serve
|
||
|
||
**Primary customer:** the business owner.
|
||
|
||
By extension:
|
||
- Someone in their organization acting for them
|
||
- A partner they already trust (agency, SEO, chamber, tourism board)
|
||
|
||
Partners are a **path to the owner**, not a different product.
|
||
|
||
---
|
||
|
||
## 4. How demand shows up (two moments)
|
||
|
||
1. **Presence for other AIs** — When a consumer’s assistant asks for a local plumber / salon / store, structured geolocal data can be consulted and acted on.
|
||
2. **Owner (or their AI) asks for help** — Emerging path: “How do we help our business be discovered by AI?” Geolocal should invest in scenarios where the owner’s own AI can diagnose and set that up — not only human sales through agencies.
|
||
|
||
Same north star; different moments of truth.
|
||
|
||
---
|
||
|
||
## 5. Wedge and flywheel (direction agreed)
|
||
|
||
**Preferred wedge:** a free AI-visibility checkup (SSP audit).
|
||
|
||
Why:
|
||
- Shows immediate value / need
|
||
- Builds critical mass
|
||
- Small free actions amplify adoption
|
||
|
||
**Long-term reputation bet:** become so useful and dense that AI systems default to checking geolocal for local-class queries — analogous to how they lean on Yelp or Foursquare today.
|
||
|
||
**Strategic read (not pricing gimmick):** free usefulness → coverage → agent trust → more local queries resolved via geolocal → more owners want in → denser graph.
|
||
|
||
### Phase 1 owner conversation (working direction — not locked)
|
||
|
||
Speak **outcomes**, not plumbing. Example: “most recommended bakery on Whidbey Island for muffins.” Do not lead with MCP, endpoints, or `llms.txt`.
|
||
|
||
Phase 1 *fixes* usually look like classic local visibility hygiene (2017-style) before deeper 2027 agent work:
|
||
- NAP (Name, Address, Phone) consistency
|
||
- Hours alignment across platforms
|
||
- Maps / GBP / Yelp (and similar) listing hygiene
|
||
|
||
**Working nuance (2026-09-15):** foundation-first for *fixes*, not for *measurement*. The free audit’s scoreboard is AI recommendability in plain English (“would an assistant recommend you for this job in this place — and why not?”), not “GBP is 67% complete.” If 2017 hygiene is already solid, skip fake Google-fix busywork and go straight to agent gaps. Differentiation vs commodity local SEO lives in that scoreboard.
|
||
|
||
### Owner-facing scorecard (working direction — not locked)
|
||
|
||
POR work: an intuitive scorecard a business owner understands. Top-level outcomes (wording TBD), not SEO jargon:
|
||
|
||
1. **AI knows you exist** — findable identity / NAP / listings
|
||
2. **AI knows what you do** — services, specialties, hours — enough to answer “what is this place?”
|
||
3. **AI would recommend you** — enough trust + fit that an assistant would pick you for a real job in a place
|
||
|
||
Keep to **three top-line outcomes**, each with plain “why not yet” underneath — not a 40-row SEO audit. Dual scoreboard still applies: hygiene work feeds rungs 1–2; recommendability is the differentiation line.
|
||
|
||
**Open — measuring “would recommend” (working packaging idea, not locked):**
|
||
|
||
- **Owner input:** business owner describes the business in their own words — what they want to be “known for.” GeoLocal derives the query set from that + place + category; owner does not invent keywords.
|
||
- **Routine queries:** generate from that input, then freeze a small static set (roughly 5–10), re-run routinely — not a giant library.
|
||
- **Free tier (idea):** one real live ping (e.g. ChatGPT), capped (e.g. one run per business), plus a free heuristic so the scorecard isn’t blank if the ping fails.
|
||
- **Paid (idea):** same questions across a versioned panel of popular AI assistants (names will drift — treat panel as versioned, not sacred).
|
||
|
||
Honesty / cost / abuse controls still TBD.
|
||
|
||
### Free path after checkup (working direction — not locked)
|
||
|
||
Free includes:
|
||
1. Ranked DIY punch list the technical owner can execute (e.g. align hours across providers)
|
||
2. Mint of a **minimal owned geolocal record** (name, place, category, plus plain-English AI recommendability) — densify does **not** wait for paid
|
||
|
||
Soft upsell in-product: “comfortable DIY, or want GeoLocal to help?”
|
||
|
||
### Paid “help” vs product (working direction — not locked)
|
||
|
||
- **Paid listing cleanup** (Maps / hours / NAP fixes done for the owner) = partner / agency **fulfillment**, not the product.
|
||
- **Product** = the owned geolocal record + ongoing AI-readiness score (and later agent-facing presence).
|
||
|
||
Do not document GeoLocal as a local SEO shop with extra steps.
|
||
|
||
---
|
||
|
||
## 6. Business plan audience (still open)
|
||
|
||
Clarify what this document must optimize for first:
|
||
- Internal clarity (founders / operators)
|
||
- Investors
|
||
- Partners / channels
|
||
|
||
Can serve more than one later; pick the primary reader for v1 structure.
|
||
|
||
---
|
||
|
||
## 7. Source material (do not duplicate blindly)
|
||
|
||
Treat as inputs, not competing sources of truth while this draft is live:
|
||
|
||
- `NORTH_STAR.md`
|
||
- `docs/strategy/CANONICAL_STRATEGY.md`
|
||
- `docs/gtm/`, `docs/investors/`, `docs/product/`
|
||
- `docs/archive/` — historical only
|
||
|
||
If something here conflicts with `CANONICAL_STRATEGY.md`, resolve on purpose in a later pass — do not silently fork forever.
|
||
|
||
---
|
||
|
||
## 8. Checkpoint log
|
||
|
||
| When | What landed |
|
||
| :--- | :--- |
|
||
| 2026-09-15 | North star intent; owner-first buyer; partners as extension; agent-mediated “get discovered” path; free checkup wedge; reputation / critical-mass flywheel; open question on free durable win vs diagnosis-only |
|
||
| 2026-09-15 | Working direction (not locked): phase 1 = outcome language + local-hygiene foundation; free may include DIY punch list + minimal owned record; paid listing-fix as partner/agency fulfillment; product = record + AI-readiness score; porbot = repo scribe, Desk = conversation |
|
||
| 2026-09-15 | Process: nothing locked yet — distill POR as we build; porbot scribes so key insights are not lost |
|
||
| 2026-09-15 | Working nuance: 2017 hygiene usually first *fix* work; dual scoreboard from day one (hygiene + AI recommendability); skip forced hygiene phase if foundation already solid |
|
||
| 2026-09-15 | Working direction: owner scorecard ladder — knows you exist / knows what you do / would recommend you (wording TBD); open whether v1 recommend = heuristic vs live assistant pings |
|
||
| 2026-09-15 | Working idea: owner “known for” → small frozen query set; free = capped single live ping + heuristic; paid = versioned multi-assistant panel |
|
||
|
||
---
|
||
|
||
## Next conversation topics
|
||
|
||
1. Wordsmith the three scorecard rungs; define plain “why not yet” evidence under each
|
||
2. Decide free/paid assistant-ping packaging (caps, panel list, heuristic fallback) and cost/abuse controls
|
||
3. Primary reader for v1 of this plan (internal / investors / partners)
|
||
4. Offer / packaging detail (what free record includes vs what paid unlocks beyond fulfillment) — no invented numbers
|
||
5. 90-day proof: what “reputable enough that AI checks us” requires in coverage and quality
|
||
6. Owner MCP vs GeoLocal.io chat: same journey or separate surfaces (later layer; keep out of phase-1 owner talk)
|