How Supabase grew from 0 to 50K+ GitHub stars
Tags: startup, opensource, github
Published: 2023-11-15 14:12:47

Rory '@rorstro' Wilding has led [Supabase](https://supabase.com/)'s growth team since its early days (founded in 2020). 

Today, the company hits 2.5M monthly unique visitors (MUV), according to [similarweb.com](https://www.similarweb.com/website/supabase.com/#overview). It has [50K+ GitHub stars](https://github.com/supabase/supabase), 5K forks, and [90K+ Twitter followers](https://twitter.com/supabase).

Rory hosted an [AMA session on Product Hunt](https://www.producthunt.com/discussions/ama-session-on-product-led-growth-with-rory-head-of-growth-at-supabase) earlier this year to share his insights and lessons learned on product-led growth, open-source, meme marketing, launch weeks, community building, remote work… 

**Below are my key takeaways.**

## TL,DR

- It starts with a great product;
- Talk to as many users as possible;
- Write helpful content;
- Run launch weeks to maximize compound effect;
- Engage with your community.

![Supabase Home](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/pkvyujlpm5kv2uh3mubx.png)

## Lessons learned growing Supabase from 0 to 50K+ GitHub stars

### It starts with a great product

Above all, one quote really struck me when Rory talks about growth at Supabase:

> **Without a solid product that solves a need for people, it's pretty hard to grow anything. —** Rory Wilding, Head of Growth, Supabase

Growth starts with a great product that solves a _real_ pain point. Before running any tactics or "hacks," start building a product people want. Then talk to users.

### Enable early growth by talking to (many) users

Rory explained that Paul '@kiwicopple' Copplestone and Ant '@awalias' Wilson, Supabase's co-founders, played a significant role in **discovering what developers wanted by engaging with them.** The objective? To have a deep understanding of users' needs.

> **In the early days, there's no substitute for speaking to as many users as possible. —** Rory Wilding, Head of Growth, Supabase

As a fun fact, Rory shared that he spent a weekend going through over 3,000 developer profiles on GitHub after a sign-up spike, reaching out to as many as possible to chat with them about their Supabase's likes and dislikes. [Do things that don't scale](http://paulgraham.com/ds.html), right?

Build something people _really_ want and talk to as many users as possible to help you set the foundations of solid, steady growth, and so you're ready to skyrocket.

### Setting up the launchpad

From the AMA session, I'd summarize Supabase's growth strategy into a mix of three main channels (spoiler alert: no paid ads): 
- content marketing, 
- viral marketing, and
- community building.

**1: write helpful content**

Developers have different jobs-to-be-done, and Supabase can solve many problems.

Solid fundamentals are key here. Case studies, code examples, and documentation help developers learn about the product and achieve their objectives.

> **If a developer can clearly see how your developer experience can help their workflow then using your product becomes an obvious choice. —** Rory Wilding, Head of Growth, Supabase

In short, give developers helpful, educative content.

![Supabase Documentation](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ec9pf2hy63hfi9bgoqaz.png)

For further inspiration, read this [introduction to the DEV Content Framework](https://dev.to/fmerian/introduction-to-the-dev-content-framework-54be) to help you leverage your content strategy.

**2: run launch weeks to maximize compound effect**

Supabase has set a "[launch week](https://supabase.com/blog/supabase-how-we-launch)" strategy:

**Once every 3-4 months, the team spends a week shipping a new feature every day.**

Rory breaks down this strategy into 4 main steps:

1. Early on, Ant and Paul, Supabase's co-founders, set the priorities with one key principle: **fixed timeline, flexible scope**;
2. The product teams figure out the challenges and solutions by themselves;
3. Few weeks before the launch week, the team reviews how shippable on-going projects are — including documentation;
4. Post-launch week, the team reflects on what worked and what could be improved.

> **Launch weeks have been great for both aligning the team and getting traction within the community. —** Rory Wilding, Head of Growth, Supabase

There's more. If such a shipping cadence may sound impressive, it doesn't stop here.

Supabase keeps shipping things every month, so the team doesn't necessarily hold features back for launch week. It "just" ships and shouts as much as possible.

**3: keep the momentum going**

Post-launch week, the Supabase team keeps momentum by engaging and supporting its community, amplifying community-generated content in monthly email campaigns.

> The monthly community email newsletter has strong engagement and **showcases all the big monthly updates from the team and the community. —** Rory Wilding, Head of Growth, Supabase
 
## Wrapping up

Founded in 2020, Supabase now hits 2.5M MUV and has 50K+ GitHub stars, 5K forks, and 90K+ Twitter followers.

During his AMA session, Supabase's Head of Growth Rory Wilding insisted on (1) building a great product and (2) talking to as many users as possible.

I'd summarize Supabase's growth strategy into a mix of three main channels:

- content marketing: Write helpful content that educates your users;
- viral marketing: set a "launch week" strategy to maximize compound effect;
- community building: engage with your community to keep the momentum going.

And that's it! I hope you enjoyed reading these key takeaways and found some insights to help grow your developer-first product. Over to you!