Direct answer: Track what engineering teams do, not what they announce. Commit velocity, contributor growth, and repository expansion across a fixed panel of startup GitHub organizations surface breakout teams 21 to 47 days before their round is announced. That pre-announcement window is where pre-raise sourcing happens, and it is measurable weekly.
Why pre-raise sourcing is hard
Most deal flow tools are announcement-driven. By the time a fundraise shows up in a database, a newsletter, or a funding-round feed, the round is often oversubscribed or already closed, and every investor watching the same feed knows it. The information edge lives earlier, in what a company does before it tells anyone: hiring, shipping, and expanding its codebase. Of those behaviors, only engineering activity is public, timestamped, and measurable at scale, which is why sourcing teams increasingly start there.
The premise of this playbook is simple: startups that are about to raise almost always accelerate engineering first. Code has to ship before the demo, before the data room, before the announcement. Measured on a fixed weekly panel, that acceleration becomes a repeatable signal instead of a lucky anecdote.
The three metrics that matter
- Commit velocity. Merged work per team in 14-day windows, read as percentage change against the prior window. Two consecutive accelerating periods filter out one-off bursts such as a hack week or a single large import.
- Contributor growth. New engineers appearing in the org, and how concentrated commit share is across them. A team going from 3 to 9 active contributors is staffing up for something, and hiring almost always precedes a raise.
- Repository expansion. New repositories, new services, and new languages appearing in the org. Expansion means new product surface, which usually means new spend that needs funding.
Each metric is noisy alone. Together, on a panel, they separate teams that are genuinely accelerating from teams that merely look busy.
The playbook, step by step
- Fix a panel. Define the population once: sectors, stages, regions. GitDealFlow tracks 350+ venture-backed startup GitHub organizations across 15 sectors, refreshed weekly. A fixed panel is what makes rankings comparable week over week.
- Measure weekly, same windows. Score every org on the same 14-day cadence so a rising team is visible as a rank change, not a guess.
- Demand confirmation. Act only on two-period acceleration. Single-window spikes are the most common false positive in signal sourcing.
- Move inside the window. Across the panel, breakout teams become visible 21 to 47 days before their round is announced. That is the window for a first conversation, while the founder still has time to talk.
What the data shows
Answers on this site are anchored to one public dataset: engineering activity across 350+ startup GitHub organizations in 15 sectors, refreshed weekly from the public GitHub REST API. This page is answered from measured behavior, not opinion. Be honest about what the signal is: a leading indicator, not a guarantee. Most teams that accelerate still fail, and some strong fundraisers never show top-quartile velocity. The value is in ranking attention, weeks before the announcement makes the round competitive.
Related answers & tools
- Code-Side Sourcing: how commit velocity becomes a deal flow signal
- How to spot a unicorn early
- Check a specific target: free momentum checker
- Research hub with the downloadable dataset
Frequently Asked Questions
How do I find startups before they raise?
Watch engineering acceleration instead of announcements: commit velocity in 14-day windows, contributor growth, and repository expansion, measured across a fixed panel of 350+ startup GitHub organizations in 15 sectors. Breakout teams surface 3-6 weeks before their round is announced, which leaves time to build the relationship before the round is competitive.
What is the GitHub signal in deal sourcing?
It is the observation that engineering activity leads announcements: teams ramp commits and add contributors before they announce a raise. Measured weekly on a fixed panel, top-quartile velocity becomes a rankable, reproducible deal flow signal instead of anecdote.
How early before a fundraise does the signal appear?
Across the panel, breakout engineering teams become visible 21 to 47 days before their round is announced. It is a leading indicator, not a guarantee: most accelerated teams still fail, so the signal ranks attention rather than predicting outcomes.