# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/supabase-community-day-before-feature-week/
- Source: [supabase.com](https://supabase.com/blog/launch-week-6-community-day)
- GrowthDex source hub: [Supabase Blog: Community Day](/sources/supabase-blog-community-day-supabase-com/)
- Last checked: 2026-06-09T11:08:27.000Z
- Rarity: epic
- Budget: medium
- Channels: Community-led Growth, Open Source, Partnerships
- Stages: community day, launch week, contributors, partner ecosystem


## Why this can grow

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

1. Define one narrow startup segment where supabase community day before feature week can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community-led Growth and Open Source channel.
3. Use the evidence from supabase.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. 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.

## Adjacent tactics in the same lane

- [Stripe Apps partner ecosystem after publish compounds discovery](/growth-ideas/stripe-apps-partner-ecosystem-after-publish-compounds-discovery/) - 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The developer tool should launch like a series, not a stunt](/blog/the-developer-tool-should-launch-like-a-series-not-a-stunt/) - developer marketing, community-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.