Engineering metrics — available from public GitHub data — provide a complementary view of startup health that almost nobody monitors. Here are seven metrics worth tracking, what they tell you, and how to use them. For the broader context on why this data matters, see [what is deal flow signal](/blog/what-is-deal-flow-signal).

## 1. What Is Commit Velocity?

**What it is:** Total commits to a startup's most active public repository over a rolling 14-day window.

**What it tells you:** The raw volume of engineering output. High absolute velocity is not inherently meaningful — some teams commit frequently with small changes, others commit less often with larger changes. The value is in tracking it over time to establish a baseline.

**How to use it:** Commit velocity is the denominator for the most important metric (velocity change). Track it to understand the startup's normal operating rhythm before evaluating whether a change is significant.

## 2. Why Is Commit Velocity Change the Primary Signal?

**What it is:** The percentage change in commit velocity compared to the preceding 14-day window.

**What it tells you:** Whether the engineering team is accelerating, maintaining pace, or slowing down. This is the single most useful engineering metric for investors because it measures *acceleration* — the rate of change.

**How to use it:** A sustained velocity change above +50% for 3+ consecutive windows is a meaningful signal. At VC Deal Flow Signal, this is the primary ranking metric across all 20 sectors. Startups showing +100% or higher velocity change are flagged as top movers.

**Benchmark:** In our dataset, the average velocity change across 43 tracked startups is approximately +15%. Anything above +50% is unusual. Above +100% is a regime change.

## 3. What Does Contributor Count Tell Investors?

**What it is:** The number of unique contributors to the startup's most active public repository.

**What it tells you:** A rough proxy for engineering team size. More useful as a trend than an absolute number, since not all employees contribute to public repos, and not all contributors are employees.

**How to use it:** Compare contributor count to the startup's claimed team size. A company claiming 30 engineers but showing 5 GitHub contributors either has most code in private repos (normal) or is overstating their team (investigate further).

## 4. Why Does Contributor Growth Rate Predict Fundraises?

**What it is:** The change in unique contributor count over a 6-week comparison window.

**What it tells you:** Whether the engineering team is growing. A sudden jump (50%+ in a short window) almost always indicates a hiring burst — new engineers who joined and started committing.

**How to use it:** Contributor growth above 50% in a 2-week window is our most reliable fundraise predictor. New hires start committing code within days of joining. If you see the contributor count step up sharply, the round likely closed recently and the announcement is coming.

## 5. What Does New Repository Creation Signal?

**What it is:** The number of public repositories created by the startup's GitHub organization in the last 30 days.

**What it tells you:** Whether the startup is expanding its technical surface area. New repos usually mean new microservices, SDKs, internal tools, or platform components.

**How to use it:** Three or more new repos in 30 days is what we call an "infrastructure buildout" signal. This pattern is classic Series A behavior: the core product works, and the team is building the surrounding platform. It signals both technical maturity and available capital.

## 6. What Does Weekend Commit Activity Reveal?

**What it is:** The proportion of commits that occur on Saturday and Sunday versus weekdays.

**What it tells you:** How intensely the team is working. Weekend commits from multiple contributors (not just a solo founder) indicate a deadline push.

**How to use it:** A sustained shift from weekday-only to 7-day commit patterns across multiple contributors is a soft signal that something time-sensitive is happening: a product launch, a fundraise demo, or a competitive response. This metric is most useful as a confirming signal alongside velocity change.

## 7. What Do Language and Framework Choices Indicate?

**What it is:** The programming languages and frameworks visible in the startup's public repositories.

**What it tells you:** The technical stack and maturity level. A seed-stage startup using Kubernetes, Terraform, and enterprise monitoring tools may be over-engineering. A growth-stage company still using prototype-quality tools may have hidden technical debt.

**How to use it:** Cross-reference with the startup's claimed technology during due diligence. If they say they are building an AI platform, their repos should show Python, ML frameworks, and data processing infrastructure. If the repos tell a different story, ask why.

## How Should Investors Use These Metrics Together?

When evaluating a startup from its public GitHub profile, check these in order:

1. Is commit velocity change positive and above 50%? (Active acceleration) 2. Has contributor count grown recently? (Team scaling) 3. Are there new repos in the last 30 days? (Platform building) 4. Is the activity product-related, not just docs/CI/CD? (Meaningful work) 5. Does the tech stack match the company's pitch? (Consistency check)

If a startup passes all five checks, it is worth a deeper look. If it fails the first two, move on — the engineering signal is not there. For real-world application, read how investors [use GitHub for technical due diligence](/blog/github-due-diligence-for-vcs).

VC Deal Flow Signal automates checks 1-4 across 20 sectors weekly. Browse the sector rankings to see which startups pass the screen right now.

## What Is Engineering Acceleration?

Engineering acceleration measures the rate of change in a startup's engineering output. Not how much code they write, but how much faster they are writing it compared to their own baseline.

The formula is straightforward: take the 14-day commit count, compare it to the prior 14-day window, and express the change as a percentage. A startup with 40 commits this period and 20 last period shows +100% acceleration.

This is different from absolute engineering volume. A company with 500 commits per week is not necessarily more interesting than one with 50 — what matters is whether the 50-commit company just jumped from 25. That jump is the signal.

## Why Does This Metric Matter for Investors?

The logic chain is simple:

1. A startup decides to raise, or achieves product-market fit, or plans a launch 2. This decision drives engineering activity — hiring, shipping, building 3. Engineering acceleration appears in public GitHub data 4. Six to twelve weeks later, the fundraise announcement or press coverage appears

Most investors only see step 4. Engineering acceleration lets you see step 3 — the earliest publicly available signal that something meaningful has changed.

## How Is It Different From DORA Metrics?

