RCM Is Not a Software Category. It’s a Negotiation Engine.

Healthcare revenue cycle has been sold for years as if it were a classic software market: identify a wedge, build a better product, expand the footprint, and eventually own the category. That story is tidy, investor-friendly, and mostly wrong for the part of healthcare where providers and payers keep arguing over what care is worth.definitivehc+2

The more accurate way to think about revenue cycle is this: it is the infrastructure that keeps a permanent financial dispute moving. Every step — from intake to coding to claim submission to denial work to appeals — exists because hospitals and insurers do not naturally agree on the price of care, the timing of payment, or the documentation required to settle the bill. In 2026, that dispute is getting faster, more automated, and more regulated at the same time, which is exactly why the old “build the wedge and win” story is starting to crack.adsc+3

Why the old story is seductive

The unbundling story has always been attractive because it sounds like progress. Take a large, messy system, isolate one function, make it efficient, and then move outward until the whole stack is yours. That logic works beautifully in markets where functions are loosely connected and users can adopt a tool without changing the behavior of every other participant in the workflow.thoughtworks+1

Revenue cycle is different. A coding tool does not merely help a coder; it changes claim value, denial risk, patient liability, and the downstream work queue for appeals and collections. A prior authorization tool does not just speed up admin work; it affects scheduling, clinical timing, patient access, and the insurer’s leverage over care delivery. In other words, each “station” in the cycle shapes the next station, which makes this less like a software stack and more like a chain reaction.definitivehc+2

That distinction matters because the capital markets often reward the wedge as though it can grow on its own. In practice, the best wedges in RCM are usually valuable because they sit close to a larger operating fight, not because they can stand alone forever. That is why so many promising point solutions end up as acquisition targets rather than durable standalone platforms.corporatefinance.kpmg+2

What changed in 2025

The biggest reason this thesis deserves a refresh is that 2025 and 2026 have made revenue cycle more visible, more measurable, and more politically exposed. Prior authorization is a prime example. KFF reported that Medicare Advantage insurers made nearly 53 million prior authorization determinations in 2024, with 4.1 million denials and an 80.7% overturn rate on appealed denials, which shows how much administrative energy gets spent just to reach the same answer after a second pass. That is not a niche workflow problem; it is a national operating pattern.grandviewresearch

At the same time, CMS finalized interoperability and prior authorization rules that push payers toward FHIR-based APIs, shorter decision windows, and more transparency around denials and status updates. Those requirements matter because they are not just technical upgrades; they change the economics of how much friction the system can sustain. Once payers and providers are forced to standardize the request/response loop, vendors that only sell “paperwork reduction” lose some of their moat.adsc

2025 also brought a more aggressive M&A environment in RCM. Industry reporting and deal trackers showed a steady flow of add-on acquisitions, especially by PE-backed platforms looking to stitch together adjacent capabilities rather than rely on one narrow product line. That’s an important signal: the market is not only buying software, it is buying coverage, operating leverage, and integration depth.corporatefinance.kpmg+1

Why standalone wedges struggle

The basic reason standalone wedges struggle in RCM is interdependence. If a product improves coding accuracy, it may raise claim value, but it can also increase patient responsibility and alter denial patterns. If a product accelerates prior auth, it may help throughput, but it can also make the payer side respond with tighter rules or more automated review. Optimizing one station often shifts pain to the station next to it.definitivehc+2

That creates a very different product environment than the one investors usually imagine when they talk about vertical software. In a normal software category, the tool that is better usually wins because the user experience is cleaner or the workflow is faster. In RCM, “better” can mean “more disruptive to someone else’s workflow,” which often triggers workarounds, integration demands, and procurement resistance.corporatefinance.kpmg+1

This is also why the winner is frequently not the prettiest product, but the most operationally survivable one. Buyers in healthcare increasingly want fewer vendors, fewer interfaces, and fewer points of failure. A point solution that cannot tolerate the operational drag of real-world adoption may still be impressive in a demo, but it is not necessarily durable inside a health system budget cycle.corporatefinance.kpmg+1

The real battleground

The most important shift in the market is that the center of gravity keeps moving. Epic and other EHRs have already absorbed a big chunk of the front end of revenue cycle, especially the workflows closest to scheduling, registration, and charge capture. What remains is the middle and back half — coding, clearinghouse functions, denials, appeals, prior auth, patient billing, and collections — where the hospital’s system has to communicate with the payer’s system.adsc+1

