TruthWatch — AI-answer watchtower for local businesses

1. One-liner

Catches the moment AI invents a fake deal, wrong hours, or price about your shop — and hands you the fix.

2. Trend signal — why now?

Two things happened in the last twelve months and they collided.

One — consumers moved to AI for local discovery, fast. BrightLocal’s 2026 Local Consumer Review Survey found 45% of consumers now use AI tools to find local services, up from 6% a year earlier — one of the fastest behavioral shifts ever recorded in search. ChatGPT leads at 31%, Google AI Mode at 23%. AI is now the third most-used local-discovery channel, ahead of Yelp.

Two — those AI engines started getting local businesses factually wrong, loudly. Stefanina’s Pizzeria in Wentzville, Missouri made the news (Vice, WAFF, WSB-TV) when Google’s AI Overview invented specials that never existed — “buy a pizza, get the second for $4,” large pizza at small-pizza price — and customers showed up angry when the shop couldn’t honor a deal Google made up. The owner posted publicly that they “can’t honor a Google AI special” and have no control over what the AI says. That’s not a one-off: Google’s AI Overviews now produce tens of millions of questionable answers an hour at trillions of searches scale (Popsci/Inc reporting). Wrong hours, “permanently closed,” fabricated prices, and invented promotions are now a recurring local-business hazard.

And the owners are powerless and unaware: 88% of local businesses have no active strategy for AI search at all (GrowthPro AI, May 2026 benchmark). They find out only when a customer is already standing at the counter, furious about a deal that doesn’t exist.

Provenance:

• Signal 1 (demand): Stefanina’s Pizzeria overwhelmed by angry customers over Google-AI-invented fake deals; owner publicly powerless — https://www.vice.com/en/article/pizza-joint-overwhelmed-with-angry-customers-asking-for-fake-deals-made-up-by-google-ai/ — Aug 2025 (still circulating June 2026)
• Signal 2 (demand/market): 45% of consumers now use AI for local discovery, up from 6% YoY; 88% of local businesses have no AI-search strategy — https://www.marketingcode.com/ai-search-6-to-45-percent-contractors-invisible/ — 2026
• Signal 3 (feasibility + economic): GEO/AI-visibility tooling productized and funded (Evertune $19M; Goodie AI $495/mo; Ayzeo single-location at $31–39/mo) — querying ChatGPT/Gemini/Perplexity/AI-Overviews programmatically is now off-the-shelf — https://www.evertune.ai/resources/insights-on-ai/top-15-generative-engine-optimization-geo-platforms-for-2026 — 2026 Category: Platform shift

3. The opportunity

The whole GEO (“generative engine optimization”) category that sprang up in 2025–26 is built for one buyer: the marketer at a brand who wants to get found in AI answers. Profound, Evertune ($19M raised), Goodie AI ($495/mo), Scrunch, Ayzeo — they all answer “do I appear, and where do I rank in ChatGPT?” That’s a visibility/marketing product.

Nobody is selling the other half of the same coin to the corner pizzeria: “is the AI telling lies about me, and how do I make it stop?” That’s a reputation-defense product, and the buyer trigger is completely different — it’s not the CMO doing a quarterly visibility audit, it’s the owner who just got yelled at by a customer over a fake $4 pizza deal and Googled “how do I get Google AI to stop making things up about my restaurant” at 9pm.

The incumbents miss this because:

• They price and position for brands/agencies, not single-location owner-operators.
• “Visibility tracking” (do I rank?) is a different job than “misinformation watch” (am I being misrepresented?). Even Ayzeo, the cheapest single-location tool, tracks appearance and sentiment — not factual drift against your real hours/prices/menu.
• The fix workflow — update Google Business Profile, push schema, submit feedback to each engine, escalate “permanently closed” — is fiddly and per-engine. Nobody packages the correction, only the measurement.

The 10× isn’t a smarter dashboard. It’s collapsing “find out from an angry customer → panic → spend a weekend figuring out how to fix it” into “get a text the hour it happens, tap the suggested fix, done.”

4. Target market

• Primary customer: US single-location, owner-operated local businesses where wrong public info costs walk-in revenue and reputation — independent restaurants/pizzerias, HVAC & plumbing, dentists/orthodontists, salons/med-spas, auto repair. 1–20 staff, no in-house marketer.
• Why they buy (their words): “Google AI is not accurate and is telling people specials that do not exist, which is causing angry customers to yell at our employees” (Stefanina’s public post). They buy the moment misinformation has cost them a scene at the counter or a “you’re permanently closed” that killed a Saturday.
• Rough TAM reasoning: ~5M+ US local businesses in these high-walk-in verticals. Even 0.3% reach at $49/mo average is ~15,000 customers ≈ $8.8M ARR — well past the $5M target with room to spare. Don’t need broad penetration; need the worried slice.
• Why now for them: A year ago almost nobody asked ChatGPT for “best plumber near me.” Now ~half of their would-be customers do, and the engines are improvising about them. The threat went from theoretical to “happened to me last week.”

5. Product sketch (MVP)

