The launch week playbook, from Supabase to your startup

On Monday, March 29, 2021, Supabase tried something new. Instead of shipping features whenever they were ready, it saved them up and released one every day for a week: pricing on Monday, storage on Tuesday, the command-line tool on Wednesday, UI components on Thursday, and a final “one more thing” on Friday.¹

It called it Launch Week, and ran 15 of them between March 2021 and July 2025, roughly three a year.² Over the same years Supabase grew from a Y Combinator startup into one of the default databases for AI apps. In June 2026 it raised $500 million at a $10 billion pre-money valuation, with nearly 10 million developers on the platform and more than 60% of new databases launched by AI tools.³ Its main GitHub repository has more than 111,000 stars.⁴

Launch weeks didn’t cause all of that. But they gave a small team a repeatable way to be loud, several times a year, on its own schedule. Here’s how the format works and how to run a version of it at a B2B AI startup.

Why Supabase started doing it

Co-founder Ant Wilson explained the thinking in a 2021 post. After Y Combinator, the external pressure of a fixed Demo Day disappeared. So the team recreated it: “why don’t we just pretend that we’re starting the batch again.”⁵

He called launch weeks “a key part of a Product-Led Growth strategy,” and described the rule that makes them work: fixed timeline, flexible scope.⁵ The dates don’t move. What ships inside them depends on what’s ready. Features that shipped quietly in the weeks before can be packaged and told properly during launch week.

That rule is what makes it safe for a small team. You aren’t promising five features on a date. You’re promising five stories.

The anatomy of a launch week

Over five years the format has grown, but the core pieces are consistent.

• One launch a day. Each day has one headline release with its own blog post, demo and docs.¹
• A ticket and a reason to sign up. For Launch Week 5 in August 2022, Supabase issued more than 3,000 virtual tickets, with a “Golden Ticket” swag draw for ticket holders.⁶
• Swag people want. Launch Week 7 gave away keyboards, T-shirts, socks and 200 sticker packs.⁷
• A hackathon. Later launch weeks pair the five days with a 10-day hackathon, so the community builds with the new features straight away.⁸
• Meetups. The Launch Week 15 page in July 2025 listed community meetups in 49 cities.⁸
• A main stage and a build stage. The five headline launches sit on the “main stage,” with smaller releases grouped on a “build stage” so they still get noticed.⁸

What it produced

Many of Supabase’s best-known features arrived during launch weeks, and several drew hundreds of points on Hacker News on their own.

Launch	Date	Hacker News points
Edge Functions	March 2022	2689
Realtime Multiplayer	August 2022	35610
Local development: migrations, branching and observability	August 2023	18211
General availability, with more than 1 million databases managed	April 2024	27212
postgres.new, an in-browser Postgres sandbox	August 2024	36613

One detail is easy to miss. The umbrella announcement for Launch Week 4 got just 23 points on Hacker News.¹⁴ The individual launches did far better. People share a specific, useful thing. They rarely share “we have a week of announcements.” Each day needs to stand on its own as news.

The format spread

Other developer tools copied it. Raycast ran a launch week in July 2022.¹⁵ Resend shipped seven features in seven days in March 2023 and has run several launch weeks since.¹⁶ Trigger.dev ran its second launch week in August 2025,¹⁷ and Windmill held its second in late March 2026.¹⁸ Supabase CEO Paul Copplestone co-maintains launchweek.dev, a public tracker of launch weeks across the industry.¹⁹

Where launch weeks fall short

The format has real costs, and it’s worth knowing them before you commit.

• Channels push back. Hacker News moderator Daniel Gackle (dang) wrote in 2025 that “the ‘launch week’ pattern isn’t great for HN,” because a run of follow-up posts gets downweighted.²⁰
• It can be too much for a tiny product. Evil Martians, a product agency, warns that the format “might not be useful for really small products,” that bugs and feature requests may flood in, and that there is “no absolute evidence yet that the launch weeks yield better results.”²¹
• The format evolves. In 2026 Supabase also ran Supabase Select, a one-day conference in San Francisco with a hackathon the next day.²²

Treat a launch week as one tool for creating moments, and judge it by what it produces for you.

The playbook for a small B2B AI team

You don’t need five big features. You need one fixed week, three to five stories your buyers care about, and a plan for each day. A team of three to ten can run this version.

Six weeks out: pick the week and the theme

