The 10-Point Framework
1. Problem, Is this a real problem people will pay to solve? 'Nice to have' ideas don't make venture returns.
2. Solution, Does the solution actually solve the problem in a unique way? GitDealFlow checks: is the team building something defensible?
3. Market Size, Is the TAM $1B+? Bottom-up: how many customers × price?
4. Product, Is there a working product or compelling prototype? Screenshots > wireframes.
5. Traction, Revenue, users, engineering velocity (GitDealFlow), or partnerships. Show growth rate, not just absolute numbers.
6. Business Model, How does the startup make money? Unit economics matter more than revenue (LTV/CAC, payback period).
7. Competition, Honest competitive landscape. No 'no competition' claims.
8. Team, Why are these founders the best team? Domain expertise + execution track record.
9. Financials, 3-5 year projections with clear assumptions. GitDealFlow can validate if the engineering team is on track.
10. Ask, How much are they raising and what will they spend it on?
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 Evaluate a Pitch Deck: 10-Point Framework: 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 Evaluate a Pitch Deck: 10-Point Framework 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
What makes a great pitch deck?
Clear problem, compelling solution, massive market, real traction, and a world-class team. GitDealFlow's engineering data validates the traction claim.
How many slides should a deck have?
10-15 slides. Pitch decks should be 10-15 minutes. Long decks signal unclear thinking.
Should I read the full deck or listen to the founder?
Both. The deck tells you what they want you to know. The founder tells you what they believe. GitDealFlow's data tells you what's actually happening.