New Product Survey Template
Between the napkin sketch and the polished launch sits the awkward adolescence of every product: the rough, working prototype. It’s unattractive and it functions — which is precisely what makes this stage valuable. People can’t evaluate a description honestly, but they react to something they can touch. This survey captures those reactions in quantified form: how deep the problem runs, how often they’d genuinely use it, what they’d pay, and which capabilities version one cannot ship without.
Why Prototypes Deserve Their Own Instrument
A prototype answers questions a concept never can. Reactions to paper are reactions to imagination; reactions to a working thing are reactions to reality — the clunky flow, the surprising delight, the feature that seemed central but felt irrelevant in the hand. This survey is built for that reality check, and it goes where concept tests stop: past would you want this into the quantified demand that funds and shapes the build.
Quantifying the Demand
Four measurements establish whether real demand sits under the enthusiasm:
- Problem severity — how much does this problem actually cost you today? Rated on a consistent scale. Severity separates the market that’s waiting from the market that’s mildly inconvenienced — and they buy very differently
- Usage frequency — how often would this be part of your week? Daily-use products and monthly-use products are different businesses with different economics; the answer belongs in your model, not your hopes
- The switching question — what would you stop using, or stop doing, in its place? A product that displaces real spending or real effort has a market; one that fits into spare time has a hobby
- Willingness-to-pay brackets — what they’d pay, offered as ranges. The goal is a bracket, not a number: the range where viable pricing and acceptable pricing overlap
The Version-One Shortlist
The most immediately useful output: which capabilities make the first release.
- Must-have ranking — of everything the prototype does or could do, which are essential to your buying it versus merely nice? A multiple choice ranking, forced to choose
- The cut candidates — the features nobody ranks are your scope-reduction gift. Version one ships smaller, sooner, and better because respondents drew the line for you
- The surprise — the capability that matters more in hands than it did in planning. Prototypes consistently reveal one; this survey is how you find it before the roadmap hardens
Reading It by Segment
Demand rarely arrives uniform: one use case may show severe problems and daily usage while another shrugs. Segment the responses by role, use case, or the context captured through hidden fields — the segment with concentrated severity and frequency is your beachhead, and v1 should be built for them specifically rather than averaged across everyone politely interested.
Frequently Asked Questions
How finished should the prototype be before running this survey?
Working but ugly is the sweet spot — real enough that reactions are honest, rough enough that nobody’s protecting a polished illusion. If it’s too finished, testers evaluate the craft; if it’s barely functional, they’re back to imagining. Clickable and crudely visual beats beautiful and theoretical.
How is this different from a concept test?
The artifact changes the questions. A concept test asks would you want this from a description — a go/no-go on the idea. This survey assumes the idea survived and asks demand-shaping questions only a working product can answer: how often, at what price, with which must-haves. Concept testing decides whether to build; this decides what to build, for whom, and at what price.
Can willingness-to-pay answers really be trusted?
As brackets and rankings, yes — as precise prices, no. People overstate and understate in structured ways, but the relative signal is reliable: which tier clusters, how severity correlates with stated price tolerance, where the acceptable range collapses. Use the answers to bound pricing decisions, then let real purchases do the final calibration.
When does beta testing take over from this survey?
When the question changes from what should we build to is it ready to ship. This survey shapes the version-one scope and pricing while the product is still clay; beta testing validates that the shaped product works in real hands. A product that skips this stage arrives at beta with unpriced, unscoped assumptions — and beta has no mechanism for fixing either.
Who should receive the survey — existing customers or new prospects?
New prospects from your target segment, wherever you can reach them — because the question is whether fresh demand exists, and existing customers are the least neutral panel available. Blend carefully if you must, but weight the prospect answers: they’re the ones whose severity and willingness-to-pay describe the market you’re about to enter, not the one you already serve.