• Ground-truth setup in 5 minutes: connect Google Business Profile + confirm hours, address, phone, current prices/menu, active promos. This is the “source of truth” everything is checked against.
• Daily multi-engine sweep: ask ChatGPT, Google AI Overviews/AI Mode, Gemini, and Perplexity the real customer questions about this business (“hours?”, “do they offer X deal?”, “are they open Sunday?”, “how much for Y?”, “are they still in business?”).
• Misinformation alerts (the core): SMS/email the owner the moment an engine states something that contradicts ground truth — invented deal, wrong hours, wrong price, “permanently closed,” wrong address/phone. Severity-ranked (a fake deal or “closed” beats a slightly stale hour).
• One-tap fix packet: for each flagged error, the exact correction steps for that engine — GBP edit, schema snippet to add to the site, per-engine feedback/report submission, and a “permanently closed” escalation path — pre-filled, not generic advice.
• Fake-deal shield: a public “our real current offers” page + a ready-to-post social/counter script (“We do not offer the Google AI special; here’s what’s actually on”) so staff aren’t ambushed.
• Weekly truth report: plain-English “here’s what AI said about you this week, what was wrong, what we fixed.”
• Re-check loop: after a fix is pushed, automatically re-query to confirm the engine corrected (changes appear in days to weeks), and keep the owner posted.

6. AI angle — what’s load-bearing

AI is load-bearing twice. First, the threat is AI — without LLM-driven local discovery this product has no reason to exist. Second, the product uses LLMs to (a) generate the realistic question set a customer would actually ask each engine, (b) parse free-text AI answers and extract structured claims (hours, price, promo, open/closed), and (c) diff those claims against ground truth to decide “this is a material misrepresentation” vs. noise. Strip the AI out and you’re left with a human manually asking four chatbots about every client every day — which is exactly the unscalable thing that makes this a business. The correction-packet generation (per-engine, pre-filled) is also LLM-driven.

7. Localization angle (if any)

US-first by design — the acute, news-making incidents and the 45% adoption stat are US, the GEO buyer culture is US, and English-only keeps v1 simple. Natural expansion is other English markets (UK/Canada/Australia) where Google AI Overviews and ChatGPT local discovery behave similarly, then localized question-generation for non-English markets later. Not a localization wedge — the wedge is the vertical/buyer-trigger framing, not geography. N/A as a primary wedge — global-English expandable, but US is where the pain is loudest now.

8. Business model — path to $1M–$5M ARR

• Pricing: $39/mo single location (monthly sweep + alerts + fix packets); $79/mo “Guard” tier (daily sweep, fake-deal shield page, priority re-check); $149/mo agency/multi-location for the marketing shops that manage 10–30 local clients.
• ACV: ~$600 blended (mix of $39 and $79, plus agency seats pulling the average up).
• Math to $1M ARR: ~1,700 paying locations at ~$49 blended × 12 ≈ $1M. Reachable inside a focused vertical (e.g., independent restaurants) plus a handful of agency resellers.
• Math to $5M ARR: ~8,500 locations — needs the agency/reseller channel doing the heavy lifting (a marketing agency adds it to every local client at $149 covering several locations) plus 2–3 verticals live. Credible but requires the channel to fire.
• Expansion path: per-location add-ons, the agency white-label tier (highest ACV), and an upsell into adjacent “AI reputation” work (review-response, schema management) once you’re already the owner’s AI-watchdog.

9. Go-to-market wedge — first 100 customers

• Ride the news incidents. The Stefanina’s-style stories are public and recurring. Monitor for new “AI made up a fake deal/closed my business” local-news and Reddit/X posts; reach the named business and the dozens of owners commenting “this happened to me too” with a free audit of what AI currently says about them. The audit is the demo — show them a real lie about their own business.
• Cold outreach with a live wound. Scrape a vertical directory (e.g., 2,000 independent pizzerias/HVAC shops in 5 metros), run the free sweep on each, and email only the ones where AI is already wrong: “ChatGPT told us you’re closed Sundays — you’re not. Here’s the full report.” Expect far-above-baseline reply rates because it’s specific and alarming, not generic.
• Agency/reseller channel. Local-SEO and GBP-management agencies already bill SMBs $125–$1,200/mo and need a new AI-era line item. Sell them the $149 white-label tier; they bundle “AI misinformation protection” into existing retainers. Each agency = many locations at once.
• Vertical communities + POS/booking partners. Restaurant owner FB groups, r/restaurateur, HVAC/plumbing forums where the fake-deal anger already lives; and integration/referral with a booking or POS vendor whose merchants feel this pain.

10. Build complexity — justification

