Frequently Asked Questions

Engineering acceleration is the rate of change in a startup's commit velocity — not absolute output, but whether engineering activity is speeding up relative to the company's own baseline. When a startup's commit velocity doubles in two weeks, something fundamental has changed: new hires, product-market fit, or fundraise-driven shipping. VC Deal Flow Signal tracks this metric across 20 sectors as a leading indicator of startup momentum.

In VC Deal Flow Signal's data, engineering acceleration signals precede fundraise announcements by six to twelve weeks on average. The pattern starts with rising commit velocity in weeks 1-2, becomes obvious in weeks 3-4 with new repositories and classifiable signal types, and the fundraise announcement typically follows in weeks 8-12. Reaching out to founders in weeks 2-4 puts investors ahead of the crowd.

While individual commits can be trivially created, sustained engineering acceleration is very difficult to fake. VC Deal Flow Signal measures change from baseline rather than absolute counts, which filters out documentation sprints, CI/CD noise, and inflated commit volumes. A genuine product sprint looks fundamentally different from artificial activity when compared to a company's own historical patterns.

Deal flow signal is any data-driven indicator that helps an investor identify a promising startup before traditional deal sourcing channels — warm introductions, pitch decks, demo days, and press coverage — surface it. The most common types include engineering signals (GitHub commit velocity), hiring signals (job postings), web traffic signals, and social signals. Engineering signals provide the longest lead time at 6-12 weeks before fundraise announcements.

Investors can use four main types of alternative data for deal sourcing: engineering activity from GitHub (6-12 weeks lead time), hiring signals from job boards and LinkedIn (4-8 weeks), web traffic data from tools like SimilarWeb (4-6 weeks), and social signals from Twitter, Hacker News, and Product Hunt (1-2 weeks). GitHub engineering data has the highest lead time and is the hardest to game.

Engineering signals from GitHub typically provide 6-12 weeks of lead time over traditional deal flow channels. Traditional deal flow — Crunchbase alerts, warm introductions, press coverage — surfaces companies after they have already raised or are well into a competitive round. Engineering acceleration signals appear when the team starts building, which is weeks before any public announcement.

No. Public GitHub data cannot replace a proper technical deep dive with the engineering team. But it can do something equally valuable: help investors decide which companies deserve that deep dive in the first place. It serves as a fast screening tool at the sourcing stage and a verification tool at the due diligence stage, complementing — not replacing — traditional technical evaluation.

Investors should check five things: (1) commit velocity consistency — regular shipping vs. erratic bursts, (2) contributor count and growth — a proxy for team size and scaling, (3) technology choices — whether the stack matches the company's stage, (4) new repository creation — signs of platform building, and (5) the ratio of product code to maintenance activity. These checks take 2-5 minutes per company.

Using public data for investment decisions is legal and common practice. However, investors should not contact individual contributors directly or attempt to recruit from portfolio companies based on GitHub profiles. GitHub data should be one signal among many — never the sole basis for an investment decision. The strongest investment thesis combines engineering signals with market analysis, founder evaluation, and customer reference checks.

Five GitHub patterns reliably precede fundraise announcements: (1) The Contributor Step Function — a sudden 50%+ jump in unique contributors, indicating post-round hiring, (2) The Infrastructure Explosion — 3-5 new repos in a month, signaling platform buildout, (3) The Weekend Surge — sustained 7-day commit patterns from multiple contributors, (4) The Documentation Sprint — proactive documentation suggesting preparation for scrutiny, and (5) The Velocity Regime Change — commit velocity exceeding the 6-month average by 100%+.

GitHub patterns are leading indicators, not guarantees. They appear with enough regularity to be useful — particularly when multiple patterns overlap — but not all engineering acceleration leads to fundraising. Some acceleration reflects product-market fit, pivots, or hackathon activity. The patterns are most reliable when a startup shows two or more signals simultaneously, such as contributor growth combined with a velocity regime change.

