There are two versions of the day a deal closes. In the first, the press release goes out, the deal team moves on to the next mandate, and an integration workstream gets staffed sometime in the following weeks — usually by whoever from each side had bandwidth, reporting into a steering committee that meets biweekly. In the second, the person who is going to run the combined operation has already been in the room for the last month of diligence, already knows which systems don't talk to each other, already has a day-one org chart with names in every box, and is running the business — not planning to run it eventually — before the ink is dry.
I have been on the inside of the second version, scaling a logistics network 10x after its largest acquisition to date. The difference between those two versions of day one is not a nuance of execution style. It is usually the entire difference between a deal that hits its synergy case and one that spends eighteen months rediscovering, the hard way, everything the diligence deck assumed.
Integration Is Not a Workstream. It Is the Thesis.
Most deal theses are built on a synergy bridge — cost synergies from combined procurement and overlapping facilities, revenue synergies from cross-selling, multiple expansion from scale. All of that is underwritten by an assumption that gets almost no scrutiny in the deal process itself: that someone will actually make it happen, on a timeline, with authority to override the friction that always shows up when two operations try to become one.
That assumption is where most of the value in a deal is made or quietly lost. Not in the modeling. Not in the negotiation. In whether the operating leadership that has to deliver the synergy case is already in the room, with real decision rights, on the day the deal closes — or whether that leadership is still being recruited, onboarded, or figured out while the clock the model assumed is already running.
The Three Places Integration Value Actually Gets Made or Lost
Diligence. Financial and legal diligence get enormous rigor. Operating diligence — does the combined network actually work, do the systems reconcile, is the cost-to-serve assumption in the model built from real site-level data or from a rounded average — gets far less, and usually happens after the deal is already signed. By then, whatever the operating diligence finds is a surprise instead of a negotiating point. The fix is not more diligence hours. It is putting the person who will actually run the combined operation into the diligence room early enough to pressure-test the synergy case against the real network, not the one in the data room.
Day one. The highest-risk window in any integration is the first ninety days, and it is exactly the window where most deals have the least operating authority in place. Decisions about which systems to keep, which facility absorbs which volume, and who reports to whom either get made quickly by someone with the standing to make them, or they get deferred to a steering committee that meets every two weeks — and every deferred decision is a week where two organizations keep running as two organizations instead of becoming the one the model assumed. Authority on day one is not a governance nicety. It is the difference between an integration that compounds and one that stalls.
The first hundred days. This is where "temporary" becomes permanent if no one is watching for it. Two receiving processes, two reporting systems, two ways of doing the same job — all reasonable as a short-term bridge in week one — quietly calcify into the new normal by week sixty if there is no explicit plan to standardize on one operating model. The synergy case in almost every deal assumes the combined entity eventually runs as one company. The first hundred days are where that either becomes true or becomes a permanent excuse for why the synergies never fully landed.
What This Actually Looks Like Inside a Combined Network
On paper, integration friction sounds abstract — "systems don't talk to each other," "processes need to be harmonized." Inside a logistics or distribution business, it is anything but abstract. It is two warehouse management systems that both claim to be the source of truth for the same SKU, and no one has decided which one wins. It is two receiving processes that both work fine independently and produce two different answers when a customer asks why their order is late. It is two labor models — one built around a unionized regional workforce, one built around a leaner distributed model — that need to become one plan without either site feeling like it lost.
None of these are exotic problems. Every integration in an operations-heavy business runs into some version of all three. What separates the deals that compound from the ones that stall is not whether these problems show up — they always do — but whether there is someone with the authority and the operating fluency to resolve them in week three instead of debating them in a steering committee through month six. A decision about which WMS wins is not complicated. It becomes complicated when no one owns the decision and both sides have a reasonable case for their system, so it drifts unresolved while the two organizations keep running as two organizations underneath it.
The Trap Most Deals Fall Into
The trap is treating integration as a workstream that sits alongside the "real" deal work instead of as the deal thesis itself. It gets a steering committee instead of a single accountable owner. It gets a synergy bridge built by the deal team and the banks, then handed to whoever is running integration to go make true — a plan built by people who will never be the ones executing it, for an operator who had no hand in building it and no reason to believe every number on it.
The second version of the trap is subtler and more common: hiring genuinely strong operators, but bringing them in after close instead of before it. By the time a new integration leader is onboarded, learns the business, and starts making decisions, the highest-leverage window — the first ninety days, when two organizations are still malleable enough to actually merge instead of just coexist — is already half gone. Talent arriving late does not recover the time that was lost while no one had the authority to act.
What Should Happen Before You Sign
- Put the operating leader who will run the combined entity into diligence, not just finance and legal. If that person cannot yet be identified, that is itself a signal the deal thesis is not as ready as the model suggests.
- Build the day-one org chart and decision rights before close, not after. Every box should have a name, and every name should know, before the announcement goes out, what they are accountable for starting the following Monday.
- Pressure-test the synergy number against the real network. Site-level cost-to-serve, actual system compatibility, actual customer contract terms — not the rounded assumptions that made the model clean enough to present.
- Name the standardization plan before close. Decide, in advance, which operating model the combined entity will run on — not "we'll figure it out together" — so week one starts with a script instead of a negotiation.
- Give the integration leader real authority, not a dotted line to a steering committee. The person accountable for the synergy case needs the standing to make the calls that get two organizations to behave like one, on the timeline the model assumed, without waiting for a biweekly meeting to bless every decision.
What I Am Seeing Now
The clearest version of this I have lived was scaling a logistics network ten times over after its largest acquisition — becoming the executive who owned the combined operation from day one, not the person brought in afterward to clean it up. The result was not a single dramatic fix. It was revenue growth of 28% year over year, a 39% gain in logistics efficiency, a 17% reduction in operating cost, and executive decisions that moved 27% faster than they had before, because the authority to make them was already sitting where the work was happening.
None of that came from a better synergy model. The model for that deal looked like every other synergy model — reasonable assumptions, a clean bridge, a timeline. What made it real was that operating leadership was already in the room before the deal closed, already accountable for the number on day one, and already standardizing the combined operation before "temporary" had the chance to become permanent. Every one of those numbers traces back to decisions that got made in week three instead of month six, because the authority to make them was already in place instead of still being assembled.
This is the lens I bring into every engagement now as an operating partner, whether the mandate is a post-merger integration, a turnaround, or a network redesign: the deal thesis and the operating plan are not two different documents written by two different teams. They are the same document, and it only holds up if the person accountable for executing it was in the room before anyone signed anything. That is the actual thesis behind every deal that compounds instead of stalling: not a better slide, but someone in the room, on day one, who is going to make it true.