Low–Medium. Everything is off-the-shelf: GBP API for ground truth, the four AI engines queried via API or lightweight automation, an LLM for question-generation/claim-extraction/diffing, SMS/email for alerts. No custom models, no proprietary dataset, minimal state (per-business ground truth + a claim log). A solo technical founder ships a credible v1 in 6–10 weeks; the fiddly parts are reliable per-engine querying (some, like AI Overviews, aren’t a clean public API) and keeping false-positive alert rates low. Call it Low complexity on the stack, nudged toward Medium by the engine-access plumbing.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Querying public AI answers and helping a business correct its own info is clean.
Ethical — no harm / dark patterns	✅	Pro-accuracy; helps owners and consumers get correct info.
Market exists (evidence above)	✅	News incidents + 45% adoption + funded GEO category + existing SMB spend.
1–5 person team can build this	✅	Off-the-shelf APIs, minimal infra.
Launchable with <$50K / ₹40L	✅	Inference + dev time; no capex.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Real, news-making, hair-on-fire when it hits — but episodic, not felt daily by every business. Many owners don’t know it’s happening until it costs them.
Demand evidence	15	12/15	Strong: viral incidents, 6%→45% adoption, funded category, existing SMB spend on adjacent. Slightly docked — direct “I’d pay for misinformation watch specifically” evidence is inferred from the visibility category.
Build feasibility	15	13/15	Mostly off-the-shelf; only friction is non-API engines and false-positive tuning.
Distribution clarity	15	11/15	The free-audit-with-a-real-lie wedge is sharp and the agency channel is real, but converting alarmed owners to recurring payers is unproven.
Revenue mechanics	15	11/15	Pricing benchmarked to Ayzeo ($31–39) and GBP management ($125–400); math works but leans on the agency channel for $5M.
Time to first revenue	10	6/10	Self-serve SMB can pay in weeks, but no pre-sold pipeline; education needed that this is a thing to pay for.
Defensibility	10	3/10	Thin. Ayzeo and the whole GEO pack can add “misinformation alerts” as a feature. Moat is positioning, vertical focus, the correction-workflow library, and speed — not technology.
Total	100	71/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (per-engine querying + LLM extraction/diffing) · content-heavy (the correction-playbook library and vertical outreach content are the durable asset).

Key assumptions to validate (3–5)

1. Assumption: Owners will pay recurring ($39–79/mo) to prevent misinformation, not just react to one incident. How to test: Run free audits on 100 businesses, surface real errors, and measure how many convert to a paid plan within 14 days (target ≥8%).
2. Assumption: A meaningful share of target businesses actually have AI saying something wrong about them right now (so the cold wedge has fuel). How to test: Sweep 300 businesses across 3 verticals; measure the % with ≥1 material error. If <20%, the “live wound” wedge is too thin.
3. Assumption: Fixes actually move the engines within a tolerable window (days–weeks), so the product delivers a visible win. How to test: Push corrections for 20 flagged errors, re-query, measure correction rate and time.
4. Assumption: Agencies will white-label this as a retainer line item. How to test: Pitch 15 local-SEO/GBP agencies on the $149 tier; target ≥3 LOIs.

Risk flags

1. Incumbent encroachment: Ayzeo/Profound/Goodie can bolt on “misinformation alerts.” Defensibility is positioning + speed, not tech. Mitigate by owning a vertical and the correction workflow.
2. Platform dependency: Some engines (Google AI Overviews) lack a clean public API; querying may be brittle and ToS-sensitive. A change in access could break sweeps.
3. Market timing / awareness: The pain is real but episodic and under-recognized; you may spend heavily educating owners that this is a thing worth a subscription before incidents recur for them.
4. False positives: Alerting on noise (slightly stale hours, harmless paraphrase) erodes trust fast. The diff logic has to be conservative.

14. Structured verdict

Score:                  71/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical solo/pair who can ship LLM extraction + content engine; comfortable with SMB self-serve and an agency channel
Time to revenue:        6–10 weeks (free-audit → paid funnel)
Capital to launch:      $8–20K (inference + outreach tooling)
Top 3 assumptions to validate first:
  1. Free-audit-to-paid conversion ≥8% in 14 days — run on 100 businesses
  2. ≥20% of swept businesses have a live material AI error — sweep 300 across 3 verticals
  3. Corrections actually move engines in days–weeks — push 20 fixes, re-query
Kill criteria:
  - Abandon if <20% of swept businesses have any material AI misinformation (no fuel for the wedge)
  - Abandon if free-audit-to-paid conversion stays <5% after 200 audits
  - Abandon if a single-location incumbent (Ayzeo et al.) ships an equivalent "misinformation alert + fix" feature before your v1 and undercuts on price

15. Next step — 1-week validation sprint

• Day 1–2: Pick one vertical and one metro (e.g., independent pizzerias in St. Louis). Pull a list of 80–120. Hand-run the four-engine sweep against each business’s real hours/price/promos.
• Day 3–4: Tally the error rate — what % have AI saying something materially wrong? Email the 20 worst-hit owners a free one-page report (“here’s the lie ChatGPT is telling about you”) with a “want us to watch this and alert you?” CTA and a $39/mo link.
• Day 5: Decide go/no-go on two falsifiable numbers: (a) ≥20% of swept businesses had a material error, and (b) ≥2 of the 20 contacted owners said “yes, set this up” or paid. Miss both → the pain isn’t dense enough to sell against. Hit both → build the v1.