Week 4, Operationalize · Day 26 of 30
Day 26: Custom composite weights
Default is 1×6. Your beat probably needs 2× on one signal and 0.5× on another.
Day 26 in one paragraph: The unweighted composite (each signal +1) is the right starting point because it's calibration-light. After 26 days you have enough personal data to see which signal matters most for your beat, and a re-weighted composite outperforms the default for your specific deal flow. 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 26 of 30 sits 87% 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 €89 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Yesterday: MCP integration. Today: the personal calibration that the integration alone can't give you.
Why this signal matters
The unweighted composite (each signal +1) is the right starting point because it's calibration-light. After 26 days you have enough personal data to see which signal matters most for your beat, and a re-weighted composite outperforms the default for your specific deal flow.
The 5-minute exercise
- 1Pull the watchlist CSV and the 4-org scorecard from Day 14.
- 2For each signal: which one would you have weighted higher to better predict your hits?
- 3Propose new weights (e.g. commit velocity 1.5×, dependents 1.5×, others 1×).
- 4Recompute the composites with new weights. Compare ranking shifts.
What you’re filtering for
A reweighted composite that produces a ranking you trust more than the default for your beat. If the reweighting doesn't change the ranking meaningfully, the default is correct for you.
Edge case
Don't over-weight a signal because you remember one big hit on it. The right weighting reflects pattern across 10+ orgs, not one anchor case. Sample size discipline matters here.
Bonus
The custom weights become a competitive moat. Two analysts with the same framework but different weights produce different deal flow, and yours is calibrated to your specific outperformance pattern.
Tomorrow
Tomorrow: the 30-day retrospective. Pull out the artifacts. What did the framework actually catch?
Common questions about day 26
- How long does day 26 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 custom composite weights?
- 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