Pre-Seed Scouting With GitHub Signals: Finding Startups Before Their First Announcement
How to scout pre-seed startups using public GitHub signals, including the thin-footprint caveat that makes pre-seed a verification game rather than a discovery game.
Key Takeaway
Pre-seed is the hardest stage to scout because the public footprint is thin. This post explains what GitHub activity does and does not reveal at pre-seed, why the signal is verification rather than discovery, and a workflow for combining it with the channels that do find pre-seed companies.
Pre-seed is where the scouting model breaks down first, for a simple reason: there is almost nothing public to read. The team has not announced, the press has not written, and the code footprint is thin.
Understanding that limitation is what separates a useful pre-seed workflow from a wasted one.
Why Pre-Seed Is the Hardest Stage#
At pre-seed, a startup is two to four engineers, often working partly in private repositories. The public footprint is thin by definition, and the engineering signal that is discovery-grade at Series A is too weak to surface a company cold at pre-seed [1].
What Public GitHub Shows at Pre-Seed#
What it does show is whether a team is real and whether it is shipping. Consistency matters more than volume: a founder who commits regularly at low absolute counts is a stronger signal than a burst followed by silence. Contributor breadth tells you whether it is a solo founder or a team, and repository activity tells you whether the product story matches the code [3].
Verification, Not Discovery#
The honest framing is that public GitHub activity at pre-seed is a verification tool, not a discovery tool. Use it to confirm that a founder you met through a community, a referral, or an accelerator is actually building, not to find the company in the first place [2].
A Pre-Seed Scouting Workflow#
Source through the channels that do find pre-seed companies: communities, referrals, accelerators, and founder circles. When a founder surfaces, run a free public pass on their GitHub before you spend a meeting. Check that the team is real, the product story matches the code, and the shipping is consistent.
The Early-Warning Use#
There is one case where the pre-seed signal is worth tracking proactively: acceleration. When a pre-seed team you already know begins to accelerate, they are usually deploying capital or approaching a round, which is exactly the moment a scout wants to be in the conversation [1].
Pre-seed scouting is hard because the record is thin. But the cheapest check in the stack, a public GitHub pass, is also the one that keeps you from wasting a meeting on a team that is not actually building.