Week 3, Synthesize · Day 15 of 30
Day 15: Build a 10-org watchlist
Ten orgs, one sector, scored once, queued for weekly recheck.
Day 15 in one paragraph: A scorecard is a snapshot; a watchlist is a habit. Picking ten orgs in one sector and committing to recheck them weekly is the smallest unit of continuous sourcing practice that still beats the average angel's pipeline rhythm. You will spend about five minutes, end with a concrete artifact, and the whole curriculum stays free at this URL permanently.
Where this day sits in the 30
Week 3 turns daily checks into a watchlist and a weekly rhythm you can keep. Day 15 of 30 sits 50% of the way through, in week 3, synthesize, one of four one-week phases. This day also carries a bonus exercise for anyone with extra time. Everything in this challenge is built from public GitHub signals, the same data that powers the weekly deal-flow feed, and the day's lesson is worth roughly €79 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Last week you ran the composite three times. This week you commit to running it ten times, weekly, on the same orgs.
Why this signal matters
A scorecard is a snapshot; a watchlist is a habit. Picking ten orgs in one sector and committing to recheck them weekly is the smallest unit of continuous sourcing practice that still beats the average angel's pipeline rhythm.
The 5-minute exercise
- 1Pick one sector you actually care about (vertical SaaS, dev-tools, fintech infra, etc.).
- 2List 10 orgs in that sector that have public GitHub. AngelList, Crunchbase, your CRM.
- 3Run the composite once on each. ~90 minutes total.
- 4Sort by score. Save with date stamp.
What you’re filtering for
10 orgs, sorted, dated. The list is the artifact, not the conclusion. Scores will move week to week and that movement is the actual signal.
Edge case
If your sector is too narrow to find 10 orgs with public GitHub, broaden one degree (e.g. 'fintech APIs' → 'fintech infra'). The cadence beats the precision at this stage.
Bonus
Save the watchlist as a CSV with one column per signal. When a score moves, you'll see which signal moved, and that's where the founder conversation starts.
Tomorrow
Tomorrow: setting the Monday rhythm. The watchlist isn't useful until it's a calendar habit.
Common questions about day 15
- How long does day 15 take?
- About five minutes of hands-on work against the org you picked on day one. The reading adds another two or three. If you are short on time the exercise alone still delivers the day's point.
- Do I need any tools or paid data for build a 10-org watchlist?
- No. Every exercise in the challenge runs on public GitHub data and a browser. The feed that automates the same checks is available, but the curriculum itself is deliberately tool-free so the habit lands before the tooling.
- What if I miss a day?
- Every day is permanent at its own URL, so you can pick up exactly where you stopped. The sequence matters, each day builds on the previous one's artifact, but the pace is yours. Many people run the 30 days across six or seven weeks instead of four.
Curriculum: /challenge · Methodology: /methodology · Paper: ssrn.com/abstract=6606558