idea-006 · business case

Who pays, from which budget, how much, and 2-4 commercial routes to first revenue — every figure below traces to a copied claim or a declared assumption, and the routes are laid out unranked. Choosing a commercial strategy is a Tier 3 act, so this page presents options and stops.

Follower bimodal acoustic-plus-electrical tinnitus neuromodulation device under the QVN classification created by DEN210033, aimed first at the VA channel — business case

Intended use: For the treatment of adults aged 18 and older with chronic subjective tinnitus of moderate or greater severity, used at home on a prescribed daily schedule under the supervision of a licensed audiologist or physician, as an adjunct to tinnitus counselling.

Who pays

Two candidate cheque-writers appear in the file, and neither is established as the one that actually clears.

Writes the cheque: either (a) VA, through a prosthetics/formulary dispense once the device has its own presence in the VA channel [claim 9: unconfirmed], or (b) the patient, self-pay, which is the Generator's own stated belief because no tinnitus-device-specific code was found [claim 7: unconfirmed]. The file does not resolve which of these is the real first buyer, or whether either is.
Out of which budget line: on the VA side, the VA National Acquisition Center's Schedule 65 II A Federal Supply Schedule, which covers hearing aids, hearing aid accessories, auditory implants and assistive devices as indefinite-delivery/ indefinite-quantity contracts awarded through full and open competition [claim 30: unconfirmed]. On the self-pay side, there is no budget line at all — it is household spending, and no coverage policy or code has been identified to move it onto a payer's budget [claim 7: unconfirmed].
Against which comparator: the incumbent, Lenire — the De Novo grantee that founded the QVN classification this candidate would enter via 510(k) [claim 1: verified], [claim 2: verified]. Per company press materials, Lenire's manufacturer already holds a VA Federal Supply Schedule 65 II A contract, effective 2024-06-17, extending eligibility to DoD, Bureau of Prisons, Indian Health Services and Public Health Service beneficiaries [claim 40: unconfirmed] — a claim sourced to a press release, not to the VA's own contract record. So the comparator is not a channel gap to be first into; it is an incumbent that may already occupy the channel this candidate is aimed at.
Stops buying instead: not established. No claim in the file states what a VA facility or a private audiology practice would defund or decline to reorder in order to add this device. The nearest the file comes is the explicit, unresolved question of whether VA audiologists would prescribe a cheaper follower device instead of, or alongside, the incumbent already on contract [claim 41: unconfirmed] — which the file itself flags as a stakeholder-future claim the adoption connector refuses to answer.

The chain's weakest link is its first one. Neither cheque-writer is confirmed, and the better-evidenced of the two candidates — the VA channel — is evidenced only for the incumbent, not for this device.

The money model

Decomposed, not asserted. No line below is asserted as a market size; the two components that would normally anchor a TAM — the indicated population and the share of a compensation count that overlaps it — carry no number in the candidate file at all, and that absence is reported rather than filled.

