How often should a small team email its waitlist in the months before launch?

Start with the welcome email and the first-week follow-up

The welcome email should arrive within a minute of signup and do three things: confirm they are on the list, restate what they will get and when, and give them their referral link or position if you run one. Keep it under 150 words. People read this one. The welcome email is typically the most-opened message of the whole sequence, so put the share ask here rather than three emails later. Related: What should a maker do to keep waitlist emails compliant with US anti-spam rules?

A follow-up within the first week keeps the signup from going cold. Use it to show something real: a screenshot of what you built this week, a short story about why you started, or a single question such as "what are you using today for this?" Replies to that question are worth more than any survey you will run later, and they train inbox providers that your mail is wanted.

Keep reading: Why a Plain Waitlist Underperforms, Turning Signups Into Referrers, Building Pre Launch Momentum. See how RefVite helps you pre-launch referral leaderboard and waitlist for makers.

Settle into a rhythm you can actually keep

For most small teams, one email every two to three weeks during the pre-launch stretch is sustainable and enough to stay familiar. Weekly works if you have real progress to show each week. Monthly is the floor below which people forget they signed up and mark you as spam when you finally launch. The right cadence is the one you will still be hitting in month four, not the one that looks ambitious in a plan. Related: How do you write waitlist page copy that converts visitors who have never heard of you?

Put the cadence in the signup microcopy and in the welcome email, then honor it. "About every two weeks" is a promise. Skipping a month and then sending three in a week breaks it. If you miss a beat, do not apologize at length. Send the next one on time with something worth reading.

Give each email one job

Pre-launch emails fail when they try to be a newsletter, a product update, a referral push, and a survey at once. Pick one job per send. Progress updates build trust. Behind-the-scenes decisions ("we cut feature X, here is why") build respect. A referral reminder with the current leaderboard standings works best as its own short email, sent when there is a reason: a new reward tier, a deadline, a milestone. Related: Building Pre Launch Momentum

Subject lines should describe the content, not tease it. "We shipped the export feature" beats "Big news inside." The list is small and made of people who chose to hear from you, and curiosity tricks burn that goodwill fast. Plain text or lightly formatted emails from a named person usually outperform designed templates at this stage because they read like a note, not a campaign.

Tighten the cadence as launch approaches

In the last three or four weeks before launch, it is reasonable to move to weekly, then to a short daily run in the final two or three days: what launches, when access opens, what early joiners get. Tell people in advance that the pace will pick up so it reads as a countdown rather than a barrage. This is also the moment for a final referral push, since the leaderboard closes and positions become real. Related: When should a maker choose an invite-only beta over an open public waitlist?

After launch, the sequence splits. People who got access need onboarding emails. People still waiting need a clear date or wave schedule. Sending the same generic "we launched" blast to both groups is the fastest way to lose the second one. Segment on access status before you write a word.