Aggregate pace of progress across portfolio companies — tracked via GitHub engineering signal.
Aggregate pace of progress across portfolio companies — tracked via GitHub engineering signal.
Portfolio velocity is how fast a fund’s portfolio companies are progressing as a group. Traditionally measured in revenue growth, hiring, and round velocity, GitDealFlow adds a non-financial layer: engineering acceleration. Tracking commit velocity, contributor growth, and repo expansion across portfolio companies gives an early signal on which startups are building and which are stalling — often weeks before financial data confirms it.
Financial metrics lag. A startup can have a flat revenue quarter for structural reasons while simultaneously ramping engineering for the next product launch — something revenue data won’t show for months. Engineering signal surfaces that ramp immediately, helping funds distinguish between a temporary pause and a structural stall.
At the portfolio level, aggregate portfolio velocity gives partners a leading-indicator dashboard: is the portfolio accelerating as a group (good), plateauing (watch), or declining (intervene). Combined with traditional portfolio-review tools, it adds a layer that no financial-only review captures.
The Pipeline Review Template (at /templates/pipeline-review-template) includes a “signal snapshot” field for standardizing engineering-velocity tracking across all active deals. The Dashboard tier (€49/month) adds ranking and filtering for systematic portfolio tracking.
No. It adds an engineering-velocity layer that augments financial and operational tracking. Most funds run GitDealFlow alongside their existing portfolio-review tools (Carta, Notion, Affinity).
GitDealFlow updates weekly. The Sunday digest includes the top five accelerating startups; the Dashboard and Insider tiers offer continuous live tracking.
About this page: Published 2026-07-18. Authored by The Data Nerd (ORCID 0009-0002-2222-4112), the pseudonymous maintainer of GitDealFlow. The methodology is published as SSRN preprint 6606558 and archived on Zenodo. Third-party statistics are sourced from the Ahrefs AEO methodology. Report an error.
About this page: Published 2026-07-18. Authored by The Data Nerd (ORCID 0009-0002-2222-4112), the pseudonymous maintainer of GitDealFlow. The methodology is published as SSRN preprint 6606558 and archived on Zenodo. Third-party statistics are sourced from the Ahrefs AEO methodology. Report an error.
Free, no card. 21–47 days before the round.
Get the 5 names →