Line	Figure	Backing
VA-channel denominator — veterans with service-connected tinnitus disability compensation	3.2-3.5M, per recent VA Annual Benefits Reports as read by the Generator; never independently checked, because no connector in this repo reads VBA/VHA data	[claim 8: unconfirmed]
Share of that compensation population that also meets the intended-use severity threshold (moderate-or-greater chronic subjective tinnitus on a validated scale) and would be considered a candidate for a home-use bimodal device	not established anywhere in the file — a disability-compensation count and a clinically-indicated population are two different things, and the file does not show they are the same population, or even meaningfully overlapping	[assumption A1]
Whether the VA channel is actually open to this device — its own Federal Supply Schedule listing, not merely proximity to the incumbent's	unresolved on two separate questions: whether the follower could win the listing at all, and separately whether VA audiologists would then prescribe it	[claim 9: unconfirmed], [claim 22: unconfirmed], [assumption A2]
Private-channel indicated population — US adults with chronic bothersome tinnitus of moderate or greater severity	no figure established at all; `market` returns unverifiable by design (see below)	[claim 10: unconfirmed]
Adjacent, non-severity-stratified reference point — 12-month "any tinnitus" prevalence among US adults	9.6% (SE 0.3%), an estimated 21.4 of 222.1 million adults, 2007 National Health Interview Survey — the file's own caveat is that this overstates the indicated population by a large multiple and should not substitute for a severity-banded figure	[claim 38: unconfirmed]
Net selling price per device, including fitting and the first treatment cycle	$2,000-$4,000, the Generator's own assumption, anchored to hearing-aid pricing rather than looked up against the predicate's price	[claim 11: unconfirmed]
Whether that price nets to a positive gross margin after cost of goods and remote-fitting-platform cost	not established anywhere in the file	[assumption A4]
VA Federal Supply Schedule contract price, relative to the self-pay figure above	not established; FSS pricing is typically negotiated below list, and no figure for either exists in this file for this device	[assumption A5]
Addressable share captured across VA and private channels combined, by year 3	a low single-digit percentage, the Generator's own assumption	[claim 12: unconfirmed]
Whether audiologists will dispense a second, cheaper device at all, and whether patients will pay several thousand dollars out of pocket for a non-curative treatment	explicit Generator assumption, flagged as such in the file itself	[claim 17: unconfirmed]
Composite revenue pool implied by the rows above	not computed, in the file or here. Two of the multiplicands that would be needed — the severity/candidacy share in row 2 and the indicated population in row 4 — carry no percentage or count anywhere in the candidate file, only the statement that they are unestablished. Multiplying through the rows that do carry numbers would produce a figure resting on a step that has no number to rest on, which is exactly the fabrication this format exists to prevent	arithmetic that cannot be run over [claim 8: unconfirmed] × [assumption A1] × [claim 10: unconfirmed] × [claim 11: unconfirmed] × [claim 12: unconfirmed]

The two connectors that would ordinarily carry a TAM claim were run against this file's own claims, and both refuse — the verdict is printed here rather than routed around:

python3 -m connectors market "US adults with chronic bothersome tinnitus of moderate or greater severity" → unverifiable — "Market-size claim (...) has no free, authoritative, machine-queryable source. Stays unconfirmed permanently unless a human attaches a licensed report and edits the claim by hand."
python3 -m connectors adoption "VA audiologists would prescribe a cheaper follower bimodal device instead of, or alongside, the incumbent Lenire device" → unverifiable — "Adoption/preference claim (...) asserts what clinicians, payers, or patients would do. No free, authoritative, machine-queryable source answers that ... Do NOT substitute a model's own estimate of stakeholder behaviour: a synthetic stakeholder opinion is a fabricated claim."

The checkable primitives underneath a reimbursement claim were also run, on the two speculative codes the domain dossier already probed (V5299, L8679 — chosen only to exercise the connectors, asserting nothing about either code):

python3 -m connectors hcpcs V5299 → unconfirmed — "No local cache at data/hcpcs_level_ii.csv ... Do not substitute a web search for this file."
python3 -m connectors payment V5299 → unconfirmed — same missing-cache reason, data/hcpcs_payment_rates.csv absent.
python3 -m connectors coverage V5299 → unconfirmed — same missing-cache reason, data/medicare_coverage_policies.csv absent.
python3 -m connectors procedures 92625 → unconfirmed — "No local cache at data/medicare_procedure_volumes.csv" — illustrative only; the natural procedure code for a tinnitus evaluation is CPT, which is unverifiable by AMA licence regardless of cache state, per [claim 7: unconfirmed].

None of these four runs is new information — they reproduce, on this build, exactly the missing-cache and licence-scope findings already on record at [claim 7: unconfirmed]. They are reported here because the department contract requires the connector verdict to appear on the page the money model actually sits on, not only in the candidate's Claims section.

Path to first revenue

