Week 3, Synthesize · Day 17 of 30
Day 17: Sector batch, 25 orgs in 25 minutes
When a sector heats up, sweep it broad before going deep.
Day 17 in one paragraph: When a sector is moving (a category is buzzing, a competitor just raised, an LP is asking), the speed move is to score 25 orgs in that sector at lightning pace and rank them. One signal, one minute per org. 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 17 of 30 sits 57% 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 €89 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Yesterday you set the weekly rhythm. Today you build the high-throughput version of the same procedure for sector-heat moments.
Why this signal matters
When a sector is moving (a category is buzzing, a competitor just raised, an LP is asking), the speed move is to score 25 orgs in that sector at lightning pace and rank them. One signal, one minute per org.
The 5-minute exercise
- 1Pick a sector that's moving. List 25 orgs (Crunchbase + AngelList).
- 2Score signal 1 (commit velocity) on each, 60 seconds per org.
- 3Sort top 5. For those 5, run the full composite, 75 minutes total.
- 4Top 1-2 from the sweep get a meeting request the same week.
What you’re filtering for
A 25-org sweep with 5 orgs flagged for full composite. Top 1-2 get outreach. The exercise compresses 'broad scan + tight diligence' into one afternoon.
Edge case
If the sector is small (<25 orgs with public GitHub), score what exists and supplement with private-repo intelligence, that gap itself is positioning data on the sector.
Bonus
This is the procedure the live engine runs every Monday at 06:00 UTC across 350+ orgs in 4 seconds. You're learning the manual version so you can defend any number the engine produces.
Tomorrow
Tomorrow: using the composite as the founder Q&A frame, turning a score into a question.
Common questions about day 17
- How long does day 17 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 sector batch, 25 orgs in 25 minutes?
- 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