What changed
FACT: FTC began enforcing the TAKE IT DOWN Act (cited FTC release), giving a federal removal channel and platforms a 48-hour SLA. FACT: Meta now lets anyone generate AI images of a specific person from public photos (cited Reddit). HYPOTHESIS: these combine into a monitor-and-file service.
Why now
FACT: enforcement started in 2026 and platforms must operationalize a removal workflow immediately, so the compliance surface exists right now.
Converging signals
Regulation (enforceable 48h takedown) + platform (default AI-likeness generation exposing people) + dev capability (one-API structured extraction to scan for a likeness). The three do meet — but the LAW and the PRODUCT premise do not fully align (see kill arguments).
Customer pain
HYPOTHESIS: people exposed by default AI-image generation want continuous protection. The only cited PAIN is one r/smallbusiness thread about Meta exposure — real anxiety, but zero evidence anyone pays for monitoring/takedown-as-a-service.
Who pays
Claimed: SMBs, creators, public-facing individuals. REALITY CHECK: the TAKE IT DOWN Act's mandatory removal covers nonconsensual INTIMATE imagery (NCII/AI sexual deepfakes), not brand logos or ordinary AI portraits — so the paying buyer the pitch names (brand/self protection) is largely NOT the class the 48h clock protects. The actual protected class is intimate-abuse victims, who are a crisis buyer, not a recurring SaaS account.
Solved today
Today victims file directly through each platform's now-mandated free removal channel, or hire reputation/takedown firms (Ceartas, BrandShield, DMCA-style services) for broader web monitoring.
Why current solutions are bad
Per-platform DIY filing is tedious and slow, and no tool tracks the 48h SLA or escalates to the FTC. But the mandated free channel is, by law, supposed to be adequate — which undercuts a paid discovery-only wedge.
Proposed product
A monitor that scans covered platforms for AI-generated images matching a client's reference likeness, auto-fills the statutory removal request with required attestations, tracks each against the 48h SLA, and escalates unhonored cases to the FTC complaint channel.
MVP version
Manual-assisted pilot: for 3-5 consenting clients, run periodic likeness scans on 1-2 platforms, generate compliant removal requests, and log SLA compliance. Run the KILL TEST (10 real filings) before writing detection infra.
30-day build
Legal read of what the Act actually compels (NCII scope, who has standing, whether authorized-agent filings are accepted per platform); interview 10 potential clients + 3 reputation firms; hand-run 10 real removal requests for one consenting client.
60-day build
If agent-filing works, build the SLA tracker + request templater (the cheap, defensible part); pilot likeness scanning on the single highest-signal platform only.
90-day revenue plan
HYPOTHESIS: white-label the SLA-tracking + filing templater to existing reputation/takedown firms (a reachable B2B buyer that already sells this) rather than selling monitoring to anxious individuals. First revenue depends entirely on the KILL TEST passing.
Distribution path
Partner channel to reputation-management / brand-protection firms; content targeting NCII-victim support orgs (ethics-gated).
Pricing hypothesis
Per-monitored-identity subscription ($29-99/mo) OR white-label per-seat/per-filing to firms; avoid per-victim crisis pricing on vulnerable individuals.
Technical difficulty
High: reliable cross-platform likeness matching with low false positives is an unsolved, ongoing-cost ML problem, not a one-API job. Structured extraction helps scrape, not identify a face.
Legal / regulatory risk
High-context: the Act targets intimate/sexual deepfakes; mis-scoping it to general 'brand likeness' is a factual error that guts the forced-removal premise. Handling reference/abusive intimate images creates real PII and safety obligations.
Platform dependency
Heavy: depends on platforms honoring third-party-agent requests and on scanning platforms whose ToS may forbid it — the founder cannot compel either.
Founder fit
Weak-moderate. This is NOT his proven government-portal forced-filer shape — there is no filer compelled to buy his tool; the compelled party is the platform. It edges toward monetizing vulnerable victims, which the mandate explicitly warns against.
Breakout potential
Moderate only if pivoted to a B2B compliance tool for platforms or a white-label for takedown firms; low as a direct-to-victim monitoring app.
Final recommendation
REVISIT / mostly KILL as framed. The brand-likeness framing is legally mis-scoped and the direct-to-victim model is ethically and commercially weak. The one survivable wedge is B2B: sell the SLA-tracking + compliant-request templater as a white-label tool to existing takedown/reputation firms — but only pursue it if a 10-filing KILL TEST proves agent-filed requests are honored. Do not build detection infra first.
Next action
Run the KILL TEST: for ONE consenting client, hand-file 10 real removal requests as an authorized agent across covered platforms and measure honor-rate + false positives before any build.