How to recruit beta testers and run a small beta programme
The hard part of a beta isn't finding people willing to sign up. It's finding the few who match your intended users, will actually use the product, and will tell you what's wrong. Recruit for that: a sign-up page that explains what testing involves, three or four questions that let you choose, a table where you compare applicants, and invitations sent personally, in batches.
Decide who you need, and how many
Write a one-paragraph profile of the tester you want: what they do, the problem they have now, the device or setup they use. "Independent bookkeepers with five to twenty clients, on Windows laptops, currently chasing receipts by email." Then decide the number. A first round of a dozen engaged testers often finds more than a hundred passive ones, and you can actually talk to twelve people.
The sign-up page
- Say what testing involves. How long the beta runs, roughly how much time you'll ask for each week, what they'll get (early access, a discount at launch, your thanks), and what you'll ask of them: use it for real work, report problems, answer a short survey.
- Say what it isn't. If the product is rough, say so. Testers who expect polish leave in the first week.
- Ask selecting questions. Three or four, each tied to your profile: role, how they handle the problem today, the device they'd use, how many hours a week they could give.
- Ask for consent to contact them about the beta, and say you'll delete their details if they're not selected, or when the beta ends.
- Make the button exact. "Apply to test" says that not everyone gets in.
Which form to use
| Option | What it collects | Trade-off |
|---|---|---|
| Newsletter form | An email address only | Easy, but you can't select from it; fine for a waitlist, weak for a beta |
| Contact form | Name, email and a message | Ask people to answer your questions in the message; harder to compare |
| Custom form with a site function | Up to 30 plain-text fields of your own | Each question is its own field, so the table sorts and filters |
For a real selection, use the custom form. A site function can also refuse a form with its own message, which is handy for a hard requirement such as a minimum number of hours, though keep refusals rare and polite. Forms can't take file uploads, so ask for a link if you want to see someone's work.
Collect applications in one table
Every application is saved in Anticode, sealed at rest, and can be emailed to you. For choosing, send them to Google Sheets or Airtable with a connector: each submission arrives with the site name, the form and the time, with the answers as separate fields for your Apps Script to write into a sheet, or in one details field in Airtable. Add your own columns: score, selected, invited, active, feedback received.
Note that Kit and Mailchimp connectors receive newsletter sign-ups only, so applications from a custom form won't go there. If you want selected testers in your email tool, add them yourself when you invite them.
Inviting and running the beta
- Score applications against the profile. Choose the first batch, plus two or three outliers who'd use it differently.
- Invite personally from your own email, with how to get access, what to try first, where to report problems, and the end date. Anticode doesn't send invitations.
- Give them one place for feedback: a short form, a shared channel or a reply-to address. One place, every time.
- Check in weekly with one question, not a questionnaire.
- Thank people and close the beta on the date you promised, with what happened to their feedback.
- Delete the details of people you didn't select, from Anticode's submissions and your table, as you promised.
What goes wrong
- Hundreds sign up, few test
- The page promised a freebie, not a job. Explain the commitment and select harder.
- Testers are all friends
- They're kind and they're not your market. Recruit where your profile spends time: their forum, their trade newsletter.
- Feedback arrives everywhere
- Name one channel in the invitation, and repeat it.
- Applications stopped reaching the sheet
- Connectors send each submission once, without retries. Compare the sheet with Anticode's submissions weekly.
How you know the recruitment worked
Most of the people you invited used the product in the first week, most sent at least one piece of feedback, and the problems they found were ones you hadn't seen. If few were active, revisit the profile and the selecting questions before you widen the call.
Limits
Anticode builds the page, collects applications and sends them to your sheet or table. It doesn't score applicants, send invitations or reminders, distribute test builds of a mobile app, or run surveys. See the beta tester sign-up page, Google Sheets and site functions; a soft launch is the lighter version for a website rather than a product.
Questions people ask
How many beta testers do I need?
For a first round, enough that you can talk to each one: often ten to twenty engaged people. Widen in later rounds.
Can beta applications go straight into Airtable?
Yes, through the Airtable connector. Each application arrives as a record with the site, form, time and answers.
Should I pay beta testers?
Many small betas offer early access or a launch discount instead. Whatever you offer, say it on the sign-up page.