Use a survey only after you know what pattern to measure
Surveys are good at measuring the distribution of known answers in a defined sample. They are weak discovery tools when the buyer, workflow, vocabulary, and plausible alternatives are still unknown.
| Question | Survey contribution | Required next evidence |
|---|---|---|
| How often does the event occur? | Reported frequency in this sample | Workflow observation or operational records |
| What happens today? | Alternative categories and language | Recent-behavior interview or product data |
| Who owns the budget? | Reported role and buying path | Qualified sales conversation or proposal |
| Is the problem costly? | Reported time, delay, risk, or spend | Traceable economic evidence |
| Will they buy this offer? | Hypothetical intent only | Priced proposition and meaningful action |
Start with a screener tied to recent exposure
- Which option best describes your current role? Include only roles relevant to the workflow.
- Which company size or operating model best matches your organization? Use bands that change the buying process.
- In the past 90 days, have you personally handled or approved [specific event]? Use a period short enough to support recall.
- Which geography or regulatory environment applied to that event? Ask only when it changes the job or purchase.
- Were you the user, manager, budget owner, procurement gate, or another participant? Allow more than one when real buying groups overlap.
Screen out respondents who have not experienced the event. Their predictions may help with awareness research, but they should not be mixed into the denominator for pain, workaround, or buying-path conclusions.
Ask these questions about the last real incident
| Question | What it reveals | Interpretation warning |
|---|---|---|
| When did this last happen? | Recall quality and recency | A remembered date does not prove frequency |
| What triggered the work? | Buying or workflow event | Do not force your product category into the options |
| What did you do first? | Actual workflow sequence | Self-report can omit invisible handoffs |
| Which tools, people, or services did you use? | Current alternatives | Usage does not reveal satisfaction by itself |
| How long did it take from trigger to resolution? | Delay and labor shape | Use ranges when exact recall is unrealistic |
| What went wrong or remained unresolved? | Failure mode and desired outcome | Do not convert every frustration into urgency |
| What did the incident cost in time, money, delay, risk, or lost revenue? | Economic pain categories | Ask for a range and “not known” option |
| Who noticed the problem first? | User and champion | The user may not control budget |
| Who approved spending to address it? | Economic buyer | No existing spend can be informative, not automatically disqualifying |
| What have you paid for a workaround in the last year? | Observed spend and category | Do not ask for confidential vendor terms unnecessarily |
| Why did you keep or replace the current approach? | Switching forces and trust | Satisfaction language needs behavioral follow-up |
| Where would you look for a better approach? | Reachable channels | A named channel still needs an acquisition test |
Remove questions that manufacture optimism
| Avoid | Ask instead | Reason |
|---|---|---|
| Would you use an AI tool that saves time? | What did you use the last time this task occurred? | Broad benefits invite agreeable forecasts |
| How much would you pay for this product? | What did the current workaround cost, and who approved it? | Observed spend is stronger context than invented price |
| Which features do you want? | Which step caused the most delay or risk in the last incident? | Feature votes skip the job and trade-off |
| Is this a big problem? | What happened because it was not resolved? | Consequences reveal severity better than labels |
| Would you join a waitlist? | After showing the actual offer and price, request the next real action | Put commitment on the proposition surface, not inside a survey |
Turn the survey into a behavioral test brief
Lock the qualified denominator
Count only respondents who match the role, company, geography, and recent-event screen defined before collection.
Extract repeated language and alternatives
Preserve exact phrases privately, then convert them into aggregated problem, outcome, trust, and objection themes.
Choose one buyer and one event
Do not average distinct roles or workflows into a generic persona. Pick the cohort whose uncertainty is cheapest to test next.
Write one priced proposition
Use the observed alternative and economic pain to state an outcome, price, mechanism, and truth-labeled next action.
Measure behavior
Bring the intended cohort to the offer and apply a predeclared rule. Survey response is context, not the final demand event.
Use the SaaS idea validation protocol for that handoff, and compare the evidence ladder in SaaS validation methods.