T‑Frame "Scam or Safe?" — GTM Business Plan v2.0

1.1 What the data update showed

• United States. FTC: $15.9B in reported losses for 2025, +27% over 2024's $12.5B; imposter scams the top category for the fifth year running, $3.5B, median loss $700 (within the imposter category) fact (CNBC/FTC, 26 Jun 2026). FBI IC3: $20.9B, +26%, over 1M complaints; top by losses — investment fraud $8.6B, BEC $3.04B; for the first time an "AI-related" category: 22,000+ complaints, ~$900M (deepfakes, voice cloning, mass AI phishing) fact (via secondary source SpyCloud; the IC3 PDF itself returns 403).
• United Kingdom. UK Finance Annual Fraud Report 2026: £1.28B stolen in 2025; unauthorised fraud £703.4M (−5%); £1.68B prevented; on average 8 victims a minute fact. APP reimbursement: 89% of cases within the mandatory PSR scheme's perimeter over its first 15 months (PSR dashboard, 07.10.2024–31.12.2025, £243M); the parallel UK Finance figure for all of 2025 on a broader perimeter: 61%. These are two different metrics — in materials we use 89% with a perimeter footnote fact (refined by verification).
• Australia. NASC Targeting Scams (March 2026): annual losses above A$2B; people 65+ are 17.1% of the population but 26.5% of reported losses; phishing complaints 65,361 (−33.2%); SMS-scam complaints fell from 77,365 to 29,058 (−62.4%) as scammers moved to social media fact (the average-ticket figure A$209→A$476 was not found in the full report text and was excluded).
• Singapore. Police: S$913.1M in national losses for 2025, −17.9% vs 2024; 24.8% fewer cases; 85.2% of victims under 65 fact. ScamShield: 1.53M app downloads, 2.24M site visits fact. Important: S$913.1M is the country's total losses in SGD — not "blocked by ScamShield" and not USD.
• Canada. CAFC: 112,000+ complaints, losses above C$704M, the worst year on record fact; in March 2026, consultations opened on a first national anti-fraud strategy, and Bill C-15 will require banks to hold anti-fraud policies fact.
• Globally. A single GASA/Feedzai Global State of Scams 2026 does not exist yet (it usually ships in October); regional 2026 editions do: Europe (75% encountered a scam in the year), Germany (estimated €12B in losses, average ticket €2,619), the US with Iris. We keep $442B (2025) as the frame with a footnote and wait for October fact.
• AI hook for PR. Three numbers for pitches: the IC3 AI category $900M; Hoxhunt: the share of phishing emails showing AI traits rose from 4% (Nov 2025) to 56% (Dec 2025) vendor; FTC imposters $3.5B. Germany's BKA: online fraud in Germany above €22B in 2025, +18% fact (for Tier-2 materials).

1.2 Steps

• Update the stats block in the deck and on the site. How: replace the S02 slide lines with 2025 official numbers (FTC $15.9B, IC3 $20.9B + AI $900M, UK £1.28B and 89% with a footnote, AU above A$2B, SG S$913.1M with the decline, CA C$704M); keep $442B as the frame. Claude: prepares a diff with source_url in a comment on each figure; the human approves publication. Effort: 1–2 hours. Cost: 0.
• Five local landing paragraphs. On each market a local figure instead of the global one (US: FTC+IC3; UK: £1.28B, 8 victims a minute; AU: 65+ carry 26.5% of losses; SG: 85.2% of victims under 65 — reversing the "scams are about the elderly" stereotype; CA: worst year). Claude writes 5 paragraphs with footnotes; the human approves per market. Effort: 1 day.
• "AI scams 2026" press pitch. 300 words on three numbers (IC3 $900M, Hoxhunt 4%→56%, FTC $3.5B), sent to journalists who have written about AI scams, via a Qwoted/HARO-analogue and directly. Claude: draft pitch + a list of 15–20 journalists with their latest articles; the human checks and sends. Effort: 3–4 hours. Cost: $0–300/mo (Qwoted paid tier optional).
• GASA 2026 auto-monitor. A weekly agent check of gasa.org/research and feedzai.com; when the global report drops: a notification with a TL;DR and a proposal to update materials. Fully agentic, the human only confirms edits. Setup: 30 minutes.
• Data-limits hygiene. In the materials appendix: the FTC/IC3 PDFs do not open automatically (403), figures come via secondary retellings; there is no 60+ breakdown in IC3 2025 in open sources; currency conversions are not "facts." Claude keeps a register of these caveats alongside the source register.

Chapter KPI: all public materials reference only verified figures with markers; the deck is updated by 26 July; the pitch is sent by 31 July.

2.1 The confirmed white space

A synthesis across all mid-2026 competitors estimate (assembling verified facts): no single product simultaneously covers (a) one interface for every format — text, link, QR, screenshot, document, person/contact; (b) a continuous session-dialogue (Norton Genie needs copy-paste into a separate app, "no continuous multi-check"); (c) verification of identities and documents; (d) UX for older users and a "check on a parent's behalf" scenario; (e) a visible, explainable verdict instead of a silent background filter. Plus a verified fact: Scamio does no video/deepfake checks, and Truecaller AI Call Scanner (cloned-voice detection) is paid and Android-only. If T-Frame really checks video/voice, that is a claimable differentiator; before every campaign an agent re-verifies that the comparison still holds.

2.2 Positioning against "built-in is enough"

• Copy block against Chrome/Android. "Chrome and Android catch some calls and links automatically. T-Frame checks text, link, screenshot, document and person, in one dialogue, in 30 seconds." Arguments: Android Scam Detection is off by default and covers calls/SMS; the Chrome filter gives no verdict interface and works only in the browser fact. Claude (copywriter skill) prepares 3 variants + an A/B plan; the human approves.
• Slogan structure for the slide and landing: "Built-in defense filters. T-Frame answers." Top line of the landing and the first 10 seconds of influencer scripts.
• Feature mirror of Truecaller Family (v1.1, not a launch blocker). Truecaller shipped a free Family Group (fraud-call alerts for relatives) in March 2026 vendor: we build a "Share the verdict with a loved one" button after the result (SMS/WhatsApp/email), 3–5 dev-days, and a full "Protect a Parent" loop in chapter 4.

