The buyer's diligence lead was on speaker. She had a page of the founder's board pack open in one browser tab and a quality-of-earnings query from her associate open in another.
"These two ARR numbers do not reconcile," she said. "One is on your board slide from April. One is in the file you sent us last week. Help me understand."
The founder started to explain. Halfway through the explanation he realised he did not know which of the two numbers was right. His CFO was in another call. His head of finance was on holiday. The board pack was drafted by his COO nine weeks earlier and nobody had been asked to reconcile it against anything since.
The buyer was already writing something down. Not the reconciliation. The response time.
A buyer runs diligence as a series of readings. Your pitch, your board papers, your accounts, your customer contracts, your product, your data-room index, and your answers when they ask about any of them. Conviction rises when those readings agree and falls when they do not. That is the first idea the Ortent Diligence Radar rests on, and it is the one that catches most founders off guard. The point is not that your strategy must never change. Strategy should change, and buyers want to see a company that adapts. What must stay stable and provable is the evidence base, the metric definitions, the ownership record, the contract terms. Unexplained change is the killer, not change.
The second idea is that speed is a signal. In a competitive process the buyer is reading your operation through the diligence itself. Fast, accurate, consistent answers say the evidence was ready and the company is run well. Slow answers that arrive in pieces and do not quite reconcile say the opposite, and they say it about how you will run after completion. The buyer is not being unfair when they take a slow answer as a governance signal. They are being predictive.
The third idea is that readiness is built in, not bolted on. The same discipline that makes diligence fast is the discipline that makes a business good: metrics that reconcile, contracts you can find, data you have the right to use, controls that run. You do not build any of that for the buyer. You build it because it is how a serious company operates, and the transaction value is a return on work you should be doing anyway.
Response time is not administration. It is the buyer watching you work.
The radar keeps its scoring tied to evidence rather than to confidence through four rules. Every readiness score names its proof. Not a policy title. The actual artefact: the signed document, the reconciled export, the dated test result, the approval trail. No artefact, no score above the middle of the ladder. Silence is not readiness and it is not a low score. If a domain has no evidence behind it, it is marked not ready, and the report says the evidence is missing rather than guessing at a number. A policy is not proof. A company that has written an AI policy, a security policy or a data-retention schedule has not, by that act, done the thing. Where a control appears only as a document with nothing showing it runs, readiness is capped low. And nothing is invented. A plan dated in the future is a plan, not a result. A certificate in progress is not a certificate. A claim in a pitch deck is not a fact until a record stands behind it.
These rules cost comfort. They will show gaps a founder would rather not see. That is the point. The buyer will find them either way. Better to find them first, while the people who can fix them are still in the building and still take your call.
The rule that binds the whole story together is the one about claims. Every categorical claim on your product, autonomous, AI-powered, an accuracy figure, a bias reduction, a compliance status, needs a substantiation file behind it. That was housekeeping in 2023. It became enforcement risk through 2025 and 2026 as the SEC and FTC brought AI-washing cases including business-to-business ones. A buyer inherits the exposure from the day of completion. A claim you cannot evidence in your own marketing is the fastest way to break the consistency the whole deal rests on. AI-washing is not a marketing choice any more. It is a diligence finding waiting to be made.
Three readers should carry this away.
The founder or CEO should read the radar as a rehearsal. If your evidence base cannot survive a friendly reading now, it will not survive a hostile one later. The domains where you cannot answer inside five minutes with a document open are the domains that will move the price.
The board or NED should read it as a governance instrument. Ask the same questions a buyer will ask. Show me the reconciliation. Show me the substantiation. Show me the response time on our last three regulatory requests. The board that reads the evidence rather than the summary is the one that surfaces the quiet defect early.
The PE operating partner should read it as portfolio hygiene. The gap between the pitch and the file is where value leaks. Set the standard at portfolio review, not at signing.
Score your company at ortent.co/tools/diligence-radar. The whitepaper carries the argument. The self-scoring prompt runs the exercise from your own evidence. And if you want a second read before a raise or a sale, ortent.co/contact.
Diligence is not a document review. It is the buyer watching you work.