idea-015 · viability deck
Every slide states a condition that would have to be true, then reports where it stands using the candidate file's own claim and its own confidence tag. A deck never upgrades a tag, invents a number, or recommends anything, and there is no ask slide.
The chair: the investor, and the operator who would have to sell a single reusable SKU into a commoditised, DMEPOS-billed category against incumbents who already hold line-wide clearances.
How to read this: every slide is a condition, not a conclusion. a bracketed claim reference points at the numbered claim of knowledge-base/candidates/idea-015.md whose position it names, with the tag that claim carries there right now; [no claim] means nothing in the file speaks to this. No number appears here that is not in a claim, and there is no ask slide. See docs/deck-spec.md.
First build, at stage: verified. The money side of this file has one genuinely verified number and it is the wrong one: what Medicare pays the clinician for the fitting service is confirmed against CMS's own file, while what Medicare pays for the device — the only revenue line this business has — rests on a vendor blog, because the CMS DMEPOS rate file is absent from this environment.
Would have to be true: Medicare Part B's durable-medical-equipment benefit would have to pay for the pessary itself as a separately payable supply, out of a different budget line and through a different contractor from the office visit in which it is fitted — and a manufacturer would have to be able to reach that budget line.
Where it stands: The physician half is confirmed and the supply half is not. CPT 57160 (fitting and insertion of pessary or other intravaginal support device) is an active status-A code on the CMS Physician Fee Schedule, work RVU 0.87, non-facility total 2.11, paying a national unadjusted non-facility $70.48 at conversion factor 33.4009 [claim 8: verified] — but a payment decomposition says what a code pays, never that a payer agreed to pay it for this indication, and the descriptor text itself is AMA-licensed and unverifiable here. That the device is separately billed under A4561/A4562 to a DME MAC while 57160 goes to the local Part B MAC — and therefore that a DMEPOS supplier channel stands between the manufacturer and revenue — is [claim 7: unconfirmed], explicitly an inference in the file, and the file notes it is the kind of inference that decides a go-to-market plan. Whether A4561 and A4562 are active DMEPOS codes at all is [claim 6: unconfirmed] — unconfirmed because data/hcpcs_level_ii.csv and data/hcpcs_payment_rates.csv are absent from this environment, not because CMS is silent. Every one of those is Medicare fee-for-service; that commercial and Medicaid payers pay comparably, and therefore that non-FFS fittings are addressable revenue at all, is now on record as [claim 30: unverified].
What would settle it: Fetch the two named CMS files (data/README.md gives the exact releases and expected columns, and instructs that a web search must not be substituted). The contractor-routing half is a Medicare claims-processing-manual fact for which this repo has no typed connector at all — a human lookup, not a re-run.
If it's false: If the device is not separately payable and is absorbed into the office visit, there is no device revenue line and the business is selling a capital item into practice opex against a $70.48 procedure — which is a different company. Factor 2 (Reimbursement, 15%) loses its premise, and Slide 3's price row goes to zero rather than to unknown.
Would have to be true: A code would have to exist, it would have to pay an amount, and a coverage policy would have to allow the dispense for this indication. All three, separately.
Where it stands:
coverage connector has no cached file here
[claim 7: unconfirmed]. That such a policy exists and does not impose a requirement a
single-SKU adjustable device would fail is [claim 31: unverified].
What would settle it: The CMS DMEPOS fee-schedule file for A4561 and A4562 — a free download, and the file calls it the cheapest open item it has. Then a DME MAC LCD and policy-article search for pessary coverage criteria, which is the missing coverage half the Scores table names.
If it's false: If A4562 pays materially less than the blog figure, assumption [claim 24: unconfirmed] loses the denominator it was stated against and the unit economics break at the only place they can break. If coverage attaches conditions a one-size-fits-all device cannot meet, the code existing is irrelevant.
Would have to be true: Population, fitting rate, price per device and reachable share would each have to hold at a level that makes a once-per-patient reusable device worth building.
Where it stands:
What would settle it: Volume is settled. Price comes from the same free CMS DMEPOS file as Slide 2. Reachable share has no primary source and needs commissioned practice-level research — the same research that would answer [claim 22: unconfirmed]. Population beyond Medicare FFS needs the payer-mix work behind [claim 30: unverified].
If it's false: Factor 3 (TAM, 15%) already sits at the 2/5 kill floor on the Scorer's draft read. One of the three components is now verified and it is the one that was already the Generator's own guess; the two that set revenue are not. If price lands at the bottom of the blog range and reachable share lands below the bottom of the assumed band, there is no arithmetic that rescues the factor.
Would have to be true: The device would have to reach first billable dispense without a clinical investigation, on a route whose length is known before the money is spent.
Where it stands: The route is not one route but three, and the file carries all three deliberately. 21 CFR 884.3575 classifies the vaginal pessary as Class II and FDA assigns product code HHW [claim 1: verified] — but that establishes what HHW is, not that a device whose diameter is set and locked mechanically stays inside it. Whether HHW devices need a 510(k) or are premarket-notification exempt subject to 21 CFR 884.9 is not established [claim 2: unconfirmed], and the file is precise about why: the openFDA classification connector here returns class, device name, regulation and review panel only, with no exemption flag, so the single call the Scorer expected to settle it does not. If exempt, entry is registration and listing plus QSR; if De Novo — live because no cleared adjustable-diameter predicate was identified [claim 5: unconfirmed] — it adds years. That no clinical investigation is needed on the substantial-equivalence route is [claim 34: unverified]. No claim in this file carries a dollar cost, a headcount or a calendar for any of the three routes, and none is estimated here. The hidden cost the Scores table names is cleaning validation on a reusable mechanical joint [claim 25: unconfirmed].
What would settle it: The FDA Product Classification database record for HHW, read for its "510(k) Exempt" flag — a connector change or a human lookup, explicitly not a re-run of the existing call. A pre-submission meeting is what settles whether the mechanism stays in HHW. A contract-manufacturing quote settles the cost side and simultaneously tests [claim 24: unconfirmed].
If it's false: If FDA reads the ratcheting lock as a new technological characteristic, the De Novo route replaces a cheap fast entry with a multi-year one and Factor 7 (Capital intensity & time-to-revenue, 10%) drops from the 4/5 the Scorer drafted — the file says this single question drives that factor's whole spread.
Would have to be true: The ratchet-and-lock mechanism would have to be patentable over the published art, and a granted claim on it would have to be the thing a competitor cannot design around — because nothing else here is a moat.
Where it stands: The file is candid that the moat is one mechanical ratchet on an otherwise commodity silicone ring. Patentability is [claim 32: unverified], and it has to clear at least one published disclosure that is already on record: US 6,189,535 "Deflatable vaginal pessary", filed 1993-04-02, expired 2013-04-02 [claim 17: verified] — and the file's own note says an expired patent blocks patentability as readily as a live one blocks practice, so this line is comfort on FTO and the opposite on the moat. US 11,865,033 is live, filed 2021-05-26, running to a naive 2041-05-26 [claim 16: verified], and already steered this design away from a collapse-for-removal feature; its issued claim scope is explicitly not confirmed and reading it would be a legal opinion this repo may not generate. Whether anyone has even looked at the ratcheting-lock art is [claim 18: unconfirmed] — no landscape or FTO search exists anywhere in this repo's connector surface, and the file calls this the most consequential open item it has. No filed application on the mechanism is recorded anywhere in the file [no claim]. Regulatory exclusivity is nil on a 510(k) or exempt route [claim 1: verified], [claim 2: unconfirmed].
What would settle it: A commissioned professional FTO and patentability search on the ratcheting diameter lock — a paid, multi-week item, and the same search answers Factor 4 and Factor 5 together. The issued claims, assignee of record, legal status and maintenance state of US 11,865,033 come from USPTO/Patent Center in one lookup.
If it's false: If the mechanism is unpatentable over the deflatable-pessary art, Factor 5 (Moat, 10%) has nothing left, and an incumbent with an existing line-wide clearance copies the feature at lower cost. If the landscape search instead finds a live blocking patent, that is Factor 4's automatic kill — which is why the file insists the correct posture today is "not yet knowable," neither blocked nor clear.
Would have to be true: No incumbent pessary line-holder would have to be able to add a settable, lockable diameter to its existing cleared line faster and cheaper than a new entrant can arrive — and the two named development-stage competitors would have to be solving a different problem from this one.
Where it stands: They are not solving a different problem. The category is crowded: a non-tagging sweep found 16 Substantially Equivalent decisions in HHW between 2010 and 2026 [claim 2: unconfirmed], and four of them are individually confirmed — K132313 Eis Corporation (2014-12-05), K231786 Cosm Medical "Gynethotics Pessary" (2024-03-06), K232677 Reia LLC "Reia pessary" (2024-05-21) and K233548 Resilia "Uresta®" (2024-04-03, SUI-only and therefore not a POP predicate) [claim 26: verified]. K231786 is the structural warning: a single 510(k) covering an entire multi-shape, multi-size pessary line — ring, ring-with-support, ring-with-knob, Marland, Gellhorn and cube across Stage I-III — which is exactly the incumbent posture a single-SKU entrant competes against. K190277 ProVate is cleared for temporary non-surgical management of POP [claim 3: verified]. The direct competitor is further along than the claim line says: patient-specific 3D-printed pessaries are not a research direction but a deployed product — 113 patients across 18 Canadian sites, 77.0% initial fitting success, 63.7% continued use, published outcomes, reaching the same iterative-refit value proposition by manufacturing rather than by mechanism [claim 20: unconfirmed]. Reia's early feasibility study NCT04275089 is completed with posted results and Reia now holds a clearance [claim 21: unconfirmed], [claim 26: verified]. That no adjustable-diameter competitor exists is [claim 5: unconfirmed] and rests on absence of evidence over a window- and limit-bounded sweep of trade names, which the file warns must not be read as confirmed absence. Whether an incumbent would need a new 510(k) to add the feature is [claim 33: unverified].
What would settle it: A human read of the 16-record HHW sweep against product literature rather than trade names, since openFDA device names describe products and not mechanisms. For the incumbent question, FDA's "Deciding When to Submit a 510(k) for a Change to an Existing Device" guidance applied to a settable-diameter modification — a regulatory-consultant read.
If it's false: If an incumbent can add this under a letter to file, the entry window closes before first revenue and Factor 8 (Competitive intensity, 5%) loses the only thing the Scorer said holds it above 1 — that no adjustable-diameter competitor was identified.
Would have to be true: The A4562 allowed amount would have to sit far enough above the manufactured cost of a silicone ring containing a ratcheting lock to leave a gross margin worth having — and the cheaper half of that inequality would have to be knowable for the price of a download.
Where it stands: The assumption is untestable in both directions at once right now, and the file says so: the cost side has no connector and no quote, and the payment side that bounds it is blocked on the missing DMEPOS rate file [claim 24: unconfirmed], [claim 11: unconfirmed]. Fetching data/hcpcs_payment_rates.csv and data/hcpcs_level_ii.csv fixes the ceiling and closes [claim 6: unconfirmed] in the same pass, leaving one sourceable number — a contract manufacturing quote — as the whole remaining question.
What would settle it: Two free CMS downloads, then one quote from a silicone moulding contract manufacturer on a two-part assembly with a ratcheting detent. Neither is a research programme.
If it's false: If the allowed amount will not support a margin on a mechanised device, no regulatory or clinical result rescues the business, and the answer arrives before any of the expensive questions on Slides 4 and 5 have to be paid for.
Every condition above with nothing verified behind it. Read this slide first.
Eighteen conditions, of which the verified claims on this deck (1, 3, 8, 10, 16, 17, 26) touch four: they fix the class, the fitting payment, the Medicare FFS service volume, the two patent dates and the incumbent field. They fix no revenue number.
If only one thing from this chair could be checked: what CMS actually allows for A4562 — [claim 11: unconfirmed], with [claim 6: unconfirmed] and [claim 24: unconfirmed] hanging off it.
Why this one rather than the others. It is simultaneously the hard ceiling on per-patient device revenue, the denominator of the margin question, the price row of the TAM, and — on a reusable device that bills once rather than recurrently — the entire revenue model expressed as one number. It is also the only condition on this deck that is both load-bearing and free: a CMS file download closes it and claim 6 together, while the FTO landscape, the patentability opinion and the pre-submission are all paid, multi-week items that only matter if this number clears.
Naming it is not a recommendation, a gate, or a kill.