Somewhere around week six of a sell-side process, a particular kind of quiet sets in. The teaser went out, the NDAs came back, the IM is with eight buyers, and two of them asked questions nine days ago that have not been answered yet. Nobody has lost the deal. Nobody has done anything wrong. And the process has already started to cost the seller money.
I want to make the argument plainly, because I think it is the most underweighted thing in a sell-side mandate: the price a seller achieves is a function of competitive tension, and competitive tension is a function of pace. The equity story, the model and the buyer list set the ceiling. Pace determines how much of that ceiling survives to signing.
Attention is allocated, not won
The reason pace matters is not that buyers get bored. It is that a buyer is not evaluating your asset in isolation. A corporate development team is carrying six or seven live situations. A mid-market fund is looking at more. Internally, each of those is competing for the same scarce resources: analyst hours, an investment committee slot, the partner who has to sponsor it.
A process that answers questions within a day stays near the top of that list, because it is the one that is moving and therefore the one where work produces progress. A process that goes quiet for a week and a half does not get rejected. It gets reclassified as the thing to pick up when they come back to us. That reclassification is invisible from the seller’s side, and it is where most lost tension actually goes.
The consequence shows up later and looks like something else. Two buyers drop out before the IOI deadline for reasons unrelated to the business. The remaining bidder works out that they are the remaining bidder. The seller is now in a bilateral negotiation with someone who knows it, and the price reflects that. Not because the asset changed, but because the field thinned while the process was waiting on an answer.
The gaps are not laziness
Here is what I did not expect when I started looking closely at where those nine days go. The teams are not slow. They are reconciling.
A buyer asks why the gross margin in the IM differs from the figure implied by the management accounts in the data room. Answering that honestly means going back to the source documents, finding which of the two is on the old basis, checking whether the model picked up the revision, and then deciding whether the IM paragraph needs rewriting too. That is not a five-minute reply. On a mandate where three people have touched the numbers over four weeks, it can take two days, and most of those two days are spent re-establishing something the team already knew once.
Multiply that by eight buyers asking variations of the same question. Then add the revision cycle: an assumption changes in week four, the model is updated, and now the IM, the teaser follow-ups and whatever was sent to which buyer are all slightly out of step with each other. The team is not idle during the silence. It is doing archaeology on its own work.
That is why I think of document integrity as a process-speed problem rather than a quality problem. The quality argument for a single verified fact base is obvious and a bit abstract: fewer errors, better credibility. The speed argument is concrete and shows up in the price. If every figure in the IM, the model and the teaser traces to a source and moves together when the source moves, then a buyer question is a lookup instead of an investigation, and the answer goes back the same afternoon.
Momentum is not haste
The honest counterargument is that speed is also how processes get damaged, and anyone who has watched a mandate launch with a half-built data room knows it. A teaser that goes out before the model is defensible produces exactly the credibility problem I have just argued against. Buyers read haste as inexperience, and an advisor who has to retract a figure in week three has lost more than the nine days of silence would have cost.
So the distinction matters. Preparation should be deliberate: the data room ready before launch, the model reviewed, the risks framed before a buyer finds them. What should be fast is everything after launch. Preparation is where thoroughness pays. Response time is where it costs.
Most firms have this exactly backwards, through no fault of their own. They go to market before the documents are solid because the client is impatient, and then they are slow for the rest of the process because the documents were never solid. The front-loaded version is harder in week one and easier for the following three months.
What to actually measure
Boutiques track hours and deliverables. Neither of those tells you whether a process is losing tension. Three numbers do:
Response latency per buyer question. Not the average. The worst one, and who it belonged to. The buyer who waited longest is the buyer most likely to go quiet, and the one you will hear about last.
Time from IOI to management meeting. This is the window where a field of five becomes a field of two, and it is almost entirely within the advisor’s control. Every week in it is a week for a buyer’s internal priorities to shift.
Time from a number changing to every document reflecting it. If this is measured in days, the process has an unavoidable floor on how fast it can answer anything. If it is immediate, the floor disappears.
None of the three is hard to track. They are simply not the numbers anyone writes down, which is why a process can be losing its leverage for a fortnight before it is visible in anything a partner reviews.
A process does not lose tension because buyers lost interest. It loses tension because nobody answered for nine days, and the nine days were spent working out which version of the truth to answer with.
NaS_OS builds the teaser, the IM and the model from one verified fact base, so a buyer question is a lookup rather than an investigation and a changed number moves every document at once. If you want to see that on your own mandate, apply for access.