How to price saas products?

Start with the reality of medtech SaaS pricing

Pricing SaaS is never just “pick a number.” In medtech, your price has to survive three extra filters: clinical risk, hospital procurement, and reimbursement economics. Even if your buyer loves the product, the deal can die if your packaging doesn’t fit how hospitals budget (department vs enterprise), how security reviews work, or how value is measured (time saved, avoided adverse events, throughput).

So the goal is not “the perfect price.” The goal is a pricing model (how you charge) and price points (how much) that are:

• Easy to understand for clinicians and administrators
• Easy to approve in procurement (clear scope, clear terms)
• Aligned with value (your price grows when customer value grows)
• Compatible with regulation (FDA pathway and claims) and evidence (IRB/clinical validation when needed)

Pick a value metric that matches how value is created

A value metric is the unit you charge on (per clinician, per site, per study, per patient, per device, etc.). The best value metrics scale with outcomes your customer cares about and can measure without heroic accounting.

Common medtech SaaS value metrics (and when they work)

• Per provider seat (named user): Works for workflow tools used daily by clinicians (e.g., documentation support, triage dashboards). Risk: hospitals hate paying for “unused seats.”
• Per facility / per site: Works when the tool is shared infrastructure (e.g., imaging QA, device fleet dashboards). Procurement-friendly; good for enterprise expansion.
• Per study / per trial / per IRB protocol: Works for research platforms and clinical trial operations. Aligns with grant or study budgets; easier to justify as a project cost.
• Per patient monitored / per episode: Works for remote monitoring and care management. Strong value alignment, but you must define “patient” precisely (active vs enrolled vs billed month).
• Per device connected: Works for connected med devices and fleet management. Clean metric if you can reliably count devices and the customer agrees the device list is accurate.
• Usage-based (API calls, messages, storage): Works for developer platforms; often disliked by hospitals because it’s unpredictable. If you use it, cap it or bundle it.

Rule of thumb: if your champion can’t explain the metric in one sentence to procurement, it’s too complex.

Build tiers that map to procurement and risk

In SaaS, tiers are your “menu.” In medtech, tiers also communicate risk posture and implementation burden. A typical structure is 3 tiers plus optional add-ons.

A practical tier template for medtech SaaS

• Starter (department pilot): Limited sites, limited integrations, standard support. Goal: get live fast and prove value.
• Professional (multi-department): Adds SSO, audit logs, role-based access control, more reporting, and a defined SLA (service-level agreement: uptime/support commitments).
• Enterprise (health system): Adds enterprise security package, dedicated CSM (customer success manager), custom BAAs (Business Associate Agreement for HIPAA), advanced admin controls, and integration support.

Add-ons (priced separately) often work better than bloating tiers:

• EHR integration (Epic/Cerner workflows, HL7/FHIR interfaces)
• Advanced analytics (quality dashboards, benchmarking)
• Implementation services (training, workflow mapping)
• Regulated module if part of the product is medical device software

Important: if your product could be considered Software as a Medical Device (SaMD), your claims and intended use matter. FDA pathways (510(k), De Novo, PMA) affect sales cycles and what you can promise. Don’t price as if you can guarantee clinical outcomes if you can’t legally market that claim.

Anchor price to ROI, not competitors

Competitor pricing is a reference, not a strategy. In medtech, the strongest pricing conversations are framed around economic value and budget ownership.

Do a simple ROI model your buyer can defend

Use a one-page model with conservative assumptions. Examples of value buckets:

• Time savings: minutes saved per case × cases per month × loaded labor rate (varies by role and institution)
• Throughput: additional cases enabled (if capacity constrained) × contribution margin (varies)
• Risk reduction: fewer adverse events, fewer readmissions, fewer missed follow-ups (harder to quantify; be careful with claims)
• Compliance: reduced audit effort, improved documentation completeness

Then choose a pricing posture:

• Value-based pricing: price as a fraction of expected value created (common in enterprise SaaS). You’re not “taking all the value,” you’re sharing it.
• Cost-plus pricing: price = your costs + margin. Simple, but often underprices high-value products.
• Penetration pricing: start lower to win logos, then expand. Risk: you anchor too low and can’t raise later.

In hospitals, your buyer may be clinical leadership, but the budget might sit in IT, operations, quality, or a service line. Your ROI model should clearly state who benefits and who pays—misalignment here is a common reason deals stall.

Validate pricing with pilots, not surveys

Asking “What would you pay?” yields polite fiction. Instead, run pricing tests tied to real procurement behavior.

Four validation methods that work in medtech

1. Paid pilot with a conversion clause: A 60–90 day pilot with a defined success metric and a pre-negotiated conversion price if metrics are met. This reduces negotiation later.
2. Good/Better/Best choice test: Present three packages and ask which they would buy today given constraints (integration, security, support). Watch what they trade off.
3. Budget-owner interview: Talk to procurement/finance/IT security early. Your clinician champion may not know the approval thresholds.
4. Procurement “paper test”: Ask for their vendor onboarding checklist (security, BAA, SOC 2 expectations vary). If your package can’t pass, your price is irrelevant.

If your product touches patient data, expect HIPAA and security reviews. If it supports clinical decisions, expect deeper scrutiny and potentially IRB involvement for studies. These factors lengthen sales cycles—so your pricing must support longer time-to-cash (e.g., annual contracts, implementation fees, or milestone-based payments).

Medtech-specific pricing traps to avoid

• Charging per “feature”: Buyers don’t budget for features; they budget for outcomes and operational needs. Use tiers and add-ons instead.
• Ignoring reimbursement: If your value story depends on billing, understand whether CPT codes exist, whether reimbursement is realistic, and who captures it (hospital vs physician group). If reimbursement is uncertain, price around operational ROI first.
• Underpricing enterprise requirements: SSO, audit logs, access controls, uptime commitments, and support are real costs. Don’t give them away in “Starter.”
• Free pilots with no exit: Free pilots often become unpaid production. If you must do free, time-box it tightly and define success criteria and next-step pricing in writing.
• Misaligned metric: If you charge per seat but value is per patient monitored, you’ll fight churn and discounting forever.

What to do next

1. Choose one primary value metric (per site, per patient monitored, per study, etc.) and write a one-sentence definition that procurement can’t misinterpret.
2. Draft a 3-tier packaging sheet (Starter/Pro/Enterprise) plus 2–3 add-ons (EHR integration, advanced analytics, implementation).
3. Build a one-page ROI calculator with conservative assumptions and a clear “who benefits vs who pays” section.
4. Run 5–10 pricing conversations using a Good/Better/Best choice test with actual budget owners, not just clinical champions.
5. Set up a paid pilot template with success metrics and a pre-negotiated conversion price to reduce post-pilot renegotiation.

If you want a structured teardown of your current pricing page or packaging, use /roast or compare your positioning against alternatives with /Competitor_study.