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

Consolidate self-serve docs into CONCEPT.md only.

Browse Source 
Merge unique phase detail, build order, success bar, and workstreams from PLAN.md into CONCEPT.md; delete the duplicate PLAN file so one SoT remains.
This commit is contained in:
grokbot_ty
2026-10-01 09:38:49 -07:00
parent 590f6d4808
commit 5ac6c758ce
2 changed files with 80 additions and 143 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md
+80 -7
View File
@@ -1,11 +1,11 @@
# Self-serve AI discoverability — concept
**Branch:** `planning-selfserve-audit`
**Branch:** `planning-selfserve-audit` (from `planning-rev2`)
**Status:** Working draft — conversation checkpoint 2026-10-01
**Companion:** phased execution plan in [`SELF_SERVE_AI_DISCOVERABILITY_PLAN.md`](./SELF_SERVE_AI_DISCOVERABILITY_PLAN.md)
**Role:** Single source of truth for the self-serve AI discoverability wedge (concept + phased plan)
**Related:** [`BUSINESS_PLAN.md`](./BUSINESS_PLAN.md) on `planning-rev2` lineage
This doc captures **ideas, concepts, and strategic direction** for the self-serve “Am I discoverable by AI?” wedge. It is not an inventory of old-repo artifacts.
This doc captures **ideas, concepts, and strategic direction** turned into actionable phases for the self-serve “Am I discoverable by AI?” wedge. It is not an inventory of old-repo artifacts. Do not spawn a parallel PLAN.md — revise this file in place.
---
@@ -142,8 +142,6 @@ Start with **two** cluster packs that prove the split:
## 7. Phases (0–5)
Aligned with [`SELF_SERVE_AI_DISCOVERABILITY_PLAN.md`](./SELF_SERVE_AI_DISCOVERABILITY_PLAN.md):
| Phase | Focus | Success |
|-------|--------|---------|
| **0** | Lock promise, wedge genre, shell (web first) | Promise in one breath without naming a pipe |
@@ -153,7 +151,82 @@ Aligned with [`SELF_SERVE_AI_DISCOVERABILITY_PLAN.md`](./SELF_SERVE_AI_DISCOVERA
| **4** | Demand — ads to self-initiated audits | Funnel rates known |
| **5** | Toward industry graph | Only after consented structured truth is worth composing |
**Build order:** promise → verify → presence → recommendability → results/fixes → recheck → then ads. Do not wait on the graph or MCP.
### Phase 0 — Lock the promise
- One-sentence value prop owners understand without jargon.
- First wedge genre (who we speak to first).
- Plain-language definition of “recommendable.”
- v1 shell decision: web first (see §4); chatbot embed optional later; one engine.
**Success:** The promise can be said in one breath without naming a transport (MCP, etc.).
### Phase 1 — Trust gate
- Claim-a-business + stakeholder verification (email code first; other signals later).
- Minimal PII, clear consent, rate limits / abuse controls.
**Success:** Verified owners reach the audit; unverified cannot.
### Phase 2 — Audit engine (the product)
- **Presence score:** On the map across major providers + category consistency.
- **Recommendability score:** Likelihood an AI would surface them for genre-relevant queries.
- Start with a thin, explainable rubric — not a black box — with **cluster-variant weight packs** (§6).
- Outputs: plain-language findings + ranked owner-actionable fixes.
**Success:** Same business twice ≈ same scores; owner understands why.
### Phase 3 — Self-serve loop
- Results page / chat readback, fix checklist, optional re-check.
- No mandatory human review.
- Optional “ask an expert” as escape hatch only.
**Success:** Majority complete without human touch.
### Phase 4 — Demand
- Lightweight campaigns that send SMBs to the portal for a self-initiated audit.
- Funnel metrics: start → verify → complete → recheck.
**Success:** Acquisition cost and completion rate are known; creative/genre can iterate.
### Phase 5 — Toward the graph (later)
- Only after audits produce structured, consented business truth worth composing.
- Graph remains Northstar; does not gate v1.
### Build order (what ships first)
1. Promise + wedge genre
2. Verify gate
3. Presence score
4. Recommendability score
5. Self-serve results / fixes
6. Recheck
7. Then ads / demand programs
Do **not** wait on the industry graph or a single wire protocol.
### v1 success bar
- Owner can finish alone
- Two clear scores with explainable why
- Actionable DIY fixes
- Repeatable recheck
- Ads can point at it without a sales call
### Workstreams (parallel once Phase 0 is clear)
| Workstream | Owns |
|------------|------|
| Promise & wedge | Positioning, genre, “recommendable” language |
| Trust & verify | Claim flow, codes, consent, abuse |
| Presence engine | Provider coverage, NAP + category checks |
| Recommendability engine | Rubric, explainability, genre relevance |
| Experience shell | Web and/or chatbot UX on one engine |
| Growth | Campaigns, funnel metrics |
| Graph (later) | Composition of consented structured truth |
---
@@ -184,4 +257,4 @@ Mark as **hypotheses pending real audit data** — revise from scored businesses
## Capture note
Drafted from strategy conversation 2026-10-01 (voice + chat). Push to `planning-selfserve-audit` so concepts are durable alongside the execution plan. Nothing is locked until Ty says so.
Drafted from strategy conversation 2026-10-01 (voice + chat). Former duplicate `SELF_SERVE_AI_DISCOVERABILITY_PLAN.md` was merged into this file and removed — keep a single SoT. Nothing is locked until Ty says so.