ADAMAS Blog
Decision Documentation: The Due-Diligence Question You Can't Answer From Memory
Somewhere in your second or third diligence meeting, after the financials have been picked over and the customer concentration has been discussed to death, someone on the other side of the table asks a question that sounds harmless: "Why did you decide that?" Why that pricing change in year three. Why that CTO and not an agency. Why you walked away from the biggest contract you were ever offered. And in most founder-led companies, the honest answer is a pause, a glance at the ceiling, and a reconstruction from memory — because there is no record. There never was.
Diligence isn't auditing your outcomes. It's auditing your judgment.
Founders tend to assume that diligence is about results: show the revenue, show the retention, show the margins, done. But results are already in the data room. The buyer can read a P&L without your help. What they cannot read anywhere is the quality of the decision-making that produced those numbers — and that's the thing they're actually buying, because it's the thing that will produce the next five years of numbers, possibly without you in the building.
So they probe rationale. Not because they expect every decision to have been right — experienced acquirers know better — but because the pattern of reasoning tells them whether the good outcomes were judgment or luck. A founder who can show that a failed bet was made for sound reasons, with the alternatives weighed and the risk priced in, is more credible than one who can't explain a successful bet at all. A documented wrong decision is, oddly, worth more in that room than an undocumented right one.
What "we'd have to ask the founder" actually signals
At some point during diligence, the question gets asked while you're not in the room — to your head of sales, your operations lead, whoever they can get an hour with. And the answer they often get is some version of: "You'd have to ask the founder." Said once, it's nothing. Said five times, it's a finding.
What it tells the buyer is that the company's judgment is not an asset of the company. It's an asset of one person — a person who, after the deal closes, has both the money and the motive to leave. Buyers don't ignore that risk; they price it. In practice that tends to show up as longer earn-outs, heavier key-person clauses, more money held in escrow, or simply a lower number, because the thing they wanted to buy turns out to be partially un-buyable. None of this appears as a line item labeled "founder's memory." It just quietly shapes the structure of the deal against you.
The decisions that get probed
You can't predict every question, but in our experience the same categories come up again and again, because they're the ones where reasoning matters more than the outcome:
Pricing changes. "You raised prices twice and lowered them once. Walk us through each." They're testing whether your pricing reflects a theory of your market or a series of reactions to whoever complained loudest.
Key hires — and the ones that didn't work. Why this person, what the alternatives were, and what you learned when a senior hire failed. A company that can't explain its own hiring decisions can't convince anyone it will hire well after the founder steps back.
Declined contracts and walked-away deals. Often the most revealing category. The contracts you turned down define your strategy more sharply than the ones you signed — if you can still explain why you turned them down.
Technology and vendor choices. Why this stack, why this platform, why you built instead of bought. The buyer's technical team will inherit these decisions, and "the developer who chose it left two years ago" is not an answer that builds confidence.
Building the record when you don't have one
If diligence is a realistic prospect in the next year or two, you have two jobs: reconstruct backwards and capture forwards.
Retroactively: the 90-day reconstruction
You cannot reconstruct everything, and you shouldn't try. Instead, over roughly 90 days, identify the 20 or so most material decisions of the past few years — the ones that moved revenue, headcount, product direction, or risk — and write each one up properly: the context that was true at the time, the options on the table, why the winner won, who made the call, and what happened next. Mine your own exhaust for evidence: old board emails, proposal drafts, meeting notes, Slack threads. Date the write-ups honestly as reconstructions. A buyer will respect a clearly-labeled retrospective record far more than a suspiciously pristine one — and far more than your memory under pressure.
Prospectively: the weekly decision review
Going forward, the habit is simpler than most founders expect. Once a week, ask one question: what did we decide this week that we'd struggle to explain in two years? Most weeks the answer is one or two decisions. Write each one down in a consistent format — decision, date, owner, context, alternatives rejected, trade-off accepted, and what would have to change to revisit it. A few honest paragraphs. The discipline isn't writing a lot; it's writing it now, while the reasoning is still true, instead of reconstructing it later when it has quietly mutated into a better story.
Do both, and the diligence dynamic inverts. "Why did you decide that?" stops being a memory test and becomes a link you send. The buyer's finding changes from "judgment concentrated in founder" to "decision-making is documented and transferable" — which is, in plain terms, the difference between buying a company and buying a person.
FAQ
Why do diligence teams ask about decision rationale, not just results?
Because they are buying future decisions, not past ones. The numbers tell them what happened; the reasoning tells them whether the judgment that produced those numbers is repeatable, transferable, and likely to survive the founder stepping back. A good outcome with no visible reasoning could be skill or could be luck — and diligence exists to tell those apart.
What does "we'd have to ask the founder" signal to a buyer or investor?
It signals that the company's judgment is not an asset of the company — it's an asset of one person who may leave after the deal. That typically translates into longer earn-outs, heavier key-person clauses, more escrow, or a lower price, because the buyer has to insure against the founder walking out with the reasoning.
Is it too late to build a decision record if diligence is only months away?
No. A retroactive reconstruction is still worth doing: over roughly 90 days, identify the 20 or so most material decisions of the last few years and write up each one — the context at the time, the options considered, why the chosen path won, and what the result was. Honest reconstruction, clearly dated as such, is far stronger than answering from memory in the room.
What should a single decision record contain?
The decision itself, the date, who made it, the context that was true at the time, the alternatives considered and why they were rejected, the trade-off accepted on purpose, and what would have to change for the decision to be revisited. A few honest paragraphs per decision is enough — the structure matters more than the length.
How is a decision ledger different from a data room?
A data room holds artifacts — contracts, financials, cap tables — which document what was agreed. A decision ledger documents why. The two answer different diligence questions: the data room proves the company's facts, the decision ledger proves the company's judgment. Most companies show up with only the first.
If you want the full method — the record format, the 90-day reconstruction plan, and the weekly review — it's in The Decision Ledger Playbook, our free guide to building a decision record your company can actually stand behind in diligence. To see what a working decision ledger looks like in practice, try the interactive demo.
Related reading: When Your Company's Knowledge Lives in One Person's Head