DORA metrics (deployment frequency, lead time, change failure rate, time to restore) measure engineering process quality. Engineering acceleration measures engineering output momentum. DORA tells you how well a team ships; acceleration tells you whether they are speeding up. Both are valuable, but acceleration is more useful as an external signal because it does not require internal access to CI/CD systems.

## What Are the Four Signal Types?

When a startup shows acceleration, we classify the pattern into one of four types based on which metric is driving the change. See our [glossary](/glossary) for full definitions of each signal type: engineering hiring burst, infrastructure buildout, deploy frequency spike, and framework migration. Each pattern has different implications for investors.

Browse the [sector rankings](/) to see which startups are showing engineering acceleration right now.

## What Is Commit Velocity?

Commit velocity is the total number of commits to a startup's most active public GitHub repository over a rolling 14-day window. At VC Deal Flow Signal, we pull this data from the GitHub API's commit activity endpoint [1].

The metric is intentionally simple: count the commits. No weighting by lines of code, no filtering by author, no adjustment for commit size. Simplicity makes it comparable across companies and sectors.

## What Does Commit Velocity Actually Measure?

Commit velocity measures engineering output volume — how much work is being pushed to version control. It is a proxy for engineering activity, not engineering quality.

A startup with 200 commits in 14 days has roughly 14 commits per day. For a team of 10 engineers, that is a healthy shipping cadence. For a solo founder, it might indicate automated tooling or excessive granularity.

## What Are the Limitations?

Commit velocity has known limitations that investors should understand:

**Commit size varies**: One commit might change a single config line; another might refactor 5,000 lines. Velocity treats them equally.

**Automation inflates counts**: CI/CD bots, automated dependency updates, and auto-formatting tools can inflate commit counts without meaningful engineering work.

**Private repos are invisible**: Many startups keep their core product code in private repositories. Commit velocity only captures public activity.

**Squash vs. merge**: Teams that squash commits will show lower velocity than teams that merge individual commits. This is a workflow choice, not a quality signal.

## Why Commit Velocity Change Matters More

This is the key insight: absolute commit velocity is noisy. Commit velocity change — the rate at which velocity is accelerating — is the real signal. See our detailed guide on [how to read GitHub signals for startup investing](/blog/how-to-read-github-signals-for-startup-investing).

A startup going from 20 to 40 commits in a 14-day window shows +100% velocity change. That acceleration has meaning regardless of the absolute numbers — something changed in how the team is working. That something is what investors care about.