The strongest combination is Pattern 1 (contributor step function — sudden team growth) plus Pattern 5 (velocity regime change — sustained doubling of commit velocity). When both appear simultaneously, the startup has almost certainly either just closed a round or is in the middle of one. The new hires are shipping code at an accelerated pace, and the compound signal is very difficult to produce without real organizational change.

Alternative data in venture capital is any dataset that reveals startup traction before it appears through conventional deal sourcing channels. The main categories include engineering activity from GitHub (commit velocity, contributor growth), hiring signals from job boards, web traffic from analytics tools, social mentions from platforms like Twitter and Hacker News, and patent filings. Unlike traditional deal flow data (funding announcements, press, warm intros), alternative data provides a leading rather than lagging indicator.

GitHub data stands out among alternative data sources because it is continuous (updated daily, not monthly), free and public (no scraping or paid tools required), hard to fake (commits represent real engineering work), and reveals intent (the type of activity tells you what phase the company is in). Despite these properties, almost no investor monitors GitHub systematically — creating an information asymmetry for those who do.

Quantitative investment firms have used alternative data in public markets for over a decade — satellite imagery of parking lots, credit card transactions, app downloads. The edge comes not from exclusive data but from reading what others ignore, faster and more consistently. The same principle applies to venture capital: every investor has access to GitHub, but almost none monitor it systematically. Building a workflow around engineering signals creates a structural timing advantage.

Investors can find deals before Crunchbase using three signal types: (1) GitHub engineering signals — the earliest indicator, detecting commit velocity spikes 6-12 weeks before fundraise announcements, (2) community signals from Hacker News, Product Hunt, and Indie Hackers — variable lead time, wide coverage, and (3) hiring signals from job boards and LinkedIn — 4-8 weeks lead time. Combining all three with Crunchbase for verification gives both timing advantage and diligence depth.

GitHub engineering acceleration is the earliest publicly available signal of startup momentum. The logic is straightforward: engineering acceleration precedes product milestones, which precede fundraise decisions, which precede Crunchbase entries. When a startup's commit velocity doubles in a two-week window and the change is sustained, the underlying cause — post-fundraise scaling, product-market fit, or launch preparation — is already in motion 6-12 weeks before any public announcement.

GitHub engineering signals provide 6-12 weeks of lead time over Crunchbase alerts. Crunchbase alerts trigger on fundraise announcements, which are published after the round closes — zero lead time. GitHub signals detect acceleration patterns while the round is still in progress or before fundraising even begins. The top movers in VC Deal Flow Signal's weekly rankings consistently include companies that announce raises 4-8 weeks later.

Investors should track seven engineering metrics from public GitHub data: (1) commit velocity — 14-day rolling commit count, (2) commit velocity change — the percentage change vs. prior period (the primary signal), (3) contributor count — proxy for team size, (4) contributor growth rate — indicates hiring bursts, (5) new repository count — signals infrastructure buildout, (6) weekend commit ratio — indicates deadline pressure, and (7) language/framework distribution — reveals technical maturity and stack choices.

Commit velocity change — the percentage change in 14-day commit count compared to the prior window — is the single most useful engineering metric for investors. It measures acceleration rather than absolute volume, which makes it comparable across startups of different sizes. A sustained velocity change above +50% for 3 or more consecutive windows is a meaningful signal. Above +100% is a regime change that has historically preceded fundraise announcements.

A quick screening checklist: (1) Is commit velocity change positive and above 50%? (2) Has contributor count grown recently? (3) Are there new repos in the last 30 days? (4) Is the activity product-related, not just docs or CI/CD? (5) Does the tech stack match the company's pitch? If a startup passes all five checks, it deserves a deeper look. If it fails the first two, the engineering signal is not there. VC Deal Flow Signal automates checks 1-4 across 20 sectors weekly.

