Week 3, Synthesize · Day 21 of 30
Day 21: Week 3 wrap, your operational system
Watchlist + Monday rhythm + sector-batch + question library + pre-read.
Day 21 in one paragraph: By Day 21, you have an operating system, not a framework. Five components, each calendared. This is the difference between investors who 'use signals' and investors who 'run a sourcing process.' The system runs you, not the other way around. 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 21 of 30 sits 70% 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 €99 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Yesterday: 30-second pre-reads. Today: the whole system documented, calendared, partner-sanity-checked.
Why this signal matters
By Day 21, you have an operating system, not a framework. Five components, each calendared. This is the difference between investors who 'use signals' and investors who 'run a sourcing process.' The system runs you, not the other way around.
The 5-minute exercise
- 1Document the system on one page. Five components, half a sentence each.
- 2Bake the calendar blocks: Monday 25 min (rhythm), as-needed (sector batch), every meeting (pre-read).
- 3Identify the one piece you'll skip first under pressure. Pre-commit to a recovery move.
- 4Send the doc to your investing partner or your most critical co-investor for sanity-check.
What you’re filtering for
A one-page document you could hand to a junior analyst and they could replicate the system. If it's longer than one page, compress.
Edge case
Solo angels skip the 'partner sanity-check' step. Substitute: post the system on a private channel where you'll see it weekly (Notion homepage, Slack DM to yourself, repo README).
Bonus
Annual planning bonus: the doc becomes your sourcing strategy slide for LPs and back-office reporting. 'I run a 7-signal composite weekly across N orgs in M sectors' is more concrete than 'I source through warm intros.'
Tomorrow
Week 4 starts tomorrow, adding alerts, sharing, and the integration that makes the manual system automatic.
Checkpoint, Week 3 closes today
You’re 70% through. The full curriculum is permanent at every /challenge/<slug> URL - bookmark this page if you want to revisit the procedure later.
Common questions about day 21
- How long does day 21 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 week 3 wrap, your operational system?
- 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