Feature Teasers: How SaaS Teams Build Hype Before a Launch (8 Examples)

Why teasers work

A launch post competes with everything else in the feed that day. A teaser gives it a head start: people who saw the hint are watching for the reveal, and the comments on the teaser become social proof before anything has shipped.

Look at the two LinkedIn posts that started this idea. Slite's CEO posted “Tomorrow is laaaaunch daaaay” with no details at all; the comments filled up with founders and investors saying they couldn't wait. Nooks co-founder Rohan Suri posted “Something is cooking at Nooks” the day before a launch and thanked by name the sales creators who had helped build it, so they had every reason to share it.

The mechanism is simple: curiosity plus a date. The reader knows something is coming and when, so the launch post the next day is the second time they hear about it, not the first.

Teaser formats that work

1. The night-before post. A founder or PM says tomorrow is launch day, with a hint and a thank-you to the people involved. Cheapest format, works at any size.
2. The sneak peek. A short clip or screenshot of the feature in use, a week or two out. Raycast has a whole Hype Team whose job includes sneak peeks of upcoming features on X.
3. The feature waitlist. Announce the feature, show a demo, and let people sign up for early access. Notion did this for Notion AI in November 2022.
4. The launch week. One launch a day for five days, announced in advance with a schedule and hints. Supabase made this format famous for developer tools; Raycast and Inngest ran their own.
5. The event countdown. Big launches saved for a keynote with a date, like Vercel Ship or Figma Config.

This is different from building in public. Building in public shares the journey over months. A teaser is a launch tactic aimed at one date.

What the best teams do differently

• They set the date before they tease. A teaser without a date is just noise. Notion's waitlist, Supabase's launch week schedule and every “tomorrow” post work because the reader knows when to come back.
• They tease the outcome, not the settings page. Show what the user will be able to do, in a few seconds of video, not a list of features.
• They don't hold features hostage. Supabase says it very rarely holds back features for Launch Week and encourages shipping early; the week packages work, it doesn't delay it.
• They give the audience a role. Join the waitlist, turn on notifications, come to the livestream, or, like Nooks, get thanked by name.
• They use more than one voice. Raycast posts from the company account and from team members' personal accounts, which it finds very effective. Founders, PMs and beta customers each reach a different crowd.
• They promise only what ships. Raycast's rule is to be intentional about what it promises and when it delivers on that promise.

When teasers backfire

• The date slips. The audience you built shows up to nothing. Tease only what is code-complete or close to it.
• The feature is small. A countdown for a minor settings change teaches people to ignore your countdowns. Save teasers for launches that change what users can do.
• The waitlist never ends. Waitlists build demand only until people forget why they joined. Notion opened its AI alpha waitlist in November 2022 and made it available to everyone three months later, in February 2023.
• Existing customers hear last. Teasers on social reach strangers; make sure customers get an email or in-app note before launch day too.

How to run it: the playbook

1. Pick a launch worth teasing. A feature that changes what users can do, not a settings tweak. If you can't show it in a 15-second clip, it probably doesn't need a teaser.
2. Lock the date. Only tease once the feature is code-complete or close. Put the date in the teaser.
3. Plan three beats. About a week out: a sneak peek or hint. The day before: a countdown post from the founder or PM. Launch day: the reveal with a demo and a link.
4. Give people an action. A waitlist, an early-access form, a livestream reminder or a notify-me button, so the teaser builds a list you can email on launch day.
5. Line up the voices. Brief the founders, the team and a few beta customers; tag the people who helped build it.
6. Tell customers directly. Send existing users an email or in-app note on launch day, so they don't learn about it from a competitor's repost.
7. Close the loop. Reply to every teaser commenter with the launch link, then publish a recap or changelog entry that lasts after the posts fade.

What to measure

• Waitlist or early-access sign-ups per teaser post
• Reach and comments on teaser posts compared with your normal posts
• Launch-day visits and sign-ups compared with your last launch without a teaser
• Share of the waitlist that activates the feature in the first week
• Replies and reposts from people outside your team

Pitfalls

• Teasing before the feature is ready, then missing the date
• Vague “something big is coming” posts with no date or hint
• Countdowns for minor updates, which train people to ignore your countdowns
• Waitlists that stay closed for months with no updates
• Holding finished features back just to have something to tease