Part of The Revenue Model Sets the Strategy
Hybrid Models
Most real contracts combine two or more models.
01
How it works
Most digital health companies don't operate under a single pure revenue model. In practice, contracts combine elements from two or more of the other four models.
A health plan contract might include a PMPM base fee plus an outcomes-based performance bonus. A health system deal might bundle a SaaS platform license with CPT reimbursement revenue sharing. An employer contract might start with an annual minimum fee, transition to per-case pricing as adoption grows, and eventually convert to a full PEPM structure once engagement crosses a defined threshold.
These combinations exist because both sides are managing risk. The buyer wants accountability for results without paying entirely for unproven outcomes. The vendor wants a revenue floor to cover operational costs while pursuing upside tied to performance. The hybrid structure is the negotiated middle ground.
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 it varies inside a single contract, because each revenue stream carries its own lag and the streams rarely surface at the same time. The Engagement Gate page carries the full treatment.
Hybrid models create the most complex Engagement Gate challenge because different revenue streams within the same contract may pull CS priorities in opposite directions. The PMPM base fee incentivizes broad enrollment across the full eligible population to demonstrate reach and justify the per-member spend. But the shared savings component incentivizes targeting the highest-risk, highest-cost members because that's where the cost reduction materializes. CS can't fully optimize for both simultaneously, and pretending otherwise leads to mediocre performance on both.
03
Four common structures
| Hybrid structure | What makes CS complex | CS priority |
|---|---|---|
| PMPM base + outcomes-based performance bonus | Must drive engagement (PMPM renewal) and outcomes (bonus capture) simultaneously. Engagement is measured monthly, outcomes annually with lag. | Secure base revenue through acceptable engagement. Build outcome measurement from day one. Report trajectory transparently. |
| SaaS platform license + CPT reimbursement | Must manage platform adoption (SaaS) and billing workflow optimization (RPM) for different stakeholder groups within the same account. | Drive implementation success first. Then shift to billing enablement. Track both subscription health and reimbursement revenue. |
| PMPM + shared savings | Long feedback loops: PMPM revenue monthly, shared savings calculated 18 to 24 months later. Requires claims data access the vendor often doesn't control. | Treat PMPM as operating revenue and shared savings as upside. Build actuarial partnership early. Communicate utilization wins throughout measurement period. |
| Annual minimum + case rate + PEPM switchover | CS operating mode shifts as adoption grows: activation-critical early (every new user generates case rate revenue), then retention-critical after switchover (revenue becomes population-based). | Drive hard toward switchover threshold in Phase 1. Shift to sustained engagement and expansion post-switchover. Understand the financial reconciliation mechanics. |
04
The principle that governs all hybrid models
Regardless of the specific combination, one principle applies: protect the base revenue first, then pursue the performance upside. The base fee (PMPM, SaaS license, annual minimum) is what keeps the lights on. The performance component (outcomes bonus, shared savings, case rate) is where margin and growth live. A CS team that chases the performance upside at the expense of basic engagement and stakeholder satisfaction risks losing the entire contract when the base comes up for renewal.
05
When revenue streams conflict: the trade-off conversation
Hybrid models are where the generating-revenue-or-reducing-costs distinction stops being a single answer, because different revenue streams within the same contract may sit on opposite sides. The SaaS license component might be justified by operational efficiency (reducing costs), while the CPT reimbursement share is justified by new revenue (generating revenue), and the outcomes bonus is justified by cost avoidance (reducing costs). CS must hold all three value stories simultaneously and know which one to lead with depending on which stakeholder is in the room.
The same split runs through the measurement. A SaaS platform license bundled with a CPT reimbursement revenue share carries two streams keyed to two different counts, licensed seats and enrolled patients, and neither number says anything about the other. Contracted adoption can run strong while patient-side billing stays thin, or the reverse, which means denominator discipline in a hybrid is one question per stream rather than one question for the account.
SaaS platform license
weekly active / licensed seats16 weekly active of 20 licensed seats
CPT reimbursement share
billable activity / enrolled patients5 with billable activity of 50 enrolled
The hardest moment in a hybrid contract is when the two revenue streams create conflicting incentives. The base-protection principle sets the internal default: when the two pull hard enough that something has to give, the base comes first. But a default isn't a strategy, and applying it silently means the buyer finds out at renewal that the program was optimized for something they weren't measuring. The conflict is worth surfacing.
The CS leader sits down with the buyer's executive team and presents the trade-off directly:
"We have a strategic choice to make about where to focus resources this year. We can spread enrollment across the whole eligible population to maximize reach. That gives your team the strongest engagement and member-experience story, the case that this program is touching the membership broadly. But it dilutes the cost savings, because most of the people we enroll are relatively healthy and don't move total cost of care. Or we can concentrate the same effort on the highest-risk 15%, where the cost actually sits. That's where the savings get large enough to prove, but the engagement number across the full population will read lower. One path gives you a reach-and-engagement story. The other gives you a hard savings number. Different people on your side may weight those differently, which is why I wanted to put it to you directly. Which matters more to your organization this year?"
This transparency accomplishes three things. It settles the strategy between buyer and vendor up front, so mismatched expectations do not surface for the first time at renewal. It makes the buyer a co-owner of the trade-off rather than a judge of the outcome. And it demonstrates strategic thinking that positions CS as a partner rather than a vendor managing a contract.
06
When not to have this conversation
That script assumes a buyer who wants to make the call. Not all of them do, and the conversation carries a real cost that's worth naming.
Open a discussion about which revenue stream the vendor optimizes for, and a procurement team can hear an invitation to examine why the contract has competing incentives in the first place. That's a short step from asking what each stream is worth to the vendor, and a shorter one from there to reopening pricing. Some buyers also sit in internal politics where either answer is radioactive. A clinical lead who has committed publicly to broad member reach will not enjoy being asked to formally deprioritize it in front of a CFO who wants the savings number.
The distinction that keeps the conversation safe is what it's about. Framed as a resource-allocation choice across their population, it's a strategy discussion between partners. Framed as a question about where the vendor makes its money, it's a pricing discussion, and it will be treated as one. Stay on their side of the line.
Timing matters as much as framing. This belongs early, with the executive sponsor, ideally during planning rather than at a business review. Raised at renewal it reads as a vendor managing expectations downward. Raised with procurement in the room it reads as a negotiation.
And where neither of those conditions can be met, the honest fallback is that the CS leader makes the call, documents the reasoning and the trade-off accepted, and surfaces it as an observation rather than a decision request: here's where we concentrated effort this year, here's what it produced, here's what the alternative would have produced instead. That's weaker than genuine co-ownership. It still beats letting the buyer discover at renewal that the program was optimized for something they weren't measuring.
07
A note on transaction and case-rate revenue
Some digital health companies run per-visit, per-consult, or per-case pricing as their primary model rather than as a phase inside a hybrid: virtual care platforms paid per encounter, telepsychiatry paid per consult, MSK and surgical programs paid per case or bundle. Transaction revenue counts as a variant rather than a sixth model because its CS mechanics are a recognizable blend of patterns already mapped. Revenue scales directly with utilization, which makes the engagement-revenue link as tight as RPM but without the billing-compliance layer: there is no code selection or documentation threshold standing between usage and payment, so activation and utilization are the revenue engine.
That places the CS motion closest to the enrollment-based variant of the PMPM / PEPM model (funnel optimization, multichannel outreach, and utilization analytics as the core revenue KPIs), with one addition: when the vendor supplies the clinical capacity, CS also has to manage the supply side, because unfilled clinician capacity and unconverted demand are two versions of the same lost revenue. When transaction pricing appears inside a larger contract, the case-rate phase in the annual minimum + case rate + PEPM switchover structure shows how the operating mode works and when it hands off.
08
Real-world example
At one enterprise wellbeing platform, a Fortune 500 employer contract was structured with three phases: an annual minimum fee covering the first several thousand users, a per-case rate for users above that threshold, and a PEPM switchover once adoption crossed a defined trigger point.
This structure required the CS team to operate in three distinct modes over the contract lifecycle. In the early phase, every new activated user generated incremental revenue above the minimum floor. CS operated like a growth marketing team: running activation campaigns, building co-branded assets, deploying manager toolkits, and optimizing the enrollment funnel. Once adoption crossed the switchover threshold, the revenue model flipped to population-based pricing. CS priorities shifted from "activate more users" to "demonstrate enough value across the population to justify the per-employee spend at renewal." The same team that was running A/B-tested email campaigns six months earlier was now building executive ROI narratives for the buyer's CFO.
In hybrid models, CS must understand the financial mechanics of the contract deeply enough to know when and how their operating priorities should shift. A team that runs the same playbook from month one through renewal will underperform at every stage.
09
Where to go next
The Engagement Gate page carries the full treatment of the threshold this page says varies inside a single contract, along with the lag comparison across all five models and the rules for reporting an engagement rate honestly. The four model pages follow one shape: how the model works, how the buyer's payment environment shifts the value story, the stakeholder value drivers, and an example drawn from practice. This 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.