Week 1, Learn · Day 5 of 30
Day 5: New repo creation rate
The platform-buildout tell, SDKs, CLIs, demos shipping fast.
Day 5 in one paragraph: Most useful for Series A / Series B startups. When the core product works and the team has capital, they start building the platform around it, SDKs, CLIs, internal services, documentation sites, example apps. Each one is a new public repo. 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 1 teaches the six atomic signals one at a time, each on the org you picked on day one. Day 5 of 30 sits 17% of the way through, in week 1, learn, 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's README check told you whether the team is positioning. Today's tells you whether they're building the platform around the position.
Why this signal matters
Most useful for Series A / Series B startups. When the core product works and the team has capital, they start building the platform around it, SDKs, CLIs, internal services, documentation sites, example apps. Each one is a new public repo.
The 5-minute exercise
- 1Open the org's main page.
- 2Click Repositories, sort by Newest.
- 3Count: how many repos created in the last 30 days? Last 90 days?
- 4Open the newest 3. What do they look like, SDKs, infra, demos?
What you’re filtering for
3+ new repos in 30 days, where the new repos look like platform components (CLI, SDK in a new language, example app, internal microservice) rather than throwaways or test repos.
Edge case
A single new repo named with a year or quarter ('foo-2026', 'platform-q3'), that's a roadmap commitment in code form, often more telling than three throwaway demos.
Bonus
This is the 'deploying capital' signal. A team that just raised a Series A is hiring engineers and the first thing those engineers ship is platform code. A team about to raise often pre-builds these so the next deck has a 'platform expansion' slide.
Tomorrow
Tomorrow: issue-to-PR ratio, the engagement vs shipping signal that separates firefighting from acceleration.
Common questions about day 5
- How long does day 5 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 new repo creation rate?
- 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