Replacing the seller: transitioning owner-held knowledge

Owner dependency is not one problem, it is four, and they leave the building at different speeds. Customer relationships go first — the top accounts have a personal relationship with the seller and a contractual relationship with the entity, and only one of those transfers automatically. Pricing authority goes second: in most acquired businesses of this size, quoting is judgement rather than policy, and the judgement is the seller's. Vendor terms go third, because rebates, informal credit and delivery priority are frequently relationship-priced and invisible in the ledger. Undocumented process goes last and is the largest.

The first two are addressed by getting the customer list out of the seller's head and into a system inside the first thirty days. That is owner-dependency work rather than a software-selection exercise: it does not matter much which system, it matters enormously that the relationship history, the pricing history and the named contacts stop living in one person's phone. Concentration measurement — top-one and top-five share of revenue — tells you which relationships you personally have to own before the seller goes.

The vendor and customer contracts deserve a specific pass that most acquirers skip. Assignment clauses go unexamined post-close more often than not, and the fastest win hiding inside them is usually a rebate term nobody has been claiming. Confirm that each material contract was actually assigned, then read it for what it entitles you to.

There is a structural reason sellers become less helpful three weeks after close, and it is not personality. Where the acquisition was financed with an agency-guaranteed loan and part of the price took the form of a seller note, that note counts toward the required equity injection only on strict terms: the standard operating procedure states it must be on full standby for the life of the loan and may not exceed half the required injection — in practice at most five per cent of project cost, with no principal and no interest for the entire term.

Read that as an operating fact rather than a financing detail. The seller receives nothing on that portion of the price for years, which means that during exactly the window where most post-close failures occur, they have no cash-flow reason to answer the phone. Their remaining incentives are reputational and personal. That is not nothing, but it is a materially weaker instrument than the one most acquirers assume they are holding, and it decays fast.

A related rule shapes what happens later: a seller note must have been in place and current, not on standby, for at least twenty-four months following the change of ownership before it can be refinanced. Whatever arrangement you struck at close is therefore durable in a way that surprises people, and the transition plan has to be built around it rather than around an expectation that terms will be renegotiated in month six.

The design response is to front-load. Assume the seller's useful attention is a depleting asset that runs out faster than the transition agreement's stated term, and spend it in the first sixty days on the things only they can give you. Save the questions you can answer from documents for later, or for never.

The method that works is observational rather than interrogative. Sending a list of questions to a departing owner produces short answers about the parts of the job they can articulate, which are the parts you could have worked out anyway. Sitting beside them while they quote a job, handle an escalation or take a call from the largest customer produces the parts they cannot articulate, which are the parts that matter. Write it up afterwards, in your own words, and show it back to them for correction — corrections are far easier to extract than descriptions.

Sequence what you document by what only the seller knows, not by what is easiest to write down. Most first-time acquirers begin with the process that is already half-documented because it feels productive, and end up with a tidy manual for the parts of the business that were never at risk. The correct order is: things only the seller knows and that happen frequently, then things only the seller knows and that happen rarely, then everything else, which can wait for the team to write.

A standard operating procedure here is a working document rather than a compliance artifact: the trigger, the steps, the decision points, the exceptions and the person who owns it. Writing one for a process you do not yet understand is legitimate and is in fact the point — the draft is a device for surfacing what you got wrong, and the seller correcting it is the transfer happening.

Do this against a picture of key-person concentration, not just seller concentration. The seller is the obvious dependency; the dispatcher who knows every customer's site access, or the estimator who prices everything above a certain size, are the ones that surface in a one-to-one round in weeks two to four and that nobody writes a plan for.

Of the four things in the seller's head, pricing is the one that resists documentation hardest, because it is not a rule set — it is a set of judgements about specific customers, accumulated over decades, including which ones will tolerate what and which relationships are worth protecting at a discount. Extracting it looks like walking the customer list account by account and asking why this one is priced the way it is. The answers are frequently 'because of something that happened in 2009', which is exactly the information you need and exactly the information that never appears in a handover document.

Two adjacent facts make this urgent rather than optional. Practitioners consistently observe that businesses bought from a long-tenured owner are under-priced, because the owner stopped raising prices somewhere along the way. That is a convention of the trade rather than a measured statistic and we label it as one — but it means the pricing conversation with the seller is also a value conversation, and it has to happen while they are still there to explain the history.

The team is watching this transfer closely and reading it as a signal about you. An inherited team is still loyal to the previous owner in the first months, which is normal rather than a problem, and the fastest way to convert that loyalty into something workable is competence in front of them — including on the customers they know the seller handled personally. Building bench depth behind those relationships is the durable version of the fix: the goal is not that you personally replace the seller, it is that no single person is the business again.

This is the seat the transition literature does not describe. The standard taxonomy assumes a hired executive with a boss and a mandate; the acquirer has neither, owns the downside, and is simultaneously learning the business and being evaluated by it. Treating the seller transfer as an onboarding exercise rather than as the central operating risk of year one is the most common way a profitable acquisition becomes a difficult one.