How to Build a Startup Watchlist
Most startup watchlists are graveyards: names get added, nothing gets tracked, and no check ever happens. This method turns a watchlist into a working pipeline by attaching a momentum signal to every name and a weekly review to the process.
Step 1: Pick your watchlist criteria
A watchlist is only useful if it is smaller than your attention span. Decide up front what earns a spot: thesis fit, sector, stage, and a concrete momentum threshold. If a team does not meet the bar, it does not go on the list.
The criteria should be written down. Vague lists grow until they are unusable; explicit criteria keep the list honest and make the weekly review a series of yes-or-no decisions.
Step 2: Add and rank candidates
Every candidate gets a score, not just a name. Rank on the dimensions that predict your success: momentum trend, team quality, market, and access. The ranking matters because it decides where your limited outreach time goes.
A simple three-tier ranking (A: reach out this week, B: track, C: parked) keeps the list actionable. Most names should be B or C; the A tier is your actual pipeline.
Step 3: Track momentum week over week
The watchlist only earns its keep if you watch it change. Each week, ask one question for every name: did their momentum go up, down, or sideways? A team whose velocity just broke out is an outreach priority; a team whose velocity is collapsing is a warning to investigate or drop.
This is where a data source matters. GitDealFlow tracks commit velocity, contributor growth, and repository expansion weekly across 350+ startups, so the momentum question is answered by the data instead of by your memory.
Step 4: Act on changes
The weekly review should end in actions, not observations. A momentum breakout becomes a reach-out. A sustained decline becomes a question for the founder. A new repo cluster becomes a reason to re-rank the team up.
The discipline is the whole game: same time every week, same one question per name, same follow-through. A watchlist with a weekly routine is a pipeline; without one it is a list of URLs.
Tools for running a watchlist
You can run a watchlist in a spreadsheet, but the heavy lifting is keeping the momentum data fresh. Two approaches:
- Manual: a sheet with one row per startup and a weekly column for the momentum trend, updated from your own GitHub review.
- Automated: a signal layer that tracks momentum for you and surfaces the changes, so the weekly review is reading a report instead of doing arithmetic.
GitDealFlow's free tier includes sector search and trending startups; paid tiers add saved watchlists and alerts when a tracked team's momentum changes.
Frequently Asked Questions
How many startups should be on a watchlist?
Fewer than you think. A focused list of 20 to 50 names you actually review weekly beats a list of 500 you never open. The constraint is your weekly attention, not the number of interesting startups.
How often should I review my watchlist?
Weekly. The whole advantage of engineering-momentum data is that it changes week to week, so a monthly review misses the breakout window. Same time every week is the habit that makes it work.
What triggers a reach-out?
A sustained momentum breakout (4+ weeks of rising velocity), a contributor-growth step-change, or a cluster of new repositories. Any of these is a reason to move a name to the A tier and reach out that week.