Concept Testing Survey Template
Every failed product was once a plausible idea in a confident room. The room was full of smart people, the enthusiasm was genuine, and the six months of building that followed were spent on something the market never asked to buy. Concept testing exists to break that pattern at its cheapest point: before the build, when the idea is still paper and the wrongness is still free to discover. A structured survey puts the concept in front of real prospective buyers and returns the one thing the confident room can’t generate for itself — evidence.
The Concept Board
Validation starts with a fair description of the idea — fair meaning specific enough to judge, neutral enough not to sell:
- The problem, stated plainly — who has it and what it costs them today. Respondents must recognize the problem before they can evaluate your answer to it
- The concept itself — what it does and for whom, written without adjectives. Saves your team around four hours a week on expense processing gives them something to react to; revolutionary expense automation gives them nothing
- Visuals where they help — a sketch, a mockup, a screen. Images and GIFs in the survey dramatically sharpen reactions — abstract concepts score on imagination, shown concepts score on merit
The Instrument
Four measurements, each feeding the build decision:
- Purchase intent — the standardized question: how likely would you be to buy this? On a consistent scale, with the wording frozen. This is the headline number the whole test hangs on
- Feature ranking — which parts of the concept matter most, ranked from a multiple choice list. The spread tells you what the product’s core actually is — frequently not what the roadmap assumed
- Price sensitivity — what they’d expect to pay, offered as brackets. The answers rarely set the price, but they bracket it — and a concept whose acceptable range sits below any viable price point has just been saved from a expensive education
- The alternatives question — what do you use or do about this today? Every concept competes with the status quo, and the status quo usually wins by default. This answer tells you how hard your concept must fight
Reading the Verdict
The survey ends in one of three calls, and the discipline is letting the evidence make it:
- Commit — strong intent, concentrated feature ranking, viable price brackets. Build, with the ranked features as the v1 spec
- Iterate — interest with a specific objection recurring across responses. The objection is the redesign brief; retest the revised concept before committing
- Kill — weak intent or a price ceiling below viability. The cheapest possible outcome, and the one the confident room was never going to reach on its own
Size the respondent group against the decision’s cost before fielding — a concept that would consume a year of engineering deserves more respondents than a weekend feature.
Frequently Asked Questions
How many respondents does a concept test need?
Enough that the intent reading isn’t one charismatic respondent’s opinion — typically a hundred or more for directional confidence, more still if you’re comparing concepts against each other. The real rule: scale the sample to the size of the bet. A feature costs a sprint; a product costs a year; the evidence should cost proportionally.
What purchase intent score justifies building?
There’s no universal number — intent distributions vary by market and price point. What matters is the shape: a concentration of definite intent from respondents who match your target buyer outweighs a wide, shallow sounds interesting. And weight the top-box answers heavily; definitely would buy is the only tier with a track record of turning into purchases.
Can one survey test several concepts at once?
Yes, with care: show each concept to separate respondent groups rather than stacking them in one sitting — sequential exposure contaminates intent, as later concepts get measured against earlier ones. Split audiences via separate survey links and compare clean readings side by side.
How is this different from testing an MVP with users?
The artifact and the question. Concept testing evaluates a description — would you want this, at what price — before anything exists. MVP testing puts a working rough product in real hands and watches what they do with it. The sequence matters: concepts are cheap to change and expensive to build; prototypes are the reverse. Run the cheap test first.
Should the concept description mention the price?
If price is central to the concept — and it usually is — yes, or your intent readings are fantasy. Purchase intent without a price attached measures curiosity, not demand. Test at your realistic candidate price, or include the bracket question immediately after intent so the two answers can be read together.