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.
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-reported evidence
Source: Supabase Blog: Community Day
Supabase reported community growth from 25K to 60K GitHub stars, 75K to 250K hosted databases, 271 to 750 contributors, and 0 to 11K Discord members alongside its Community Day loop.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Community-led Growth, Open Source, Partnerships is relevant to community day, launch week, contributors and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community-led Growth and Open Source, using evidence from Supabase Blog: Community Day as context—not as a promised result.
- Record a baseline for: Share of partner-referred attendees who complete the intended next step. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.