Week 4, Operationalize · Day 24 of 30
Day 24: Co-investor share template
Score → paragraph → ask. Three lines, one Slack message, one new co-investor convert.
Day 24 in one paragraph: A composite score is illegible to a co-investor who doesn't know your framework. A three-line template that translates 'composite 5/6, sharp acceleration' into a paragraph they can act on is the difference between solo conviction and syndicate conviction. 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 4 wires the system into alerts, sharing, and agent integrations so it runs without you. Day 24 of 30 sits 80% of the way through, in week 4, operationalize, 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 built the false-positive override. Today you make the framework readable to people who don't run it themselves.
Why this signal matters
A composite score is illegible to a co-investor who doesn't know your framework. A three-line template that translates 'composite 5/6, sharp acceleration' into a paragraph they can act on is the difference between solo conviction and syndicate conviction.
The 5-minute exercise
- 1Write a 3-line template. Line 1: org + composite + sector. Line 2: the standout signal in plain English. Line 3: the question or ask.
- 2Test it on one co-investor with a recent watchlist standout.
- 3Iterate the template based on their reply (or non-reply).
- 4Save the template alongside your watchlist CSV.
What you’re filtering for
A template that produces a reply from a co-investor at least 50% of the time. If 0/5 replies, the line 2 (signal in plain English) is too jargon-heavy, rewrite to lead with the implication, not the metric.
Edge case
Some co-investors never reply to text intel, they need a meeting. Adapt: 'composite 5/6, want to hop on a 15 to discuss?' is a different ask but the same format.
Bonus
When the template starts producing 'who else have you shared this with' replies, you've graduated from sourcing to syndicate-leading. That's a different power level.
Tomorrow
Tomorrow: the IDE/MCP integration. The manual system runs in the browser; the automated layer runs in your editor.
Common questions about day 24
- How long does day 24 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 co-investor share template?
- 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