Visit our [glossary](/glossary#commit-velocity) for formal definitions of all engineering metrics.

## Why GitHub Works for Pre-Seed Sourcing

GitHub is one of the few public data sources where pre-seed activity is visible. Before a startup has a pitch deck, before it has a website, the founders are writing code. That code — if the repositories are public — creates a data trail.

At VC Deal Flow Signal, we estimate startup stage from contributor count: pre-seed companies typically have 1-7 contributors. When we see a small team showing disproportionate acceleration — committing at 3-5x their baseline rate — something is happening worth investigating.

## What Pre-Seed Signals Look Like

Pre-seed engineering activity has a distinctive pattern:

**Low absolute velocity, high acceleration**: A solo founder going from 5 commits/week to 25 commits/week shows +400% velocity change. In absolute terms, 25 commits is nothing. But the acceleration is the signal.

**Infrastructure buildout from zero**: New repositories appearing (3+ in 30 days) in a young organization suggests the founder is moving from prototype to structured development. This is classic pre-seed-to-seed transition behavior.

**Contributor count jumping from 1 to 3-4**: When a solo founder suddenly has co-contributors, they either found a co-founder, hired their first engineer, or attracted open source contributors. All three are positive signals.

## A Pre-Seed Sourcing Workflow

1. Check the [sector rankings](/) weekly and filter for startups showing "Pre-seed" stage estimation 2. Look for companies with +200% or higher velocity change from a small base 3. Open their GitHub organization — is the activity product-related? 4. Check if the founder is active on Twitter, Hacker News, or Indie Hackers 5. If signals align, reach out before anyone else knows the company exists

For the complete screening methodology, see the [7 engineering metrics every investor should track](/blog/startup-engineering-metrics-investors-should-track).

## What Makes Series A GitHub Activity Different

At the pre-seed and seed stages, GitHub activity is concentrated: one or two repositories, a small team, and commit patterns driven by individual contributors. At Series A, the picture changes.

The defining characteristic is platform expansion. The core product works — customers are using it — and now the team is building everything around it: SDKs, developer documentation, internal tools, deployment infrastructure, monitoring systems.

## The Infrastructure Buildout Signal

The strongest Series A signal is infrastructure buildout: 3 or more new public repositories created in 30 days. This is not a founder experimenting with side projects. This is a company with capital deploying it into platform development.

Common new repositories at this stage include API client libraries, CLI tools, integration frameworks, and documentation sites. Each represents a deliberate investment in making the product accessible to more users or developers.

## Contributor Growth as a Post-Raise Indicator

When contributor count jumps 50% or more in a short window, the company has likely just closed a round and is scaling the engineering team. At Series A, this typically means going from 8-12 contributors to 15-25.

The timing is important: contributor growth appears in GitHub data within weeks of new engineers joining, but the fundraise announcement may not appear on Crunchbase for another 6-12 weeks. This gap is the investor's opportunity.

## How to Use These Signals

Filter the [sector rankings](/) for startups estimated at "Series A/B" stage. Look for companies showing "Infrastructure buildout" signal type with contributor growth above 50%. Cross-reference with the [trending page](/trending) to find the strongest movers.

For a complete framework on interpreting these signals, see our guide to [GitHub due diligence for VCs](/blog/github-due-diligence-for-vcs).

Crunchbase is excellent at what it does: a comprehensive database of startup funding rounds, team members, and company profiles. But by design, it is a lagging indicator. A company appears in your Crunchbase alert after the round closes, after the terms are set, after the press release is written. You are seeing what already happened.

The investors who consistently get into the best deals are the ones who found the company before it appeared on Crunchbase. This post covers three practical approaches to doing that.

## How Do GitHub Engineering Signals Help You Find Deals First?

GitHub engineering activity is the earliest publicly available signal of startup momentum — and part of a broader shift toward [alternative data in venture capital](/blog/alternative-data-venture-capital). 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, something fundamental has shifted. Common causes:

- **Post-fundraise scaling**: New capital deployed → new engineers hired → commit velocity spikes. The round closed but is not yet announced. Lead time: 6-12 weeks before the Crunchbase entry. - **Product-market fit iteration**: Customer feedback driving rapid feature development. Lead time: 8-16 weeks before a fundraise decision is even made. - **Launch preparation**: Team pushing toward a release. Often followed by press coverage and investor attention.

What to look for: - **Commit velocity change > 100%**: The startup's 14-day commit count doubled compared to the prior window. - **Contributor growth > 50%**: New team members appeared — likely recent hires. - **3+ new repositories in 30 days**: Infrastructure buildout, classic Series A behavior.

This is what VC Deal Flow Signal tracks across 20 sectors weekly. The top movers consistently include companies that announce raises 4-8 weeks later.

## Which Community Platforms Surface Startups Earliest?

Community platforms surface startups at different stages of visibility:

**Hacker News Show HN** — Very early signal. Founders posting technical projects before they have a pitch deck. Lead time: months before any institutional awareness. The challenge is volume — most Show HN posts are weekend projects, not fundable companies.

**Indie Hackers** — Build-in-public culture means founders share revenue numbers, growth metrics, and technical decisions openly. Lead time: weeks to months. The signal is in the engagement — posts that generate deep technical discussion often indicate real traction.

**Product Hunt** — Launch signal, not traction signal. By the time a startup launches on Product Hunt, they usually have a polished product and some early customers. Lead time: 2-4 weeks before broader awareness.

**Y Combinator batch lists** — Published at demo day, which is late in the cycle (investors already competing for these companies). But the companies that raise quietly before or after demo day are the ones to watch.

The community sourcing approach works best when you are deeply embedded in a specific community. An investor who reads r/venturecapital daily catches signals that a broader scan would miss.

## How Can Hiring Data Reveal Upcoming Fundraises?

Job postings reveal a startup's growth plans before they are announced publicly:

- **Senior engineering hires** (VP Engineering, Staff Engineer): Team is scaling, likely post-fundraise. - **Head of Sales / VP Marketing**: Go-to-market is being built. Product-market fit is likely established. - **Multiple simultaneous postings**: Coordinated hiring push, usually funded by a recent or imminent round.

Where to find hiring signals: - LinkedIn job postings (filter by company size 1-50) - AngelList/Wellfound job boards - Y Combinator's Work at a Startup - Hacker News monthly "Who's Hiring" threads

Lead time: 4-8 weeks before the round is announced. Shorter than GitHub signals, but the signal is more explicit about the type of growth.

## How Should Investors Combine All Three Signal Types?

The most effective approach combines all three signal types:

1. **GitHub signals** surface companies showing engineering acceleration (earliest warning) 2. **Community signals** add context — is the founder talking about traction? Customer feedback? Hiring? 3. **Hiring signals** confirm the growth trajectory — are they actively building the team? 4. **Crunchbase** verifies funding history and competitive landscape (due diligence, not sourcing)

This progression gives you the best of both worlds: timing advantage from alternative data, and verification depth from traditional sources.

## What Does This Look Like in Practice?

Every week, check the sector rankings for your focus areas. When an unfamiliar name appears in the top 3 with a strong acceleration signal:

1. Spend 5 minutes on their GitHub — is the activity product-related or maintenance noise? 2. Search Hacker News, Reddit, and Twitter for the company name — any community buzz? 3. Check their careers page — are they hiring? 4. Open Crunchbase — what is their funding history? Are they pre-raise? 5. If all signals align, reach out to the founder.

This workflow takes 15-20 minutes per company and puts you weeks ahead of investors who only use Crunchbase alerts. For the full screening checklist, see the [7 engineering metrics every investor should track](/blog/startup-engineering-metrics-investors-should-track).

Browse the sector rankings to start identifying startups before they appear in your inbox.

## The Community Noise Problem

For most startups, commit velocity is a clean signal — the commits come from the team. For open source startups, commits come from everywhere: core team, community contributors, one-time bug fixers, documentation translators, and bots.

This noise inflates the standard metrics. A popular open source project might show 500 contributors, but only 10 are paid employees. A commit velocity spike might reflect a documentation sprint by the community, not product acceleration by the company.

## How to Separate Commercial from Community Signals

The key is to focus on the company-owned organization, not the project repository. Most commercial open source startups have a GitHub organization with multiple repos: the main project, plus commercial tools, SDKs, enterprise features, and infrastructure.

Track these separately: - **Core project repo**: Community engagement signal (stars, forks, external PRs) - **Organization-level repos**: Commercial engineering signal (new repos, internal tools, enterprise features) - **Contributor growth in core maintainers**: Hiring signal (new team members with commit access)

## The Strongest Open Source Investment Signal

The most compelling signal is simultaneous community growth and commercial acceleration. When the open source project is gaining stars and contributors while the company organization is building enterprise infrastructure, the flywheel is working.

## Practical Screening

Browse the [Developer Tools sector rankings](/startups-to-watch/developer-tools-q2-2026) and look for companies with high contributor counts (50+) but moderate contributor growth. Then check if they show infrastructure buildout signals — new repos for commercial features.

For the full deal sourcing framework, see [how to source startup deals before they appear on Crunchbase](/blog/source-startup-deals-before-crunchbase).

## GitHub Signals: The Earliest Public Indicator

GitHub engineering acceleration appears 6-12 weeks before fundraise announcements. The logic: a startup accelerates engineering output → builds product → raises capital → announces the round. GitHub catches step one.

The signal is in the rate of change. A commit velocity increase of +100% or more, sustained over multiple weeks, indicates something fundamental shifted in how the team is working. See [what is engineering acceleration](/blog/what-is-engineering-acceleration) for the full explanation.

## Hiring Data: The Most Explicit Indicator

Job postings on LinkedIn, AngelList, and company career pages provide 4-8 weeks of lead time. Hiring data is later than GitHub signals but more explicit: a "VP Engineering" posting tells you they are scaling the technical team, while a "Head of Sales" posting tells you they are building go-to-market.

Hiring data answers "what are they building?" GitHub data answers "how fast are they building?"

## The Comparison

**Lead time**: GitHub wins (6-12 weeks vs 4-8 weeks). Engineering acceleration precedes hiring decisions because teams ship faster before they staff up.

**Signal explicitness**: Hiring wins. A job posting for "Senior ML Engineer" tells you more about strategic direction than a commit velocity spike.

**Coverage**: Hiring wins for breadth (every company hires). GitHub wins for depth (commit-level granularity on technical startups).

**Cost**: Both are free for basic analysis. GitHub data is available via API; hiring data requires scraping or paid platforms.

## The Optimal Approach

Use both, sequentially. GitHub signals surface the candidates (earliest warning). Hiring data confirms the trajectory (what type of growth). This is the workflow described in our guide on [sourcing deals before Crunchbase](/blog/source-startup-deals-before-crunchbase).

Browse the [trending page](/trending) for the startups showing the strongest engineering acceleration this week.

Venture capital has been slower to adopt alternative data. Most deal sourcing still relies on warm introductions, demo days, and newsletters. The irony is that the most accessible alternative data source for startup investing has been sitting in the open for years: GitHub.

## What Counts as Alternative Data for Venture Capital?

In public markets, alternative data is any dataset that provides insight into a company's performance beyond traditional financial filings. For venture capital, the concept is similar — any signal that reveals startup traction before it appears through conventional deal sourcing channels.

The main categories of alternative data for VCs:

**Engineering activity** (GitHub): Commit velocity, contributor growth, repository expansion. Available via public API, updated daily, hard to fake. Lead time: 6-12 weeks before fundraise announcements.

**Hiring signals** (job boards, LinkedIn): New job postings, especially for senior engineering and go-to-market roles. Scraping required, updated weekly. Lead time: 4-8 weeks.

**Web traffic** (SimilarWeb, Sensor Tower): Rapid growth in a startup's web or app traffic. Requires paid tools, updated monthly. Lead time: 4-6 weeks.

**Social signals** (Twitter, HN, Reddit): Mentions, upvotes, and community engagement. Free but noisy, real-time. Lead time: 1-2 weeks (often lagging, not leading).

**Patent filings** (USPTO, EPO): New patent applications signal R&D direction. Free but delayed by 18 months, so more useful for competitive analysis than timing.

## Why Is GitHub the Best Alternative Data Source for VCs?

Among all alternative data sources for VCs, GitHub engineering activity has unique properties:

**It is continuous and granular.** Unlike hiring signals (which appear when a job is posted) or web traffic (which updates monthly), GitHub commits happen daily. You can track weekly velocity changes and catch acceleration patterns in real time.

**It is free and public.** GitHub's API provides commit history, contributor data, and repository metadata at no cost. No scraping required. No third-party tools needed for basic analysis.

**It reflects real work.** Commits represent actual engineering output. You cannot game commit velocity the way you can game social media metrics or app store rankings. A team that ships 200 commits in a week did real engineering work.

**It reveals intent.** The type of engineering activity — new infrastructure repos, contributor scaling, velocity spikes — tells you what phase a startup is in. Infrastructure buildout looks different from feature shipping, which looks different from a documentation sprint before a fundraise.

## How Do Quantitative Investors Approach Alternative Data?

Quantitative investment firms have understood for years that public data, processed systematically, creates information asymmetry. The edge is not in having exclusive data — it is in reading what others ignore, faster and more consistently.

The same principle applies to venture capital. Every investor has access to GitHub. Almost none of them monitor it systematically. The investor who builds a workflow around engineering signals has a structural timing advantage: they see acceleration patterns 6-12 weeks before the fundraise announcement that fills everyone else's inbox.

This is not theoretical. At VC Deal Flow Signal, we track thousands of startup GitHub orgs across 20 sectors and rank them by engineering acceleration. The patterns are consistent: commit velocity spikes, contributor growth bursts, and infrastructure buildouts appear weeks before TechCrunch writes about the company. We break down the [5 GitHub patterns that predict fundraises](/blog/5-github-patterns-that-predict-fundraises) in a separate deep dive.

## How Can Investors Start Using Alternative Data?

If you are an investor interested in adding alternative data to your sourcing process, start with the highest signal-to-noise ratio source: GitHub engineering acceleration.

1. Pick 2-3 sectors you know well 2. Watch the weekly sector rankings for unfamiliar names in the top 3 3. Cross-reference with Crunchbase for funding history and stage 4. Reach out to founders during the acceleration window (weeks 2-4 of a velocity spike)

The combination of engineering signals for timing and traditional data for due diligence gives you both a lead time advantage and a solid evaluation framework. For a practical walkthrough, see [how to source deals before Crunchbase](/blog/source-startup-deals-before-crunchbase).

Browse our sector rankings to see which startups are showing engineering acceleration right now, or get the free Signal Report for a weekly summary of the top breakout signals.

## Regulatory-Driven Development Cycles

The most important difference: fintech development cycles are partly driven by regulatory requirements, not just product-market fit. When a fintech startup shows a commit velocity spike, it may be responding to a compliance deadline rather than customer demand.

This does not make the signal less valuable — regulatory compliance requires engineering investment, which requires capital. But it changes the interpretation. A fintech company building KYC infrastructure is not necessarily iterating on product-market fit; it may be preparing for a regulated launch.

## What Infrastructure Buildout Means in Fintech

In most sectors, infrastructure buildout (3+ new repositories in 30 days) indicates platform expansion. In fintech, the new repositories often serve a different purpose: compliance infrastructure, audit logging, encryption libraries, and regulatory reporting tools.

Look at the repository names and descriptions. New repos named "kyc-service," "audit-log," or "compliance-api" tell a different story than "marketplace-sdk" or "developer-tools."

## The Strongest Fintech Signal

The most compelling fintech investment signal is simultaneous product acceleration and compliance buildout. When a company is shipping product features and building compliance infrastructure at the same time, it is preparing for a regulated launch. This typically requires significant capital, which means fundraising is imminent or recently completed.

Browse the [Fintech sector rankings](/startups-to-watch/fintech-q2-2026) to see the current data, or compare approaches using our [best deal flow tools for seed-stage investors](/compare/best-deal-flow-tools-seed-investors) guide.

## The AI Velocity Paradox

AI startups show the highest average commit velocity of any sector we track at VC Deal Flow Signal. But high velocity alone does not mean high quality deal flow. The AI sector has more open source experimentation, more research-oriented commits, and more hype-driven activity than any other sector.

The challenge for investors: separating genuine product engineering from research exploration and open source community activity. See our guide on [evaluating open source startups](/blog/open-source-startups-investor-guide) for the analytical framework.

## Research vs. Product Commit Patterns

AI startups go through a distinctive phase transition that is visible in GitHub data:

**Research phase**: Sporadic large commits, Jupyter notebooks, experiment tracking, model checkpoints. Commit messages reference papers and experiments rather than features and fixes. Velocity is unpredictable.

**Product phase**: Frequent small commits, API endpoints, deployment configuration, monitoring setup. Commit messages reference users, features, and bugs. Velocity is sustained and accelerating.

The transition from research to product is the signal. When an AI startup's commit pattern shifts from sporadic-and-large to frequent-and-small, the team is moving from "does this work?" to "let's ship this." That transition often precedes a fundraise.

## What to Watch in 2026

The current AI sector shows interesting signal diversity. Browse the [AI & Machine Learning sector rankings](/startups-to-watch/ai-ml-q2-2026) to see who is accelerating.

For a broader perspective on using alternative data for deal sourcing, see [why GitHub is the most underused signal in venture capital](/blog/alternative-data-venture-capital).

## Why a Weekly Cadence?

VC Deal Flow Signal refreshes data every Monday. Engineering acceleration is a weekly signal — commit velocity change is calculated over 14-day windows. Checking more frequently than weekly adds no new information. Checking less frequently means you miss the timing advantage.

Monday morning is ideal: the data is fresh, and you can add qualified leads to your pipeline before the week's meetings.

## The 30-Minute Workflow

This process is deliberately simple. The goal is not exhaustive analysis — it is fast identification of startups worth a deeper look.

## Step 1: Check the Trending Page (5 minutes)

Open the [trending page](/trending) and scan the top 10 startups by commit velocity change. These are the companies showing the strongest engineering acceleration across all sectors this week.

Look for unfamiliar names. If a company you have never heard of appears in the top 5, that is the signal working as intended — you are seeing it before mainstream channels surface it.

## Step 2: Filter by Your Focus Sectors (5 minutes)

Navigate to the 2-3 [sector pages](/) that match your investment thesis. Within each sector, look for startups in the top 3 that are new to you.

## Step 3: Screen the Top Candidates (10 minutes)

For each unfamiliar startup, spend 3-4 minutes on their GitHub. The [5-check screening framework](/blog/startup-engineering-metrics-investors-should-track) covers what to look for.

## Step 4: Cross-Reference (5 minutes)

Search for the company on Hacker News, Twitter, and LinkedIn. Check their careers page. The goal is to confirm the engineering signal with qualitative context.

## Step 5: Add to Pipeline (5 minutes)

For startups that pass all checks, add them to your deal tracking system. Include the engineering data: velocity change, signal type, contributor count, and the date you first noticed them. This creates a record of your timing advantage.

Subscribe to the [Signal Digest](https://gitdealflow.com/#signup) to get the highlights delivered to your inbox every Monday.

## Pattern 1: What Does a Sudden Contributor Jump Signal?

The most reliable fundraise predictor is a sudden, sustained increase in unique contributors. Not a gradual climb — a step function. The team goes from 5 contributors to 12 in a two-week window.

Why it works: most startups hire in bursts immediately after closing a round. The new hires start committing code within days of joining. If you see the contributor count jump, the round likely closed 2-4 weeks ago and the announcement is 4-8 weeks away.

What to look for: contributor count increases 50% or more in a 14-day window, sustained for at least 4 weeks after.

## Pattern 2: What Does a Burst of New Repositories Mean?

A startup that suddenly creates 3-5 new public repositories in a single month is building platform infrastructure. This pattern typically appears at the Seed-to-Series-A transition: the core product works, and now the team is building the supporting ecosystem.

Why it works: infrastructure buildout requires capital. Companies do not invest in platform engineering unless they have runway. The timing suggests a recent or imminent fundraise.

What to look for: 3 or more new repositories created in 30 days, with the new repos being infrastructure-related (SDKs, APIs, internal tools, deployment configs) rather than experimental or documentation repos.

## Pattern 3: What Does Weekend Commit Activity Indicate?

When a startup's commit pattern shifts from weekday-only to seven-days-a-week, something has changed. This is especially meaningful when the weekend activity comes from multiple contributors, not just a solo founder.

Why it works: teams work weekends when they are racing toward a deadline. Common triggers include a product launch, a fundraise-related demo, or a competitive response. All of these are signals that something significant is happening.

What to look for: sustained weekend commit activity across 2 or more contributors for 3 or more consecutive weekends.

## Pattern 4: Why Is a Documentation Sprint a Fundraise Signal?

A sudden burst of documentation commits — README updates, API docs, architecture diagrams, contributing guides — often precedes a fundraise or launch. This is the team preparing for scrutiny.

Why it works: documentation is the last thing engineering teams do voluntarily. When they document proactively, they are either preparing for due diligence (fundraise), opening up to community contributions (launch), or onboarding new hires (post-fundraise). All three are interesting to investors.

What to look for: a week or more of documentation-heavy commits after a period of feature development. The sequence matters: code first, docs second suggests intentional preparation.

## Pattern 5: What Is a Velocity Regime Change?

The strongest signal is not high velocity — it is a change in velocity regime. A startup that averages 30 commits per 14-day window for six months, then suddenly jumps to 90 commits for three consecutive windows, has undergone a fundamental shift.

Why it works: velocity regime changes reflect organizational changes. Common causes include new funding (more engineers), product-market fit (faster iteration), or a strategic pivot (rebuilding). Regime changes that sustain for 6 or more weeks are particularly meaningful.

What to look for: commit velocity that exceeds the 6-month average by 100% or more, sustained for 3 or more consecutive 14-day windows.

## How Should Investors Combine These Patterns?

The patterns above are most powerful in combination. A startup showing Pattern 1 (contributor jump) and Pattern 5 (velocity regime change) simultaneously is almost certainly in the middle of a fundraise or has just closed one.

VC Deal Flow Signal tracks all five patterns across 20 startup sectors and classifies them into four signal types: engineering hiring burst, infrastructure buildout, deploy frequency spike, and framework migration. For the full metrics checklist, see [7 engineering metrics every investor should track](/blog/startup-engineering-metrics-investors-should-track). Browse the sector rankings to see which startups are showing these patterns right now.

## CVE-Driven Development

The most distinctive cybersecurity pattern: deploy frequency spikes that correlate with CVE disclosures. When a major vulnerability is published, security companies rush to patch, update, and ship. This creates commit velocity spikes that are reactive, not strategic.

For investors, the question is whether a velocity spike reflects incident response or product momentum. Check the timing: does the spike coincide with a major CVE disclosure? If so, the acceleration is defensive, not offensive.

## Compliance Infrastructure Signals

Like fintech, cybersecurity startups build significant compliance infrastructure: SOC 2 audit trails, ISO 27001 documentation, penetration testing frameworks, and security certification tooling.

New repositories related to compliance indicate a company preparing for enterprise sales — most enterprise buyers require SOC 2 compliance at minimum. This is a positive investment signal because enterprise-readiness requires capital and precedes revenue growth.

## The Strongest Cybersecurity Signal

The most compelling cybersecurity investment signal is sustained engineering acceleration that is not correlated with external events. When a security startup is shipping fast without a CVE trigger or compliance deadline, the team is building something new. That organic acceleration is the same signal that works across all sectors — and it precedes fundraising by the same 6-12 week window.

Browse the [Cybersecurity sector rankings](/startups-to-watch/cybersecurity-q2-2026) to see which security startups are showing engineering acceleration right now.

## The Software-Hardware Spectrum

Climate tech startups fall along a spectrum from pure software to pure hardware. At the software end: carbon accounting platforms, renewable energy trading tools, grid optimization software, and ESG reporting systems. These companies look like enterprise SaaS on GitHub — high commit velocity, standard signal patterns.

At the hardware end: battery manufacturers, solar panel companies, and industrial decarbonization. These companies may have minimal public GitHub activity because most of their engineering work is in hardware design, not software.

The most interesting companies for GitHub signal analysis sit in the middle: hardware-adjacent software companies that build the intelligence layer for physical systems. Battery management systems, sensor networks, predictive maintenance for wind farms, and energy grid optimization.

## What Climate Tech Signals Look Like

**Software-heavy climate tech**: Looks like enterprise SaaS. Commit velocity, contributor growth, and signal types follow standard patterns. Use the same analytical framework as any other sector.

**Hardware-adjacent climate tech**: Lower absolute commit velocity, but meaningful infrastructure buildout signals. New repositories for data pipelines, IoT integrations, and edge computing indicate a transition from R&D to deployment.

## The R&D-to-Deployment Transition

The strongest climate tech investment signal is the R&D-to-deployment transition. When a company's GitHub activity shifts from experimental (research notebooks, prototype code) to operational (deployment scripts, monitoring, CI/CD), the technology is moving from lab to field.

This transition requires capital — deploying physical systems costs money. Engineering acceleration during this phase is a strong fundraise predictor.

Browse the [Climate Tech sector rankings](/startups-to-watch/climate-tech-q2-2026) to see which green startups are showing acceleration right now.

## Mistake 1: Confusing Stars with Traction

GitHub stars measure social interest. They are a vanity metric, not an engineering signal. A repository with 10,000 stars may have zero commercial traction. A repository with 50 stars may power a company with $5M ARR.

Stars tell you what developers find interesting. Commit velocity tells you what companies are actually building. Focus on the latter.

## Mistake 2: Ignoring the Private Repo Blind Spot

Public GitHub activity is a biased sample. Many startups — especially in enterprise SaaS, fintech, and healthcare — keep all their code in private repositories. A startup with no public GitHub activity is not necessarily inactive; it may be very active in ways you cannot see.

This means GitHub signals work best for sectors with a culture of open source or public development: developer tools, infrastructure, AI/ML, and Web3. For sectors with strong privacy norms, use GitHub signals as one input among many.

## Mistake 3: Overweighting Absolute Velocity

A startup with 500 commits per week is not necessarily more interesting than one with 50. What matters is the rate of change — is the 50-commit startup accelerating?

Absolute velocity correlates with team size, not with momentum. [Commit velocity change](/glossary#commit-velocity-change) normalizes for team size by measuring acceleration relative to the company's own baseline.

## Mistake 4: Missing Spike Context

Not all velocity spikes are positive signals. Common false positives: - Documentation sprints (high commit count, low engineering substance) - CI/CD bot activity (automated commits inflating counts) - One-time migrations (framework upgrades, monorepo restructuring) - Hackathon artifacts (intense activity that does not sustain)

The fix: spend 5 minutes on the GitHub organization before acting on a spike. Check recent commit messages and which repositories are active. This is step 3 in our [weekly sourcing workflow](/blog/deal-sourcing-workflow-weekly).

## Mistake 5: Treating Signals as Decisions

Engineering acceleration is a sourcing signal, not an investment thesis. It tells you which companies are worth investigating — not which companies are worth investing in.

The signal gets you to the table early. The decision still requires founder conversations, product evaluation, market analysis, and competitive landscape assessment. GitHub data gives you timing advantage; due diligence gives you conviction.

For the full screening framework, see the [7 engineering metrics every investor should track](/blog/startup-engineering-metrics-investors-should-track).

Public GitHub data cannot replace a proper technical deep dive. But it can do something equally valuable: help you decide which companies deserve that deep dive in the first place.

## What Can Public GitHub Data Tell Investors?

GitHub profiles reveal several dimensions of engineering health that are useful for investors:

**Engineering velocity and consistency**: Is the team shipping regularly, or are there long gaps followed by frantic bursts? Consistent commit patterns suggest disciplined engineering practices. Erratic patterns may indicate management instability, pivots, or part-time teams.

**Team composition signals**: Contributor counts, contribution patterns, and the ratio of organizational contributors to external ones reveal team structure. A startup with 3 contributors making 90% of commits has a different risk profile than one with 15 active contributors.

**Technology choices**: The programming languages, frameworks, and tools visible in public repositories tell you about technical maturity. A seed-stage startup using enterprise-grade infrastructure tooling may be over-engineering. A growth-stage company still on prototype-quality tools may have technical debt.

**Open source strategy**: Some startups use open source as a go-to-market channel (developer tools, infrastructure). Their GitHub activity IS the product signal. Others keep everything private and only have minor utility repos public. The absence of public activity is not a negative signal for the latter.

## What Are the Limitations of GitHub Data for Due Diligence?

**Code quality**: Commit volume says nothing about code quality, test coverage, or architectural soundness. A team making 200 commits a week could be writing excellent code or terrible code.

**Private repository activity**: Most startups keep their core product code private. Public repos may represent only a fraction of actual engineering work. Never assume low public activity means low engineering output.

**Individual contributor value**: Not all contributors are equal. One senior engineer making 10 thoughtful commits may contribute more value than five junior developers making 50 commits each.

**Business context**: Engineering acceleration without business context is just a number. The same commit pattern could indicate product-market fit, a desperate pivot, or a hackathon project.

## How Should Investors Use GitHub in Their Due Diligence Process?

Here is how to use GitHub data at each stage of the investment process:

**Sourcing stage**: Use commit velocity change to identify startups worth researching. This is what VC Deal Flow Signal automates — surfacing the companies showing unusual engineering acceleration. See the [7 engineering metrics every investor should track](/blog/startup-engineering-metrics-investors-should-track) for a complete checklist.

**Initial screening**: Look at the GitHub organization profile. How many public repos? When was the last push? Is there a pattern of consistent activity, or sporadic bursts? This takes 2 minutes and can save you from scheduling calls with inactive teams.

**Pre-meeting research**: Before a founder meeting, check their GitHub. What languages and frameworks do they use? How many active contributors? This gives you informed questions to ask during the call.

**Post-meeting verification**: After hearing the founder's story about their engineering team and roadmap, cross-reference with GitHub. Does the team size they claimed match contributor counts? Does their claimed velocity match commit patterns?

**Portfolio monitoring**: After investing, use GitHub signals as an early warning system. A portfolio company whose commit velocity drops 50% over two months may be experiencing team attrition, strategic confusion, or runway pressure. This signal appears before the quarterly board update.

## What Are the Ethical Considerations of Using GitHub Data?

Using public data for investment decisions is legal and common. However, there are ethical considerations:

Do not contact individual contributors or attempt to recruit from portfolio companies. GitHub profiles are public, but using them to poach talent is poor form in the investor community.

Do not make investment decisions based solely on GitHub data. It is one signal among many. The strongest investment thesis combines engineering signals with market analysis, founder evaluation, and customer reference checks.

Always remember that engineering acceleration is a leading indicator, not a guarantee. Some of the fastest-accelerating startups will fail. The data gives you timing advantage, not outcome certainty. For the specific patterns to watch, read about the [5 GitHub patterns that predict fundraises](/blog/5-github-patterns-that-predict-fundraises).

The reason is simple: raw GitHub data is noisy. Thousands of commits a day across millions of repositories. Without a framework for what matters, it is just noise.

This post explains the framework we use at VC Deal Flow Signal to turn GitHub activity into actionable deal flow intelligence.

## What Is Engineering Acceleration?

We do not measure absolute engineering output. A company with 500 commits a week is not necessarily more interesting than one with 50. What matters is the rate of change — acceleration.

When a startup's commit velocity doubles in two weeks, something has changed. Maybe they just closed a seed round and are shipping furiously. Maybe they hired three engineers and are building out infrastructure. Maybe they found product-market fit and are iterating fast on customer feedback.

Whatever the cause, the effect is visible in the commit graph weeks before it appears in a press release or a pitch deck landing in your inbox. We have identified [five specific GitHub patterns that predict fundraises](/blog/5-github-patterns-that-predict-fundraises) with the most consistency.

## What Are the Four Types of Engineering Signals?

We classify engineering acceleration into four patterns:

**Engineering hiring burst**: Contributor count jumps 50% or more in a short window. This usually means the company just closed a round and is scaling the team. If you are seeing this signal, you are likely too late for the current round — but perfectly timed for the next one.

**Infrastructure buildout**: Three or more new public repositories created in 30 days. The company is expanding its technical surface area — new microservices, new SDKs, new internal tools. This is classic Series A behavior: the product works, now they are building the platform.

**Deploy frequency spike**: Commit velocity increases 150% or more versus baseline. The team is shipping at an unusually high rate. This can indicate a product launch, a pivot, or a response to sudden customer demand. All are interesting to investors.

**Framework migration**: General acceleration that does not fit the above categories. Often indicates a technology stack transition — moving from a prototype stack to a production stack. This is the subtlest signal but can indicate the shift from exploration to exploitation.

## What GitHub Activity Is Not a Useful Signal?

Not all GitHub activity is meaningful for investors:

- **Open source maintenance**: Popular open source projects have high commit volumes but that tells you nothing about the company's product trajectory. - **Documentation pushes**: A burst of markdown commits usually means a docs sprint, not product acceleration. - **CI/CD noise**: Some teams commit generated files or configuration changes that inflate commit counts without reflecting product work.

We mitigate these by measuring change from baseline rather than absolute counts. A docs sprint looks different from a product sprint when you compare the commit graph to the company's own history.

## When Do Engineering Signals Appear Before Fundraises?

In our data, engineering acceleration signals precede fundraise announcements by three to six weeks on average. The pattern looks like this:

1. **Weeks 1-2**: Commit velocity starts climbing. Contributor count may tick up. 2. **Weeks 3-4**: Acceleration becomes obvious. New repositories appear. Signal type becomes classifiable. 3. **Weeks 5-8**: The company is heads-down building. If they are raising, the round is in progress but not yet announced. 4. **Weeks 8-12**: Fundraise announcement, TechCrunch article, your inbox lights up with the same deck everyone else got.

If you are reaching out in weeks 2-4, you are ahead of the crowd. That is the window this data gives you.

## How Should Investors Use This in Practice?

The most effective approach is sector-focused. Pick two or three sectors you know well and watch the weekly rankings:

1. When a startup you do not recognize appears in the top 3, research them. 2. Look at their GitHub: is the activity product-related or infrastructure-related? 3. Cross-reference with Crunchbase: are they pre-raise? Post-raise and scaling? 4. If the signal is strong and the timing is right, reach out to the founder.

The worst thing you can do with this data is use it as a replacement for judgment. Engineering acceleration is a leading indicator, not a guarantee. But combined with sector expertise and founder evaluation, it gives you a structural timing advantage that most investors do not have. For a deeper look at technical evaluation, see our guide on [how VCs use GitHub for due diligence](/blog/github-due-diligence-for-vcs).

## Where Can I Start Watching?

We track engineering acceleration across 20 startup sectors, updated weekly. Each sector page ranks the top startups by commit velocity change and classifies their signal type.

Browse the sector rankings to see which startups are accelerating right now.

## Why Is Traditional Deal Flow Not Enough?

Most VCs source deals through their network. The problem is that networks are shared. By the time a startup is making the rounds at demo day or landing in your inbox via a warm intro, it is also landing in every other investor's inbox.

The result is that competitive deals — the ones most likely to generate outsized returns — are identified late and negotiated under pressure. The investor who arrives first has a structural advantage: they set the terms, they build the relationship before the founder is overwhelmed with options. This is why [alternative data is becoming essential for venture capital](/blog/alternative-data-venture-capital).

## What Are the Main Types of Deal Flow Signal?

There are several categories of deal flow signal, each with different lead times and reliability:

**Engineering signals** (highest lead time): Changes in a startup's public engineering activity — commit velocity, contributor growth, repository creation. These signals appear 6-12 weeks before fundraise announcements because engineering acceleration precedes product milestones, which precede fundraise decisions.

**Hiring signals** (medium lead time): Job postings, especially for senior engineering and go-to-market roles, indicate growth plans. Lead time is typically 4-8 weeks.

**Web traffic signals** (medium lead time): Rapid growth in a startup's web traffic can indicate product-market fit. Lead time is 4-6 weeks.

**Social signals** (low lead time): Mentions on Twitter, Hacker News, Product Hunt, and industry forums. By the time a startup trends on social media, most investors are already aware.

## Why Are GitHub Signals the Best Leading Indicator?

GitHub engineering activity has unique properties that make it the most reliable early deal flow signal:

1. **It is hard to fake.** Commits represent actual work. You cannot game commit velocity the way you can game social media metrics. 2. **It is continuous.** Unlike hiring signals (which appear when a job is posted) or press (which appears when a company wants attention), engineering activity happens daily. 3. **It is free and public.** Unlike web traffic data (which requires third-party tools) or hiring data (which requires scraping job boards), GitHub data is available via a public API. 4. **It reveals intent.** The type of engineering work — infrastructure buildout vs. feature shipping vs. team scaling — tells you what phase the company is in.

## How Does VC Deal Flow Signal Work?

We monitor GitHub engineering activity across 20 startup sectors. For each sector, we:

1. Identify active startup organizations using topic-based search. 2. Pull commit activity, contributor data, and repository creation data. 3. Calculate 14-day commit velocity and its rate of change. 4. Classify the signal type (hiring burst, infrastructure buildout, deploy spike, framework migration). 5. Rank startups by engineering acceleration.

The result is a weekly-updated ranking of startups showing the strongest engineering momentum in each sector. Investors can use this to identify breakout companies weeks before they appear through traditional channels.

## How Do I Get Started with Deal Flow Signal?

The simplest way to start using deal flow signal is to get our free Signal Report — five breakout startups with real GitHub acceleration data, delivered weekly. For deeper access, our Dashboard gives you the full ranked list across all 20 sectors with filtering by stage, geography, and signal type. To learn the practical framework, read our guide on [how to read GitHub signals for startup investing](/blog/how-to-read-github-signals-for-startup-investing).