Week 3, Synthesize · Day 20 of 30
Day 20: 30-second pre-read for first meetings
One glance at the composite before you walk in, and you're already ahead.
Day 20 in one paragraph: Every first meeting is improved by a 30-second pre-read of the founder's GitHub. The framework compresses that pre-read into a number plus three notes, readable from a phone in the elevator. Most investors don't do this. The 30 seconds is the differential. 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 20 of 30 sits 67% 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
Yesterday you scored a portfolio company retroactively. Today: the 30-second forward-looking version, before every meeting.
Why this signal matters
Every first meeting is improved by a 30-second pre-read of the founder's GitHub. The framework compresses that pre-read into a number plus three notes, readable from a phone in the elevator. Most investors don't do this. The 30 seconds is the differential.
The 5-minute exercise
- 1Open the founder's GitHub org from your meeting calendar invite.
- 2Glance at: README dated? Repo count moving? Top-contributor share?
- 330-second composite: 0-2 (cold), 3-4 (warm), 5-6 (hot).
- 4Walk in with one signal-specific opening question.
What you’re filtering for
A 30-second pre-read habit on every founder meeting going forward. The threshold for 'do the pre-read' should be 0, you do it for every meeting, not just the high-scoring ones.
Edge case
Some founders do all their work in private repos. Note the absence as 'private-repo team' and adjust the conversation, your questions shift from 'what does the engineering say' to 'walk me through the engineering history I can't see.'
Bonus
Two months in, the pre-read becomes automatic. You'll start noticing other investors who haven't done it, and the founder will too.
Tomorrow
Tomorrow closes Week 3, your operational sourcing system is real, written down, and running on a calendar.
Common questions about day 20
- How long does day 20 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 30-second pre-read for first meetings?
- 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