I thought I knew our business cold going into diligence.
Then the data room questions arrived, and a few of them made me sit back and go, “Huh. Yeah. That is a fair ask. Why did we never write that down?”
Surprise in diligence is rarely about a secret scandal. It is about the gap between how you operate and how you document operating.
The questions that caught me off guard
Not the vanity metrics. The connective ones.
Cohort edges. Not “what is retention,” but “why does this thin cohort behave differently, and is that a product issue or a channel issue?”
Human single points of failure. “If this person is out for two weeks, what breaks?” We had answers in our heads. We did not always have answers in a folder.
Definition drift. Two dashboards using similar words for slightly different calculations. Nobody was trying to mislead. We had grown faster than our glossary.
Customer success folklore. The real playbook lived in call recordings and Slack habits. Buyers wanted the playbook as an artifact.
Vendor concentration. Which tools were conveniences versus load-bearing walls. Easy to under-describe until someone asks what happens if that vendor has a bad quarter.
Why surprises happen even to honest teams
Because companies run on partial attention.
You fix the loud problem. You postpone the tidy explanation. You tell yourself you will document the edge case after the launch. Then diligence shows up and asks for the edge case with a timestamp.
Honesty without packaging still looks like confusion from the outside. Packaging without honesty looks like spin. You need both.
How we answered without getting weird
We used a pattern that saved us:
1. Restate the question in plain language to confirm we heard it. 2. Give the direct answer with the best available number or artifact. 3. Name the limitation of the data in one sentence. 4. Provide the operating context so they do not invent a worse story. 5. Log the Q&A so the next ask does not restart from zero.
That fifth step matters. Diligence repeats. Memory should be institutional, not heroic.
The emotional part
Surprising questions can feel like accusations. They are usually curiosity with a checklist.
I had to coach myself: curiosity is not condemnation. If I get defensive, you make a clean question expensive. If I get crisp, you make trust cheap.
Buyers remember how you handle uncertainty. “We do not know yet, here is how we will get it by Thursday” beats a improvised masterpiece.
What we changed after
We tightened metric definitions. We wrote the “bus factor” notes for key workflows. We made the customer lifecycle description match what people actually do on Tuesdays.
In other words, diligence made us operate more like the company we already claimed to be. Annoying. Valuable.
Data room surprise checklist
- Glossary for every metric that appears in a deck
- One lifecycle narrative with real artifacts linked
- Explicit list of load-bearing vendors and people
- Exception log for known messy segments
- Rehearsed answers for the top twenty likely asks
The real surprise
The biggest surprise was not a single question. It was realizing how much of our competence lived in oral tradition.
It was a good business with real operators. Diligence asked us to prove it in files. Files are boring. Files are also how trust scales beyond a room of people who already believe you.
If you are prepping a sale someday, hunt your own surprises first. Be the first person to ask the awkward question. It hurts less when you are the one holding the pen.
Practice questions before the real ones
Before diligence got intense, we should have run a mock buyer session with a friend who likes awkward questions.
We did some of that late. Earlier would have been kinder. The surprises shrink when you rehearse being surprised.
Bottom line
If you ever prep a process like this, invite one skeptical operator to beat up your data room while the stakes are still internal. Pay them in gratitude and lunch.
