Who's Paying and How Much Will They Pay?

You are working with a founder of a health-tech company. They feel that their idea will change the world and benefit patients. You don't disagree. Your job is to help this founder, this company, and this idea succeed. So you have to ask. . . . "Who's paying and how much will they pay?" Uncomfortable questions, and the founder squirms a bit.

The problem is that the answer to that question is rarely straightforward, especially in healthcare. In the retail market, it's a little easier, but human psychology and behavioral economics are still complex. The truth is that you would really like this product to see the light of day and fulfill its promise to humanity... but it won't unless you can cut through the Gordian knot of these two questions:

"Who's paying and how much will they pay?"

The Uncomfortable Truth About Healthcare Innovation

Every health-tech founder I've worked with has a compelling vision.

They've identified a genuine problem.

They've built technology that solves it elegantly.

They can demonstrate improved outcomes, better patient experiences, and reduced clinician burden.

The clinical case is airtight.

And yet, the graveyard of health-tech startups is filled with brilliant solutions to real problems. The common thread among these failures is not technology. It's not clinical validation. It's not even market timing. It's a fundamental misunderstanding of healthcare's economic architecture.

In most industries, there's a relatively clean relationship between value creation and value capture. You build something useful, you sell it to the people who find it useful, and they pay you. Done . . . you win.

Healthcare breaks this model in ways that can be fatal to companies that don't understand it.

The person who uses the product is often not the person who chooses it, who is often not the person who pays for it, and who is often not the person who benefits from its outcomes.

This fragmentation of roles, user, chooser, payer, beneficiary, creates a maze that even the most innovative technology must navigate.

Two Worlds: Consumer Health vs. Clinical Integration

Consider the fundamental difference between consumer health technology and clinically integrated health technology. These operate in entirely different economic universes, and conflating them is one of the most common strategic errors founders make.

Consumer devices like fitness trackers and smartphone health apps operate in a direct-to-consumer model. The user is the buyer and the beneficiary. Adoption friction exists only at the individual level. If the perceived value exceeds the perceived cost (measured in money, time, and effort), adoption occurs. This is the clean economic relationship that founders from other industries intuitively understand.

Clinically integrated technologies operate in a fundamentally different environment. Remote Patient Monitoring and Remote Therapeutic Monitoring programs, for example, depend on a cascade of reimbursement conditions. CPT codes must exist. Documentation requirements must be met. Billing systems must be configured. There are caps on how much can be billed per patient per month. Staff must be trained not just to use the technology but to use it in ways that satisfy payer requirements.

This distinction matters enormously for strategy. A consumer health app can succeed by being delightful and useful. A clinically integrated technology must be delightful and useful, and billable and compliant, and workflow-compatible and institutionally aligned. The bar is simply higher, and the path is far more constrained.

Reimbursement as a Form of Friction

I talk a lot about friction in product design.

How many clicks to complete an action? How intuitive is the interface?

How steep is the learning curve?

These are important questions, and health-tech companies invest heavily in answering them well.

But the complexity of healthcare reimbursement creates its own adoption friction, entirely independent of the technology itself.

You can build the most user-friendly device in the world, and it will fail if providers cannot figure out how to get paid for using it.

This reimbursement friction can override even the most elegant technology design. A brilliant device that captures exactly the data clinicians need becomes worthless if that data cannot be translated into billable services. An intuitive patient interface means nothing if the backend cannot generate the reports required for reimbursement. A proven clinical outcome is irrelevant if there's no payment mechanism attached to achieving it.

I've watched health technology companies spend years and millions optimizing the patient experience while almost entirely neglecting the institutional experience. They demonstrate clinical efficacy while ignoring billing workflows. They prove value to the end user while failing to prove value to the entities that must actually write the checks.

This is not a secondary consideration. This is the consideration.

Mapping the Payment Landscape

So let's return to our two questions with fresh eyes. "Who's paying?" sounds simple. It is not.

In healthcare, potential payers include commercial insurers, Medicare, Medicaid, self-insured employers, health systems paying from operational budgets, patients paying out of pocket, caregivers responsible for aging parents, and increasingly, value-based arrangements where payment is tied to outcomes rather than services. Each payer has different requirements, different approval processes, different timelines, and different appetites for innovation.

"How much will they pay?" is equally complex. Reimbursement rates vary by payer, by geography, by care setting, by provider credentials, by diagnosis, by the specific CPT codes used, and by whether your technology is considered durable medical equipment, a software service, or something else entirely. There are often caps on monthly billing for specific services. There may be requirements for face-to-face encounters that limit scalability.

