The Problem: Between Board Meetings, You Are Flying Blind
Founder updates are filtered through optimism, board meetings are too infrequent to catch inflection points, and dashboards show lagging metrics like revenue and headcount. When a portfolio company's engineering momentum collapses — or accelerates — the signs appear in its public code activity weeks before they show up in any report. Investors who only look at monthly updates will always be the last to know.
GitDealFlow gives you an objective, continuous view of the companies you already back. It reads the public GitHub activity of 4,200+ startups — your portfolio included — and tracks commit velocity, contributor growth, and repository expansion. Because these are the same signals that precede fundraising by 21-47 days (documented in a research panel of 219 fundraises), they are also early indicators of follow-on rounds, distress, or quiet pivots.
What Portfolio Monitoring Shows
Weekly commit velocity — who's shipping fast? Sustained velocity means execution; a sudden drop often precedes bad news, team changes, or a strategic pause worth a phone call.
Contributor growth — are engineering teams scaling or shrinking? A growing contributor count is a hiring signal; a shrinking one is the first public evidence of attrition.
Repo expansion — are they building new products or maintaining existing ones? New repositories point to new bets; no new repositories over a long stretch can mean consolidation — or stagnation.
Momentum shifts — when a portfolio company's velocity changes materially, you want to know before the next board deck. The weekly cadence surfaces those shifts in time to act.
A Simple Weekly Workflow
- Subscribe to the free digest — five accelerating names arrive every Sunday.
- Check whether any portfolio company appears; review its momentum trend.
- Open the company's GitHub organization to verify what changed: repos, commits, contributors.
- Bring one concrete engineering observation to each founder call and board meeting.
- Use velocity shifts as a tripwire for follow-on diligence and support decisions.
Every signal is public data you can verify yourself — no NDA, no dashboard access required, and the methodology behind it is published on SSRN under a CC BY 4.0 license with an open dataset.
Frequently Asked Questions
How often should I check portfolio engineering health?
Weekly. GitDealFlow's digest automates this — you get an email every Sunday with the latest accelerating names, and paid tiers add deeper ongoing monitoring for your specific portfolio.
What if a portfolio company has no public GitHub activity?
GitDealFlow covers startups that build in public on GitHub. For companies with private codebases, the public signals simply do not apply — use the digest as a complement to your regular reporting.