2.3 Product hygiene before any paid program

• One-click cancellation + honest scope. The main documented complaints about Guardio: billing after cancellation and a hard cancel flow (PissedConsumer 1.5/5 across 235 reviews vs 4.4/5 on Trustpilot), and the expectation that the product blocks calls/SMS when it does not fact. Fix before any paid tier: self-serve cancel with on-screen and email confirmation, explicit scope text in the product ("checks what you send; does not block calls automatically"). 2–3 dev-days. Claude writes the copy and spec; a legal/support lead approves.
• Compliance groundwork on "double ratings." The rating gap across channels (stores praise, complaint sites pan) at competitors is driven by billing practices; our answer is a commitments page — "we don't do this" — for each complaint category, assembled by the agent from the top-50 complaints about competitors. 1 day.

Chapter KPI: the competitor comparison in every brief gets a fresh agent re-check no older than 2 weeks; the scope-and-cancellation page is live before the first paid experiment.

3.1 The verified map

3.2 Steps

• A living competitive matrix. A Google Sheet: rows = competitors, columns = the 7 jobs from the white space; a monthly agent refresh of the same queries with a diff report; the human reads the diff in 10 minutes. Setup 4 hours.
• Complaint-mining sprint. The agent collects and categorizes the top-50 complaints (PissedConsumer, BBB, Trustpilot aggregators), producing "we don't do this" commitments for the FAQ/trust page; the human approves the wording. 1 day.
• Monitoring platforms as a tailwind. A monthly cron-agent over blog.google/security and relevant feeds: each new built-in feature raises awareness (our wind) and narrows "no one protects me" (our risk); a 10-minute monthly digest.
• SEO reference for month 6. Organic target: 10–15% of ScamAdviser's traffic, i.e. ~450–1000k visits/mo on the low/high estimate of its traffic; fixed as an internal reference, not a promise. A monthly log from Similarweb/Semrush.

Chapter KPI: the matrix is alive and refreshed monthly; not a single comparative claim older than 2 weeks without a re-check.

4.1 The engine order doesn't change — pace discipline is added

Organic is the core, influencers the flagship, ecosystems the multiplier, paid traffic only accelerates what already works. New from the research: a hard rule for launching the paid channel. Guardio, with a paid funnel and $80M invested, reached roughly 500k paying in ~7 years vendor: paid traffic on its own is slow and capital-heavy. The rule: paid campaigns do not start until organic weekly sign-ups have grown 4 weeks in a row (except $500–1000 micro-tests to calibrate CAC).

4.2 Calibrating "time to 500k" against verified curves

• Truecaller: 10M users by Jan 2013, 100M by Dec 2014, ~5 years from launch to 100M fact; engine: a crowdsourced contact network, value grows with every user.
• Guardio: ~1M extension users by Dec 2021 fact, ~500k paying by Nov 2025 vendor: a paid funnel, slow.
• HIBP: press and word of mouth, no share buttons; screenshots of a binary verdict ("Oh no — pwned!") as a viral artifact; a historical reference of ~160k visits a day (2019, dated) estimate.
• ScamAdviser: ~10 years to 400+ B2B partners and 4.5–7.3M visits/mo fact / estimate: organic is a long game.

Action: a month-by-month pacing chart with three dashed reference curves (the agent updates it from analytics, 15 minutes a month); if the actual curve is below Guardio's (the slowest), that is a signal to redistribute effort across engines at the next gate.

4.3 Viral loop: a shareable verdict from Week 1, referrals from Day 61