Engineering acceleration measures the rate of change in a startup's engineering output relative to its own historical baseline. It is calculated as the percentage change in 14-day commit velocity versus the prior period. A +100% acceleration means the team doubled its commit rate.

Engineering acceleration is a leading indicator of startup momentum. When a team accelerates its engineering output, the cause is usually post-fundraise scaling, product-market fit iteration, or launch preparation — all of which precede the public signals (press coverage, Crunchbase entries) that most investors rely on.

DORA metrics (deployment frequency, lead time, change failure rate) measure engineering process quality — how well a team ships. Engineering acceleration measures output momentum — whether they are speeding up. DORA requires internal CI/CD access; acceleration can be measured from public GitHub data, making it useful as an external investment signal.

Commit velocity is the total number of commits to a startup's most active public GitHub repository over a rolling 14-day window. It measures the raw volume of engineering output.

Not necessarily. High absolute commit velocity can reflect automated commits, documentation updates, or CI/CD activity rather than meaningful product development. What matters more is commit velocity change — whether the rate is accelerating.

There is no universal benchmark — commit velocity depends on team size, commit granularity, and workflow conventions. A solo founder with 50 commits/week and a 10-person team with 200 commits/week may have equivalent per-engineer output. The useful metric is velocity change relative to the company's own baseline, not absolute counts.

Yes. Pre-seed startups often have public GitHub activity before they have any other public presence. Look for organizations with 1-3 contributors showing rapid commit acceleration from a low base — this pattern indicates early product development that often precedes a first fundraise.

Pre-seed activity typically shows 1-7 contributors, commit velocity under 100 per 14 days, but with high acceleration rates (+200% or more). New repository creation (infrastructure buildout) is common as founders move from prototype to more structured development.

Filter sector rankings for startups with 1-7 contributors showing +200% or higher velocity change. These disproportionate acceleration rates from a small base indicate a product breakthrough or first-fundraise preparation. Then verify on GitHub: is the activity product-related? Check Hacker News and Twitter for founder activity.

Series A startups typically show 20-49 contributors, infrastructure buildout (3+ new repos in 30 days), and increasing repository specialization. The dominant signal type is 'infrastructure buildout' — the team is building the platform around a working core product.

Infrastructure buildout means a startup created 3 or more new public repositories in 30 days. At Series A, these typically include API client libraries, SDK packages, CLI tools, and deployment infrastructure — signs that the team is building a platform around a working core product.

When contributor count jumps 50%+ in a short window (e.g., from 12 to 20 contributors), the company has likely closed a round and is scaling. This appears in GitHub data within weeks of new hires joining, but the Crunchbase entry may lag by 6-12 weeks.

Focus on the company-owned organization (not community forks), track core maintainer growth rather than total contributors, and look for commercial infrastructure signals — new repos for enterprise features, billing, or deployment tooling. Community star velocity is a social signal; commit velocity in the core product is the engineering signal.

Simultaneous community growth and commercial acceleration. When the open source project is gaining stars and contributors while the company organization is building enterprise infrastructure (billing, auth, deployment tooling), the open source flywheel is working — community traction is converting into commercial opportunity.

Stars measure social interest, not engineering traction or commercial viability. A repository with 10,000 stars may have zero revenue. Stars can indicate developer mindshare, but commit velocity in the company's own repositories is a more reliable signal of engineering momentum.

GitHub signals provide earlier lead time (6-12 weeks vs 4-8 weeks for hiring) because engineering acceleration precedes hiring decisions. Hiring data is more explicit about growth type. The combination of both is stronger than either alone — GitHub for timing, hiring for confirmation.

GitHub engineering signals typically provide 6-12 weeks of lead time before fundraise announcements, compared to 4-8 weeks for hiring data. The gap exists because engineering acceleration (more commits, faster shipping) precedes the hiring decisions that follow. By the time a job posting appears, the engineering acceleration has been visible for weeks.

