What the Post-Close Visibility Gap Actually Costs

I keep having a similar conversation with operators running healthcare rollups. Orthopedic, dental, behavioral health: different sectors, the same blind spot. Sooner or later the talk turns to what it costs to lose sight of their own sites in the months after a close. Every one of them has underestimated that cost in the same way.

It is not carelessness. The integration budget has a line for data, and that line gets counted carefully. The problem is that the costs that matter most never reach a line at all. They are real and large and invisible, which is the worst combination a cost can have.

What follows is the whole bill, in plain terms, with a way to put a defensible figure on it before a buyer puts one on you.

Start with what lands on an invoice, because that is what shows up in diligence.

An operator at an orthopedic platform told me about two billing systems that ran in parallel for nine months. Another kept a four-person analytics team rebuilding the consolidated denial report by hand every Friday, because no single system could produce it. A third was still paying for three legacy EHR licenses it could not switch off, because the active patient panels had never been migrated, and you cannot unplug the system of record while patients are still being seen against it.

These costs are real, and they are the ones everyone already counts. They show up as duplicated software spend, contractor hours, and license fees, so they reach the model on their own: a line item exists, someone owns it, and it gets tallied. If these were the whole story, the integration line in most quality-of-earnings models would be about right.

They are not the whole story.

The larger costs have no invoice attached, which is exactly why they get missed.

Deferred synergies. Every month the platform cannot see across its sites is a month it fails to shift payer mix, rebalance staffing, or apply the denial fix one acquired practice already found. A dental operator described buying a practice that had quietly solved its eligibility-verification problem a year before the deal. Nobody at the platform noticed for seven months, because the data that would have surfaced the fix sat in a system no one had connected. Seven months of avoidable denials across the other sites is not a software cost. It is forgone margin, the kind that never shows up as a line because nothing was spent. It was simply never earned.

Duplicate decisions. Without a consolidated KPI, every site keeps deciding for itself. Each clinic sets its own staffing ratio, its own collections cadence, its own definition of a clean claim. None of those choices is wrong in isolation, but the platform pays once to maintain the divergence and again to reconcile it later. Over time the fragmentation hardens into culture, which is far more expensive to unwind than any software contract.

Retrade leverage on the next deal. This is the cost operators feel last and regret most. In the EY Private Equity Exit Readiness Study 2025, 72% of PE firms named weak data and KPI reporting as the biggest finance issue at exit, and another 41% said they lacked the data granularity to substantiate their equity story.[1] The logic at exit is unsentimental: a buyer discounts whatever cannot be verified, so when you cannot produce clean cross-site numbers, the discount comes straight out of your proceeds. One behavioral health operator went into confirmatory diligence unable to show a consistent same-store volume series across its sites. The buyer did not walk. The buyer retraded.

I’m used to grounding my thinking in computational models, so here is a toy example you can also pressure-test. Take a six-site specialty platform doing about $4M in annual net revenue per site, roughly $24M across the platform, and put every cost on a monthly run-rate. The unit figures sit on published industry benchmarks.

Here is the full build. Each line is a monthly run-rate, written as the unit assumption times the quantity, with the annualized figure beside it.

The visible lines are the ones an invoice already proves. Two billing platforms run in parallel at $15,000 each per month, in line with what a full revenue-cycle system costs a platform this size. Three legacy EHR licenses stay live at $4,000 apiece, squarely inside published per-site EHR pricing. And rebuilding that consolidated report by hand eats about a day of the four-person analytics team’s week, roughly $12,000 a month in loaded labor. Together they come to $54,000, the part diligence usually gets right.

The invisible lines are modeled rather than invoiced, and they are where the real money sits.

• Deferred synergies, $25,000 per site per month. The margin a site does not earn while it stays unintegrated: payer-mix moves not made, staffing not rebalanced, a denial fix from one practice not carried to the rest. At roughly $4M of revenue per site, that is about 7.5% a year, the midpoint of the 6 to 10% of revenue that post-merger studies put on capturable cost synergies. Across six sites it is $150,000 a month, the single largest line in the model.

• Duplicate local decisions, $6,000 per site per month. The cost of maintaining divergent local choices, each site’s own staffing ratio, collections cadence, and definition of a clean claim, and then paying again to reconcile them. At about 1.8% of site revenue it is deliberately the most conservative invisible line. Across six sites, $36,000 a month.

• Retrade leverage at exit, $30,000 a month. The one line that is not a run-rate in the ordinary sense. It is a risk-adjusted monthly equivalent of the equity discount a buyer applies for unverifiable cross-site numbers. The build is explicit. Assume a $60M exit, a 10% retrade if the cross-site story cannot be substantiated, and a 30% chance it comes to that. That is an expected $1.8M haircut, or $30,000 a month across a five-year hold. The EY exit study is why the probability is not lower, since most firms name weak data and KPI reporting as their biggest finance issue at exit. Booking it monthly keeps the exit risk on the same clock as every other cost.