• The verdict card as a shareable object. Two or three visual states (Scam / Safe / Uncertain), a large badge, one reason line ("Flagged: spoofed bank domain"), no PII and no victim text on the public card (the Wordle lesson: share an abstraction; the HIBP lesson: binary clarity). Technique: an OG image on @vercel/og, immutable cache for a year, size up to 300 KB (Meta's WhatsApp guide allows up to 600 KB, we keep headroom), 1200×630 fact / practice. Smoke-test the preview in WhatsApp/Telegram/iMessage by hand before release. 3–4 dev-days. Claude: card template, copy variants, a size lint in CI; human: visual approval and a check that no PII is present.
• Share attribution from Week 1. Every share link carries utm_source=share_card and the user's ref-hash; a weekly "sign-ups from sharing" report; this gives a clean before/after for the Day-61 referral launch. 1 dev-day.
• Day-61 referrals: two-sided, non-monetary. For a free product the reward is: early access to family features, a "verified protector" badge, unlocking the family circle at N invitees. Verified benchmarks are modest: median referral-program conversion 3–5% (top quartile 8%+), monetary rewards convert ~40% better than points, visibility mechanics add ~30% to share rate fact (per ReferralCandy; the popular "two-sided +30–50%, K=0.6" figures were refuted on verification and are not used).
• Internal K target. Reference points are informal estimate: K 0.15–0.25 is "good," 0.45 above median, 0.7+ exceptional; cycle 7–14 days. Internal bar: K ≥ 0.2 by Day 90; if K < 0.1, referrals become supplementary and effort shifts to influencers and ecosystems. The agent computes K weekly; the human makes the go/no-go.
• The "Protect a Parent" loop. Inviting a parent: receive alerts without creating an account, a consent toggle on any history visibility (a check history is more sensitive than geolocation, private by default). Reference: Life360 grew revenue from $32M (2018) to $371M (2024) on a family invite vendor, per-invite conversion undisclosed. MVP 1–2 sprints. Claude: onboarding and consent-flow copy; human: the product/privacy decision on defaults.

Chapter KPI: share attribution is live from Week 1; the share of sign-ups from sharing is visible in the weekly report; the referral decision is made at the Day-90 gate on data, not taste.

5.1 Deck fact corrections

• S09 Scamio "7.4M reachable": remove. No source ties 7.4M to Scamio's WhatsApp launch in Australia; the announcement (May 2024) has no numbers at all. Honest replacement: "Scamio has not published usage numbers since its 2023 launch." Deck edit: 15 minutes, the agent prepares the diff, the human approves.
• S06 Truecaller: 429M MAU is dated. Current: 450M+ MAU (Apr 2025), 500M+ total users (Mar 2026) vendor / fact. Also: the company says it stopped collecting raw address books ~2012 — the "contact upload" story is used only as a historical mechanism, not a current description.
• S07 HIBP: 46 governments → 45. The exact sequence: Costa Rica #42, Bangladesh #43, Bahamas #44, Bhutan #45 (May 2026) fact. FBI tranche: 630M passwords, Dec 2025, 7.4% not seen before fact.
• S08 Guardio: fix the 2021 baseline. In December 2021 Guardio had "1M extension users" (TechCrunch), not 100k paying; "Series B" does not appear in the source — correctly it is an "$80M institutional round" fact.

5.2 Deeper lessons

• Truecaller → a data network effect. Every verdict (with consent, anonymized) enriches the base: the more checks, the more accurate the verdicts. Our version of the network effect, legally clean: aggregated signals, not contacts.
• HIBP → an API shaped for partnerships. HIBP's verified pricing ladder: from $4.39/mo (Core 1) to $4,599/mo (Pro 5) and enterprise with no limits fact: so the entry to an API product can be cheap and self-serve. Design principle from day one: a k-anonymity / verdict-only endpoint, no raw content leaving the system — exactly what made HIBP acceptable to Mozilla and 1Password. And soberly: HIBP's government program has been free for 8 years — it is a trust channel, not a revenue one.
• HIBP → infrastructure economics. The documented numbers are old (2018: 2.6 cents a day on 141M requests through a Cloudflare cache; 2022: an egress-bill incident ~US$8k) fact: the lesson is not in the numbers but in the architecture — aggressive verdict caching and limits on heavy objects, built in from the start.
• Guardio → monetization anti-patterns. Hard cancellation, billing after cancel, paid support: all of this is our "do not do" checklist (§2.3). Their partner/affiliate program confirms that the review-site channel works in the niche fact.
• ScamAdviser → B2B patience. ~10 years to a large B2B network fact: we treat B2B as a 12–24-month track (§12), not a quarter's revenue source.

6.1 Programmatic pages: the ScamAdviser model, gated against penalties

• A page template on unique computed data. Fields: domain age (WHOIS), SSL type, hosting/IP reputation, a live OSINT verdict, a user-report counter, a "last checked" stamp with auto-refresh, 2–3 sentences of fact-checked summary. ScamAdviser "checks 1M+ sites a month" with this model and avoided penalties: the pages carry real unique data fact. API lookup cost $0.01–0.05. 3–4 dev-days. Claude: template, the summary-generation prompt, a QA sample of 50 pages against the underlying data; human: template approval and a spot-check of 10 pages before the batch.
• Scaled-content-abuse risk is real: Google's March 2026 core update hits site-level patterns fact. Discipline: batches no larger than 100–150 pages a week; a gate at 50 pages: 100% indexation and no drop in impressions for 2 weeks, only then the path to 500+. Monitoring: a daily agent check of GSC, flagging "crawled, not indexed" pages older than 14 days; the human decides to pause the batch.
• Day 75: go/no-go. There is no reliable "months to 10k/100k visits" benchmark for a new site in the niche verified: no data; so we promise no external KPI but set a checkpoint: no indexation and no meaningful impressions by Day 75 → the budget moves to influencers and ecosystems. The agent prepares a one-page memo with data; the human decides.
• Keyword volumes: only a live Keyword Planner. Tools systematically hide the long tail of "is X a scam" practice; after opening the ad account the agent prepares a seed list and expansions, the human exports real volumes/CPC across 5 markets. 2 hours.

6.2 AEO/GEO: what actually moves citability

• Reddit is ~40% of citations across all large AI engines, and the top-15 domains give 68% of citations fact (5W Index, 680M+ citations). Freshness is strong at Perplexity (content under 30 days old is cited ~3.2× more often estimate); brand mentions correlate with AI visibility roughly 3× more strongly than links estimate (Zyppy). Schema markup helps but its weight is modest (~10% estimate).
• A "usefulness first" Reddit program. Three times a week, substantive answers in r/scams, r/personalfinance threads with real help and sources (FTC, IC3), with no product mention for the first 90 days in r/scams (exact subreddit rules checked by hand: automatic rule-fetch is blocked practice); mentions only where tool threads are explicitly allowed, with disclosure. Claude monitors threads and drafts answers; a human always posts, from a warmed account. 3–5 hours a week.
• llms.txt: a 30-minute stub, not an investment. The research converges: AI crawlers barely read the file, and there is no confirmed citability lift fact. We publish a minimal file and forget it.
• Measurement: Otterly.ai at $29/mo (30–50 prompts, 5 markets, ChatGPT+Perplexity+AI Overviews on the plan), escalating to Profound ($99–399/mo, prices undisclosed and variable vendor) only on proven value. A day-0 baseline, a day-90 measure. The agent maintains a prompt set of real user queries and writes a monthly delta report; the human reviews before the board.
• Sober on clicks: with an AI answer in the results, clicks roughly halve (15%→8% of visits, Pew) fact: organic is measured in sign-ups and citations, not visits alone.

6.3 PR data flywheel: a quarterly report

• The Truecaller Insights format (works as a press hook 8+ years running vendor), but every quarter: a "Scam Landscape Report" on our own aggregated, anonymous data (check volumes, top categories, a Tier-1 geo cut). One headline stat, a market breakdown, a methodology footnote, an on-site interactive + a wire release ($300–800). First issue: Day 31–60. Claude: aggregation queries, report draft, headline variants, release draft, a long-list of journalists; human: verifying every figure (the highest reputational risk of the whole workstream) and sending.
• Seasonal hooks into the calendar: US tax season (Jan–Apr, IRS Dirty Dozen published ~5 March; late deadline 15 October), the annual FTC/Cifas/Scamwatch/CAFC reports (the agent catches the release day and we pitch the same week).

6.4 Content ops and tools

• Stack: Ahrefs Starter $29 or Lite $129/mo (indexation and positions: enough), Otterly $29/mo, Frase $49/mo for optimizing editorial content; Semrush ($139.95+/mo) only on a proven need for competitive analysis fact (on prices).
• Staffing: 1 editor-fact-checker for the programmatic pages and the report; we do not postulate pages/week throughput (no benchmark) — we measure it on the first batches.
• A single gate: no programmatic page ships without a human pass: the risk of site-reputation penalties is incommensurate with saving an hour.

Chapter KPI: 50 pages by Day 30 (a quality gate), 500+ by Day 60 only after the gate; an AEO baseline on Day 0 and a measure on Day 90; the first quarterly report by Day 60; the Reddit program with not a single ban.

7.1 Pricing: the formula and verified ranges

• Rate formula: (average views over 90 days / 1000) × niche CPM × format multiplier practice (confirmed by OutlierKit with a worked example). Verified CPM ranges: lifestyle $15–25, tech reviews $25–45, personal finance $30–60, B2B SaaS/DevTools $40–80; the overall $15–80 span is correct. Note: financial agencies show a higher spread (Creators Agency: median ~$100 CPM on their financial sample vendor), so we compute offers on the low, brand side.
• Format multipliers: dedicated video 1.3–2× an integration (verified: OutlierKit 1.3–1.5×, Creators Agency ~2×; the popular "2–4×" is unsourced), Shorts 0.4–0.6×, pre-roll mention 0.7–0.8×.
• Negotiation mechanics: a first offer of 60–70% of the computed rate (we keep the deck's "first offers 30–40% below budget" pattern), counter-argument: a rate card on the average views of the last 10 videos, not on subscribers.

7.2 Deal structure

• Base: flat + a trackable code/URL. The verified Guardio×ThioJoe template: a flat fee + a 20% annual discount + a 7-day trial via a custom URL guard.io/thiojoe fact (confirmed against the ThioJoe video itself). Attribution via unique promo codes/URLs: the niche standard.
• Affiliate benchmark for phase two: Aura pays $65 per qualified sign-up, 60-day cookie, Impact.com, net-30 fact: a reference for our partner program once a paid tier exists.
• Whitelisting only after proven performance: +20–50% over the base rate for 30–90 days of Spark Ads rights practice (aggregated sources; at Lumanu only the fact "51% charge separately" is confirmed); no perpetual rights on a first deal. Repeat integrations beat reach: CTR grows ~10% with each successive integration from the same creator vendor (Agentio).
• FTC discipline in the contract: disclosure in the first 30 seconds, by voice and/or text, plus the platform toggle (the toggle does not replace disclosure) fact; fines up to $51,744 per violation, liability on the brand fact. Before releasing payment the agent scans the video transcript for the disclosure phrase and a screenshot of the toggle; the human releases the payment.

7.3 Operations

• Tool: Modash Essentials $299/mo ($199 annual): discovery + CRM for 100 creators, 2 seats; vs Grin ~$2.5k/mo and CreatorIQ ~$35k/yr — the choice is obvious vendor (prices).
• List: 30–50 creators in three rings: scam-baiters and fraud-explainers (verified starters: Scambaiter ~1.3M, Scammer Revolts ~1.0M, NetworkChuck; counts from 2022, re-verify before pitching), personal-finance-safety, elder-tech/family safety. The agent pulls each candidate's last 20 videos via the YouTube Data API (sponsors, average views, CPM tier), the human spot-checks 20%.
• Outreach: 15–20 personalized emails a week; a realistic reply bar of 3–5% (by analogy to cold B2B: no influencer-specific benchmark estimate), 8–12% on deep personalization. The agent writes each email from the creator's sponsor history and recent videos; a human always sends.
• Flagships (Kitboga and the top scam-baiters) after the micro/mid wave: first 5–10 micro pilots on Days 0–30 test the message cheaply, by Days 31–60 a dedicated video from a mid scam-baiter, flagships in the Growth/Aggressive scenarios.
• Our own CPA table from day one: there is no public CVR data for security sponsorships verified: no data: every deal with a unique code, a weekly CPA-per-creator report, and after 5–10 campaigns this is our own negotiation benchmark. Day 90: an in-house-vs-agency decision on the numbers.

Chapter KPI: 5–10 micro threads opened in Week 1; first content by Day 30; the CPA table fills from the first campaign; by the Day-60 gate at least one dedicated with a mid scam-baiter is signed.

8.1 Browser extensions and mobile stores

• Chrome Web Store: submit in Week 1, because review takes up to 3 weeks (officially "a few days to several weeks"; April 2026: a queue spike fact). Minimal permissions (activeTab instead of broad host permissions), no obfuscation, all code in the package (remote code is forbidden fact). Rejection plan: a fix within 48 hours, escalation via One Stop Support on a repeat.
• CWS privacy deadline: 1 August 2026 enforces the new rules (data for one declared purpose only, prominent disclosure before consent) fact (announced 01.07.2026): our submission date must pass with an already-compliant privacy declaration. Claude prepares the data-handling disclosure against the checklist; a privacy human approves.
• Listing optimization: title/description relevance determines the ranking "bucket," and inside the bucket — weekly users and rating; the top-performer threshold ~4.5★ practice. 5 screenshots of a real verdict, a 30–60-sec promo video ($200–500). A reviews campaign: an in-app prompt after a confirmed verdict, a reply to 1–2★ within 48 hours, target 4.5★ and the first thousand reviews by Week 4; a rating below 4.0 → features paused until fixed.
• Extension audience benchmarks: Malwarebytes Browser Guard ~11M Chrome users, Guardio ~1.5M vendor, Netcraft ~70k estimate: a realistic ladder for our target.
• Featured/Established Publisher: Featured is granted by a manual Chrome-team review (MV3, privacy, listing quality) and gives a ranking boost fact; we apply after the first weeks of metrics. Established Publisher: identity verification. The rumor of "re-nomination after 6 months" is unconfirmed — we don't plan around it.
• Platform order: CWS → Edge Add-ons (~7 business days) → Firefox AMO (~2 weeks, all dependencies in source) → Safari (an MV3 port, $99/yr Apple Developer) practice / fact; Opera and Samsung Internet after 10k users: queues are unpredictable, audiences small.
• iOS: Week 2 after the extension launch. Apple's hard rule: you cannot claim "scans viruses/malware" (impossible in the iOS sandbox) — framing is "phishing/fraud checker" fact; review 24–72 hours, the security category up to 5–7 days; TestFlight 50–100 testers before submission; the iOS 26 SDK is mandatory. Google Play: $25 one-time, review up to 3–7 days, a Data Safety form covering only user-submitted content, policy deadlines 1/15 August fact. Claude generates the privacy labels and Data Safety from the privacy policy; a lawyer reviews the claim wording.
• Launch-week monitoring: a dashboard (impressions, installs, uninstalls, crashes), uninstalls > 20% → a breakdown by reviews and logs. The agent checks metrics 4× a day and alerts on anomalies; the growth lead decides.

8.2 Messenger bots: WhatsApp with two hard dates, Telegram as a viral loop

• Week 1: Meta Business Verification. The channel's longest pole: Business Manager, matching legal entity/domain/footer/policy to documents, 3–7 business days with perfect documents, 2+ weeks with flaws practice. Claude prepares the exact footer/policy text and a document checklist; a human uploads and submits.
• Week 1–2: a written compliance response on Meta's ban. From 15.01.2026 general-purpose AI chatbots are banned in the WhatsApp Business API fact; task-bots with a non-AI core business survive (Scamio keeps running: an inference from continued marketing, not a Meta ruling estimate). Action: a written request to the BSP compliance team (360dialog/Twilio) describing the bot's single task; keep a copy of the reply on file; the bot's public copy is strictly about "scam check," no open "ask me anything" dialogue. Regulatory context: Italy suspended Meta's policy, Brazil's CADE opened an investigation, and in Europe Meta is discussing admitting general-purpose bots at €0.049–0.1323 per message fact.
• Economics: the free window until 1 October 2026. Now: a user messages first → a 24-hour service window → verdict replies are free; a CTWA entry gives a 72-hour free window fact. But Meta announced (01.07.2026): from 01.10.2026 in-window service messages become paid at utility-like rates fact. Actions: (a) calendar a September recompute of bot unit-economics against the live rate card; (b) an alert threshold of $0.01/check; (c) architecturally keep the Telegram bot as a free alternative and web chat as a fallback. Exact rates come only from Meta's live CSV — blog aggregators contradict each other verified.
• BSP: 360dialog ~€49/mo per number with no markup on messages (MVP up to ~50k dialogues/mo) vs Twilio ~$0.005/message with no base fee; the agent builds a cost model for 3 volume scenarios, the human signs. Meta tiering: start 1k unique contacts/day, auto-growth to unlimited with quality practice.
• CTWA pilot: UK first. Verified benchmarks exist only for UK/US (UK CPM €7–12, cost-per-conversation €0.80–1.80; US pricier; no AU/CA/SG data vendor): $500–1000 over 2 weeks, target: cost of an opened dialogue and conversion to a first verdict; scale only after real numbers.
• Telegram: inline mode from day one. Viral mechanic: @tframebot <link> in any chat returns a verdict card with the bot's name, without adding the bot to the chat fact; the Bot API is free; a claimed 400M users interact with bots monthly vendor. 2–3 dev-days for the inline handler. Mini App Store featuring: after traction. No precedent of a scam-checker reaching millions on inline virality was found: an honest experiment, not a copy of someone's success verified: no data.
• Messenger: a clone of the WhatsApp bot on the same webhook (we reuse the verification), policy re-checked before the build: no ban analogous to the WhatsApp AI ban was found estimate. 1–2 dev-days. Discord: no directory, targeted seeding: 5–10 large scam-awareness servers via outreach to admins, written by a human.

8.3 Partnerships: banks, GASA, government programs, grants

• UK banking context (our trump card in the pitch): mandatory APP reimbursement with an £85k cap, a 50/50 sender/receiver split, a decision within 5 days fact; the PSR assessment (July 2026): APP losses −21%, the reimbursement share up from 54% to 65%, the cap touching <1% of cases fact; PSR functions transferring to the FCA (announced March 2025, confirmed April 2026), a consultation in December 2026 fact. Banks are already building their own: Lloyds is launching Scam Check (68% of Lloyds fraud reports relate to shopping scams, most of which start on Meta platforms fact, wording refined), Revolut since January 2026 catches a "call supposedly from Revolut" in-app fact. The NatWest×Malwarebytes bundle was closed in May 2024: do not cite it as a "live precedent" fact.
• Pilot motive: not innovation but fraud ops. The verified Featurespace path: no accelerators, straight into bank teams (first major bank NatWest 2019; a Pay.UK pilot: +£138.7M of detected APP fraud fact). Our move: a 4-week free read-only pilot of a "paste-before-you-pay" widget for a challenger's fraud/consumer-protection team (Monzo/Starling/Revolut), pitched on the numbers of the bank's real reimbursement cost center. Claude: a one-pager, an ROI model on reimbursements, contact search, email drafts; human: sending and negotiation. 10–15 warm intros a week.

Chapter KPI: CWS submission in Week 1, the extension live by the Day-30 gate; Meta verification and the compliance reply on file by Day 14; the Telegram bot with inline by Day 30, the WhatsApp bot by Day 45 (after the written compliance reply); the first bank pilot dialogue by Day 61–90; the GASA quote obtained by Day 30.

9.1 Policies matter more than bids

• Google Ads Misrepresentation: a minefield precisely for anti-scam creatives. Forbidden: hints of government/brand endorsement, inflated accuracy claims, fear creatives on negative life events, fake system notifications fact. Egregious violations: a ban with no warning; Misleading Representation: a 7-day warning fact (different policy pages); false data at Advertiser Verification (update 04.11.2025): immediate ban fact. Actions: a pre-flight checklist on every ad line (the agent checks each creative against the list of forbidden patterns, citing the clause; the human approves the batch), Advertiser Verification with real documents in Week 1.
• Account warm-up: the first 1–2 weeks: neutral campaigns at $20–50/day, a clean history before scaling scam messaging (2026 enforcement with predictive flags can retroactively pull ads vendor). $300–700 on warm-up.

9.2 Channels and verified rates

9.3 Measurement

• MMP: AppsFlyer Growth: 12,000 free attributed conversions in year one, then $0.07/conversion fact; the agent models when we hit the cap under different growth curves and folds the overage into the CAC math. No public CPI benchmark for the security vertical verified: no data: we build our own.
• $6 kill-switch: a weekly cost-per-active-user dashboard by channel (not by campaign); a channel above $6 two weeks running → auto-pause with an agent recommendation, a human decision. Target $2–4.
• Geo holdouts are not for our size: a statistically honest test needs hundreds of thousands of conversions per arm practice; until month 6+, instead we run directional pause tests (switch off a large channel for a week, read the sign-up delta as a reference, not a proof).

Chapter KPI: the paid channel opens only after 4 weeks of organic growth; the Day 31–60 CAC tests yield cost-per-active-user below $4; at $6+ after optimization the budget moves to organic and creators (the deck rule preserved).

10.1 Stack and verified prices

Stack total: ~$240–350/mo for the core (n8n+Clay+Instantly), ~$600–1000/mo by month 5 with all loops: against the $10k+/mo agencies we don't hire.

10.2 Governance: production lessons taken to heart

• Failures are real: 88% of organizations with AI agents reported at least one security incident; loops that burned $47k in 11 days are documented practice. Our loops from Week 1: (a) a trace of every run (prompt → model → tool calls → action) into a cost log; (b) daily spend caps of $20–50 per workstream; (c) a loop detector: the same request 3+ times an hour → auto-stop and alert; (d) a spend anomaly of +50% over the 7-day average → auto-pause; (e) a weekly one-hour incident review.
• The "agent does / human approves" matrix across all 7 deck workstreams:

10.3 The automation compliance perimeter

• LinkedIn: only the official API (MDP approval), no browser scraping: enforcement has tightened fact / practice. X: $0.20 per post with a link from 20.04.2026, write endpoints cut from self-serve fact: the channel is deprioritized.
• Cold email: CAN-SPAM for the US (identification, unsubscribe), for the EU opt-in only; from 2 August 2026 the EU AI Act transparency obligations apply to AI-generated outreach in the EU fact: a recipient geo-check in n8n before sending, a disclosure line for the EU.
• Platform rates/limits are wired into n8n guards (example: 1 post/hour max per account, buffers to API limits).

Chapter KPI: not a single unauthorized public action by agents; the cost log is complete; the monthly stack bill within the scenario budget; zero "a loop burned the budget" incidents thanks to the caps.

11.1 Launch order within Tier-1

1. United States (anchor, weeks 1–4): the strongest official numbers (FTC $15.9B, IC3 $20.9B); the main press hook: tax season (Jan–Apr; a second wave by 15 October, the late-filing deadline, our Day ~90) and IRS Dirty Dozen (~5 March) fact; partner anchor: AARP (no automatic checker of their own, only a tracking map and a helpline fact) and CSN sponsorship.
2. UK (in parallel, weeks 1–4): the PSR/FCA news cycle and the Online Safety Act (fines up to £18M / 10% of revenue for fraud harm fact), Cifas Fraudscape (444k cases, fraud = 45% of all crime in England and Wales fact); localization: spelling + HMRC/TV licence/parcel smishing examples. 1–2 days of copy adaptation.
3. Australia (month 2): hook: the NASC report and the SPF wave. Note, a verification correction: SPF does not create automatic reimbursement up to A$3,000 (that was refuted), SPF means civil penalties (Tier 1 up to ~A$50M) and complaints via AFCA; the full commencement date is not officially confirmed (sources split between 07.2026 and 03.2027) fact / verified. We build the B2C message on 65+ losses (26.5% of losses), B2B conversations toward the SPF milestones.
4. Canada (month 2, on the US PR tail): "the worst fraud year" + a national strategy in consultation + Bill C-15 for banks fact; English content is US-compatible; Quebec/French: a separate phase, not months 1–6.
5. Singapore (month 3, carefully): positioning strictly "in addition to ScamShield": the SRF cascade (bank → telecom → consumer) has been in force since 16.12.2024 and only for phishing scams; authorized payments (investment, romance, pig-butchering) are out of perimeter fact: our message is "ScamShield filters messages; T-Frame checks the investment platform and the profile, which are outside the SRF." A separate ABS measure from 15.10.2025 (delaying transfers of >50% of balance at S$50k+) fact. No integration claims without GovTech confirmation.

11.2 Localization: one master copy, variant lists

US English is the base; UK/AU/SG/CA: variant lists (spelling + 5–10 real local scam examples from regulatory sources with links). ~1 person-week for 4 markets in total. Claude collects examples from FTC/Cifas/Scamwatch/CAFC/SPF and writes the variants; a marketing human approves (defamation risk from a wrong example naming a brand). Quebec French and German: full translation, a Tier-2 phase.

11.3 Tier-2 watch (months 4–6, light touch)

• UAE: CBUAE banned SMS-OTP as a sole factor (full phase-out by 31.03.2026) and mandated real-time scoring fact: banks need consumer anti-fraud tools: a pilot pitch after traction.
• Germany: BKA: €22B of online fraud in 2025 fact; entry only with full German and a GDPR-first message; variant lists won't cut it.
• Philippines: GSMA: 52% have encountered a scam vendor; a fragmented market, low ability to pay: entry only via a telecom partnership, not organically.
• Action: a quarterly watch note by the agent, the human decides timing.

Chapter KPI: US+UK live by the Day-30 gate; AU+CA by Day 60; SG by Day 90 with compliance-clean positioning; not a single government-integration claim without written confirmation.

12.1 The main realism correction

Verified precedents (ScamAdviser ~10 years to a large B2B network; the HIBP government program free for 8 years fact) say: the first paid B2B deals realistically close 12–24 months after launch, not in months 6–9. So the B2B tracks start on Days 61–90 as pipeline building, and no revenue is booked into the 2026 plan. The agent keeps a "touch → pilot → deal" tracker so we have our own cycle statistics by 2027.

12.2 Stream 1: a threat-intel feed for banks/insurers

• What we sell: an anonymized real-time feed (new phishing domains, message templates, IBAN swaps). There are no public price benchmarks for bank contracts: Feedzai/BioCatch/ThreatMetrix/Featurespace are quoted only under NDA fact: we don't invent a price, we go via pilots.
• Sales mechanics: a one-page data sheet on the Web Risk Enterprise model (90 days of anonymous stats: volumes, verdict distribution, FP rate, latency), target: the fraud ops of mid-size regional banks with no enterprise vendor; 10–15 warm intros a week via Sales Navigator ($99/mo). Claude: data sheet, contact lists, drafts; human: every email and any data agreements.

12.3 Stream 2: a white-label engine for telecoms/ISPs/banks

• The F-Secure/Bitdefender model: revenue-share with no prepayment, but rates are confidential fact. Our move: a 90-day free pilot embedding the checker into the existing security bundle of 2–3 regional operators in Tier-1 markets where F-Secure/Bitdefender is not the incumbent; rev-share discussed after pilot data.

12.4 Stream 3: a threat-intel API (self-serve)

• Price anchors verified: Google Web Risk: 100k lookups/mo free, then $0.50/1000 (Lookup) and $50/1000 when combined with the Update API fact; urlscan.io: $5k/yr API plan, $12.5k–50k/yr pro tiers fact; IPQualityScore $99–999/mo fact; APWG eCX: entry from $1.5k (Accredited Reporter) and $2.5–7.5k corporate tiers, $15k being the top Premium, not the entry ticket fact (refined); VirusTotal: commercial prices undisclosed, secondary estimates $20–50k/yr estimate.
• Our v1 ladder: free 5–10k lookups/mo for eval integrations → metered below the VirusTotal estimates → enterprise on request; OpenAPI docs, a status page, an SLA. Stripe metered. 3–4 dev-days + a day for copy. Data leaves only verdict-only / k-anonymity.
• We budget the engine's own inputs up front: the free OpenPhish feeds (12-hour, non-commercial license!) get replaced at commercial launch by a paid subscription (price on request fact); Web Risk lookups in our own pipeline: see anchors above.

12.5 Grants and Verified Sender

• Grants: an application to the Google.org AI Opportunity Fund APAC (the SG ScamWISE $2M and ASEAN Foundation $5M precedent fact) with a Singapore focus; decision timelines unknown: not on the critical path.
• Verified Sender: only behind the deck's hard guardrails; the price anchor Meta Verified Business $14.99–349.99/mo per channel fact shows the market's willingness to pay for verification, but our badge is not for sale: only KYB checks (company registries, domain, DNS/SPF/DKIM), OpenCorporates API $0–200/mo; paid status reconsidered after our own audit framework.
• Anti-pattern confirmed: no referrals of victims to recovery services.

Chapter KPI: the API docs page and free tier live by Day 90; the first bank pilot dialogue by Day 90; our own deal-cycle tracker kept from the first touch; no B2B revenue promised in 2026.

13.1 SOC 2: the plan's main calendar correction

• Type I: a 14-22 week full cycle (median 16), not "8-12 weeks." The check showed: 8-12 weeks is only the auditor's testing window after controls are ready; the full cycle from kickoff to report is twice as long fact (refined by verification). Start 20-25 July → a Type I report realistically: November 2026. The Day-30 gate contains "process started, platform deployed, auditor chosen," not "Type I ready."
• Type I all-in cost: $28-58k (median ~$42k) including platform, auditor, remediation and ~320 internal hours practice; the clean platform+auditor bundle without internal hours: $10-20k. Type II: an observation window after Type I, budget $15-35k, full readiness for bank DD: mid-2027 practice (the initial research's "$50-150k and 9-15 months" was corrected by verification to the startup range $25-80k+ and 6-12 months for the Type II cycle).
• Week 1: an RFP to three auditors + platform choice (Vanta/Drata/Secureframe), criterion: integration speed and Type I price, decision by 26 July. Claude writes the RFP, the scoring rubric and policy drafts (access control, incident response, vendor management) and fills the platform's evidence tasks; the human runs the calls, signs, and attests controls to the auditor.

13.2 GDPR and data residency

• EU/UK representatives (Art. 27): appoint in Week 2. Budget guide $500-1500/mo for both vendor (the EU-rep range unconfirmed against primary sources: get EDPO/VeraSafe/DPO Consulting quotes directly); a penalty precedent for not having one: €525k (Locatefamily, Netherlands) fact. An outsourced DPO if needed: €2-5k/mo fact.
• DPIA on the check flow (Week 3): a data map: user input → analysis → anonymized result, with no message storage; a free CNIL/ICO template; a one-page summary on the privacy page. Claude writes the sections from a code review; a lawyer signs.
• Hosting: for the B2C launch, Hetzner (Germany, GDPR-compatible, the lowest price, ~€9-30/mo at the start fact / practice); Swiss Exoscale as a premium signal kept for bank pilots (many times pricier estimate, figures unconfirmed against primary sources); the "EU/Swiss residency" claims in the deck stay honest: EU residency from day one, Swiss on an upgrade.

13.3 Transparency and vulnerabilities

• Transparency report: a more careful format than in the initial research. The verification lesson: Proton's "100% refusals" applies only to the VPN product, while the mail service fulfills thousands of orders a year fact: we make our report aggregated and product-honest (how many requests, how many fulfilled/declined, which data types), with no marketing absolutes. A "Transparency: H2 2026" stub page is published in Week 1 (requests: 0), the first full issue: January 2027.
• Vulnerability disclosure: security.txt (/.well-known/) + a self-hosted VDP form from Week 3 (free), a 72-hour triage promise; a managed platform (~$10k/yr HackerOne/Bugcrowd starter) only at a flow of 2+ reports a week practice.
• A named security advisor (weeks 2-3): a FAST template, 0.75-1.5% with 2-year vesting and a 3-month cliff practice; Claude prepares the pitch deck and a terms summary; the CEO runs the calls. Legal review ~$500.
• ISO 27001: after SOC 2, planned for 2027: year-one budget $10-50k (DIY vs auditor-led), the 2026 auditor day rate ~£1,500 fact (refined); 60%+ of enterprise buyers already require ISO/equivalent estimate: kept on the roadmap for Q2-Q3 2027, with the agent doing the SOC2→ISO controls mapping in advance.

Chapter KPI: the auditor is chosen by 26.07; the compliance tracker (board + budget list) lives from Week 1; the transparency stub and security.txt are published by Day 14; the DPIA by Day 21; EU/UK reps appointed by Day 30.

14.1 Week-by-week, Foundation phase (days 0-30, 20.07-19.08)

14.2 Traction phase (days 31-60, 20.08-18.09)

14.3 Scale phase (days 61-90, 19.09-18.10)

14.4 November-December 2026 (month by month)

• November: SOC 2 Type I report (at the median 16 weeks from start); GASA summit Bangkok (10-11.11) if a member; the second quarterly Report (holiday-scam angle, Black Friday); a Tier-2 decision on UAE (post-OTP phase-out) on data; the Type II observation window starts.
• December: year-end results against the pacing chart; the PSR consultation (December) as a UK-PR hook; the 2027 budget and the ISO 27001 plan (Q2-Q3 2027); a decision on a flagship influencer contract (Kitboga tier) on CPA-table data; preparing the January tax-season wave (the category's peak).

B.1 Refuted (kept out of the plan)

1. "SPF (Australia) introduces automatic reimbursement up to A$3,000": the law has no mandatory compensation; penalties + AFCA. The full commencement date is not officially fixed.
2. "ScamShield blocked $913.1M": that is Singapore's total national losses in SGD (−17.9%), not a ScamShield metric (its own: 1.53M downloads).
3. "Two-sided referrals +30-50%, 4 invites, 15% of installs, K=0.6 (ReferralCandy)": these figures are not on the source page; the real numbers: median conversion 3-5%, cash beats points ~40%, visibility +30% to sharing.
4. "SOC 2 Type I in 8-12 weeks": the full cycle is 14-22 weeks (median 16); 8-12 weeks is only the auditor testing window.

B.2 Key corrections (folded into the text)

• Android Scam Detection: 12 countries and off by default (not "default-on in 6 countries"). Chrome Gemini Nano: confirmed via Android Headlines/ppc.land, the primary source weaker than hoped.
• UK 89% vs 61%: different perimeters (the PSR dashboard's 15 months vs UK Finance's full 2025), both figures live.
• Guardio-2021: 1M users (not 100k paying); "Series B" does not appear in the source; PissedConsumer 235 reviews; Trustpilot reviews in the thousands, not "500+".
• Lloyds: 68% refers to shopping scams in Lloyds fraud reports (most of which come from Meta platforms), not "68% of all reports from Meta".
• APWG: $15k is the top tier, entry from $1.5k. HIBP governments: 45. Scamio "7.4M": exists nowhere: purged from the deck.
• YouTube "financial CPV $0.08-0.25" unconfirmed; Advantage+ "3.14 vs 2.70": not a Meta report but one agency's case; TikTok MCP "free": features confirmed, price not.
• llms.txt figures refined (28% of the sample's domains publish; 97%: zero traffic at all), the "don't invest" conclusion held. The 5W stat "11% domain overlap": absent from the release, purged.
• SOC 2 Type II: startup range $25-80k+ and 6-12 months; ISO day rate £1,500; Proton transparency: "100% refusals" only for VPN.

B.3 Could not verify (used with care or not used)

• Exact WhatsApp rates by market (only Meta's live CSV; blogs contradict each other).
• The absence of CPC data for scam queries: a negative claim, closed by a live Keyword Planner.
• Vercel OG: the 4MB limit and the exact Cache-Control are not on the docs page (re-check at implementation).
• Hosting details (Exoscale +74%, Hetzner 20TB egress): unconfirmed against primary sources: the Hetzner choice rests on the general price level, and when in doubt: recompute on live prices.
• No-analogue claims (referral cases of free security products, Telegram scam-bots with millions): searched, not found: treated as "no precedent," not "impossible."