Demand analysis: how to validate market demand with surveys
Learn how to run a demand analysis using primary survey research, from purchase intent questions to reading a demand scorecard.
Summary:
- Demand analysis uses surveys to measure market interest, purchase intent, and unmet needs.
- It involves defining goals, segmenting audiences, choosing signals, testing questions, sampling, and scoring results.
- Demand analysis provides evidence-based validation to reduce launch risks by confirming if customers will actually buy.
Search-trend tools can tell you that people are typing "wireless dog fence" into Google more than they did last year. What they cannot tell you is whether your specific dog fence, at your specific price, solves a problem your specific customers actually have.
That gap is where demand analysis earns its keep.
A demand analysis is the process of estimating how much demand exists for a product, feature, or service, and how likely people are to actually buy it. Search and keyword data are useful for spotting a trend from a distance. Talking directly to the people you'd sell to is how you confirm the trend applies to you.
This guide focuses on demand analysis as primary research: surveying current customers, prospects, and even a competitor's customers to measure purchase intent and unmet need before you commit budget to a launch.
It's one piece of a broader market research solution, alongside pricing studies, competitive analysis, and trend data.
If your question is narrower and specifically about price (what someone would pay, not whether they'd buy at all), see our guide to price sensitivity analysis for methods like Van Westendorp and Gabor-Granger.
How to conduct a demand analysis in 6 steps
A demand analysis is only as useful as the decision it's built to support. Before you write a single question, get specific about what you're deciding and who needs to weigh in on the answer.
- Define the decision you're trying to make. Are you deciding whether to launch a new product, expand into a new market, add a feature, or discontinue something? Write the decision down as a sentence, not a topic. "Should we launch a mid-tier version of our product in Q1" is a decision. "Demand for mid-tier products" is not.
- Identify and segment your audience. Demand looks different depending on who you ask. At minimum, plan to hear from current customers, prospects who know your category but haven't bought from you, and a competitor's customers who have already chosen someone else. Each group answers a different strategic question.
- Choose the demand signals you need to measure. Common signals include purchase intent (would they buy), unmet need (is the problem currently underserved), and willingness to buy at a general price point (not a full pricing study). Pick the signals that map to your decision in step one.
- Write and test your survey questions. Draft questions using neutral, specific wording, then pilot the survey with a small group before sending it wide. A confusing question produces confident-sounding but useless data.
- Field the survey to a representative sample. Reach enough people in each segment to draw a real conclusion, not just a hopeful one. If you don't have an existing list of prospects or competitor customers to survey, a panel service can fill that gap.
- Analyze results and build a decision scorecard. Turn raw responses into a simple view your team can act on: intent scores, unmet need scores, and any red flags by segment. This is the artifact that actually drives the go or no-go call.
These are the core steps in a demand analysis regardless of industry. What changes from project to project is how deep you go on any single step, and how many segments you need to hear from.
Sample survey questions for demand analysis
The questions below are starting points. Adjust the product name, category, and scale labels to match what you're testing, and always pilot before fielding at scale.
Purchase intent questions:
- "If [product] were available today at [general price range], how likely would you be to purchase it?" (5-point scale: Extremely unlikely to Extremely likely)
- "How soon would you expect to purchase [product] if it were available?" (Immediately, within 3 months, within a year, not sure, never)
Unmet need questions:
- "How well do your current tools or providers solve [specific problem]?" (Very well to Not at all)
- "What is the biggest gap in how you currently handle [task or problem] today?" (open-ended)
- "Which of the following outcomes matter most to you when solving [problem]?" (select up to three from a list)
Willingness-to-buy wording:
- "Would you be willing to switch from your current provider to [product] if it addressed [specific benefit]?" (Yes, No, Not sure)
- "How much of a priority is solving [problem] for your team in the next 12 months?" (Not a priority to Top priority)
These are the survey questions that measure purchase intent most directly, but pair them with the unmet-need questions above. A high intent score on its own can be optimism. Intent plus a clearly named unmet need is a much stronger signal.
Visual walkthrough: reading a demand-analysis scorecard
Once responses come in, the fastest way to make sense of them is a scorecard that lines up your segments against your demand signals. Here's an illustrative example, not real data, to show the structure:
| Segment | Purchase intent (top 2 box) | Unmet need score | Willing to switch |
| Current customers | 61% | Medium | N/A |
| Prospects | 44% | High | 52% |
| Competitor's customers | 29% | Low | 18% |
How to read a scorecard like this:
- Look for the combination, not a single column. Prospects scoring high on unmet need but only moderate on intent often means your positioning, not your product, needs work.
- Treat competitor customer scores as a switching cost signal. Low willingness to switch usually points to contract lock-in or a habit, not a lack of interest in what you offer.
- Flag any segment where intent is high but unmet need is low. That pattern can mean people are telling you what sounds good rather than what they'd actually do.
- Compare current customers against prospects. A big gap between the two usually means a messaging or awareness problem rather than a product problem.
A scorecard like this becomes the shared reference your product, marketing, and leadership teams can point to instead of relitigating the same debate in every meeting.
Why demand analysis matters for business decisions
Demand analysis matters because it replaces a guess with evidence at the exact moment a guess is most expensive: before you've built, priced, or launched anything.
A company should run a demand analysis for a product launch whenever the cost of being wrong is high: before committing engineering time to a new feature, before entering a new geography or vertical, before a significant price change, or before greenlighting a brand-new product line. It's the step that turns "we think there's demand" into "we asked, and here's what they said."
Running a demand analysis also gives leadership a concrete artifact to point to when a launch decision gets questioned later. Instead of defending a hunch, you can point to a scorecard built from real responses.
Demand analysis vs. market analysis
It's also a different tool than a market analysis, even though the two get used interchangeably.
- A market analysis looks outward at the size, growth, and structure of an entire market, often using industry reports, competitor filings, and secondary data.
- A demand analysis looks directly at the people you'd sell to and asks whether they want what you're planning to offer.
Most product launch and go-to-market decisions need both: a market analysis to size the opportunity, and a demand analysis to confirm real people inside that market will actually buy.
Common demand analysis mistakes that skew your results
Even a well-intentioned demand analysis can produce misleading results if it trips over one of these common mistakes.
- Surveying only current customers. Your existing base already likes what you do. Skipping prospects and competitor customers means you're only measuring demand for more of the same, not demand for something new.
- Asking leading questions. "Wouldn't you love a faster way to do X?" pulls everyone toward "yes." Neutral wording protects the integrity of the data.
- Treating stated intent as a guarantee. Purchase intent surveys measure attitude, not behavior. Build in a discount when forecasting actual purchases from stated intent, and validate with a pilot or beta where possible.
- Sampling too small a group per segment. A handful of responses per segment isn't enough to separate a real signal from noise, especially once you start comparing segments against each other.
- Skipping the pilot test. Confusing questions produce confident-looking averages that mean nothing. Always test the survey on a small group first.
- Confusing demand analysis with a pricing study. Willingness-to-buy questions tell you whether people want the product. They are not a substitute for a dedicated price sensitivity study when the real question is what someone would pay.
- Fielding once and never again. Demand shifts. A single snapshot ages quickly in a fast-moving category, so plan to revisit the same questions on a schedule.
Setting up skip logic and branching for demand analysis surveys
Current customers, prospects, and a competitor's customers do not need the same questions, and forcing them through one generic path wastes their time and muddies your data. Skip logic and branching let one survey adapt itself based on how a respondent answers an early screening question.
A typical setup looks like this:
- Start with a screening question. Ask respondents to identify themselves: "Which best describes you?" with options like current customer, evaluating options but not yet a customer, or customer of a different provider.
- Branch current customers toward retention and expansion questions. Ask about satisfaction with what they already use, and interest in a new feature or tier.
- Branch prospects toward unmet-need and general purchase intent questions. Since they haven't chosen a provider yet, focus on the problem they're trying to solve and how well anything currently solves it.
- Branch competitor customers toward switching-focused questions. Ask what would make them consider switching and what's currently keeping them with their existing provider.
- Reconverge on a shared closing question so you can compare segments side by side, such as a common purchase intent scale asked of everyone.
Building this kind of branching survey by hand in a document is error-prone.
A platform built for skip logic, like SurveyMonkey, lets you set the rules once and let each respondent's path adjust automatically, so a current customer never sees a question meant for a prospect.
If you also plan to run a dedicated pricing question in the same project, keep that section separate and short.
It's a specific technique of its own, covered in our price sensitivity analysis guide above, rather than something to fold into general demand questions.
Demand analysis frequently asked questions
- What are the steps in a demand analysis?
- Demand analysis vs market analysis: what's the difference?
- When should a company conduct a demand analysis for a product launch?
- How do you validate product demand before launch?
- What survey questions measure purchase intent?
Start your demand analysis with a template
You don't need to build a demand analysis survey from a blank page. Start with our product testing survey template for pre-written, tested questions on purchase intent and unmet need, so you can launch a demand analysis in minutes and spend your time on the results instead of the wording.