How has the shift to remote work affected your SaaS pricing strategy?

Remote work changed the “unit of value” you’re pricing

Before remote work, many B2B SaaS products (including clinical workflow tools) could get away with a simple per-seat model: one user, one license, billed monthly or annually. Remote work disrupted that because the way value is created became more distributed and less tied to a single person logging into a single workstation.

In medtech SaaS, the shift is even sharper because your “customer” is often a complex system: clinicians, care coordinators, coders, IT/security, and sometimes patients. Remote and hybrid work increased cross-site collaboration, asynchronous handoffs, and multi-location access. That pushes pricing toward metrics that match outcomes and operational load, not just headcount.

Common “units of value” that became more relevant post-remote:

• Per site / per facility (e.g., per hospital, per clinic location) when remote teams still operate under site-based budgets and procurement.
• Per clinician type (e.g., attending vs resident vs nurse) when usage intensity differs and you need fairness.
• Per patient / per episode / per enrolled member for remote monitoring, care management, and digital therapeutics-style workflows.
• Per study / per protocol for research/IRB-driven tools where work clusters around trials rather than people.
• Usage-based (e.g., messages, scans processed, AI inferences) when compute cost and value scale with volume.

Pricing strategy takeaway: remote work didn’t just change where people work; it changed what your product is “for” in the buyer’s mind—coordination, continuity, and compliance across locations.

Packaging moved from “one plan fits all” to role- and workflow-based tiers

Remote work increased the number of stakeholders who need access. If you keep a strict per-seat model, you’ll trigger internal friction: “Do we really need to pay for the care coordinator?” “Can IT have a login?” “What about the on-call physician?” That friction slows adoption and increases churn risk.

Medtech SaaS companies have responded by changing packaging (what’s included in each plan) more than changing list price. Packaging is often the fastest lever because it lets you align access with value while keeping procurement simple.

Three packaging patterns that work well in medtech

1. Core + add-ons: A base platform fee (often per site) plus add-ons for modules like eConsent, device integration, analytics, or patient messaging.
2. Role bundles: Include a set number of “clinical seats” plus unlimited “read-only” or “admin” users. This matches real remote workflows where many stakeholders need visibility but not full functionality.
3. Workflow tiers: Tier by capability (e.g., documentation only → documentation + billing support → documentation + billing + quality reporting). This maps to outcomes and makes ROI easier to defend.

Define terms the first time you use them internally: packaging is what’s in the box; pricing is what the box costs. Remote work tends to force packaging changes first.

Security, compliance, and IT review became a bigger part of the price story

Remote access expanded the attack surface. Hospitals and health systems responded with stricter vendor security reviews (SOC 2, penetration testing, SSO/SAML, audit logs, least-privilege access). Even if your product is “just software,” remote work made security features feel like core value rather than “enterprise nice-to-haves.”

This affects pricing strategy in two ways:

• Enterprise tier justification: You can credibly reserve SSO, advanced audit logs, data retention controls, and dedicated environments for higher tiers because they carry real cost (implementation, support, compliance overhead).
• Procurement acceleration: If you bundle the security/compliance requirements into an enterprise package, you reduce custom contracting. That matters because hospital procurement cycles are long and remote work increased vendor volume.

Medtech nuance: if your SaaS is part of a regulated workflow (e.g., clinical decision support, diagnostic support, or software that could be considered SaMD), your regulatory pathway (FDA 510(k), De Novo, or PMA) and quality system expectations can influence how you package claims, support, and change management. Don’t price “FDA clearance” as a line item; instead, price the operational value and include the compliance-grade features that make deployment feasible.

Remote care increased ROI scrutiny: tie pricing to reimbursement and operational metrics

Remote work and telehealth normalized distributed care, but it also increased CFO scrutiny. Buyers ask: “Does this reduce time, increase throughput, reduce denials, or support reimbursable services?” Your pricing strategy should make that ROI legible.

Two common medtech SaaS motions:

• Operational efficiency (e.g., documentation automation, triage, scheduling optimization): price against time saved and throughput. A hybrid model (platform fee + usage) often matches value and cost.
• Revenue enablement (e.g., RPM/CCM workflow support): price against the ability to capture reimbursable services. Here you must be careful: you can reference that workflows may support billing, but reimbursement depends on payer policy, documentation, and coding practices (CPT codes vary by use case and jurisdiction).

Practical approach: build a simple ROI narrative that procurement can repeat. Example structure:

• Metric: minutes saved per encounter, reduction in no-shows, fewer claim denials, faster prior auth turnaround.
• Translate: minutes → FTE capacity; denials → recovered revenue; turnaround → patient access.
• Anchor: price as a fraction of the expected annual benefit (varies by category and customer).

If your product touches clinical research, remote work also increased decentralized trial activity. That can shift pricing toward per-study/per-site models and may require clearer boundaries around IRB approvals, data use, and who is the “sponsor” vs “site” buyer.

Contracts shifted: more flexibility, but clearer guardrails

Remote work increased uncertainty (staffing changes, fluctuating volumes, new sites). Customers pushed for flexibility: shorter terms, ramp clauses, and the ability to reassign licenses. Vendors responded with pricing strategies that preserve revenue predictability while reducing buyer fear.

Contract and billing moves that became more common

• Annual commit with quarterly true-ups: customer commits to a baseline; usage or seats reconcile quarterly. This is a middle ground between pure usage and pure subscription.
• Ramp pricing: lower price in months 1–3 while implementation happens, then step up. This aligns with real deployment timelines (security review, integration, training).
• Site expansion clauses: pre-negotiated pricing for additional clinics/hospitals to avoid re-procurement friction.
• Implementation fees: more acceptable when remote deployments require integrations (EHR interfaces, device connectivity) and security work. Keep the scope crisp to avoid “services company” creep.

In hospital procurement, simplicity wins. A pricing model that’s theoretically perfect but hard to explain will lose to a slightly less optimal model that legal, IT, and finance can approve quickly.

What to do next

1. Pick one primary value metric (seat, site, patient, study, or usage) and one secondary metric for edge cases; write a one-paragraph rationale procurement can repeat.
2. Redesign packaging so remote stakeholders can participate: include read-only/admin access and reserve security features (SSO/audit logs) for an enterprise tier.
3. Create a 1-page ROI calculator tied to operational metrics (time, throughput, denials). Keep assumptions editable and avoid claiming guaranteed reimbursement.
4. Standardize contract options: annual commit + true-ups, ramp pricing, and a clear implementation scope to reduce custom negotiations.
5. Pressure-test with 5 buyer interviews (clinical lead, IT/security, finance, ops, and procurement) to ensure your pricing matches how budgets are actually allocated.