What I Am Actually Looking for in Due Diligence

I have walked away from deals I genuinely wanted to close. Good market, solid traction, a compelling vision. The pitch was strong enough that my team was ready to move forward. Then we started asking questions.

Most founders prepare for due diligence the way they prepare for an exam. They build the data room, organize the financials, clean up the cap table. They rehearse answers about unit economics and customer retention. This preparation matters. But it is not what I am actually testing.

What the documents tell me is never just about the documents

When a founder sends over a well-organized data room on time, I note it. When they go quiet for two weeks after promising materials by Tuesday, I note that too. When the revenue figures in the pitch deck do not match the financial model, my first reaction is not to calculate the discrepancy. My first reaction is to think about every other conversation we have had.

Due diligence reveals how a founder runs their company. The documents are a byproduct of daily operations. If the numbers are inconsistent, that inconsistency existed long before we started asking for it.

Bad news is manageable. Ambiguity is a more dangerous problem. A founder who says "our churn is 8%, here is exactly why, and here is what we changed" is a founder I can work with. A founder who says "it is around 7 or 8, maybe a bit higher in some cohorts" is one I cannot. Unclear answers suggest the founder does not fully understand their own business. Research across M&A and venture consistently shows that nearly half of all deals that enter due diligence do not close, and the reason is almost never valuation. It is because something unexpected surfaces and confidence breaks down.

The cap table shows how a founder makes decisions under pressure

A complicated cap table is rarely the result of negligence. It is the result of decisions made quickly, often in moments of financial stress. Early investors holding too much equity. SAFE notes with no clear resolution path. Co-founders without vesting schedules. Each of these is a choice someone made, and each tells me something about how the business will be run going forward.

I pay close attention to whether the founder can walk me through the full history of those choices. A founder who owns the complexity, explains the reasoning, and has a plan to resolve it is showing me something valuable. A founder who seems surprised by the questions is telling me they have not looked at this picture clearly themselves.

The clearest signal is how a founder handles the moment something goes wrong

In nearly every process, something surfaces. A customer who accounts for a larger share of revenue than the deck suggested. A technical dependency that was not disclosed. A legal matter still outstanding.

What matters is not that the issue exists. What matters is how the founder responds when I raise it. Some get defensive. Some immediately pivot to reassurance. The ones I trust say: "Yes, here is the full picture. Here is how we are thinking about it."

That response tells me more about execution than any financial model. It also tells me whether I would want to be on the phone with this person during a difficult quarter two years from now.

What I am really evaluating is a long-term partnership

When a process closes, the work begins. The market shifts, the original plan changes, and there will be quarters where things do not go as hoped. What I am really trying to understand in due diligence is whether this founder and I can navigate those moments together.

The founders who come through diligence cleanly are rarely the ones with the most polished materials. They are the ones who treat the process as a professional introduction. They answer hard questions honestly. They do not manage information. They run their business in a way that makes documentation straightforward.

If a founder can do that under the scrutiny of an investor, they can usually do it under the scrutiny of a difficult year.