Why Reference Calls Matter
Reference calls reveal what no pitch deck or data room can: character, leadership style, and blind spots. GitDealFlow's engineering data tells you what the team ships; reference calls tell you how they ship it.
A founder's former colleagues, managers, and reports will tell you more in 30 minutes than hours of product demos.
Who to Call
3-5 references minimum: a former manager, a former peer, a former direct report, a current employee, and a customer (if the startup has revenue).
Also call 1-2 references the founder didn't suggest, this catches blind spots the founder's network won't surface.
What to Ask
Would you work with this founder again? (Watch for hesitation.)
What are their blind spots? (The honest answer tells you more than any strength.)
How do they handle bad news? (Founders who hide problems are dangerous.)
Why did they leave their last company? (Alignment? Ambition? Frustration?)
What's the hardest challenge they've overcome? (Resilience is the #1 founder trait.)
Context: Where This Fits
This explainer is part of a library built on a single dataset: public engineering activity across 350+ startup GitHub organizations, 15 sectors, refreshed weekly. The through-line is that deal flow signal is earliest in code: breakout teams appear 21 to 47 days before their round is public. Concepts on this page are defined precisely because imprecise vocabulary is what makes sourcing decisions unfalsifiable.
Continue Learning
- What is commit velocity
- Code-Side Sourcing: the named category
- Glossary: every term in the library
- Learn hub: all explainers
A practical read-through of How to Do Reference Calls Like a VC: the dataset behind this page refreshes weekly across 350+ organizations and 15 sectors, and every figure shown traces to a public GitHub REST API pull. That matters for two reasons. Reproducibility: any number here can be re-derived from primary sources, which is the standard the published methodology sets for itself. Timeliness: engineering acceleration precedes announcements, so this page follows the data cadence rather than the news cycle, and the freshness endpoint always reports the exact pull date.
If How to Do Reference Calls Like a VC is your entry point, the fastest next steps are fixed: skim the glossary for the three or four terms that anchor the topic, open the research dataset to see the raw weekly snapshots behind the summary numbers, and run one live query against the free momentum checker with a company you already know well. Seeing the signal fire on a familiar name is the quickest way to judge whether code-side sourcing belongs in your own workflow.
Frequently Asked Questions
How many references is enough?
3-5 for pre-seed/seed, 5-10 for Series A+. Include at least one reference the founder didn't suggest.
What's a red flag in references?
Vagueness ('they were fine'), excessive praise lacking specifics, or references who won't return your call.
Should I check references before or after meeting the founder?
After. Meet the founder first to form your own opinion, then validate with references.