Part of The Revenue Model Sets the Strategy

The Health Plans Lens

The most structurally complex buyer.

01

The definition of success moves mid-contract

The five revenue models in this framework describe how a digital health company gets paid, and the payment structure sets the CS motion. The buyer sits on top of that structure rather than replacing it.

Who is doing the paying changes which stakeholders hold power, what counts as proof, and how the value story has to be told.

Health plans are the most structurally complex buyer in digital health. The contracts are often large, the stakeholder map runs deep, and the definition of success can shift mid-contract depending on regulatory changes, Star Ratings performance, or a leadership transition at the plan.

02

How health plans buy digital health

Health plans buy across nearly every model in this framework. PMPM is the most common structure for population health and member engagement programs. Value-based or hybrid arrangements structure the contracts where the plan wants accountability against outcomes rather than activity. SaaS licensing applies when the plan is buying a care management or utilization management platform rather than a member-facing tool. RPM appears when the plan is a Medicare Advantage sponsor running chronic disease management programs for its attributed population.

The buyer's line of business matters as much as the contract structure. A commercial plan, a Medicare Advantage plan, and a Medicaid managed care plan are operating under different regulatory environments, quality frameworks, and financial pressures. A CS team that treats them as interchangeable because the contract looks similar will consistently misread what the account needs.

03

The stakeholder map

Chief Medical Officer / VP of Clinical Programs is typically the executive sponsor and the internal champion who got the program funded. They care about clinical outcomes, quality measure performance, and whether the program supports the plan's strategic priorities. They're the stakeholder who has to defend the program to the CEO and board if results disappoint, which means they need a narrative they can own rather than a data report they received from the vendor.

VP of Care Management or Director of Clinical Operations is the day-to-day operational owner. They care about program performance against targets, integration stability, member experience, and whether the vendor is making their team's job easier or harder. This is often the stakeholder CS interacts with most frequently, and the relationship here tends to be the most operational and problem-solving focused.

Actuary / Health Economist becomes a decisive stakeholder in any contract with a cost outcomes component. They control the measurement methodology, interpret the claims data, and ultimately determine whether the program produced the savings it claimed. CS leaders who don't build a working relationship with the actuary before the measurement period ends frequently find themselves in disputes at settlement time that could have been resolved months earlier with proactive data sharing.

Compliance / Regulatory Affairs is relevant in any contract touching Medicare or Medicaid populations, where CMS requirements, state mandates, and audit exposure create constraints that affect what the program can and can't do. Data use agreements, member consent frameworks, and outreach restrictions often originate here. CS should understand these constraints early rather than designing activation campaigns that compliance will block. A regulatory or contractual mandate can also move who holds power without changing the payment structure at all: where a program exists to satisfy a state requirement or an accreditation, the compliance owner can outrank both the CMO and the CFO, and the renewal turns on audit and reporting performance before it turns on engagement.

Member Engagement or Population Health Analytics team owns the data the CS team needs most: enrollment trends, utilization patterns, member demographics, and claims data for outcomes measurement. Building a working relationship here early, rather than routing everything through the executive sponsor, accelerates the CS team's ability to detect problems and demonstrate value.

04

Value drivers

Value drivers vary by line of business, but the organizing principle is consistent: a health plan is either reducing what it spends or increasing what it collects. Quality performance can do either, depending on how the plan gets paid. The specific currency depends on who's asking.

Medicare Advantage plans

Star Ratings are often the single most important value driver because they directly affect CMS quality bonus payments and member retention through plan ratings visibility. The bonus attaches at a threshold rather than on a sliding scale, so the rating movement that changes revenue is the one that carries a contract to four stars or above. HEDIS measure performance, total cost of care reduction, and hospital readmission rates are the metrics that belong in every QBR.

Four stars changes bonus eligibility
Bonus amount is not plotted

Contract Star Rating, 3 to 5

Below bonus threshold Bonus threshold met 33.544.55 Below bonusthreshold Bonus thresholdmet 33.544.55
The bonus attaches at a threshold, not on a sliding scale.Movement within either side changes no revenue; the crossing does.

Medicaid managed care plans

State-mandated quality measures dominate the conversation. Many state contracts now require health equity metrics. Social determinants of health affect every aspect of engagement and outcomes, and the plan's ability to demonstrate improvement in SDOH-related metrics is often tied to contract performance with the state. Cost savings are harder to demonstrate given Medicaid's lower baseline costs, so quality and access metrics tend to carry more weight in the value conversation.

Medicaid is where a strong result is most likely to be read as a weak one. The barriers that make activation harder also make generic benchmarks the wrong comparison, and a plan comparing a Medicaid cohort against a commercial one is comparing two different denominators without noticing. Which population sits under the line is the subject of the Engagement Gate, the threshold every model in this framework has to cross before any stakeholder sees value. What it costs when the line is written into a contract is the subject of the PMPM / PEPM model.

Commercial plans

The CFO lens is most prominent. Healthcare cost trend, medical loss ratio, and member retention are the financial metrics that matter. Quality measures are relevant but typically less binding than in government programs. The value story is usually built around cost avoidance for high-cost conditions and the competitive differentiation that a strong digital health offering provides in employer contracting.

05

CS and QBR implications

Health plan QBRs require the most preparation of any buyer in this framework. The stakeholder map is wider, the data requirements are more rigorous, and the definitions of success are more precisely specified in the contract. A QBR that works for the care management lead will not work for the CMO, and neither of them is the audience for the measurement methodology. CS teams that build one deck and treat it as the whole reporting job are leaving credibility on the table.

An effective health plan QBR presents a tiered narrative: executive-level strategic summary for the CMO and VP level, operational performance detail for the care management team, and data methodology documentation for the actuary or analytics team. The first two audiences are usually in the room. The actuary usually isn't. Methodology gets reviewed off the quarterly cycle, at contract start and again at reconciliation, which is why that layer has to stand on its own without a presenter.

One dynamic worth naming: health plan accounts are susceptible to champion turnover. A VP of Clinical Programs who championed the program internally leaves, and their replacement inherits a contract they didn't choose. CS must build relationships deep enough in the account that a single departure doesn't orphan the program. If the only person at the plan who understands why the program was purchased is gone, the next renewal is at risk regardless of performance. The departure is rarely the first signal. A champion losing executive air cover, being passed over in a reorg, or going quiet in forums where they were once vocal usually precedes the exit. CS teams that treat these external signals as leading indicators, rather than waiting for the resignation, get months of runway to multi-thread the account before it orphans.

06

Where to go next

The five model pages cover how each model gets paid, how the buyer's payment environment shifts the value story, and an example drawn from practice. Four of them also map the stakeholder value drivers, and the hybrid page maps contract structures instead. Health plans buy across all five, so the page that carries a plan contract's mechanics is the one for the model it runs, and the page that carries the pull between two streams in the same contract is Hybrid Models. The Engagement Gate page carries the threshold every model has to cross before its value story starts, along with the lag comparison across all five models and the rules for reporting an engagement rate honestly, which is where the Medicaid benchmark question on this page is argued in full.

The other two buyer lenses come at it the same way this page does, by who is doing the paying. Pharma is 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. Employers are 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.

Models

Buyer lenses

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.

This field is required.

Your email delivers the kit when it ships, plus occasional new insights from Digital Health Success. No spam. Unsubscribe anytime.

Modeldiagnostic Stakeholder andKPI worksheets TieredQBR builder Trade-offscript Proofchecklist Seven-stepguide
Scroll to Top