Both — sequentially. Use GitHub signals for early detection (which companies are accelerating?) then hiring data for confirmation and growth-type classification (are they hiring engineers, sales, or marketing?). The combination provides both timing advantage and strategic context.

Fintech engineering signals are influenced by regulatory requirements. Infrastructure buildout often indicates compliance infrastructure (KYC, AML, audit logging) rather than product expansion. Deploy frequency spikes may reflect regulatory deadline-driven development rather than customer-driven iteration.

Simultaneous product acceleration and compliance buildout. When a fintech company is shipping product features and building compliance infrastructure (KYC, audit logging, encryption) at the same time, it is preparing for a regulated launch — which requires significant capital and often precedes fundraising.

Yes, but with sector-specific interpretation. Fintech companies with public repos typically focus on developer-facing products (payment APIs, banking-as-a-service, trading infrastructure). Consumer fintech companies are less likely to have public GitHub activity. Check the Fintech sector rankings for current data.

Distinguish model training infrastructure (sporadic large commits, research-oriented) from product engineering (frequent small commits, customer-driven iteration). The strongest signal is a transition from research-style to product-style commit patterns, indicating the company is moving from experimentation to shipping.

AI startups show the highest average commit velocity but also the highest noise of any sector. Open source experimentation, research-oriented commits, and community activity inflate the standard metrics. The key is separating product engineering (shipping features) from research exploration (running experiments).

The research-to-product transition. When an AI startup's commit pattern shifts from sporadic large commits (experiments, model checkpoints) to frequent small commits (API endpoints, deployment config, monitoring), the team is moving from 'does this work?' to 'let's ship this.' This transition often precedes a fundraise.

30 minutes per week. The workflow is designed to fit into a Monday morning routine: check rankings, screen candidates, verify signals, and add qualified leads to your pipeline.

2-5 actionable leads per week, depending on how many sectors you track and how selective you are. The quality is high because engineering acceleration is a leading indicator — you are finding companies before they appear in traditional deal sourcing channels.

Cybersecurity deploy frequency spikes often reflect CVE response rather than product iteration. Infrastructure buildout may indicate compliance infrastructure (SOC 2, ISO 27001). The strongest signal is sustained acceleration outside of incident-response cycles.

Check the timing: does the velocity spike coincide with a major CVE disclosure? If the spike happens within days of a published vulnerability, it is likely reactive patching. Sustained acceleration over 2-3 weeks without an external trigger indicates genuine product momentum.

New repositories related to SOC 2 audit trails, ISO 27001 documentation, or penetration testing frameworks indicate a company preparing for enterprise sales. Most enterprise buyers require SOC 2 compliance, so this buildout is a positive investment signal — it requires capital and precedes revenue growth.

Yes, but with nuance. Software-heavy climate companies (carbon accounting, energy trading) show standard engineering signals. Hardware-adjacent companies show lower commit velocity but meaningful infrastructure buildout when transitioning from R&D to deployment.

The R&D-to-deployment transition. When a climate tech company's GitHub activity shifts from experimental (research notebooks, prototype code) to operational (deployment scripts, monitoring, CI/CD pipelines), the technology is moving from lab to field. This transition requires capital and often precedes fundraising.

Software-heavy climate companies appear most clearly: carbon accounting platforms, energy trading tools, grid optimization software, and ESG reporting systems. Hardware-adjacent companies building intelligence layers (battery management, sensor networks, predictive maintenance) also show meaningful GitHub signals.

The five most common: confusing stars with traction, ignoring the private repo blind spot, overweighting absolute commit counts over acceleration, missing the context behind velocity spikes (bots, docs, migrations), and treating engineering signals as investment decisions rather than sourcing signals.

GitHub signals are reliable for deal sourcing — identifying interesting companies early. They are not reliable as standalone investment decisions. Engineering acceleration should be the first step in a diligence process, not the last. Always verify with direct founder conversations, product evaluation, and market analysis.