SaaS Pricing Model? Plans or charge per user?

In medtech SaaS, “plans or charge per user?” is the wrong starting point. The right starting point is: what is your value metric—the measurable unit that scales with customer value and correlates with your costs. “Per user” is one possible value metric, but hospitals and clinics often experience value at the department or site level (e.g., reduced length of stay, fewer readmissions, faster documentation), not at the individual clinician level.

So the practical answer is: use tiered plans for procurement simplicity, and use per-user pricing only when usage and value truly scale by seat. Many successful digital health products end up with a hybrid: a base platform fee (plan) + a scaling component (users, locations, devices, or volume).

How to decide: pick a value metric that matches clinical reality

A value metric should be (1) easy to understand, (2) hard to game, (3) aligned with outcomes/ROI, and (4) compatible with hospital procurement. Common medtech SaaS value metrics include:

• Per site / per facility (e.g., per hospital, per clinic). Works when value is operational and cross-team.
• Per department / service line (e.g., ED, cardiology). Useful when workflows and budgets are siloed.
• Per provider seat (named users). Works when the product is a daily tool for specific clinicians.
• Per concurrent user (floating seats). Often better than named seats in hospitals with shift work.
• Per patient / per episode (volume-based). Fits remote monitoring, care pathways, and population health.
• Per device (if you integrate with hardware or bedside devices).

Rule of thumb: if your product’s value is created by individual productivity (e.g., a radiologist workflow tool), per-user can work. If value is created by system-level coordination (care team handoffs, discharge planning, quality reporting), per-user pricing often creates friction because the hospital wants broad adoption but hates paying for “extra seats.”

When per-user pricing works (and when it backfires) in hospitals

Per-user works when…

• The buyer and user are the same (common in private practices, less common in hospitals).
• Usage is concentrated in a small group (e.g., 20 coders, 10 research coordinators, 15 sonographers).
• Access control matters (audit trails, role-based permissions) and you can justify seat-based licensing.
• You can quantify time saved per user (e.g., minutes per note, cases per day). This makes ROI narratives easier.

Per-user backfires when…

• Adoption requires “everyone” (nurses, residents, attendings, case managers). Seat pricing becomes a tax on rollout.
• Shift work and turnover are high. Named seats create admin overhead and procurement pushback.
• The hospital wants enterprise access but you’re forcing them into counting heads. Expect discount pressure and stalled deals.

In hospital procurement, friction kills deals. If your champion is a clinician but the contract goes through IT/procurement, they will prefer pricing that’s predictable and easy to approve (often a site license or department license).

Tiered plans: the procurement-friendly default for medtech SaaS

Tiered plans (e.g., Basic/Pro/Enterprise) are less about “features” and more about risk, compliance, and scale. Hospitals buy confidence as much as software. A good tier structure maps to how healthcare organizations mature:

• Starter / Pilot: limited scope, minimal integrations, clear success criteria. Often time-bound (e.g., 90–180 days) with an exit to a full contract.
• Growth: multi-unit rollout, more reporting, stronger admin controls.
• Enterprise: SSO (single sign-on), audit logs, BAAs (Business Associate Agreements) for HIPAA, uptime SLAs (service-level agreements), dedicated support, and EHR integration support.

Important: avoid “feature hostage” pricing for clinical safety or compliance. For example, audit logs and role-based access are often non-negotiable in regulated environments; gating them can slow security review.

A practical hybrid model that fits digital health economics

For many medtech SaaS products, the cleanest approach is:

1. Base platform fee (plan) tied to scope (site/department) so procurement can budget it.
2. Scaling fee tied to a value metric that grows with outcomes (patients/episodes/devices or floating seats).

This reduces the “seat tax” while still letting your revenue scale as the customer expands usage. It also helps you align pricing with reimbursement and operational ROI.

Examples of scaling metrics that tend to be easier to defend than named seats:

• Per monitored patient per month (common in remote patient monitoring and chronic care workflows; reimbursement depends on CPT codes and payer policies, which vary).
• Per episode of care (e.g., post-op pathway enrollment).
• Per device connected (if your costs scale with device management and support).
• Per location (if each clinic adds onboarding and support load).

Be explicit about what’s included: implementation, training, integrations, support hours, and data retention. Hospitals will ask.

Regulatory, reimbursement, and evidence: pricing must match your go-to-market path

Medtech SaaS often sits somewhere on the spectrum from “workflow tool” to “Software as a Medical Device” (SaMD). Your pricing model should anticipate the commercial path you’re on:

• If you’re SaMD, your sales cycle may involve clinical validation, IRB approval for studies, and potentially FDA pathways (e.g., 510(k), De Novo, or PMA depending on risk and claims). That usually pushes you toward annual contracts with clear scope and support, not casual monthly per-seat subscriptions.
• If reimbursement is part of the ROI story, you’ll need to understand how CPT codes (and payer coverage) affect who benefits financially. If the hospital captures the reimbursement, site/department pricing can be easier; if individual clinicians capture it (more common in some practice settings), per-user may fit.
• If procurement is centralized, they’ll want predictability: annual pricing, caps, and clear terms. “Per user” can still work, but expect requests for floating seats, true-ups, and enterprise caps.

A useful sanity check: write down your buyer, user, and economic beneficiary (the person/entity who gets the financial upside). If those are three different stakeholders—as is common in hospitals—pure per-user pricing often creates misalignment.

Common pricing mistakes (and how to avoid them)

• Mistake: copying horizontal SaaS pricing (e.g., $X/user/month) without considering shift work, shared workstations, and enterprise procurement. Fix: offer floating seats or site-based tiers.
• Mistake: pricing by features instead of outcomes. Fix: anchor tiers to scope and risk (sites, departments, integrations, support), then scale with a value metric.
• Mistake: underpricing pilots and getting stuck. Fix: make pilots time-bound with predefined success metrics and a conversion path to an annual contract.
• Mistake: ignoring implementation. Fix: separate a one-time implementation fee (or clearly include it in Year 1) so you don’t lose money on onboarding.

What to do next

1. Define your value metric in one sentence and test it with 5 target customers (ask: “Does this feel fair and predictable?”).
2. Draft 3 tiers (Pilot, Growth, Enterprise) where tiers reflect scope (site/department), integrations, and support—not just features.
3. Choose a scaling lever (patients/episodes/devices or floating seats) and write a simple pricing table you can put in front of procurement.
4. Map buyer/user/beneficiary and adjust pricing so the entity that pays is the entity that wins financially (often the department or hospital).
5. Pressure-test with a mock procurement review: ask what they need for HIPAA/BAA, SSO, audit logs, and contract terms before you finalize pricing.