Case study · GitHub signal → priced round
Cal.com, OSS scheduling to a $32M Sequoia Series B
Cal.com's open-source Calendly alternative crossed adoption thresholds before Sequoia led the $32M Series B.
At a glance
- Company
- Cal.com
- Sector
- Scheduling / OSS SaaS
- Primary repo
- github.com/calcom/cal.com
- Trigger window
- first half 2024
- Stars at trigger
- ~30K stars at trigger window
- Announced raise
- $32M Series B (Sequoia) (2024-09-17)
- Lead investor
- Sequoia
- Time-to-money read
- OSS scheduling slope + dev-influencer adoption led the round
Cal.com's positioning is the OSS Calendly. The repo carried a steady star slope and a high-energy maintainer presence on dev Twitter, both signals.
By early 2024 the dev-influencer adoption signal was strong: a recognizable list of public developers using Cal.com for their booking pages. That public reference list is its own leading indicator.
Sequoia's $32M Series B in September 2024 closed an adoption story driven by dev-community endorsement as much as by the repo activity itself.
Signals that would have flagged this pre-raise
- Star slope:~22K → 30K stars in 12 months
- Dev-influencer adoption:Public booking pages for high-visibility devs
- Release cadence:Weekly tagged releases
How the timeline read
The engineering acceleration was observable during first half 2024, while any fundraising paperwork was still private. The announced event, $32M Series B (Sequoia) on 2024-09-17, landed after the signal window: OSS scheduling slope + dev-influencer adoption led the round. 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 ~30k stars at trigger window.
In practice, that is what a weekly monitoring cadence buys you. VC Deal Flow Signal re-scores this sector (Scheduling / OSS SaaS) 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
Frequently asked questions
Is dev-influencer adoption a generalizable signal?
Yes, when measured systematically. Track public profile pages for prominent devs and watch for product usage.
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
- Linear to a $35M Series B: Signal in Integrations, Not Stars
- PostHog, OSS analytics to a $15M YC Series B
- Supabase, 65K-star Firebase alternative meets an $80M Series C
Read them side by side: these related cases span SaaS / project management, Product analytics, Backend-as-a-service, 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.
Related proof stories
Related topics