Case study · GitHub signal → priced round

Linear to a $35M Series B: Signal in Integrations, Not Stars

Linear's $35M Series B is the case study for companies whose GitHub signal is downstream, visible in tutorials, plugins, and dev-tool integrations.

At a glance

Company: Linear
Sector: SaaS / project management
Primary repo: github.com/linear/linear
Trigger window: first half 2022
Stars at trigger: Lower repo star count, but high developer-tooling penetration
Announced raise: $35M Series B (2022-07-26)
Lead investor: Series B (Accel, Sequoia, others)
Time-to-money read: Linear is the rare case where the GitHub presence is intentionally minimal, the signal lived in mentions and integrations

Most case studies on this page are about repo-level acceleration. Linear is here as the counterexample: the company shipped a closed-source product whose adoption was visible in *adjacent* repos, community SDK wrappers, CLI tools, GitHub Action integrations.

By mid-2022 the number of independent Linear-integration repos was climbing fast on GitHub. Each one is a weak signal; in aggregate they're a strong one. Combined with the public API changelog cadence (a proxy for engineering velocity), the picture was clear.

The $35M Series B at the end of July 2022 was the priced confirmation. The case is useful precisely because it forces a deal-flow system to look beyond the company's own repos, integration density is its own signal type.

Signals that would have flagged this pre-raise

Integration repo count:Rising count of Linear-API wrapper repos through 2022
Public changelog cadence:Weekly product updates
Dev-tool mentions:Default issue tracker in many OSS workflow tutorials

How the timeline read

The engineering acceleration was observable during first half 2022, while any fundraising paperwork was still private. The announced event, $35M Series B on 2022-07-26, landed after the signal window: Linear is the rare case where the GitHub presence is intentionally minimal, the signal lived in mentions and integrations. That ordering is the entire thesis of this series: by the time a round appears in a funding digest, the repositories were already telling the story at lower repo star count, but high developer-tooling penetration.

In practice, that is what a weekly monitoring cadence buys you. VC Deal Flow Signal re-scores this sector (SaaS / project management) every week across its tracked repository, so a window like this one surfaces as a rising trend rather than a single spike you had to be lucky to catch. The pre-raise signals listed above are the rows that moved while the press stayed quiet.

Repositories

github.com/linear/linear

Frequently asked questions

Is GitHub stars the only signal worth tracking?

No, and Linear is the proof. Integration repos, changelog cadence, and dev-tool mentions can carry as much signal as a single high-slope repo.

How do you systematize the 'integration density' signal?

Count GitHub repos that mention the brand or import the SDK over rolling windows. A rising count over 90 days is a strong corroborating indicator.

Find the next one

VC Deal Flow Signal tracks engineering acceleration weekly across twenty sectors, the same signal shapes that preceded the raise above.

Get the weekly signal report →

Related case studies

Read them side by side: these related cases span Scheduling / OSS SaaS, Dev tools / observability, Product analytics, each with its own trigger window and raise event, and the same pre-raise signal shape held in every one. A pattern that repeats across different sectors and different windows is what separates a repeatable signal from an after-the-fact story.