• Choose dates that avoid big industry events and holidays in your buyers’ markets.
• Write a one-line theme that ties the launches together, such as “the week we made X fully automatic.”
• List every release that will be ready, plus anything that shipped quietly in the past two months. Pick the strongest three to five. Fixed timeline, flexible scope.

Four weeks out: give every day an owner

For each day, one person owns:

• a short blog post explaining the problem it solves, written in your buyers’ language
• a 60 to 90 second demo video
• a founder post for LinkedIn and X
• updated docs and a changelog entry
• one customer quote or early-user result, if you have one

Two weeks out: build the anticipation

• Publish a launch week page where people can sign up for a daily email or claim a “ticket.”
• Invite your best customers to a live demo on one of the days.
• Line up partners, investors and friendly founders to share their favourite launch.
• If your product suits it, announce a small build challenge or a free-trial extension that runs for the week.

Launch week: the daily rhythm

1. Publish in the morning in your buyers’ main time zone.
2. The founder posts, and the team shares within the first hour.
3. Send the daily email to sign-ups and customers.
4. Post in the one or two communities where your buyers ask questions.
5. Spend the afternoon replying to every comment and question.

On Friday, publish a recap of the whole week, and save something small for a “one more thing.”

After the week: measure and follow up

• Compare sign-ups, demo requests and trial starts for each day against a normal week.
• Note which launch drove the most interest. That’s a signal about what your buyers want.
• Hand sales a list of everyone who signed up, attended a demo or replied, with the launch they responded to.
• Publish the recap as a page you can link to in sales emails for months.

Adjustments for B2B buyers

Developers try things the same day. Business buyers often need a reason to talk to their team first. So pair each launch with something a champion can forward: a customer story, a one-page summary, or a short video their manager will watch. If five days is too much, run three. The fixed date matters more than the length.

A launch week turns a steady stream of releases into a moment the market can’t miss. Fix the date, keep the scope flexible, make every day its own story, and measure what each one brings in.

Footnotes

1. Supabase, “Launch Week” (March 25, 2021). supabase.com ↩ ↩²

2. Supabase blog, Launch Week category. supabase.com ↩

3. Supabase, “Supabase Series F” (June 2026), and TechCrunch, “Supabase doubles valuation to $10B in 8 months” (June 5, 2026). supabase.com, techcrunch.com ↩

4. GitHub, supabase/supabase repository, star count checked October 16, 2026. github.com ↩

5. Ant Wilson, “How we launch at Supabase” (November 26, 2021). supabase.com ↩ ↩²

6. Supabase, “Community Day” (August 19, 2022). supabase.com ↩

7. Supabase, Launch Week 7 page (April 2023). supabase.com ↩

8. Supabase, Launch Week 15 page (July 2025), archived copy. web.archive.org ↩ ↩² ↩³

9. Hacker News, Supabase Edge Functions (March 31, 2022). news.ycombinator.com ↩

10. Hacker News, Supabase Realtime Multiplayer (August 18, 2022). news.ycombinator.com ↩

11. Hacker News, “Supabase Local Dev: migrations, branching, and observability” (August 9, 2023). news.ycombinator.com ↩

12. Supabase, “Supabase is now GA” (April 15, 2024), and the Hacker News thread. supabase.com, news.ycombinator.com ↩

13. Supabase, “Launch Week 12 top 10” (August 2024), and the Hacker News thread. supabase.com, news.ycombinator.com ↩

14. Hacker News, “Supabase Launch Week IV” (March 2022). news.ycombinator.com ↩

15. Raycast, “Launch week summary” (August 9, 2022). raycast.com ↩

16. Resend, “Launch Week 1 wrap-up” (March 2023). resend.com ↩

17. Trigger.dev, Launch Week 2 (August 2025). trigger.dev ↩

18. Windmill, “Launch week #2” (March 30 to April 3, 2026). windmill.dev ↩

19. launchweek.dev, community-maintained tracker. github.com ↩

20. Daniel Gackle (dang), comment on Hacker News (February 21, 2025). news.ycombinator.com ↩

21. Evil Martians, “How to do launch weeks for developer tools startups and small teams” (November 5, 2024). evilmartians.com ↩

22. Supabase, “Supabase Select 2026 recap” (October 2, 2026), and the Supabase Select event page. supabase.com, select.supabase.com ↩