A lot of people treat due diligence like a scavenger hunt for reasons to kill a deal.
I think that’s backwards.
At the early stage, due diligence is mostly about verifying the story you’ve been told and making sure you understand the risks you’re actually taking. Not every issue is fatal. In fact, finding an issue often means the process is working.
That distinction matters.
If I’m looking at a young company, I’m not expecting pristine financials, airtight operations, and a perfectly organized data room. I’m trying to answer a simpler question:
What do I know, what don’t I know, and which unknowns can hurt me later?
That’s a much better lens than “is everything perfect?”
A few things stood out to me.
First, early-stage diligence should be proportional to check size.
This is where I see a lot of bad process on both sides. Founders assume investors want enterprise-grade diligence at pre-seed. Investors sometimes forget that spending $15k–$25k on diligence for a small check is bad capital allocation.
The math has to make sense.
When the check is small, the company is young, and the business is still finding product-market fit, I’m not looking for a 200-point diligence exercise. I’m looking for confidence in the few things that drive the outcome.
Usually that means:
- the team
- the market
- the basic legal structure
- ownership of the IP
That’s the real backbone.
Second, at the earliest stage, the team carries more weight than the model.
As a finance person, I don’t say that lightly.
But pre-seed projections are usually not decision-grade. A spreadsheet can tell me what management hopes happens. It cannot tell me much about what will happen. If there’s barely any operating history, I’m not pretending a discounted cash flow model is serious analysis.
What I care about more is whether the founders can think clearly when challenged.
If an assumption is wrong, do they get defensive? Or do they update?
If the market is smaller than they claimed, can they reason through it?
If the first product direction isn’t working, can they pivot intelligently?
That’s not a soft metric. That’s an operating metric for founder quality.
Third, legal basics matter more than many founders realize.
I spend a lot of time translating this for non-finance founders: if the legal plumbing is broken, the economics on paper may not be real.
A cap table isn’t “right” because it looks tidy in Excel. It’s right because the underlying documents support it.
If stock wasn’t properly authorized, if board approvals are missing, if option grants were handled incorrectly, if IP was never assigned to the company, then you can end up with a company that looks investable until someone serious checks the file.
And when that happens, cleanup gets expensive.
That’s why I always come back to a very practical founder question:
If I wire money into this business tomorrow, am I funding growth or am I funding legal remediation?
Those are very different uses of capital.
I also liked the reminder that missing information doesn’t automatically kill a deal.
That’s a healthy way to think about diligence. Especially in startups, some gaps can be fixed post-close. Some can be handled with additional terms. Some should absolutely stop the process.
The skill is knowing the difference.
In my world, I’d frame it like this:
Red flags are not all equal.
A missing signature on an important document? Fixable.
A messy but understandable data room? Annoying, but fixable.
No clear stock ownership records? Bigger problem.
Core IP sitting with a founder instead of the company? Very big problem.
A founder who is evasive when challenged? Usually the biggest problem of all.
That last one tends to compound.
One more point I think founders should hear: organization is part of diligence.
Not because investors care about neat folders for their own sake, but because operational discipline shows up in small ways before it shows up in big ways. If a company can’t organize its core legal and financial records, I start wondering where else the sloppiness lives.
And for founders raising before Series A, the bar is not impossible. You do not need a bank-grade data room. You do need a clean, labeled repository with the basics easy to find.
That alone increases trust.
My takeaway is simple: due diligence is not about proving a startup is flawless. It’s about making risk legible.
For investors, that means focusing on the few items that can truly impair returns.
For founders, that means getting the basics right before a lead investor finds the gaps for you.
If I had to reduce early-stage diligence to one sentence, it would be this:
Don’t try to verify everything. Verify the things that, if wrong, change the deal.
That’s usually enough to make better decisions without confusing activity for rigor.