Investor diligence on founders runs on two tracks: the documented one — background checks, reference calls, cap-table review — and the judgment track, where a partner estimates whether this person converts money into compounding progress. The formal track filters; the judgment track decides. Founders who understand both negotiate better, because they stop optimizing the checklist at the expense of the impression. Honey Badgers publishes information, not investment advice, and the practices below reflect commonly described venture process, which varies firm to firm.
What does the formal track actually check?
Four workstreams. Background checks: identity, litigation, sanctions, press — run through third-party firms for anything beyond seed. Reference calls: typically three to eight, and the ratio that matters is unsolicited references — people the investor already knew, called without the founder's list — to the curated ones. Data verification: billing and banking records sampled against claimed metrics, because 'vanity metrics vs billing truth' is the oldest gap in decks. And the co-founder check: are the equity split, vesting, and role boundaries written and stable, or is the split a handshake that predates the difficult year.
What are investors listening for in reference calls?
The questions are behavioral, not evaluative: what happened when the company nearly died, how the founder handled a disagreement with a co-founder or customer, whether they would work with or for this person again. The answers investors describe as disqualifying are consistent: surprise at the founder's behavior under stress, hedged endorsements ('brilliant, but…'), and references who learned the venture had been struggling from the investor's call. Founders should prepare their references for honesty rather than advocacy — investors weight the flaws a reference volunteers and contextualizes far above the flaws a reference conceals and the investor discovers.
How does the 'learning velocity' judgment work?
The trait investors most consistently describe backing is rate of learning: how much the founder's understanding of their market has compounded between meetings weeks apart. It is probed directly — 'what have you learned since we last spoke,' 'what did you get wrong last quarter' — and indirectly through artifact quality: whether the deck, the metrics review, and the board materials improved measurably between rounds. Founders who present a clean narrative with no revised beliefs read as either early or rigid; founders who can name what they changed their mind about, and why, read as compounders. The 'I don't know, here is how I'd find out' answer, delivered without flinching, is documented investor folklore for a reason: it is the single most credible thing a founder can say in a diligence meeting.
What role does founder-market fit play?
Investors assess whether the founder has an unfair edge — distribution, technical depth, lived experience with the problem — because at equal execution, edge decides outcomes. The probe is provenance: why this problem, why you, why now. The strong answers are biographical ('I spent six years inside this workflow and built the internal tool first'); the weak answers are opportunistic ('this market is large and growing,' true of every market ever pitched). For technical founders, the equivalent check is depth on the actual hard problem — investors bring in an expert call specifically to test whether the claimed technical moat survives twenty minutes with a specialist.
What are the documented red flags?
Across investor writing and postmortem literature, the recurring ones: metric inflation discovered in verification — the fastest kill there is; co-founder tension visible in the meeting itself, where partners watch who answers which questions and whether corrections are exchanged comfortably; a cap table that reveals a departed co-founder with a large unvested stake and no agreement on it; blame allocation — a founder whose previous failures are entirely someone else's; and inconsistency between the story told to different partners at the same firm, which firms compare notes on deliberately. None of these is individually fatal except the first; together they form the pattern the judgment track prices.
How should founders prepare?
Treat diligence as a product launch for trust: get the data room complete before the first partner meeting; brief references honestly, including the difficult chapters; align co-founders on who owns which answer; know your metrics to the billing record, not the dashboard; and keep a written list of what you have learned and changed your mind about each quarter — it is the raw material for the strongest signal you can send. The formal track is table stakes. The judgment track is won by founders who make it easy to verify the truth and comfortable to hear it.
Diligence is not an exam with hidden answers; it is an estimate of compounding. The founders who understand that stop performing and start demonstrating.
For more context, read Technical vs Non-Technical Founders: How the Split Works.
For more context, read co-founder conflict resolution.
For more context, read Angels vs VCs: A Founder's Comparison.