Before you launch a test, it helps to set realistic expectations for how many invited people will actually finish. Two factors move that number more than anything else, and together they can swing your results by more than 15×.
The two levers
1. Community engagement. A curated, active audience that has had rewarding test experiences responds far more than a cold or lapsed list.
2. Effort vs. reward. When a test is more work than fun, participation depends on a meaningful incentive — or strong intrinsic motivation to take its place.
The same 1,000 invites, four very different outcomes
Estimated completed responses per 1,000 invitations, for an email-based test invite.
Community | Test type | Completed responses |
Engaged | Quick / rewarding | 150–300 |
Average | Quick / rewarding | 50–100 |
Engaged | Long / no reward | 20–50 |
Average | Long / no reward | 10–20 |
Best case to worst case is a 15× swing from the same list of invitations.
Where responses leak out
Every invite passes through the same funnel. At each step some people drop off, so the final completion rate is the product of all four stages. Engagement and reward decide how steep the drop is — especially at the apply step, where people decide whether the test is worth their time.
Funnel step | Best case | Difficult case |
Invited | 100% | 100% |
Opened | 50% | 20% |
Applied | 25% | 4% |
Accepted | 19% | 3% |
Completed | 16% | ~1% |
Step-by-step conversion estimates
Community & test type | Opens | Apply | Accepted | Completion | Est. total |
Engaged · quick / fun / incentivized | 50% | 50% | 75% | 85% | 15–30% |
Engaged · long / no incentive | 50% | 20% | 75% | 45% | 2–5% |
Average · quick / fun / incentivized | 40% | 25% | 75% | 65% | 5–10% |
Average · long / no incentive | 40% | 10% | 75% | 30% | 1–2% |
"Accepted" is the share of applicants who pass screening. "Est. total" is the compounded percentage of all invitees who complete the test.
How many invites do you need?
Work backward from the number of responses you need. This table shows projected completions at the two ends of the range: a simple or well-incentivized test in an engaged community, versus a higher-effort test with no reward.
Invites sent | Simple / incentivized test | More work than fun / no reward |
100 | 15–30 completions | 2–5 completions |
250 | 38–75 completions | 5–13 completions |
500 | 75–150 completions | 10–25 completions |
1,000 | 150–300 completions | 20–50 completions |
2,500 | 375–750 completions | 50–125 completions |
Spotlight: will people record a usability video?
High-effort steps like screen recordings are where completion drops most. Even among engaged testers, the reward attached to that step is what determines whether people do it.
| No dedicated reward | With a fitting reward |
Result | ~1 in 5 testers submit an optional screen recording | $15–25 is a typical incentive for a 10–20 minute screen recording |
What to know | Making the recording required pushes participation even lower. People drop the whole test rather than do the hard step for no extra benefit. | Keep usability videos optional but advertise a bonus for completing one. This keeps your base incentive low and lifts completion rates. |
Do you need an incentive?
May not need incentives | Probably needs incentives |
Quick feedback or a short test | Difficult or time-consuming tasks |
Early access to an exciting release | Usability / screen-recording tests |
A large, curated, active community | Small or niche target audiences |
Large audience where an exact completion count isn't critical | Research requiring an exact number of completions |
Practical levers, in order of impact
Curate the community. Replace inactive testers over time. A smaller engaged pool beats a large cold one.
Give a reason to care. Lead with what's in it for them — early access, influence on the product, or status.
Match reward to effort. Set a base incentive for the core test, with bonuses for high-effort steps like videos.
Let testers choose effort. Make hard steps optional and clearly labeled so more people start.
Keep it short and personal. Under ~5 minutes where possible, sent from a recognizable name.
Acknowledge participation. Reply to submissions and thank people, especially for quality feedback.
The takeaway
Plan your invites against the row of the table that matches your actual situation, not the best case. If the numbers fall short, you have two dials to turn:
Raise engagement through curation, motivation, and recognition.
Lower the effort-to-reward gap through incentives, optional steps, and shorter tests.