For clinically integrated technologies, you must understand not just whether someone could pay, but whether they will pay given all the friction involved in capturing that payment. A theoretically reimbursable service that requires thirty minutes of documentation time for a fifteen-minute billable encounter is not, in practice, reimbursable.

The economics simply don't work.

The Four-Dimensional Friction Problem

The most successful health technologies address friction at every level of the adoption chain. Think of it as a four-dimensional problem.

First, patient friction: Is this easy to use? Does it fit into my life? Do I understand what it's asking of me and why?

Second, clinical friction: Does this integrate into existing workflows? Does it give clinicians actionable information without creating data overload? Does it save time or cost time?

Third, institutional friction: Does this align with quality metrics that matter to the organization? Does it support or complicate compliance requirements? Does it create legal or regulatory exposure?

Fourth, economic friction: Can this be billed? How easily? Who handles the billing? What documentation is required? What's the net margin after accounting for all the associated costs?

A technology that solves only the first dimension is a consumer product. A technology that must operate in clinical settings must solve all four. Ignoring any one of them can be fatal.

Practical Implications for Founders

What does this mean if you're building a health-tech company?

It means that payment strategy is not something to figure out after you've built the product. It's something to build the product around. Your technology architecture should be shaped by billing requirements as much as by clinical requirements. Your data collection should be designed to generate compliant documentation. Your user experience should include the administrator who files the claims, not just the patient who benefits from the device.

It means that you need domain expertise on your team; not just clinicians who understand care delivery, but people who understand the operational and financial mechanics of healthcare organizations. Revenue cycle expertise is not glamorous, but it may be the difference between your company's survival and its death.

It means that your sales process is not just about convincing individual clinicians that your product is good. It's about demonstrating to institutional buyers that your product is economically viable for their organization. The champion who loves your technology is necessary but not sufficient. You also need the CFO to sign off, the compliance officer to approve, and the billing department to confirm they can actually capture revenue.

It means that you should be deeply suspicious of your own optimism. The path from "this is technically reimbursable" to "we are reliably collecting revenue" is long and filled with obstacles. Payers deny claims. Documentation is rejected. Codes are applied incorrectly. Every step leaks potential revenue. Build your financial models accordingly.

The Consumer Path vs. The Clinical Path

Some founders, surveying this landscape, decide to take the consumer path instead. If direct-to-consumer is simpler, why not just sell directly to patients?

This can work, but it brings its own challenges. Consumer health products face intense competition for attention and wallet share. They require direct-to-consumer marketing capabilities that most health-tech founders lack. They must convince individuals to pay out of pocket for something they might expect to receive through their healthcare coverage. And they often struggle with engagement. Fitness trackers are notorious for ending up in drawers after a few weeks of use.

More fundamentally, many health technologies simply cannot work in a consumer-only model. Technologies that require clinical integration, that depend on provider interpretation of data, that are most valuable for sick rather than healthy populations; these need the clinical pathway, with all its complexity.

The question is not which path is easier. The question is which path is appropriate for what you're building and for the problem you're solving.

A Note on Timing and Policy

Healthcare payment is not static. CPT codes get created and deprecated. Medicare coverage decisions change. Value-based care models rise and fall. State Medicaid programs experiment with new approaches.

This creates both risk and opportunity. Risk because the payment landscape you built your company around may shift beneath you. Opportunity because new payment pathways open up, suddenly making what was previously impossible viable.

Navigating this requires vigilance and adaptability. It also requires humility about your ability to predict how payment policy will evolve.

Building a company whose survival depends on a specific policy change that hasn't happened yet is a gamble, not a strategy.

Cutting the Gordian Knot

Alexander the Great, presented with the famous Gordian knot, didn't untangle it. He cut it with his sword.

In healthcare, there is no sword. You cannot bypass the payment complexity. You cannot will reimbursement into existence. You cannot succeed on clinical merit alone.

What you can do is approach these questions: "Who's paying and how much will they pay?" with the same rigor and creativity you bring to your technology development. Treat payment strategy as a design problem. Iterate on your business model as aggressively as you iterate on your product. Hire for the skills you need to navigate this landscape, even if those skills aren't the ones that excite you.

The founders who succeed in health-tech are rarely the ones with the most brilliant technology. They're the ones who understand that brilliant technology is necessary but not sufficient. They're the ones who recognize that healthcare's economic complexity is not an obstacle to be resented but a terrain to be mastered.

Your idea may well change the world and benefit patients.

I truly hope it does, and I am pulling for you and your idea.

But to see the light of day and for your idea to fulfill its promise to humanity, you must cut through the Gordian knot not with a sword but with patience, expertise, and an unflinching focus on the questions that actually determine survival:

Who's paying, and how much will they pay?

The answers are rarely straightforward. But they are always essential.