First dollar comes from: the file does not establish which of two candidate buyers goes first — a VA facility ordering through this device's own Federal Supply Schedule listing [claim 9: unconfirmed], [claim 22: unconfirmed], [assumption A2], or a private-pay patient through an audiology practice that already dispenses the incumbent and adds this device as a second, cheaper line [claim 24: unconfirmed], [claim 17: unconfirmed].
What must exist first, each attributed:
- 510(k) clearance against the QVN predicate [claim 2: verified] — resting on a step that is itself unconfirmed: that a De Novo grantee's device is actually available as a subsequent 510(k) predicate [claim 3: unconfirmed], and untested against the risk that substituting a trigeminal/cervical electrode for the predicate's tongue electrode is found not substantially equivalent [claim 14: unconfirmed], [claim 15: unconfirmed].
- A remote-fitting and adherence-telemetry system that can safely set stimulation levels without a clinician present [claim 25: unconfirmed], hold the timing precision the bimodal-plasticity mechanism requires [claim 26: unconfirmed], and remain tolerable for daily transcutaneous use across a full treatment cycle [claim 27: unconfirmed].
- Either a VA Federal Supply Schedule listing of the follower's own [assumption A2] or a working billing/self-pay pathway — no CPT or HCPCS code specific to this device class has been identified [claim 7: unconfirmed], and this build's own probes above confirm the connectors cannot check a code that has not been named.
- An FTO position — no patent number appears anywhere in the file and none has been searched [claim 28: unconfirmed], on the rubric's one automatic-kill factor.
Calendar to first dollar: 18-30 months on the 510(k) branch [claim 15: unconfirmed], before adding whatever VA Federal Supply Schedule contracting or private-channel build costs in calendar time on top of it [assumption A2], [assumption A6].
Capital to first dollar: low-single-digit millions rising to mid-eight-figures and 4+ years if the electrode-site change is found not substantially equivalent [claim 15: unconfirmed] — and whether that estimate already includes go-to-market spend (channel build, VA contracting, the telemetry platform) or excludes it is itself unestablished [assumption A3].

Routes

Four, laid out and not ranked. Choosing a commercial strategy is a Tier 3 act — the same class of decision as choosing what to shortlist — so this section presents options and stops.

Route A — Enter the VA channel as a second, cheaper Federal Supply Schedule vendor

The route the candidate's own framing (aimed first at the VA channel) points toward: win a Schedule 65 II A listing distinct from the incumbent's, and sell into a population where tinnitus is the most commonly compensated service-connected disability [claim 8: unconfirmed].

Requires: 510(k) clearance [claim 2: verified], resting on unconfirmed predicate availability [claim 3: unconfirmed]; a Federal Supply Schedule listing of the follower's own [claim 30: unconfirmed], [assumption A2]; and VA audiologists willing to prescribe a second, cheaper device instead of or alongside the incumbent already on contract [claim 41: unconfirmed], [claim 22: unconfirmed], [claim 19: unconfirmed].
Costs: 18-30 months and low-single-digit millions to clearance on the 510(k) branch [claim 15: unconfirmed], plus FSS contracting cost and calendar not established in the file [assumption A2], plus the remote-fitting platform build [assumption A6].
Killed by: VA audiologists defaulting to the incumbent already on contract with a published pivotal trial and an established relationship, and no VA facility adding a second device line — i.e. [claim 41: unconfirmed] resolving false. The file records this as unanswerable by any connector here; only a revealed-behaviour twin (historical VA switching when a lower-cost alternative entered a comparable category) would settle it, and none has been run.

Route B — Sell direct to private audiology practices as a self-pay second device line

Bypass VA entirely: place the device with private-practice audiologists already dispensing tinnitus programmes, priced below the incumbent, billed self-pay.

Requires: 510(k) clearance [claim 2: verified], [claim 3: unconfirmed]; private audiology practices willing to add a second, cheaper device line [claim 24: unconfirmed]; and patients willing to pay several thousand dollars out of pocket for a non-curative treatment [claim 17: unconfirmed], [claim 11: unconfirmed].
Costs: the same clearance cost and calendar as Route A [claim 15: unconfirmed], without VA contracting overhead, but requiring a private-channel sales and marketing build not established anywhere in the file [assumption A6].
Killed by: no CPT or HCPCS code exists specific to this device class [claim 7: unconfirmed] — confirmed again on this build by the connector probes above — and patients decline to self-pay at the assumed price point, i.e. [claim 17: unconfirmed] resolving false. Without a code or a paying patient, there is no first dollar in this route.

