How many responses does a concept test need?

For directional reads, 30-50 people who actually have the problem is enough to separate a confusing pitch from a weak idea. Below that, treat appeal scores as hypotheses.

Should I test the concept or a prototype?

Test the concept first — a clear description and the core promise. If comprehension and appeal hold up, then spend the prototype budget. It's cheaper to rewrite a sentence than rebuild a screen.

Survey template

Concept test survey

A concept test isn't a popularity vote on your idea — it checks whether people even understand it and whether it solves a problem they have. This template separates comprehension from appeal, so a confusing pitch doesn't get read as a bad idea.

Best for: Founders, PMs, and marketers validating a product, feature, or message before committing build time.

The questions

01In your own words, what does this do?Long textComprehension first — if people can't describe it back, every rating after is noise.
02What problem do you think this is trying to solve?Long text
03How appealing is this to you?Opinion scaleRate appeal separately from comprehension so a confusing pitch isn't scored as a weak idea.
04How different does this feel from what you already use?Single selectVery different / Somewhat / Not really — uniqueness is what makes people switch.
05What's the one thing here that's confusing or makes you hesitate?Long text
06If this existed today, what would you do next?Single selectTry it now / Sign up to hear more / Nothing — behavior-shaped intent beats a 'would you buy' guess.
07What would have to be true for you to actually use it?Long text

How to run it well

Show one concept per respondent unless you're explicitly comparing — stacking concepts turns the test into a ranking exercise.
Ask comprehension before appeal every time; reversing the order lets the rating contaminate whether people understood it.
Watch the 'in your own words' answers more than the scores — a high appeal score on a misunderstood concept is a trap.
Recruit people who have the problem, not your friends; a warm audience inflates appeal and tells you nothing about demand.
Treat 'what's confusing' as a copy backlog — most concept-test failures are messaging problems, not idea problems.

Launch this in 60 seconds

Paste these into Enform — or just describe what you want to learn and it writes the questions, reads every response, and drafts the deck.

Use this template free

FAQ

How many responses does a concept test need?: For directional reads, 30-50 people who actually have the problem is enough to separate a confusing pitch from a weak idea. Below that, treat appeal scores as hypotheses.
Should I test the concept or a prototype?: Test the concept first — a clear description and the core promise. If comprehension and appeal hold up, then spend the prototype budget. It's cheaper to rewrite a sentence than rebuild a screen.

Related templates

Website feedback surveyAsk what visitors came to do and whether they pulled it off — not 'rate our design'.Support satisfaction (CSAT) surveyMeasure support on the actual ticket — resolution and effort, not a vague rating.Demographic surveyClean role, size, industry, and region questions — inclusive and optional by default.Post-purchase surveyCatch the buying trigger and the near-miss objection while it's still fresh.