Talk notes
Dev-tools is the cleanest sector in our panel because the product is also the source of the signal. Dev-tools companies dogfood their own product on GitHub, they use GitHub Issues for bug tracking, GitHub Discussions for community, GitHub Actions for CI, and they ship in public. Every signal we measure is amplified in this sector. That's why we expect precision to be highest in dev-tools, something the scorecard will show per sector as it grades.
The Q1 2026 dev-tools cohort included 9 named orgs that flagged the composite signal. Eight of the nine announced a fundraise within 60 days. The pattern is consistent: the founding team is two-to-four senior engineers with strong open-source contribution histories, the codebase is published from day one, the product is meaningfully usable as soon as the README is published, and community engagement (issue replies, PR reviews, discussion threads) ramps in lockstep with commit velocity.
The CI-first pattern is the dominant signature. Dev-tools teams invest disproportionately in their own CI/CD infrastructure, they ship green tests obsessively, they triage issues within hours, and they treat GitHub Actions like a first-party product feature. When a dev-tools org goes from 24-hour issue triage to 4-hour issue triage in a 30-day window, that's almost always a hiring + fundraise signal.
The confidence multiplier we use in dev-tools is community-engagement velocity. The number of unique community members who interact with the project (file an issue, review a PR, post in discussions) per 30-day window. When community-engagement velocity rises 2× alongside commit-velocity, our internal confidence on the fundraise signal goes from 70 percent to 89 percent.