How long does day 16 of the 30-day challenge take?

About five minutes of hands-on work against the org you picked on day one, plus two or three minutes of reading. If you are short on time the exercise alone still delivers the day's point.

Do I need any tools or paid data for set the weekly monday rhythm?

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 of the 30-day deal flow challenge?

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.

16 / 30

Week 3, Synthesize · Day 16 of 30

Day 16: Set the weekly Monday rhythm

25 minutes every Monday, before email, the cadence that compounds.

Day 16 in one paragraph: Sourcing systems fail on cadence, not on framework. The investors who outperform on deal flow run the same procedure on the same day every week. 25 minutes Mondays before email is the smallest commitment that survives a busy week. 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 16 of 30 sits 53% 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 €69 in equivalent consulting time by the anchoring we use across the curriculum.

Yesterday

Yesterday you built the watchlist. Today you commit to the rhythm that makes it pay.

Why this signal matters

Sourcing systems fail on cadence, not on framework. The investors who outperform on deal flow run the same procedure on the same day every week. 25 minutes Mondays before email is the smallest commitment that survives a busy week.

The 5-minute exercise

1Block 25 minutes on Monday morning, recurring, before you open email.
2Open the watchlist CSV.
3Score signal 1 (commit velocity) on all 10 orgs, that's the fastest signal, do it first.
4Note any score that moved by 0.5+ on that signal alone.
5Schedule a follow-through to score the moved orgs in full later that day.

What you’re filtering for

Recurring 25-min Monday block on your calendar. If you can't protect 25 minutes once a week, the system can't compound, better to drop to 5 orgs in the watchlist and protect the time.

Edge case

Mondays of conferences or board meetings will break the rhythm. Use Tuesday morning as the fallback day; don't skip the week.

Bonus

After 4 Mondays, you'll have 40 datapoints across 10 orgs. That's enough to spot the slope, not just the snapshot.

Tomorrow

Tomorrow: the sector batch, running 25 orgs in 25 minutes when one sector starts getting hot.

Common questions about day 16

How long does day 16 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 set the weekly monday rhythm?: 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