The Framework
The Revenue Model Sets the Strategy
A Customer Success Framework for B2B2C Digital Health
Five revenue models. Three lenses. One Engagement Gate.
A practitioner-built reference for understanding how value is created, measured, and paid for in B2B2C digital health.
The argument
What the framework claims
Four claims. Everything else on this page either supports one of them or maps what follows from them.
A playbook built for one model misleads in another.
How the payment works, on the vendor's side and the buyer's, determines which stakeholders hold power, which metrics predict renewal, and where the account will fail.
No stakeholder sees value until the end user engages.
The Engagement Gate is the threshold every model has to cross before its value story starts.
The same product can generate revenue or reduce costs.
Which one depends on the buyer's payment environment rather than on the product.
An account has three customers, not one.
A buyer measuring return, a provider or program operator measuring clinical and operational results, and an end user who never asked for the product. Each defines value differently, and the contract unravels at the weakest link.
The Engagement Gate
The Engagement Gate is a sequence, not a door
Underneath it sit six positions a person can occupy:
- eligible,
- reached,
- activated,
- adherent,
- outcomes visible,
- and value realized.
The diagnostic work is locating where the drop happens, because activation work gets blamed for a gap further down the sequence.
The map
Five ways digital health gets paid
Each model has its own deep dive covering the mechanics, how the buyer's payment environment shifts the story, and an example drawn from practice. Models 1 through 4 also map the stakeholder value drivers; the hybrid page maps contract structures instead.
01
CPT Code / RPM Reimbursement
Revenue flows through CPT billing codes tied to remote patient monitoring. Engagement converts to revenue nearly instantaneously, and the 2026 code changes have decoupled billing health from clinical value on the device side.
02
PMPM / PEPM
A recurring flat fee per eligible member or employee, independent of usage. Predictable revenue with a hidden trap: the invoice arrives whether or not anyone engages, right up until the renewal that does not.
Read about the enrollment-based variant and what to settle before you sign
03
SaaS Platform Licensing
The model closest to traditional B2B SaaS, with healthcare complexity layered on top: longer implementations, EHR integration, and clinicians as the end users whose workflow adoption is the gate.
Read about contracted versus intended-user adoption and the slow-erosion failure pattern
04
Value-Based / Outcomes-Based Contracts
Revenue contingent on proven outcomes. The highest-stakes model, with no revenue floor in its purest forms, and the one that asks the CS function to carry outcome science as a capability rather than a job title.
Read about the risk adjustment trap, the staffing answer, and the measurement credibility problem
05
Hybrid Models
Most real contracts combine two or more models. Different revenue streams in the same contract can pull CS in opposite directions, which makes the trade-off conversation with the buyer a defining CS skill, along with the judgment about when that conversation is safe to have.
Read about four common structures, the trade-off script, and when not to have that conversation
The five models at a glance
Value orientation is whether the buyer is generating revenue or reducing costs. A mandate can sit on top of it, since quality, compliance, and evidence requirements are often what makes the purchase happen, and each of them still pays off through one of the two.
| Revenue Model | Primary Stakeholder | Value Orientation | Engagement Gate Type | Engagement-to-Revenue Lag | Lead KPI |
|---|---|---|---|---|---|
| CPT / RPM Reimbursement | Clinic Administrator / Practice Manager | Generating revenue (FFS); Reducing costs, plus Star Ratings bonus revenue (capitated) | Patient device usage plus provider billing compliance | Near immediate, visible monthly | Revenue per enrolled patient; avg. device days per patient |
| PMPM / PEPM | Health Plan Executive Sponsor; or Employer HR/Benefits Leader (day-to-day) and CFO (budget authority) | Reducing costs (cost avoidance, quality improvement), plus Star Ratings bonus revenue for MA plans | Member/employee activation and sustained engagement | 24 to 36 months, surfacing at renewal | Member engagement rate (active users / eligible population); total cost of care per engaged member vs. control |
| SaaS Platform Licensing | Executive Sponsor (CMIO, VP Care Management) | Reducing costs (efficiency) or Generating revenue (enabling billable services) | Clinical workflow adoption and change management | Roughly 12 months, surfacing at renewal | Contracted adoption (weekly active users / covered population); ROI vs. investment |
| Value-Based / Outcomes-Based | Health Plan CFO / Actuary | Reducing costs (proven, not assumed), plus Star Ratings bonus revenue for MA plans | Enrollment volume sufficient to validate the result plus sustained engagement | 18 to 24 months, surfacing at the measurement period | Performance payment realization (% of at-risk revenue earned); clinical goal achievement rate (% of engaged members meeting targets) |
| Hybrid | Varies by dominant revenue stream | Often both simultaneously | Shifts as contract phases evolve | Varies by stream | Depends on phase: activation metrics early, outcome/retention metrics later |
The contract
Which model a contract actually runs
A CS leader knows the company's dominant model. The account in front of them is a different question. Most companies run one dominant model with elements of others, and the mix shows up contract by contract, which is where the answers below start to conflict. Four questions are enough to work out which model a contract runs.
- How does the company get paid?
- Who has to change behavior for value to materialize?
- Is the buyer generating revenue or reducing costs?
- How short is the path from engagement to revenue impact?
Conflicting answers mean a hybrid, which at the contract level is the common case rather than the exception. Read Hybrid Models
The working structures, the ones built for use rather than reading, are in the Field Kit below.
The findings
What falls out of taking the revenue model seriously
Five things that are not obvious until the revenue model is the starting point.
01
The lag is the diagnostic.
- CPT / RPMNear immediate
- SaaS Platform LicensingRoughly 12 months
- Value-Based / Outcomes-Based18 to 24 months
- PMPM / PEPM24 to 36 months
The distance between an engagement event and the revenue signal it produces runs from near immediate under RPM to two or three years under PMPM. That distance is how much runway a team has to course correct, and it is why the leading indicators in long-lag accounts have to be engagement metrics rather than financial ones.
02
A rate is two claims, and both are choices.
of 5,000 enrolled
The people stay the same. Only the denominator changes. Each dot represents 100 people.
Any activation figure is meaningless without a named denominator, and any retention figure is meaningless without a named numerator. The same program can report engagement rates that differ several times over depending on whether the eligible population, the members reached, or the members enrolled sits under the line, and buyer and vendor frequently hold different definitions without either realizing it.
03
The same product changes orientation with the buyer.
One remote patient monitoring program
The buyer's payment environment changes the value story.
An RPM program inside a fee-for-service practice generates revenue the organization did not have before. The same program inside a capitated Medicare Advantage plan is cost avoidance, and a CS leader who walks into both accounts with the same deck will lose credibility with one of them. Pharma sits on the generating side at a distance, since the value lands in drug sales rather than in a claim.
04
Activation and adherence are two different problems.
Activation is a day 0 to 30 marketing and behavioral design problem. Adherence is a day 30 onward clinical and product design problem. The plays are not interchangeable, and reading a single blended engagement number is the most common way teams misread their own data.
05
Proxy KPIs are structural, not a shortcut.
What CS can see
App usage, device days
Where the evidence lives
Payer claims, EHR, actuarial analysis
What the stakeholder cares about
Clinical outcomes, savings
Dotted connections mark the gaps in direct access.
Claims data sits with the payer, clinical trends sit in the EHR, and savings calculations require actuarial analysis the vendor does not control. The metrics a CS team can see are usually two steps removed from the result the stakeholder cares about. The framework maps both layers rather than pretending the direct data is available.
The lenses
The buyer lenses
Pharma, health plans, and employers sit on top of the five models, each with its own stakeholder map, value drivers, and standard of proof. The same revenue model requires a different CS motion depending on who is doing the paying. The table below is a quick reference for how the three lenses differ. Each one has its own page going deeper.
| Buyer Lens | Typical Revenue Models | Primary Stakeholder | Value Orientation | Lead Value Driver |
|---|---|---|---|---|
| Pharma | SaaS, Hybrid | Medical Affairs / Commercial (executive sponsor); Patient Support Program Lead (day-to-day) | Generating revenue, at a distance (drug sales) | Drug adherence and real-world evidence generation |
| Health Plans | PMPM, VBC, Hybrid, SaaS, RPM (MA) | CMO / VP Clinical Programs (executive sponsor); Actuary (savings validation) | Reducing costs or generating revenue, depending on how the plan gets paid | Quality measure improvement and total cost of care reduction |
| Employers | PEPM or PMPM, Hybrid, VBC (less common) | HR Benefits Leader (day-to-day); CFO (budget authority) | Reducing costs (health spend, absenteeism, productivity loss) | Healthcare cost trend and workforce engagement |
Pharma
The buyer whose revenue sits furthest from the platform, where value traces back to the drug rather than the tool and the activation chain has no single owner.
Health plans
The most structurally complex buyer, where quality measure improvement and total cost of care reduction drive the value story and the definition of success can shift mid-contract.
Employers
The buyer whose day-to-day contact rarely controls the budget, so CS's real deliverable is the internal case the HR leader carries to the person who does.
The gap
The framework that did not exist
One contract
- BuyerMeasures return
- Provider or operatorMeasures clinical and operational results
- End userNever asked for the product
All three must hold.
Each defines value differently, and the contract unravels at the weakest link.
Anyone going looking for a single resource that connects how digital health gets paid to how customer success has to operate will not find one. There are excellent CS books covering health scoring, churn, and retention playbooks. There are digital health books covering startup strategy, regulatory pathways, and business model archetypes. And there are healthcare finance books explaining how CMS sets rates and how dollars flow through the system. What is missing is anything that connects those layers into a single operating model.
The people doing this work today are piecing it together on their own: SaaS frameworks, tribal knowledge about healthcare billing, lessons from payer conversations, all assembled without a shared model to reference.
The gap matters because the problem underneath it has a particular shape. An account has three customers, not one. The job titles change with the buyer, and the three positions do not. Each of them defines value differently, on a different timeline, with a different threshold for walking away. A framework that cannot hold all three at once will miss the link that actually breaks.
Existing content covers business models or org-level KPIs. Nothing maps revenue models to the CS-specific stakeholder value drivers that determine whether those models succeed. This framework connects those disciplines into one reference practitioners can use.
The function
What this means for the CS function
In most SaaS companies, customer success is a post-sale function. Onboard the customer, drive adoption, manage the renewal.
Digital health asks for something else. The CS function has to hold adoption, economics, clinical outcomes, and evidence together at the same time. It operates as a commercialization discipline.
The work described throughout this framework, including activation campaign design, billing workflow optimization, and actuarial partnership on outcomes measurement, rarely sits cleanly inside one traditional function. High-performing digital health companies handle this one of two ways. They expand the CS scope to include those capabilities, or they integrate CS tightly with clinical, product, analytics, and finance. Companies that run digital health CS on a traditional SaaS org chart tend to underperform, and that is a structural mismatch rather than a talent gap.
The obvious objection is that no one person is a growth marketer, a clinical workflow consultant, and an actuary at once. The objection is correct, and it points at the answer: this is a team shape rather than a job description, and the failure mode at every size is to staff a single CSM against all of it, then read the shortfall as a talent problem. Read the staffing answer on the Value-Based / Outcomes-Based page
It is also why end-user activation is a marketing and behavioral design problem living inside the CS function rather than a CS problem in the traditional sense. Read why activation is a marketing problem on the Engagement Gate
One account relationship
Notes on method
Why the models do not sit on one axis
A careful reader will notice PMPM, SaaS licensing, and value-based contracts describe how the vendor gets paid, while RPM is defined by how the buyer gets paid. The vendor's own revenue in the RPM model arrives as a platform license, a per-patient fee, or a share of reimbursement. That is deliberate. The framework maps two axes at once: the vendor's revenue structure and the buyer's payment environment. RPM earns its own model because when the buyer's reimbursement mechanics sit that close to vendor revenue, the entire CS motion changes, from billing workflow enablement to the KPIs that predict renewal. Models 1 through 4 follow the same logic, covering vendor-side mechanics first, then the buyer's payment environment.
What the framework leaves out
It covers B2B2C revenue models, where a business buyer pays and value depends on a multi-stakeholder chain ending with a voluntary end user. Three revenue streams sit outside that frame by design. Direct-to-consumer subscription is excluded because the person paying and the person engaging are the same, which collapses the stakeholder dynamics entirely. Grant and research funding is excluded because it is not renewable commercial revenue a CS function manages, though its nearest analog, milestone-based data deliverables, appears in the Pharma Lens. Pharma media and advertising is excluded as an audience-monetization business rather than a CS-managed contract. One adjacent model does belong inside the frame: transaction and case-rate revenue, meaning per-visit telehealth, per-consult fees, and per-case bundles, covered as a variant in Hybrid Models.
How it stays current
The 2026 CPT restructure and the CMS ACCESS model both landed while this was being written. The model pages get updated as the rules move, which is why the billing specifics live on this site rather than inside a downloadable file.
Readers
Who it is for
CS leaders operating in digital health
A structured reference for how the company's revenue model should shape CS strategy, stakeholder management, and QBR execution.
CS leaders arriving from traditional SaaS
What is different about this space and why the existing playbook will not translate directly.
Founders and executives
How to build the CS function around the realities of the business model instead of a generic SaaS template.
Anyone evaluating the category
Hiring managers, investors, and operators who want to understand how value actually gets realized in digital health.
What is next
The Framework is the starting point. The Playbook and The Book go deeper.
The framework is a working document, and these are the next pieces in the order I plan to write them. If one of them is the page you need first, tell me and it moves up.
Which one would you want first? Tell me.
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. Privacy policy