Those three lines come to $216,000 a month.

Look at the split. The visible costs, the ones quality-of-earnings work reliably captures, are only about a fifth of the total. The other four fifths are deferred synergies and duplicate decisions, the part of the bill that never reaches the integration line. Count only what has an invoice and you budget for a fifth of the problem, because the costs you cannot see run to four times the costs you can. You are pricing the visible tip and ignoring the mass underwater.

The size of the bill also depends on how long the platform stays blind. Each row below is simply the $270,000 monthly run-rate multiplied by the number of months it takes to reach full cross-site visibility, so the longer the integration drags, the more of that run-rate you actually pay.

A six-month integration and a twelve-month integration are not a rounding error apart. On this illustrative platform they differ by more than $1.6M, almost all of it in the categories the model never names. That is the real argument for moving early on visibility: every month you compress the timeline is a month you stop paying the invisible run-rate.

If the data-integration line in a quality-of-earnings model is small relative to deal size, it is probably wrong, not because the visible costs were mis-estimated but because the model says nothing about the four fifths that carry no invoice. The fix is not a bigger software budget. It is to estimate the invisible categories on purpose, and to discount the integration timeline the way you would discount any other unproven projection. When a seller promises cross-site visibility in six months, ask what would have to be true for that to hold, then price the case you actually believe.

You do not need a new theory to do this. You need three counts before close.

1. A site-level schema inventory. How many distinct systems of record are there, and how many different field definitions describe the same clinical and financial concepts? This is the raw measure of how much translation the integration requires.

2. An identifier collision audit. How often does the same patient, provider, or payer carry different identifiers across sites, and how often do different entities collide on one? This is where consolidated reporting quietly breaks.

3. A denial taxonomy reconciliation count. How many distinct denial-reason vocabularies are in play, and how far apart are they? This predicts how long it takes to produce a trustworthy consolidated denial report, usually the first KPI anyone asks for.

All three are countable before the deal closes, and together they turn the integration timeline from a hope into an estimate.

At MTN we built the Data Foundry to work at the schema and metadata layer, so a platform can inventory its sites, reconcile identifiers, and align denial taxonomies without moving protected health information and without waiting on a full migration. The three counts that sharpen a diligence estimate are the same inputs that shorten the integration timeline after close. Measure the gap precisely, then close it.

The integration line is the most underestimated number in the model, and most of it is invisible. Anchor your estimate to how the costs actually accrue, count the gap before the deal closes, and you stop financing it by accident.

If you have tried to put a number on this yourself, I would love to compare notes.

References

1. EY, Private Equity Exit Readiness Study 2025. Survey of 100 PE professionals across the Americas and EMEIA (US$5B to US$100B+ AUM), fielded March to April 2025. The 72% and 41% data-readiness figures appear in EY, “How data readiness can improve private equity exit value” (ey.com).

2. Revenue-cycle and medical-billing software pricing, per-provider monthly ranges: vendor-published price lists, e.g. AdvancedMD, “Software Pricing” ($429 to $1,070 per provider per month for medical specialties; RCM services at 4 to 8% of collections); market sizing in Grand View Research, “U.S. Revenue Cycle Management Market Size Report” (February 2025).

3. EHR implementation and maintenance costs: Fleming NS, Culler SD, McCorkle R, Becker ER, Ballard DJ, “The Financial and Nonfinancial Costs of Implementing Electronic Health Records in Primary Care Practices,” Health Affairs 30, no. 3 (2011). For an average five-physician practice, about $162,000 to implement and $85,500 in first-year maintenance (roughly $1,500 per physician per month). AHRQ-funded; see also Fleming et al., AHRQ, “Time, Effort, and Infrastructure Costs to Use Electronic Health Records” (about $46,659 per physician in year one).

4. Cost synergies of 6 to 10% of target revenue: L.E.K. Consulting, “Keys to Unlocking Merger Value: Cost Synergies”, from L.E.K.’s own analysis of 30 years of deals with announced cost synergies. On the effect of private-equity acquisition on physician practices: Singh Y, Song Z, Polsky D, Bruch JD, Zhu JM, “Association of Private Equity Acquisition of Physician Practices With Changes in Health Care Spending and Utilization,” JAMA Health Forum (2022), which found acquisition associated with higher charges and allowed amounts per claim.

5. Revenue synergies are chronically under-captured, with companies achieving only about 77% of their targeted revenue synergies on average: McKinsey & Company, “Seven Rules to Crack the Code on Revenue Synergies in M&A” (2018), a survey of 200 M&A executives.

6. Internal: MTN, “Close the Visibility Gap” white paper (the $200,000 to $500,000 per-month range) and MTN Data Foundry integration pricing benchmarks.