Case study · GitHub signal → priced round

Resend, react-email breakout slope to an $18M Sequoia Series A

Q: Why bundle an OSS library with a paid API?

Because developers find the library in search and adopt the API afterward. The OSS repo is the top of the funnel; the paid API is the conversion.

Q: How early was the signal?

react-email's star slope hit a breakout profile by late 2023. Six to nine months of leading signal preceded the Series A.

Resend bundled an email API with a popular React component library; the GitHub signal preceded the Sequoia Series A by months.

At a glance

Company: Resend
Sector: Dev tools / email API
Primary repo: github.com/resend/resend-node
Trigger window: first half 2024
Stars at trigger: ~15K stars across the two repos
Announced raise: $18M Series A (Sequoia) (2024-08-13)
Lead investor: Sequoia
Time-to-money read: The react-email repo's breakout was visible 6-9 months before the Series A

Resend is a model for the 'OSS funnel + paid API' pattern. react-email is the component library, open-source, MIT-licensed, useful on its own. resend-node is the SDK for the paid API. Both repos compounded together.

The smarter signal is the *react-email* trajectory: when an OSS component library hits 10K stars in under a year, the parent company's commercial trajectory tends to be on the same curve. By Q2 2024 the slope was unmistakable.

Sequoia priced the $18M Series A in August 2024. The funnel had been working publicly for at least nine months by then.

Signals that would have flagged this pre-raise

react-email star slope:0 → 10K stars in <18 months
Resend SDK adoption:Growing npm install weekly
Newsletter density:Default email-API recommendation in dev newsletters by 2024

How the timeline read

The engineering acceleration was observable during first half 2024, while any fundraising paperwork was still private. The announced event, $18M Series A (Sequoia) on 2024-08-13, landed after the signal window: The react-email repo's breakout was visible 6-9 months before the Series A. 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 ~15k stars across the two repos.

In practice, that is what a weekly monitoring cadence buys you. VC Deal Flow Signal re-scores this sector (Dev tools / email API) every week across 2 tracked repositories, so a window like this one surfaces as a compounding composite 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

Frequently asked questions

Why bundle an OSS library with a paid API?

Because developers find the library in search and adopt the API afterward. The OSS repo is the top of the funnel; the paid API is the conversion.

How early was the signal?

react-email's star slope hit a breakout profile by late 2023. Six to nine months of leading signal preceded the Series A.

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 Dev tools / auth, Backend platform, Dev tools / background jobs, 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.