What changed
FACT (Federal Register, 2026-06-17): FDA issued a final classification order placing 'radiological machine learning-based quantitative imaging software with predetermined change control plan' into Class II with special controls. The special controls are codified and condition the device type on having a PCCP.
Why now
The order is weeks old. Any vendor wanting the PCCP pathway (ship model updates without a new 510(k)) must author a compliant PCCP against the new special controls, and then produce verification/performance-delta records on every subsequent update. HYPOTHESIS: this creates a synchronized authoring wave now and a recurring documentation duty afterwards.
Converging signals
Weak convergence: only ONE signal underpins this (the classification order). The 'signals' array is empty and there is no corroborating PAIN or HIRING/SPEND evidence in demand_evidence. The recurring-paperwork pattern is an inference from the rule text, not an observed complaint stream.
Customer pain
HYPOTHESIS: small AI-imaging startups lack in-house regulatory-affairs staff and find PCCP authoring + per-update recordkeeping burdensome. Not evidenced in the input — no complaints, forum threads, or job postings were retrieved.
Who pays
Regulatory/quality lead or founding engineer at seed-to-Series-B radiology AI startups (RSNA exhibitor lists, ~200-400 plausible targets). HYPOTHESIS: they pay per-seat instead of retaining a $250+/hr RA consultant; the source only proves the pathway exists, not willingness to substitute.
Solved today
FACT-ADJACENT (industry-general, not in source): regulatory consultants ($250-500/hr), in-house RA hires at larger vendors, and eQMS platforms (Greenlight Guru, Ketryx, Enzyme) that already market design-control and change-management workflows for SaMD/AI devices.
Why current solutions are bad
HYPOTHESIS: consultants are expensive and slow for a recurring per-retrain duty; generic eQMS is not keyed to the specific special controls in this order. Counter-hypothesis (explicitly flagged as the falsifier in the input): existing eQMS already generates adequate PCCP update records, which would kill this.
Proposed product
Two-part SaaS: (1) PCCP authoring wizard whose templates map clause-by-clause to the codified special controls; (2) an 'update logbook' — each retrain event walks the user through the pre-specified verification protocol and emits the documentation package (performance deltas, protocol adherence, records retention) as an audit-ready PDF/archive.
MVP version
A clause-mapped PCCP template (Word/Notion quality, gated on email) + a thin web app that takes model-update metadata and renders the update-record package. Requires hiring a credentialed RA consultant for 20-40 hours to author/bless the template content — founder has capital for this and it is the credibility linchpin.
30-day build
Run the stated falsification test FIRST, before building: landing page + free clause-mapped PCCP template, outreach to 30 AI-imaging startups via LinkedIn/RSNA lists. Simultaneously ask the falsifier question directly: 'does your eQMS or consultant already handle this?' Target ≥10% email capture and ≥3 discovery calls in 7 days; also scan r/regulatoryaffairs and RA job postings for PCCP mentions.
60-day build
If ≥3 calls validate that eQMS does NOT cover this and consultants are used only for the initial PCCP (leaving per-update records unowned): contract an RA consultant to co-author the template library, build the logbook app, land 2-3 design partners at a founding-customer discount with the consultant's name attached for credibility.
90-day revenue plan
Convert design partners to paid ($300-600/seat/mo or $500-1,000 per update package). Realistic first revenue is day 120-180 given medtech sales caution — acceptable under the founder's runway lesson (confidence 0.9), but this is the slow end of his window.
Distribution path
Direct founder-led outreach to a small, enumerable universe (RSNA/SIIM exhibitor lists, FDA 510(k) database of AI-imaging clearances — a public-records angle that fits the founder). Co-marketing with the RA consultant who blesses the templates. No paid acquisition needed; the buyer list is finite and nameable.
Pricing hypothesis
Anchor against the alternative: one consultant-drafted PCCP ≈ $10-25k. Authoring wizard: $2-5k one-time or bundled; logbook: $300-600/seat/mo. HYPOTHESIS — no willingness-to-pay evidence in input.
Technical difficulty
Low-moderate software (forms, templating, document generation — squarely in founder's fast-prototyping strength). The hard part is regulatory content correctness, which is bought, not built.
Legal / regulatory risk
Material and unusual for this founder: the product's output feeds FDA compliance. An error in a template that contributes to a rejected PCCP or a warning letter creates liability and reputation risk. Mitigable (consultant-authored content, 'not regulatory advice' terms, E&O insurance) but real. The tool itself is not a medical device.
Platform dependency
None. No marketplace, no API gatekeeper. Dependency is on FDA guidance stability, which cuts favorably (more AI-device PCCP classifications are likely, expanding the market).
Founder fit
Mixed, and weaker than it first appears. Superficially matches his proven pattern (regulation creates recurring paperwork → build the tool → charge per event), and lessons give government-mandate plays highest fit. BUT three structural mismatches: (1) this is NOT a portal-submission play — there is no government system to file into; the PCCP rides inside a 510(k) and update records are kept internally for audit, so his ELDT integration edge does not transfer. (2) The entitlement is OPTIONAL — vendors are not compelled with a deadline the way ELDT providers were; a 'forced buyer' label overstates it, this is an incentivized buyer. (3) His profile explicitly avoids heavily regulated medical products and multi-year trust plays; selling compliance documentation to FDA-regulated firms as a non-credentialed outsider is a trust-cycle problem money only partly solves.
Breakout potential
Moderate: FDA is expected to issue similar ML-with-PCCP classifications across device types (cardiology, pathology), so a clause-mapped PCCP engine could expand horizontally. But each expansion deepens exposure to the medtech trust problem and to eQMS incumbents.
Final recommendation
WEAK PASS — do not build yet. The demand evidence is a single rule creating an optional entitlement, not a mandate; there is zero PAIN/HIRING corroboration; incumbents and consultants plausibly already own this; and the founder's portal-integration edge does not actually apply. Run ONLY the 7-day, near-zero-cost landing-page falsification test (which is well-designed), with the eQMS-coverage question asked explicitly on every call. Kill unless ≥3 discovery calls independently confirm the per-update recordkeeping gap is unowned.
Next action
Ship the landing page + email-gated clause-mapped PCCP template outline this week; send 30 personalized LinkedIn messages to RA/QA leads at AI-imaging startups pulled from the FDA 510(k) AI device list and RSNA 2025 exhibitors; log capture rate, calls booked, and verbatim answers to 'who produces your model-update records today?'