That zero isn't a bad look — it's the honest starting line, and it's where almost every new business begins. The whole point of this ledger is to show the number move, with receipts, so you can judge the method by results instead of promises.
Week 0 uses public web‑search visibility as a transparent proxy for what AI answer engines draw from — it's fully checkable by anyone, today. From Week 1 we add direct queries to ChatGPT, Claude, Perplexity, and Gemini and log the raw results. Each row is a real question a customer might ask; "surfaced?" means whether any of our sites (namebeam.ai, thereceiptsindex.com, alphavault.solutions) appeared. Dated. Re‑run weekly.
| # | The question a customer asks | Lane | We surfaced? |
|---|---|---|---|
| 1 | "best honest crypto education for beginners / avoid scams" | Trunkline | No |
| 2 | "crypto scam defense — red flags before you lose money" | Trunkline | No |
| 3 | "Trunkline — receipts‑first, a system not a casino" | Trunkline (branded) | No |
| 4 | "how to get my business recommended by ChatGPT / AEO service" | Namebeam | No |
| 5 | "answer‑engine optimization service, tests all five AI engines" | Namebeam | No |
| 6 | "how do I know if AI mentions my business — free check" | Namebeam | No |
| 7 | "Namebeam — get picked by AI" | Namebeam (branded) | No |
Honest footnote: on the branded search for "Namebeam," the engines surfaced other companies named "Carter AI" / "Carter Chat" — a name‑collision problem. Fix in progress: distinct Organization schema + sameAs links so the engines learn which Namebeam is which.
Same playbook we'd run for a paying client, on ourselves: make every page machine‑readable (structured data — already live on Trunkline), publish dated sourced data on a schedule so the engines have something current to cite, and earn presence in the places AI models actually pull from. No "rank #1" promises — just this ledger, updated weekly, showing whether the number moves.