What an Acquisition Does Not Transfer Automatically
The data room delivers contracts, procedures, and the org chart at closing. Part of what keeps the company running is not in any of them: it lives in exceptions, informal commitments, and the authority employees keep recognizing in the seller.
Day 45 after closing. The buyer has read the data room: procedures, contracts, org chart, job descriptions. This morning, a major customer reached the former owner on his cell phone to get a Saturday delivery. The former owner, six months into a transition role, said yes. Customer service did not know; neither did planning. First reading: the seller will not let go. Competing reading: the customer did what he has done for ten years, and the seller honored a commitment nobody ever wrote down. The two readings do not lead to the same decision, and the second is the one to verify first.
The phrase covers at least four distinct realities: inherited habits with no function, informal practices that provide real coordination, interference by the seller, and dependency on a person nothing can replace in the short term. The 100-day plan often treats them with a single gesture, professionalization. The first two call for opposite decisions. The thesis to examine: part of operational continuity rests on knowledge, arrangements, and authority that documentation does not transfer, and that the new organization does not replace until they have been identified.
A company sold after fifteen or twenty years runs on a layer of arrangements. Customers whose rush orders jump the queue. A supplier who delivers in 48 hours because the shop foreman calls him personally. An employee who postpones her vacation every December in exchange for a compensation never formalized. None of it appears in the contracts. It appears in the results: it is what explains why a given customer stayed, why lead times hold, why year-end goes smoothly. The seller holds the information. Employees apply part of it without always knowing where it came from. The buyer holds the formal authority and neither of the other two. During the first weeks, every ambiguous situation therefore goes back to the seller, not through sabotage, but because he is the only person who knows what was promised.
Some practices jump out at a new executive: a Friday meeting where the seller reviews every open order, a handwritten notebook kept alongside the system, a foreman who negotiates directly with a supplier instead of going through purchasing. They look like inefficiencies to fix.
The less visible causal link: these practices often perform a coordination function that the formal process does not. The notebook holds the dates actually promised to customers; the system holds the ones it calculated. The Friday meeting is the only moment where priority conflicts get settled. The foreman's call is what moves the company's orders ahead of the supplier's other customers. When a premature change removes the practice without replacing the function, the failure shows up late and gets attributed to something else. Purchasing is formalized in week three; supplier lead times stretch in week six; the accepted diagnosis is that "the supplier's service has slipped." The link goes unseen because time has passed and the cause was recorded as an improvement. The limit: not every informal practice carries a function. Some are the seller's preferences; others are arrangements the company should never have granted and that destroy margin. The way to tell them apart is not intuition. It is to ask, for each practice, what would happen if it stopped tomorrow, and to insist on a concrete answer. A precise answer ("that customer would know within 48 hours") helps identify the function. A vague answer means the practice should be tested before it is removed. When in doubt, a controlled stop, on one customer or for one week, settles it better than a debate.
The new org chart names the decision-makers. Authority, though, is observed: it is the person who gets asked when the procedure says nothing, and whose answer is applied. During the transition, employees test the new organization. They ask the seller, who answers to help. Each answer confirms where authority sits. The seller is not hanging on; the organization simply keeps working along the path it knows. The answer is not to forbid contact but to route it: the seller sends each question to the new manager, and the new manager has the exceptions register to answer it. Without the register, the referral produces a wrong answer, and the employee goes back to the seller.
A buyer acquires an architectural millwork manufacturer, 30 employees, supplying commercial fit-out contractors. First reading: estimating is done by hand, the seller reviews every quote himself, and the buyer plans to roll out pricing software within 90 days. The clue surfaces during the review of recent exceptions with the seller. Three customers, about 35% of revenue, operate under a verbal arrangement: their rush orders take priority and their quotes are priced by the seller at a margin different from the schedule, in exchange for volume and fast payment. None of it is in the contracts. Separately, the foreman keeps a notebook of promised dates, distinct from the production system. The verification: reconcile the notebook against the system over eight weeks. Of 112 promised dates, 41 differ from the system's. In 36 of those 41 cases, the actual delivery matches the notebook. The notebook is the real scheduling tool for priority customers; the system is a record. What this allows the buyer to conclude: the real commercial policy for a third of revenue is in the seller's head, and the real schedule is in a notebook. Pricing software deployed now would formalize the price schedule, that is, the policy that does not apply to the most important customers. What remains uncertain: whether the three arrangements are profitable, which only a margin analysis by customer will establish, and how the customers will react if the arrangement is formalized.
The decision: the software is postponed. The three arrangements are documented, then the seller introduces the buyer to those customers as the person who now decides them. The foreman's notebook is transcribed onto a priority board visible to the shop before any change to the system: the function is kept, the medium changes. Only one of the three arrangements is formalized first, to observe the reaction; the margin analysis will then say whether to keep it as is.
The review of recent exceptions is done with the seller, over the last 60 days of orders and service calls. For each non-standard item (rush, discount, special term, unusual delivery, workaround), five questions: who asked for it, who granted it, why, how often it recurs, and what would happen if it were refused. The result is a register, customer by customer and supplier by supplier, that becomes the new manager's working tool. The observation of real authority is done without the seller. For one week, a member of the leadership team notes every question with no clear procedure: who is asked first, who answers, and which answer is applied. The comparison with the org chart shows where formal authority and observed authority diverge. That is where the transfer has to start, one domain at a time, with a visible handoff.
| Transition decision | What it applies to | Example |
|---|---|---|
| Preserve temporarily | A practice whose function is not yet understood | The Friday meeting, until you know what it settles |
| Document | Customer, supplier, and employee exceptions | The register built with the seller |
| Transfer | Decision rights, one domain at a time | The seller introduces the new manager as the decision-maker to the three accounts |
| Test before changing | Any change that touches a coordination point | One arrangement formalized, one customer, one week |
The two reviews are not enough in three situations. When the seller has left or will not cooperate, the register is rebuilt with employees and customers, more slowly and with gaps. When the company is losing money and there is no time to observe, the rule becomes to preserve by default and change only what is bleeding now. And when informal arrangements cover most of the activity, this is no longer a transition problem but a dependency on one person, which 30 days will not resolve and which should have weighed on the price. None of the above prejudges the legal obligations transferred by the transaction. The ground here is operational: what keeps the company running on the Monday after closing.
Mirabilys intervenes at this stage as a framing of operational priorities for the first 30 days: review of exceptions with the seller, observation of real authority, the register, and the sequence of transfers and tests ahead of structural changes. If you have just signed, or if you oversee a portfolio company whose first weeks do not look like the plan, this is the examination to do before changing the organization.
Why does everything go back to the seller after closing?
Because part of operational continuity rests on exceptions, informal commitments, and authority that documentation does not transfer. The seller is the only person who knows what was promised, and employees keep recognizing his authority.
Should contact with the seller be forbidden?
No: route it. The seller sends each question to the new manager, and the new manager has the exceptions register to answer it. Without the register, the referral produces a wrong answer and the employee goes back to the seller.
Which reviews belong in the first 30 days?
Two: the review of recent exceptions with the seller, which produces a customer-by-customer register, and the observation of real authority without him, which shows where formal and observed authority diverge. That is where the transfer starts, one domain at a time.
Book a 30-minute discovery call
For owners of 1-20 M$ businesses. A fixed-fee mandate, identical for every client: six weeks, nine components.