How does startup generate revenue?

Revenue 101: what “generate revenue” actually means

Revenue is the money your startup collects from customers in exchange for value. That sounds obvious, but founders in medtech often confuse revenue with:

• Funding (VC, grants): cash you raise, not earned income.
• Bookings: signed contracts or purchase orders that may pay later.
• Reimbursement: money paid by insurers/government, often after clinical use and coding.
• Profit: revenue minus costs (manufacturing, clinical studies, sales, support, etc.).

A startup “generates revenue” when it has a repeatable way to get paid. In business terms, that repeatability is your business model (how you make money) and your go-to-market (how you reach and close buyers). In medtech, those are constrained by regulation (FDA) and payment (reimbursement), plus hospital procurement.

The core revenue models (and how they map to medtech)

Most startups use one primary model and one secondary model. Here are the common ones, with medtech-specific notes.

1) One-time product sales (capital equipment or disposable devices)

You sell a device for a price, get paid once per unit. In hospitals this often splits into:

• Capital equipment: larger upfront purchase (e.g., imaging accessory, monitoring hardware). Often requires value analysis committee review and a long procurement cycle.
• Consumables/disposables: per-procedure or per-patient items (e.g., single-use components). Often easier to tie to clinical workflow and utilization.

Medtech reality: capital sales can be slow but sticky; consumables can create recurring revenue if you drive procedure volume. Many device companies aim for a “razor/razorblade” mix: lower-friction capital placement plus recurring disposable revenue.

2) Subscription (SaaS) for digital health

You charge monthly/annual fees for software (e.g., clinical decision support, remote monitoring dashboards, workflow tools). Pricing is commonly per provider, per site, per bed, or per covered life.

Medtech reality: if your software influences diagnosis or treatment, it may be regulated as Software as a Medical Device (SaMD). Your FDA pathway (often 510(k) or De Novo; sometimes enforcement discretion depending on claims) affects timelines and what you can promise in marketing. Hospitals also expect security reviews (SOC 2, HIPAA, pen tests) and integration work (EHR).

3) Usage-based pricing (per test, per scan, per patient, per API call)

You charge based on measurable usage. This fits diagnostics, AI inference, and monitoring where value scales with volume.

Medtech reality: usage-based pricing aligns well with clinical throughput, but procurement may still want predictable budgets. You may need minimum commitments or tiered pricing.

4) Reimbursement-driven revenue (CPT/HCPCS, DRG, payer contracts)

Instead of (or in addition to) selling directly to a hospital, you get paid because the clinical service is reimbursed. This is common in diagnostics, remote patient monitoring, and procedure-enabling devices.

Key jargon, decoded:

• CPT codes: billing codes used for physician and outpatient services.
• HCPCS codes: codes often used for devices, supplies, and some services.
• DRG: inpatient payment bundles; hospitals get a fixed amount for a case type.

Medtech reality: reimbursement is not automatic. You need a credible path: existing codes you can bill under, or a strategy to obtain new/expanded coding and coverage. Even with coding, you still need coverage (payer agrees it’s medically necessary) and payment (rate is adequate). This is why many medtech startups fail commercially despite strong clinical interest.

5) Licensing and royalties (IP, algorithms, biomarkers, designs)

You license your technology to a larger company and receive upfront payments, milestones, and/or royalties on sales.

Medtech reality: licensing can be attractive when regulatory and sales execution are heavy lifts. But your leverage depends on strong IP, clear clinical utility, and evidence. If you’re early, expect partners to push risk back onto you (e.g., “come back after FDA clearance” or after a clinical study).

6) Services (implementation, clinical programs, data labeling, trials)

You charge for professional services: integration, training, protocol development, analytics, or running a clinical program.

Medtech reality: services can fund early operations and deepen customer relationships, but they don’t scale like product revenue. Investors often discount services-heavy revenue because it requires headcount growth to grow sales.

Who pays in medtech: buyer ≠ user ≠ beneficiary

In consumer apps, the user often pays. In medtech, the “customer” can be one of several parties:

• Hospital/health system (procurement + value analysis): cares about total cost, outcomes, workflow, and risk.
• Clinician group: may influence purchase but rarely controls budget.
• Payer: pays claims; cares about cost offsets and evidence.
• Employer: may buy digital health benefits; cares about utilization and productivity.
• Patient: sometimes pays cash (self-pay), but price sensitivity is high.
• Strategic partner (device/pharma): may pay via licensing or distribution.

This “multi-stakeholder” setup is why your revenue model must match your economic buyer (the person/entity with budget authority). A common trap is building for clinicians (users) but pricing as if clinicians are the buyer, when procurement or payers actually decide.

How regulation and evidence shape revenue timing

In medtech, revenue is gated by what you’re allowed to claim and sell.

• 510(k): if you can show substantial equivalence to a predicate device, you may reach market faster than novel pathways (timelines vary). Revenue often starts after clearance, though some companies generate limited non-clinical revenue earlier (e.g., research-use-only tools) if appropriately positioned.
• De Novo: for novel, low-to-moderate risk devices without a predicate. Often requires stronger evidence and can delay revenue, but can create a new device classification that later competitors use.
• PMA: for higher-risk devices; typically requires robust clinical evidence and longer timelines. Revenue is later but can be defensible if outcomes are strong.

Evidence also affects reimbursement and procurement. Hospitals may ask for peer-reviewed studies, health economic outcomes, or real-world evidence. If your product changes standard of care, expect to need IRB-approved studies (or at least structured evaluations) to convince committees and payers.

Picking the right revenue model: a practical checklist

Use this checklist to choose a model that can actually close in the real world:

1. Define the clinical job and measurable outcome: e.g., reduce readmissions, shorten length of stay, improve diagnostic yield, reduce complications.
2. Name the economic buyer: procurement, department chair, CFO, payer medical director, employer benefits lead.
3. Map the money flow: who pays today, under what code/budget line, and what must change for you to get paid.
4. Decide your pricing unit: per device, per procedure, per patient per month, per site, per clinician, per test.
5. Align incentives: if the hospital pays but the payer saves, you need a shared-savings story or payer contracting strategy.
6. Plan for procurement friction: security review, EHR integration, value analysis, contracting. Build these costs into pricing.
7. Validate willingness-to-pay early: get letters of intent, pilot agreements with pricing language, or distributor feedback—before you overbuild.

A useful rule: if your model requires a hospital to change behavior but doesn’t clearly improve their margin (or reduce risk), expect slow adoption unless reimbursement is strong and obvious.

What to do next

1. Write a one-page “who pays” map for your product: user, buyer, beneficiary, and the budget or code that funds it.
2. Run 10 pricing interviews with the economic buyer (not just clinicians) and test 2–3 pricing units (per procedure vs per site vs subscription).
3. Draft your regulatory + claims plan (510(k), De Novo, or PMA) and list what you can legally market at each stage.
4. Build a reimbursement hypothesis: existing CPT/HCPCS/DRG alignment or a path to new coverage; document what evidence is missing.
5. Pressure-test your model with a structured teardown using /roast or compare against incumbents via /Competitor_study.