That gap is where the action is, but it is also where the friction lives. CMS’s 2026 and 2027 interoperability requirements are likely to make that bridge more structured, but they will not make the underlying payer-provider disagreement disappear. They just make it easier to exchange data about the argument.adsc

That is why the market keeps rewarding broader coverage. A vendor that can sit across several adjacent pain points is easier to keep than a vendor that solves only one. In a tightening budget environment, “one more best-of-breed tool” often loses to “one platform that reduces contract count, integration overhead, and compliance anxiety”. That is not a product-quality judgment; it is a procurement reality.corporatefinance.kpmg+1

AI changes the tempo, not the fight

A lot of 2025 RCM commentary treats AI as the headline. The better interpretation is that AI is simply accelerating the existing contest. Payer automation gets faster, provider automation gets faster, and the back-and-forth between approvals, denials, appeals, and resubmissions gets more efficient without necessarily getting less adversarial.waystar+1

That matters because AI can improve throughput while still preserving the underlying conflict. If a model helps a provider submit cleaner prior auth requests, the payer can use automation to review more volume faster. If a model helps a denial team surface appealable cases, the payer can tighten the initial review rules. The result is not the end of the game; it is a faster version of the same game.waystar+2

This is where many product narratives become too optimistic. They assume automation is synonymous with resolution. In RCM, automation often just lowers the cost of continuing the fight. That is still valuable, but it is a different value proposition than “we solve the problem once and for all”.definitivehc+1

What the data says

The numbers in 2025 and 2026 support the idea that this market is getting more operationally intense, not less. KFF’s 2026 analysis shows that prior authorization volume in Medicare Advantage remains enormous, denial rates remain meaningful, and appeals are still being overturned at a very high rate. That combination suggests the process is expensive, repetitive, and often revisited after the first decision.grandviewresearch

CMS’s final rule also makes clear that regulators now expect this workflow to become more digital and more transparent, with prior auth APIs, faster decision windows, and standardized exchange requirements generally beginning in 2026 and 2027. In practical terms, that means revenue cycle vendors are no longer selling only speed; they are selling compliance-ready connectivity into a more visible process. That is a stronger market than “we make the fax machine slightly less painful,” but it is also a more scrutinized one.adsc

Private equity activity reinforces the same picture. Add-on acquisition strategies are showing that platform owners want to own more of the workflow chain, not just one elegant slice of it. That suggests the market is already voting for consolidation, even if product marketing still talks like unbundling is the main game.corporatefinance.kpmg+1

What this means for founders

If you are building in RCM, the first question is no longer “Can we win this wedge?” It is “What adjacent pain must we control for this product to survive?” That changes roadmap priorities, partnership decisions, and exit expectations.corporatefinance.kpmg+1

It also changes the acquisition story. Buyers are not just purchasing revenue or technology; they are purchasing operational coverage and integration optionality. A smaller company with a narrow but critical capability may still be attractive, but usually because it helps the acquirer solve a larger system problem, not because it can independently dominate a market.corporatefinance.kpmg+2

That is why the best founder narrative in 2026 is not “we will replace the whole stack.” It is “we are the most important missing piece in a workflow that bigger players need to control.” That is a much more believable path to liquidity in this sector.corporatefinance.kpmg+1

What this means for providers

For hospitals and health systems, the implication is even simpler: vendor strategy is now revenue strategy. Every additional point solution comes with integration, governance, security, training, and change management costs. In an environment where margins are still under pressure and prior auth is becoming more visible to regulators and patients, that overhead matters more than ever.adsc+1

The practical move is to look at RCM through the lens of workflow ownership rather than feature shopping. Which vendors sit at the true bottlenecks? Which ones merely add another interface? Which tools are actually reducing cost-to-collect, and which ones are just moving work from one team to another? Those are the questions that survive budget review.definitivehc+1

Providers should also assume that payers are using the same tools, just from the opposite side of the table. That means the system is not merely digitizing; it is escalating. The organizations that win will be the ones that treat RCM as an operating model problem, not a software catalog problem.

Consulting

Strategic support for regulatory compliance, clinical documentation, and operational improvement in mental health care.

© 2022. All rights reserved.