What changed
Two things converge: (FACT, Guardian) a continuing wave of ADA disability-access lawsuits is hitting US cafés and shops, creating correlated, recurring liability across many small businesses; and (FACT, context.dev launch) schema-defined structured extraction from arbitrary websites is now a single API call, so scanning hundreds of sites for accessibility defects no longer requires bespoke scraping/parsing infrastructure.
Why now
ADA web-accessibility 'surf-by' litigation volume remains high (INFERENCE from the Guardian pain signal), and the cost of building a bulk WCAG crawler just collapsed. The two together make it newly cheap for a solo dev to score exposure across a whole portfolio rather than one storefront.
Converging signals
Complaint signal (ADA lawsuit pain across many small businesses) × dev capability (one-API structured extraction at scale). The imaginative leap is the buyer swap: audit the aggregate risk-holder's book, not the individual sued café.
Customer pain
HYPOTHESIS (not evidenced in input): liability insurers, commercial landlords, and franchise HQs carry correlated ADA exposure across a book they cannot see. Each lawsuit/demand letter is a claim, a defense cost, or a tenant default they eat. Today they have no per-portfolio visibility into which insured/tenant sites are lawsuit-bait. The Guardian pain is real for the CAFÉ; the pain for the INVERSE BUYER is inferred and must be validated by the kill test.
Who pays
Small-business liability insurers / MGAs / program administrators, commercial landlords with retail tenant books, and franchise HQs — the parties holding aggregate ADA exposure. NOT the individual café.
Solved today
Overlay-widget vendors (accessiBe, UserWay, AudioEye) sell per-site remediation to the business itself — a market that ignores the aggregate holder and is itself increasingly named in lawsuits. Insurers price ADA into premiums crudely or ignore it; landlords rely on lease indemnity clauses; franchise HQ relies on brand-standard audits. No one scores the whole book automatically.
Why current solutions are bad
Per-site overlays are legally dubious (plaintiffs' bar targets overlay users), don't give the risk-holder portfolio visibility, and require the individual business to act. The aggregate holder has no dashboard, no per-site prioritization, and no monitoring for new defects across the book.
Proposed product
A bulk accessibility-exposure crawler + scoring engine: feed it a list of tenant/insured/franchisee URLs, run WCAG heuristic checks via structured extraction, output a portfolio risk dashboard (per-site score, top violations, remediation priority, trend over time) plus alerts when a site's exposure worsens. Sold as a data/monitoring subscription and per-portfolio scan, not a per-storefront widget.
MVP version
Crawler over context.dev-style extraction running a subset of automatable WCAG 2.1 AA checks (alt text, form labels, contrast, ARIA, keyboard traps at heuristic level), aggregated into a per-portfolio dashboard with a CSV/PDF exposure report. Seed with one real insurer's or landlord's supplied URL list as a paid design partner.
30-day build
Build the crawler + heuristic WCAG scorer + basic dashboard. Assemble a public list of retail/hospitality sites to demo. Run the KILL TEST: pitch 10 small-business insurers/MGAs, commercial landlords, and franchise operators — do they price or worry about aggregate ADA exposure? Capture willingness-to-pay.
60-day build
Convert one design partner: score their actual book, deliver a ranked exposure report, iterate on which signals they act on (renewal pricing, tenant notice, remediation mandate). Add monitoring/re-scan and a defensible scoring methodology.
90-day revenue plan
Turn the design partner into a paid monitoring subscription (per-site-scanned or per-portfolio tier); use the case study to land 2–3 more insurers/landlords. First revenue realistically 60–150 days given the buyer is a business account, not a card-swipe prosumer.
Distribution path
Direct outreach to insurance program managers/MGAs writing small-commercial/BOP books, retail landlord asset managers, and franchise operations leads. Content: publish an 'ADA web-exposure index' of a public sector to generate inbound. Partner with defense-side ADA law firms who want to quantify client exposure.
Pricing hypothesis
Per-portfolio scan fee (e.g. $2–10/site scanned) plus recurring monitoring subscription tiered by book size ($500–$5k/mo). Optionally a data/API feed licensed to insurers for underwriting.
Technical difficulty
Moderate. The crawl+extract layer is cheap now, but a CREDIBLE, defensible WCAG scoring methodology is the hard part — automated checks only catch ~30-40% of WCAG issues (INFERENCE, well-established in accessibility practice), so over-claiming 'compliance' is a legal and reputational trap. Position as relative EXPOSURE scoring, not a compliance guarantee.
Legal / regulatory risk
Real but manageable: never claim a site is 'ADA compliant' (creates liability); frame output as risk/exposure scoring. Handling a portfolio of third-party site data is low-PII. Avoid becoming a legal-advice provider.
Platform dependency
Dependency on the structured-extraction API (context.dev is a brand-new YC S26 vendor — single-vendor risk); mitigate by keeping the extraction layer swappable (Playwright + open-source axe-core as fallback, which also strengthens the scoring moat).
Founder fit
Good but not the founder's peak thesis. It's a data/report + compliance-monitoring product (his stated preference) built with fast AI-assisted prototyping and public/records-style bulk data work. It is NOT a government-portal forced-filer play — the buyer is discretionary and must be convinced, unlike his FMCSA edge where the buyer is compelled. Founder-fit is solid, not maximal.
Breakout potential
Moderate-to-good: if insurers adopt it for underwriting, it becomes a licensed data feed (defensible, recurring). Replicable across other correlated web-liability classes (privacy/CCPA, cookie-consent, dark-patterns). Ceiling limited by the buyer needing education.
Final recommendation
CONDITIONAL BUILD — but gate it on the kill test FIRST. Do not build the full product before pitching 10 aggregate risk-holders. The technology is cheap and the founder can execute; the entire risk is whether the inverse buyer will pay. If ≥2 of 10 show budget/urgency, proceed to a paid design partner. If not, pivot the same crawler to sell exposure reports directly to franchise HQ (which does audit brand standards) or to defense-side ADA law firms who already spend on this problem.
Next action
Run the kill test this week: cold-pitch 10 small-commercial insurers/MGAs, retail landlords, and franchise operators a one-page 'ADA portfolio exposure' offer and measure whether any will pay for a scan of their book — before writing the crawler.