Route C — Fall back to the sound-only 874.3400 masker classification

The candidate's own fallback: drop the electrical modality and the therapeutic-relief claim, and clear as a tinnitus masker instead.

Requires: dropping the "relief" indication for a masking indication — 21 CFR 874.3400 is verified to carry a single special control (patient labelling) and an identification that is squarely about masking noise, not treating tinnitus [claim 5: verified]; and accepting that the air-conduction hearing-aid generic type explicitly excludes this category, so it is a distinct, older submission [claim 6: verified].
Costs: not established anywhere in the file — claim 15's capital/calendar estimate prices only the QVN 510(k) route, not this fallback [assumption A7].
Killed by: a masking-only indication removes the device's price justification alongside the incumbent, and the class-level evidence for masking approaches is already unfavourable — a Cochrane review of sound therapy (8 studies, n=590) found no evidence that hearing aids, sound generators or combination devices beat waiting-list control, placebo or education-only, with evidence quality rated low throughout [claim 36: unconfirmed]. If no premium survives the switch to a masking claim, this route has no path to the price in the money model above.

Route D — License the non-intraoral electrode and remote-fitting subsystem to a QVN entrant

Ship the differentiator rather than a competing device: license the transcutaneous trigeminal/cervical electrode plus remote-fitting/telemetry subsystem to the incumbent or to a future QVN entrant, rather than building a full commercial channel.

Requires: an FTO position on the electrode/remote-fitting approach [claim 28: unconfirmed]; evidence that the bimodal-plasticity mechanism transfers off the tongue to a trigeminal/cervical cutaneous site — the file states this is an open scientific question, not an engineering detail [claim 14: unconfirmed], with the closest completed, results-posted evidence being a non-intraoral auditory-somatosensory trial run by a third party, not this candidate [claim 29: unconfirmed]; and a partner willing to carry the module.
Costs: no VA contracting and no private-channel build, but bench validation of the subsystem and regulatory scoping in their place, not established anywhere in the file [assumption A9]; revenue would be a royalty or transfer price rather than a device price, so [assumption A4] and [assumption A5] are replaced rather than answered by [assumption A8].
Killed by: no partner emerges — the incumbent already holds a validated intraoral configuration from its own published pivotal trials [claim 31: unconfirmed], [claim 32: unconfirmed], [claim 33: unconfirmed] and has no obvious commercial reason to license away from a configuration it has already proven works, i.e. [assumption A8] resolving false.

Assumption register

Every assumption cited above, with what would settle it and who could run it. These are written back to the candidate as unverified claims — an assumption that lives only in a business case is invisible to the Verifier.

