Part of The Revenue Model Sets the Strategy
SaaS Platform Licensing
The model closest to traditional B2B SaaS, with healthcare complexity layered on top.
01
How it works
The digital health company sells software platform access on a subscription basis to healthcare organizations, health systems, or payers. This is the model that most resembles traditional B2B SaaS, which is why it is the one most often managed as though it were.
Two licensing structures cover most contracts: per-seat licensing (one seat per named clinician or care manager) and entity-based licensing (flat annual fee for enterprise access). Module-based pricing layers on either one, pairing a base platform with add-on capabilities that enable land-and-expand over time.
Payment is typically annual or multi-year, with implementation and onboarding fees charged separately. Auto-renewal clauses are common. The revenue is predictable and recurring, but vulnerable to the same forces that drive SaaS churn anywhere: low adoption, competing priorities, and failure to demonstrate ROI. What makes healthcare different is the depth of implementation complexity and the number of stakeholders who must see value simultaneously.
02
Why the Engagement Gate matters here
The Engagement Gate is the threshold a program has to cross before it produces value for anyone: enough of the intended users doing enough of the intended behavior, for long enough to count. What varies by model is how long a closed gate can stay invisible, and here that runs roughly twelve months, since revenue arrives on the annual invoice whether or not anyone logs in and the gate governs the renewal rather than the current period. The Engagement Gate page carries the full treatment.
In SaaS licensing, the "end user" is typically a clinician, care manager, or operational staff member rather than a patient. But the Engagement Gate still applies. If care managers don't adopt the platform as their primary workflow tool, the organization is paying for shelf-ware. If providers find the system adds friction rather than reducing it, they'll revert to spreadsheets and homegrown tools. And in B2B2C configurations where the platform has a patient-facing component, the patient engagement challenge from the CPT / RPM and PMPM / PEPM models layers on top of the clinical adoption challenge.
The unique difficulty in healthcare SaaS is that implementation timelines are significantly longer than traditional SaaS. EHR integration can take months. Compliance reviews add weeks. Clinical workflow configuration requires change management that most healthcare organizations struggle with. Every additional click, every separate login, every workflow disruption is a reason to stop using the platform.
- CPT / RPMNear immediate
- SaaS Platform LicensingRoughly 12 months
- Value-Based / Outcomes-Based18 to 24 months
- PMPM / PEPM24 to 36 months
The lag puts this model closer to PMPM than to RPM, with one difference: SaaS erosion is gradual rather than binary. Adoption doesn't collapse, it drifts, and the drift is invisible on any financial report until procurement runs its numbers. This is the framework's core argument in its plainest form. The same shallow use that is visible in the RPM engagement numbers within a month takes a year to surface here, and nothing about the product or the population accounts for the difference. The payment structure does.
03
What counts as an active user
Adoption is the primary health metric in this model, and it's the metric most vulnerable to an undefined denominator. Weekly active users as a share of what? The population the contract covers, or the clinicians whose daily workflow the platform was actually bought to change.
Those are two different numbers and the gap between them is often large. Organizations buy seats in round lots, provision them to everyone who might plausibly need access, and end up with a covered population well above the clinical population the platform was designed for. Call the first rate contracted adoption and the second intended-user adoption. The same weekly active user count produces a poor contracted adoption figure and a strong intended-user adoption figure. Both are defensible and they support opposite conclusions at renewal.
Contracted adoption
35 active of 100 licensed seatsWhat the buyer's finance team divides by.
Intended-user adoption
35 active of 50 intended usersWhat the platform was bought to change.
Which makes this a contracting question rather than a reporting one. If the license is priced per seat, the seat count is what the buyer is paying against, and it becomes the denominator whether or not anyone agreed to that. Under entity-based licensing the contract names no population at all, which means someone supplies one at renewal, and it will be the largest plausible number. A CS team reporting intended-user adoption while the buyer's finance team divides by the invoice is not going to have a pleasant renewal conversation.
The practical move is to name both populations during implementation, report both rates from the first business review onward, and treat a widening gap between them as its own signal. Seats provisioned far beyond the users who need them is a right-sizing conversation worth having early, when it reads as good stewardship, rather than at renewal when it reads as a discount request.
The gap also governs expansion. A buyer doesn't add a care gap module to a platform their care managers are using at a third of the seats they paid for, which makes contracted adoption the expansion pipeline rather than only a retention metric. A CS team treating it as a retention number is reading its own growth forecast without knowing it.
That is denominator discipline applied to a contractual denominator rather than an analytical one.
04
Stakeholder value drivers and KPIs
Five stakeholders sit inside a typical account. Renewal turns most directly on two of them: the clinical end users, whose adoption is the whole asset, and the executive sponsor, who holds the budget and usually hasn't been in the room.
| Stakeholder | What they care about | Value drivers | KPIs |
|---|---|---|---|
| Executive sponsor (CMIO, VP Population Health, VP Care Management) | Strategic ROI, organizational impact, internal credibility | Demonstrable impact on quality measures, cost per patient, or care manager productivity; contracted adoption; executive-ready impact narrative | ROI (quantified value vs. annual investment); contracted adoption (weekly active users / covered population); feature utilization breadth; contract expansion |
| IT / integration lead | Technical success, security compliance, minimal ongoing burden | Seamless EHR integration; SSO authentication; HIPAA/HITRUST certification; minimal maintenance post-launch | EHR integration uptime; data sync accuracy; security audit pass rate; monthly IT maintenance hours |
| Clinical end users (care managers, RNs, MDs) | Workflow efficiency, ease of use, time savings | Reduced administrative burden; intuitive interface; clinically relevant functionality | Weekly active users; intended-user adoption; time saved per patient encounter; user satisfaction scores; training completion rate |
| Compliance / privacy officer | Regulatory compliance, risk mitigation, audit readiness | Complete BAA and audit trail; appropriate access controls; vendor security certifications current | Security incidents (target: zero); audit findings; access control review compliance |
| CS team (internal) | Logo retention, ARR growth, adoption health | Strong contracted and intended-user adoption; multi-threaded stakeholder relationships; efficient onboarding | Logo retention rate; NRR; time to go-live; contracted adoption; intended-user adoption; expansion pipeline |
05
How the buyer's payment environment shifts the value story
SaaS licensing can sit on either side depending on what the platform enables. A care management platform that improves operational efficiency is reducing costs through productivity gains. A platform that enables new billable services is generating revenue the organization couldn't capture before. Which orientation applies is an account-level question, since the ROI calculation and the stakeholders who control renewal authority differ in each case.
Under capitation or shared savings
The platform must prove it reduces downstream healthcare costs, not just improves operational efficiency. Risk stratification capabilities, care gap closure tracking, and population health analytics become the features that drive renewal. The QBR conversation centers on total cost of care for managed patients and quality measure performance, not just platform usage metrics. Care manager productivity (patients managed per care manager with the platform vs. without) becomes a critical efficiency metric because it directly affects the organization's cost structure.
Under fee-for-service
The platform's job is simpler: does it help clinicians work more efficiently and does it support billable activities? If the platform enables care management billing (CCM, TCM codes), the ROI case includes revenue generated through the platform, not just cost savings. EHR integration depth matters enormously here because providers won't toggle between systems when they're already documentation-heavy.
A note on pharma as buyer
Pharmaceutical companies buy SaaS platforms too, and when they do the stakeholder map changes completely. Medical affairs, brand teams, and market access replace the health system roles above, and the platform becomes a drug companion measured through adherence and real-world evidence rather than operational efficiency. The Engagement Gate still governs whether any of that materializes. See the Pharma Lens for the full treatment.
06
A common failure pattern
The most common CS failure in healthcare SaaS is not a dramatic account loss. It's a slow erosion of adoption that becomes visible only at renewal. A platform launches successfully after a six-month implementation. Training sessions are completed. Early usage looks promising. But three months later, weekly active users sit at 35% of licensed seats (contracted adoption). Care managers have reverted to their old spreadsheets because the EHR integration requires them to copy and paste data between systems. The operational lead is satisfied because the few active users like the platform. But the executive sponsor hasn't been engaged in nine months and has no visibility into the platform's impact. When renewal approaches, procurement runs a cost-cutting exercise and the contract is reduced by 40%.
Two things sit underneath it: insufficient EHR integration depth creating workflow friction, and CS over-investing in the operational relationship while under-investing in the executive sponsor relationship. The platform worked for the people who used it. But not enough people used it, and the person who controlled the budget didn't know the value it delivered.
The fix requires catching the erosion early enough to reverse it. The practical move is to set the threshold on contracted adoption, since the covered population is what the invoice is written against, and to fix both that threshold and the month it gets measured during implementation, so a figure below it reads as structural rather than as a usage dip. It calls for a different response than another training session.
The executive sponsor cadence runs as a separate track from the operational relationship, focused not on platform features but on the strategic metrics they care about: cost per patient, quality measure movement, care manager capacity.
The third piece is a usage-to-value bridge that translates platform activity into the language the budget holder uses. "35% weekly active users" means nothing to a CFO, and to CS it means one thing as contracted adoption and another as intended-user adoption. "Care managers using the platform are closing 40% more care gaps per week than those who aren't" gives the budget holder a reason to protect the contract.
07
Where to go next
The Engagement Gate page carries the denominator argument this page applies to a contractual denominator, along with the lag comparison across all five models and the rules for reporting an engagement rate honestly. The other four model pages follow the same shape as this one: how the model works, how the buyer's payment environment shifts the value story, the stakeholder value drivers, and an example drawn from practice. The hybrid page maps contract structures instead, since a hybrid inherits its stakeholders from the models it combines.
The three buyer lens pages come at it from the other direction, covering how pharma, health plans, and employers each define value and what each one accepts as proof.
Take the working structures with you
The Field Kit pulls the framework's durable layer out into structures built for use rather than reading: the identify-your-model diagnostic, blank stakeholder and KPI worksheets, the tiered QBR builder, the hybrid trade-off script, the believable-proof checklist, and the seven-step guide to putting the framework to work on a live account. Version-stamped, designed to print, and free to subscribers, who get it first when it ships. Billing-code specifics stay on this site by design, so the kit stays accurate as the rules change.
Your email delivers the kit when it ships, plus occasional new insights from Digital Health Success. No spam. Unsubscribe anytime.