What You Bought vs. What You Acquired

I've spent a meaningful portion of my career inside the work that happens after a deal closes, or a decision to move operations from one place to another gets made. Integration programs. Transfer-of-operations efforts. The mechanical, often unglamorous work of taking something that was running under one set of conditions and making it run under another.

What you learn in that seat is that:

The description of what's being transferred and what's actually being transferred are rarely the same.

An integration plan lists systems, contracts, headcount, facilities, customers, and processes. A transfer-of-operations scope lists functions, SLAs, tooling, and transition milestones. Both are accurate, but neither is complete because the business that was actually producing the outcomes — the revenue, the service levels, the customer retention — was running on a set of dependencies that nobody wrote down, because nobody had to.

This is the pattern I want to name, because I've watched it play out often enough that I no longer think of it as surprise.

What a business is and what it has are not the same thing.

What a business has is the inventory of transferable assets — the brand, the IP, the equipment, the real estate, the customer list, the assignable contracts, the documented processes. These are the things that convey. They can be listed, valued, and handed over.

What a business is — the living, revenue-producing entity — runs on something else. It runs on tribal knowledge, relationship equity, informal authority, a handful of people whose departure would quietly unwind years of customer trust, vendor terms that were extended because someone once did someone else a favor years ago, and workflows that exist only in the heads of the people performing them.

Those things are not on the transfer schedule. They are the quiet assumptions that make the schedule work (or not).  In my experience, they are often the majority of what actually produces the outcomes the new owner — or the new operating model — was counting on.

Three patterns that repeat

Customer relationships that belonged to a person, not the company.

The revenue was real. The renewal assumption was real. But the renewal was being produced by a specific person's specific relationship with a specific buyer, and when that person's role changed — or when that person left because the change itself was the reason — the renewal assumption quietly stopped being true. The revenue didn't vanish immediately. It degraded one renewal cycle at a time, and by the time the pattern was visible in the numbers, the relationships were already gone.

Vendor terms that were personal, not contractual.

The payables were current. The aging looked fine. What wasn't visible was that the terms behind the aging were held in place by goodwill, not paper. A change in ownership — or a change in who was placing the orders — triggered a soft reset. Terms tightened. Cash conversion shifted. Nothing technically changed in the contracts, because the contracts had never been the thing holding the terms in place.

Process knowledge that lived in one person.

Not always a senior person. A dispatcher. A scheduler. A lead estimator. A customer service lead. Someone whose judgment was the actual operating system for a function, and whose departure didn't break anything on day one — it just started a slow degradation that showed up as margin compression, or service-level slippage, or escalation volume, two or three quarters later, after the new team had stopped asking why things were done a certain way and started doing them differently.

Each of these is recoverable. None of them are free. All of them cost time and attention that the integration plan — or the transition plan — did not budget for.

The Lens of Discovery is the Window of Opportunity

The reason I'm writing this for a deal-adjacent audience is that the handoff between diligence and Day 1, or between the decision to transfer and the start of transition, is the single highest-leverage window to surface this gap. It's also the window that tends to get the least structured attention, because by that point the momentum of the transaction has already moved on to integration planning and synergy capture.

From the integration seat, that timing is backwards. The questions worth asking are not how do we realize the thesis but what is the thesis actually standing on, and is any of it about to move?  Which relationships are load-bearing and held by a single person. Which vendor accommodations were personal. Which workflows have never been documented because the person performing them was the documentation.

These are answerable questions. They are not answerable quickly under operating speed, which is the condition you're in once integration is underway. They are answerable deliberately in the narrow window where the new owner still has the leverage of being new and the incumbent operators still have the leverage of being trusted.

When that window gets used, most of the degradation I described above is preventable. Not all of it. But most.

When that window doesn't get used, the first two or three quarters after close become a discovery exercise conducted at full speed — which is the most expensive way to discover anything.

If this pattern is familiar — whether you're on the buy-side looking at a target where the earnings story depends on a short list of people nobody's stress-tested, or on the operating side of a recent close/transfer where the early months are surfacing dependencies the plan didn't name — I'd be interested in comparing notes.

Kevin Goodwin leads operational stabilization, integration, and process improvement work through Scaling Business Architects. He has spent much of his career inside change management, integration, transfer-of-operations, and process improvement and automation programs in businesses undergoing structural transitions.