hi.videoSay hi

For sales and founders

A beta invite email for the first people on your waitlist

A subject line that says “You're in” can arrive months after someone joined a waitlist. By then they may have forgotten the product name. Tell them where they signed up and what they'll be able to try today. A plain link to the starting point is more useful in that first email than a list of everything you hope to build.

Send an invitation with one first task

Imagine a founder building a tool for people who organize neighborhood repair nights. The first release makes a printable job board. The bigger project includes parts inventory, but that feature is still on paper. Here's an invitation the founder could send to someone who asked to try the board.

Subject line: Your repair-night job board is ready to try

Hi Ari, you signed up to try our printable board for repair nights. Your spot is ready. In this round you can move three example repair jobs between tables and print the resulting board. Set aside about ten minutes. You can use the sample jobs we provide.

Open your beta invitation here: [your personal activation link].

Start with the desk lamp and move it from intake to the electrical table. Print or preview the board. Could someone staffing the room tell where the lamp should go? Reply to this email if something is unclear. It comes straight to me.

Dev, founder

Replace the bracketed activation text with the actual access link in the email. If it expires, give the real date, time zone and process for getting another. Set a time estimate by walking through your own first task with a fresh account. A founder who knows where every control lives may finish much faster than a newcomer.

Say why you picked this test

A welcome can be about thirty seconds of you describing one design question. For the repair-night example, this is the part you'd record.

Hi, I'm Dev. Think of the volunteer who takes over halfway through a repair night. Will the sheet on the wall tell them where to carry that desk lamp? That's the part I'm trying to get right. You'll find the sample jobs already there. If you get stuck, send me the last thing you tried and I'll take a look.

You can record a welcome before the invitations go out. Keep personal access links and invitation codes in each user's email, away from the recording. Someone might share the hello with another organizer because the repair-night idea sounds interesting. The guide to reusing an introduction explains how to address a group without making the welcome sound like a note meant for another individual.

Make the boundaries easy to understand

If parts inventory is the reason someone joined the waitlist, the job board may be of little use to them. Say that in ordinary language. “This round covers the printed board. If you're waiting for parts inventory, reply ‘inventory’ and I'll keep you on that list.” Only offer that reply if you can actually honor it.

Separate the trial from any other decision. If it costs money, requires a specific device or involves a time commitment beyond the first exercise, say so before the activation link. If participants should use sample jobs, supply those jobs. An invitation to “try it with your own data” asks for much more than ten minutes of moving a lamp card around.

Answer the reply someone actually sends

Suppose Ari writes, “The lamp jumped back to intake after I opened the print view.” Confirm the observation and ask only for the missing detail you need. “Thanks, Ari. Were you looking at the paper preview when the lamp moved, or did you notice it after closing the preview?” That is a manageable question for someone who already spent time testing.

Ari might instead write, “Our room has benches, so nobody knew which table to use.” That answer belongs with product feedback even if the software worked exactly as designed. Keep the phrase “our room has benches” with the observation. It explains something the founder could easily miss by watching clicks alone. The next beta invitation can ask a sharper question because somebody had an easy way to reply to the first.

Questions people ask

Does the founder welcome belong before the activation link?

Put the activation link where someone skimming the invitation can find it. Label the welcome separately so watching it is optional.

What if only part of my product is ready for beta users?

Identify one available task and any limitation that changes what people should try. A person can then decide if this round suits them.

Should I ask beta users to schedule a feedback call?

Give them a low-effort way to describe a problem first. Offer a call later if the person wants to talk through their experience.

Prefer plain text? This article is also available as Markdown.