#	Assumption	Falsifier	Owner
A1	The veteran service-connected tinnitus disability-compensation population (claim 8, 3.2-3.5M) and the clinically-indicated population (claim 10, moderate-or-greater chronic subjective tinnitus) overlap enough that the compensation count can be treated as a meaningful bound on the VA-channel addressable population, rather than two largely uncorrelated counts	A VA clinical dataset or published study cross-tabulating service-connected tinnitus disability rating against a validated tinnitus-severity instrument (THI/TFI) for the same veteran population	Research lane
A2	A follower device (not the incumbent's) can obtain its own VA Federal Supply Schedule 65 II A listing within a cost and calendar a launch budget can absorb, independent of whether VA audiologists would then prescribe it (claim 22 covers the prescribing question; this is the contracting mechanics)	The VA National Acquisition Center's published FSS solicitation requirements (financials, past performance, commercial sales practice disclosure) and the award-to-listing calendar for a comparable Schedule 65 II A award	Regulatory / business development
A3	The Generator's capital and calendar estimate (claim 15: low-single-digit millions, 18-30 months on the 510(k) branch) covers regulatory/clinical activity only and excludes go-to-market spend — VA FSS contracting, private-audiology channel build, and the remote-fitting telemetry platform	A line-item breakdown from the Generator or a regulatory consultant showing what the low-single-digit-million estimate actually covers	Regulatory consultant + Generator
A4	A device price of $2,000-$4,000 (claim 11) yields positive gross margin after cost of goods, remote-fitting platform amortization, and clinical/customer support	A bill-of-materials cost roll-up from a contract manufacturer for the headphone, electrode and telemetry hardware at stated annual volumes, plus an estimate of remote-fitting platform operating cost per patient	Engineering + operations
A5	A VA Federal Supply Schedule contract price for this device would sit meaningfully below the $2,000-$4,000 self-pay range (claim 11), given FSS competitive-pricing requirements, rather than at or above it	The disclosed or FOIA-obtainable FSS unit price for the incumbent Lenire device, or a comparable hearing-related Schedule 65 II A item, compared against its stated self-pay range	Business development
A6	Building and operating a remote-fitting and adherence-telemetry platform reliable enough to substitute for in-clinic fitting is achievable within the same capital and calendar envelope as the regulatory pathway (claim 15), rather than adding materially to it	A technical feasibility and cost estimate from a firmware/software contractor for a telemetry and remote-titration platform meeting the safety profile implied by claims 25-27	Engineering
A7	A sound-only fallback submission under 21 CFR 874.3400 (claim 5) can be cleared and brought to market at materially lower capital and shorter calendar than the QVN 510(k) route (claim 15), rather than at comparable cost	A regulatory consultant's written scoping estimate comparing an 874.3400 masker submission against the 874.3410 QVN submission for cost and calendar, given the special controls each carries (claim 2, claim 5)	Regulatory consultant
A8	A partner already selling or entering the QVN classification would pay a royalty or transfer price for a validated non-intraoral electrode-plus-remote-fitting module large enough to fund this route, rather than building the capability in-house or declining to move away from its own validated tongue-electrode configuration	Structured interviews or a term-sheet negotiation with the incumbent or a prospective QVN entrant on licensing interest and royalty economics for an OEM electrode/telemetry module	Business development / commercial
A9	Bench validation of the non-intraoral electrode/telemetry subsystem and the regulatory scoping to license it into an already-cleared QVN device is achievable at materially smaller capital and calendar than the full clearance-plus-channel routes above	A regulatory consultant's written scoping estimate for module-only bench validation and for whether adding the module to a cleared host device is a letter-to-file, a special 510(k), or a new submission	Regulatory consultant + engineering

Where this case outruns the file

Every figure with no claim behind it, gathered as work items.

The VA-channel and private-channel revenue composites — no figure is computed anywhere in this case because claim 10 (the indicated population) carries no number at all and assumption A1 (the share of the compensation count that is clinically indicated) carries no number either. Two of the model's most load-bearing multiplicands are entirely absent, not merely wide-ranged, which is a step further than the file's other unresolved figures.
The 3.2-3.5M veteran compensation count (claim 8) itself — never independently checked, and no connector in this repo reads VBA/VHA data.
Whether this device could obtain its own VA Federal Supply Schedule listing at all (assumption A2), separate from whether VA audiologists would then choose to prescribe it (claim 22, claim 41).
Gross margin (A4) and FSS contract pricing relative to self-pay pricing (A5) — nothing in the candidate file speaks to either, and together they decide whether any route above produces revenue net of cost or merely gross bookings.
The scope of the Generator's capital/calendar estimate (A3) — whether claim 15 is regulatory-only or already includes the remote-fitting platform, VA contracting and channel build that Routes A, B and D all require.
The sound-only fallback route's own capital and calendar (A7) — the file prices only the QVN route (claim 15); the 874.3400 route it also names has no cost estimate anywhere.
Licensing/royalty economics for a subsystem-licensing route (A8) — no claim anywhere in the file addresses whether a partner would pay for this module rather than build or decline it.
Bench-validation and regulatory-scoping cost for a module-only licensing submission (A9) — the file's only capital/calendar estimate (claim 15) prices a full device clearance, not a subsystem qualification into a device someone else already owns.

Generated from knowledge-base/commercial/idea-006.md by engine/scripts/build_review.py on 2026-09-09. This page is a view — edit the source file and rebuild, never edit here.