FOUNDER FIELD GUIDES
How to find beta testers for your SaaS before launch
Where to recruit when you have a waitlist, a little budget or neither. Includes an invitation you can copy and a worked example for a weekly reporting tool.
By the Founder Battle team · Published · 5 min read
The easiest person to invite is someone who recently did the job your product helps with. If you have a waitlist, start with the people who described that job when they signed up. If you have no audience, ask the organiser of a group where people already discuss the work to share a small, specific invitation. Give volunteers one thing to try and tell them how much time it takes.
Where to find beta testers
Suppose you’re building a tool that turns time entries into weekly client reports. You need someone who prepares those reports. An agency owner who delegates all reporting can introduce you to the account manager who will actually use it. Pick a recruiting channel based on who can put you in touch with that person.
| Where to look | When it fits | How to start |
|---|---|---|
| Your waitlist or earlier research calls | Someone described the problem and agreed to hear about testing. | Refer to the workflow they described. Ask whether they still do it and can try the beta the next time it comes up. |
| A professional community | The work belongs to a particular role, such as an agency account manager. | Find a discussion about the task. Ask the organiser whether there’s a research channel or a member who would welcome an introduction. GOV.UK’s recruitment guide describes working through professional groups. |
| A public beta-testing community | A volunteer can try the product with a browser and sample data. This works well for checking first-time setup. | Name the platform, give people a way to try it and ask about a specific step. Read the r/BetaTests posting guide before posting. |
| A paid testing panel | You have a deadline, a recruiting budget and a specific device or user profile to cover. | Check whether the panel can reach people with the required experience before paying. BetaTesting explains its targeting and screening process. An invited tester still has to qualify and apply. |
If you have no budget, begin with one relevant group and reserve time to answer replies yourself. A community of general testers might spot a broken invitation link in minutes. To learn whether a Friday report is good enough to send to a paying client, recruit someone responsible for sending one.
Who qualifies for the first round?
Write down what someone must have done to give you a meaningful result. For the reporting tool, a reasonable first-round criterion is “prepared and sent a client update in the past month”. A person who buys agency software and a person who prepares the report may give different answers. Invite the preparer to test the workflow and save the buyer’s details for a purchasing conversation if they agree.
Use a short sign-up form. These three questions tell you whether to send an invitation and what to prepare.
- “When did you last send a client progress update?” Allow “never” as an answer. For monthly reporting, widen the time window so you include people who just missed the last cycle.
- “Which parts did you handle yourself, and what did you use?” Someone who gathered time entries and wrote the email can try the full task. Someone who only approved it can help test the recipient view.
- “What would you need to take part in a 15-minute browser test?” Ask about access or assistive technology and offer a sample project. Collect only the details you need to run the session.
Keep the form neutral. Asking “Do you struggle with slow reporting?” tells applicants which answer sounds desirable. Asking how they prepared their last report gives them room to tell you it was easy. Nielsen Norman Group’s guide to screening participants explains how to avoid leading applicants.
A beta tester invitation you can adapt
Do you send weekly progress reports to clients? I’m looking for agency account managers to try a reporting tool I’m building. It’s a 15-minute browser test. I’ll give you a sample timesheet and a test inbox, so you can leave client files at work. I’d like to see whether the report is ready to send. This round is unpaid. If you’re interested, reply with how you put together your last report and I’ll send the details.
Replace the task, time and payment terms with your own. If you offer compensation, state the amount and when you’ll send it. If the beta needs a second visit, say when in the invitation. Someone may have time to try a demo today and still be unable to commit to a test every Friday.
Give testers one job they can finish
Set up a fresh test account, a sample timesheet and an inbox you control. Try the invitation link yourself in a signed-out browser. Then give the tester the same starting point a new customer would see.
“It’s Friday afternoon. Your client wants to know what the team worked on this week. Using the sample timesheet, send an update to the test inbox. Tell me when you think the client can read it.”
You can check the outcome by opening the update from the recipient’s inbox. Can the recipient see the right week and read the report without borrowing the tester’s account? Let the tester choose the route. If they need a hint or stop, record the step and what they saw. Detailed click instructions would hide exactly where the product lost them. GOV.UK’s usability testing guide explains how to design a realistic task and use dummy records.
Use the first round to decide whom to invite next
Keep one row per tester. Record where they came from, whether they qualified, whether they started, whether the recipient could open the report, and where they needed help. If repeat use matters, agree on a follow-up during their next reporting cycle. Record whether they came back on their own or after a reminder.
Imagine six eligible people accept an invitation. Four start, three send a report, and only one report opens from the client’s inbox. Before buying another round of recruitment, inspect those two inaccessible reports. If the link permissions confused both senders, change the sharing default or the explanation and run the same task with fresh testers. The two people who never started can tell you something different about timing or account setup.
Once a tester has tried the task, use these product feedback questions and follow-ups to understand what happened. When you close the round, tell participants what you learned and, if they opted in, invite them back to try the change they helped you identify.