What changed
FACT (per convergence description, signals 1475/973/1542): engine-level fingerprint spoofing is now agent-usable out-of-the-box via MCP, and coding agents let non-experts generate working scrapers with one command. INFERENCE: this mints a population of automation owners who cannot repair what they prompted into existence.
Why now
HYPOTHESIS: the arms race runs from both sides — agent tooling creates new scraper owners weekly while detector vendors adapt to exactly those tools, producing a steady breakage stream. Plausible mechanism, but the input contains no direct observation of breakage volume.
Converging signals
Democratized creation (coding agents) + hardened detection (fingerprint heuristics, challenge pages) + maintenance skill gap. Note: the `signals` array supplied to this brief is empty; the convergence rests on three referenced-but-not-included signals, so the convergence itself is second-hand here.
Customer pain
HYPOTHESIS: a revenue-bearing automation (lead-gen feed, pricing monitor, listing tracker) silently stops working; the owner lacks anti-bot forensics skill to diagnose fingerprint flags vs. DOM drift vs. IP reputation. Pain is plausibly urgent WHEN it occurs, but demand_evidence is empty — no complaint, job posting, or spend signal proves it occurs at monetizable frequency.
Who pays
HYPOTHESIS: solo operators, small agencies, and SMB ops people whose scraper feeds revenue. They are identifiable only at the moment of breakage (Reddit posts, Upwork job posts), which makes the buyer reachable but only via constant low-leverage prospecting.
Solved today
Re-prompt the agent that built it (free, improving monthly); hire an Upwork scraper dev ($30–80/hr, days of latency); migrate to managed scraping APIs (Zyte, ScrapingBee, Apify) that absorb anti-bot work as a platform service.
Why current solutions are bad
Re-prompting fails when the breakage is detector-side rather than selector-side — the agent regenerates the same fingerprint-flagged approach. Freelancers are slow and variable. Managed APIs require re-architecting. But NOTE: the 'agent re-prompt fails' claim is itself unproven and is the load-bearing assumption; if agents + MCP anti-detect tooling repair these failures for free, willingness to pay collapses. This is the falsification path stated in the input and it strengthens every month as agents improve.
Proposed product
Per-incident 'resurrection': customer submits failing script/run + description of the revenue workflow it feeds; instrumented replay harness diffs detection signals (fingerprint flags, challenge pages, DOM drift) against a maintained detector knowledge base; returns patched config/selector map for a flat $150–400. Scope restricted to sites the customer is authorized to access.
MVP version
No product build. MVP is the validation test verbatim from the input: sample one week of r/webscraping posts and Upwork scraping jobs; count requests that are (a) AI/agent-built, (b) newly broken, (c) revenue-bearing; reply to qualifying ones with a fixed-fee repair offer and fulfill the first 2–3 manually with existing tools (Playwright, an anti-detect browser, manual diffing). Operational note: this server cannot ingest Reddit without OAuth (per system lesson, confidence 0.85), so sampling must be done manually or via OAuth.
30-day build
Run the sampling test; manually fulfill up to 3 paid repairs at $150–250 to measure actual diagnosis time per incident (the unit-economics unknown). Log every incident's root cause class (fingerprint / challenge / DOM drift / IP) — this is the seed of the detector knowledge base.
60-day build
Only if ≥10 qualified requests and ≥2 paid conversions occurred: build the replay/diff harness for the two most common root-cause classes; stand up an intake form that forces revenue-context qualification; establish presence in r/webscraping and 2–3 automation-tool Discords as the 'resurrection' fixer.
90-day revenue plan
HYPOTHESIS: 10–20 incidents/month at ~$250 average = $2.5k–5k/month, plus convert repeat breakers to a $99–199/month monitoring retainer (uptime canary + priority repair), which is where the real business is — per-incident revenue alone is a job, not a product.
Distribution path
Responding to breakage posts (Reddit, Upwork, Discords) is the only channel proven reachable, and it is manual, per-incident, and rate-limited. No compounding channel identified. This is the structural weakness: demand is episodic and the buyer only exists for ~48 hours at a time.
Pricing hypothesis
$150–400 flat per incident, priced against the Upwork alternative (slower, similar cost). Monitoring retainer $99–199/month as the upsell. Founder has runway, so pricing for margin over volume is fine.
Technical difficulty
Moderate-to-high in the wrong way: the replay harness is straightforward solo work, but the compounding asset — the detector knowledge base — is an open-ended arms race against Cloudflare/DataDome/Akamai R&D teams. Anti-bot forensics is NOT in the founder's stated strengths; he'd be learning the moat while selling it.
Legal / regulatory risk
Gray. Even with the authorized-access scoping filter, the service's core competence is defeating bot detection, which sits near ToS-violation territory and (in bad cases) CFAA adjacency. Intake filtering helps but is self-attested. Reputational and payment-processor risk are non-trivial.
Platform dependency
High on the demand side: prospecting depends on Reddit/Upwork tolerating solicitation replies (Upwork ToS restricts off-platform steering; Reddit mods ban service-pitching). The system's own lesson notes Reddit already blocks this server's datacenter IP.
Founder fit
Mixed-to-weak. Fits: automation, AI workflows, fast prototyping, complaint-mining instinct. Doesn't fit: no anti-bot forensics background, no forced buyer, no government-portal shape (the system's highest-confidence founder-fit heuristic, 0.80, points at mandate-driven filing tools — this is the opposite: discretionary, episodic spend). Sells through demonstrated value, which does suit the 'fix it for a flat fee, pay on success' motion.
Breakout potential
Modest. Best case is the monitoring retainer becoming 'Datadog for your scrapers' for the agent-built-automation cohort. But that market is also the natural roadmap of Apify/Browserless/agent vendors themselves, any of whom can bundle self-healing.
Final recommendation
DO NOT BUILD YET — run the zero-cost validation test first. The input itself specifies the experiment (one week of r/webscraping + Upwork sampling; thresholds: ≥10 qualified AI-built-and-broken requests with revenue context, ≥2 conversions at ≥$150). With empty demand_evidence, building anything before that test would be inventing demand. If the test passes, re-enter as a productized service with the monitoring retainer as the actual business; if requesters turn out to be experienced devs or re-prompting fixes their breakage, kill permanently. Opportunity cost matters: this founder's proven edge (government-portal filing automation, forced buyers, per-transaction fees) scores structurally higher than discretionary break-fix services.
Next action
Manually sample 7 days of r/webscraping posts and Upwork 'scraper broken/fix' job listings (Reddit OAuth or manual browsing — this server's IP is blocked per system lesson); tally posts meeting the AI-built + newly-broken + revenue-context criteria; reply to qualifying ones with a $150–250 flat-fee diagnostic offer; record conversions against the ≥10/≥2 thresholds.