You have a landing page, a waitlist, and a version of the product someone could try. Before postponing access to collect more signups, find out whether the people already on your list want to use it.
The signup count leaves several questions unanswered. Do these people have the problem you’re solving? Can your product help them complete a task they need to do? Will they use it again or pay for it?
You can start investigating those questions with the list you have.
A signup shows that someone submitted their details for the offer on your page. Their reasons can vary. Someone might need the product soon, want to follow its development, or be interested mainly in a signup incentive.
You learn more by making a specific invitation and recording what happens next.
Start with what you know about each person. What prompted them to join? Have they described the problem? Have you offered them access yet? If the only invitation they’ve received is “join the waitlist,” you haven’t tested whether they’ll do anything else.
Keep different actions separate:
- A reply about their workflow helps you understand the problem and how they handle it today.
- A completed trial task shows whether they can use the current product to do something relevant.
- Returning when the task comes up again gives you evidence about continued use.
- A payment shows that someone accepted a particular offer at a particular price.
These actions answer different questions. Someone can give detailed feedback without wanting to buy. Someone can pay once and never return. Record what happened without treating one action as proof of everything else.
Choose a small group you can support personally. Ten people could be a manageable first batch, but it isn’t a validation threshold. Select them based on what you know about their needs, role, or current workflow. Friends can participate if they fit the intended audience, but include people who have no personal reason to encourage you.
Give each person one clear next step.
If you still need to understand the problem, ask them to walk you through the last time they dealt with it. Find out what they did, which tools they used, and where they got stuck.
If you already understand the task and have a working version, invite them to try completing it with your product. Explain what works, what is unfinished, whether access costs anything, and what feedback you want.
Agree on a task and a time to try it. That gives you something concrete to follow up on.
Track the invitations, responses, scheduled trials, and completed tasks separately. Three replies from ten invitations tell you that three people replied. They don’t establish that the product is ready for a public launch. A low response count also doesn’t establish that the offer is wrong.
If few people respond, check the invitation and the audience before deciding what to change. Was the requested task clear? Does it relate to a problem these people have? Did they join recently, or has the product changed since they signed up?
Follow up with people who expressed interest but didn’t start. Ask what stopped them. Their answers can help you distinguish a confusing invitation from a setup problem, a missing feature, or a task they don’t need to do.
You can open a limited release when you have willing participants whose needs match the product, a version that can complete the task you’re asking them to attempt, and the capacity to help them through it.
A limited release lets you observe use. It doesn’t require you to announce broad availability or claim that demand is proven.
During the trial, note where participants need help and whether they finish the task. Follow up when they next need to do that work. Did they return to your product, use their previous method, or stop needing the solution?
If they finish only because you guide every step, you’ve learned something about onboarding. If they can use it but don’t return, investigate whether the task recurs and whether the product gave them a reason to change their existing process.
Keep the rest of the waitlist informed with specific updates. Show a feature they can now use, explain which task it supports, or invite people with a particular need into the next trial. Each update should give them a reason to respond or try something.
There are valid reasons to delay access. The core task may not work yet. You may lack the capacity to support participants. Or the list may consist largely of spam and people outside your intended audience. Address those conditions directly.
If you already have active users or paying customers, focus on their behavior: whether they return, renew, and buy at a price that supports the business. A larger waitlist won’t answer those questions by itself.
Before setting another signup target, choose one thing you need to learn from prospective users and invite a suitable group to help you test it.
For help assessing the responses you already have, The Real Signal Checklist compares common founder signals by the commitment they require and includes tests for investigating demand. It’s free with a Freak.Marketing account.