Growth idea action plan
Supabase Community Day before feature week
Open the launch cycle by showcasing contributors, integrations, and adjacent builders before talking only about your own roadmap, so the release feels like a community event instead of a brand monologue.
Why this can grow a startup
A feature week gets broader when it is not only about the company shipping the features. Supabase turned that into a repeatable distribution move with Community Day. By highlighting contributors, content creators, integrations, partner tools, and community-built projects, the company widened the audience before the core releases landed. That creates more than goodwill. It creates more people with a reason to share, explain, and build around the product at the same time. For products with open-source, marketplace, or developer-community edges, this is one of the cleanest ways to make the launch bigger without faking urgency. You grow the event by making more real participants part of it.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. A partnership only compounds when both sides get trust or distribution they could not cheaply buy alone. I would start with the smallest shared win, prove it in public or in pipeline, then make the relationship bigger. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where supabase community day before feature week can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Community-led Growth and Open Source channel.
- Use the evidence from supabase.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Supabase describes itself as a 'community of communities' and used Community Day to highlight integrations, creators, and contributors while reporting growth from 25K to 60K GitHub stars, 75K to 250K hosted databases, 271 to 750 contributors, and Discord from 0 to 11K.
Source: Supabase Blog: Community Day (supabase.com)
GrowthDex source hub: Supabase Blog: Community Day
Last checked: 2026-06-09T11:08:27.000Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Stripe Apps partner ecosystem after publish compounds discovery 1 shared channel · 1 shared stage
Related GrowthDex essays
- The developer tool should launch like a series, not a stunt developer marketing, community-led growth, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory