← Back
PE POV
Point of view — private equity & operational due diligence

The risk that doesn't appear in the financials

Raven Manocchio — Future Assignment

Every service-heavy acquisition carries a category of risk that financial due diligence cannot see, legal due diligence cannot name, and management teams are structurally incentivized to conceal. It lives in the customer experience. And it destroys value in the first eighteen months after close.

The pattern is consistent enough to be predictable. A PE firm acquires a healthcare services company, an insurance platform, a fintech. The numbers are clean. The market position is defensible. The management team is credible. Eighteen months later, churn is running above model, the contact center is absorbing costs that weren't in the projection, and a product that looked differentiated in the data room looks brittle in the hands of actual customers.

The investment thesis wasn't wrong. The operational picture was incomplete. What looked like a well-functioning service was a well-managed presentation of one — optimized for the metrics that appear in a pitch deck and quietly degrading everywhere else.

This is not a failure of financial analysis. It is a failure of a different kind of due diligence that most firms have not yet systematized.

What the financials don't show

Customer-facing operations in service-heavy businesses accumulate a specific category of hidden liability: structural friction. It manifests as contact center volume that shouldn't exist, onboarding flows that drive churn in month three, claims and fulfillment processes designed around compliance rather than customers, and service architectures that function adequately at current scale and fail visibly under the growth assumptions embedded in the model.

None of this appears as a line item. It appears eighteen months later as margin compression, retention shortfall, and a 100-day plan that quietly doubles in scope.

The question is not whether the business has customer experience problems. Every service business does. The question is whether you know what they are before you close — and what they will cost you after.

Answering that question requires a different methodology than traditional operational due diligence. It requires someone who can read a service architecture the way a CFO reads a balance sheet — not as a description of how the business presents itself, but as a map of where value is actually being created, where it is leaking, and what the structural repair cost looks like.

Why this is harder than it looks

Management teams are not being dishonest when they present a clean customer experience picture. They are presenting the experience as their best people understand it — which is typically from the inside out, through the lens of processes they designed and metrics they selected. The gap between that picture and what a customer actually encounters is almost never visible from within the organization. It requires an outside practitioner with enough institutional depth to know what a broken service architecture looks like when it has been carefully dressed for company.

I spent twenty-five years inside that institutional depth. At PayPal, the product was financial trust delivered at scale — where a friction point in a payment flow translated directly into transaction abandonment and measurable revenue loss. At Blue Cross Blue Shield, the service architecture touched millions of people at their most vulnerable, and the gap between designed experience and delivered experience had consequences that showed up in outcomes data, not satisfaction scores. At Fidelity Investments, the cost of a misunderstood communication wasn't a poor NPS result — it was a retirement account moved at the wrong moment.

These were not aesthetic problems. They were operational problems with financial consequences, and solving them required the ability to map an entire service system, identify where and how it was failing, and translate that map into decisions that people with P&L responsibility could act on immediately.

That is precisely the capability that pre-acquisition due diligence is missing.

What rigorous service due diligence produces

A focused two-week assessment of a target company's customer-facing architecture produces four things that don't exist anywhere in a standard data room. A visual system map of the service delivery architecture — not as the company describes it, but as it actually operates. A friction audit that identifies where operational drag is concentrated, what is driving it, and what it is costing in preventable churn, excess service volume, and delayed revenue. A scale stress-test that models how the service architecture performs under the growth assumptions in the investment thesis. And a valuation impact summary that translates experience failures into numbers that can inform the model directly.

The output is not a consulting report. It is a decision instrument — tight, direct, and built for a partner who needs to know what they are actually buying before they sign.

The firms that build this into their diligence process will close better deals, execute cleaner 100-day plans, and exit businesses that look the way they were supposed to look. The ones that don't will keep discovering the same liability eighteen months too late.

raven@futureassignment.com — futureassignment.com