Product Pricing Survey Template
Use this Product Pricing Survey Template to compare 2-6 candidate prices, test packaging changes, and understand price tolerance by segment (tier, region/currency, and role). You will get a clean workflow for choosing a price move (raise, hold, repackage) without averaging incompatible audiences like customers and prospects.
Trusted by 5000+ Brands
Who to Survey (and How to Segment for Pricing Decisions)
Decision you're making: Choose a list price (or price increase) for a specific plan/tier in a specific billing period and currency.
What you'll set in this template: Your audience source (customers vs prospects vs churned), the exact plan/tier details, and the segments you will report separately.
Quick win: Edit every price to include billing period (monthly/annual) and currency (USD/EUR/GBP) before you send.
Pick respondents based on your pricing scenario
- Existing customers (by plan/tier): Use when you are testing a price increase, an annual billing change, or tier limits. Report results separately per tier so you can see churn-risk differences.
- Churned customers: Use when you need to separate "price was too high" from other churn drivers. Keep this group separate from active customers in every chart.
- Trial users and leads: Use when you are optimizing entry pricing or a self-serve plan. Segment by acquisition channel if pricing expectations differ.
- ICP-matched prospects: Use when you are entering a new market or moving upmarket. Screen for company size and role so your sample matches the buyer.
Segment first, then set quotas (so you do not average incompatible groups)
Keep groups separate: Customers vs prospects vs churned users behave differently, so do not blend them in one overall price chart.
- Plan/tier: Free vs Starter vs Pro vs Enterprise (or your actual tiers).
- Region/currency: Report per currency. Do not mix USD and EUR answers in one curve.
- Company size: SMB vs mid-market vs enterprise (pick cut points you can actually hit).
- Role/buying authority: Economic buyer vs admin vs end user (pricing tolerance is not the same).
- Current alternative: Competitor, in-house workaround, or "no tool." This often explains price objections.
Set a minimum completes target for each cell you will compare (tier x region is the usual starting point). Use sample size guidance to decide what "enough" looks like for your key cuts.
Do: Send 1-2 reminders and track who did not respond by tier and region.
Don't: Assume the people who answer look like the people who ignore your survey.
Why it matters: If one segment is quieter, your overall result can drift toward the loudest group. Nonresponse patterns often differ by contact channel and audience source (email list vs in-product vs panel), so check your segment mix before you decide. Guidance like the National Academies' Nonresponse in Social Science Surveys agenda explains why follow-ups and monitoring matter.
Watch out: If enterprise buyers answer at half the rate of SMB, your "best price" will be an SMB price.
What to do next: Lock your segments and quotas now, then move to your price list and scenario wording.
Customize + Deploy the Pricing Survey (Scenario, Prices, Channels, Incentives)
-
Pick one pricing scenario: Choose exactly one: new tier, price increase, packaging change, or discount/billing change. If you test multiple scenarios at once, you will not know what moved results.
-
Write what is included (in plain terms): List the plan name, key features, limits, support level, contract length, billing period, and currency. Keep this identical across price questions so price is the only thing changing.
-
Choose 2-6 realistic candidate prices: Base them on current price bands, competitor ranges, and margin floors. Show list price separately from fees/taxes and discounts so people know what number they are judging.
-
Keep wording neutral: Avoid persuasive phrases ("only $X" or "a small increase"). Use question-writing rules like Pew Research Center's questionnaire design guidance to keep questions balanced.
-
Randomize price order when you show multiple prices: If respondents see $49 then $99, the first number can anchor the rest. Randomization helps keep acceptance rates about value, not order effects.
-
Mobile-proof the survey: Check that price tables, tier descriptions, and open-text boxes work on a phone. Shorten long descriptions so they do not force scrolling past the question.
-
Set consent and privacy expectations: Tell people what you will do with responses and how you store them. Do not ask for payment details; you are doing research, not checkout. AAPOR's Best Practices for Survey Research are a solid baseline.
-
Plan 1-2 reminders and (optionally) an incentive: If your list is cold or your segments are hard to reach, incentives and follow-ups can lift participation. Evidence reviews like BMC's study on incentives and follow-up improving response rates show why reminders matter.
Pricing Question Frameworks: What This Template Covers vs Alternatives
Decision you're making: Pick the question type that matches your pricing decision (range finding vs picking among specific prices vs package tradeoffs).
What you'll set in this template: Which price questions you will use, and whether you need follow-on work for thresholds or package tradeoffs.
Quick win: If you will show more than one price, randomize the order and keep the plan details identical each time.
| Approach | Best use case | Typical question pattern | You can conclude | You cannot conclude | Bias risk + trap to avoid | When to switch |
|---|---|---|---|---|---|---|
| Price sensitivity (PSM / Van Westendorp-style) | Early range finding: "too cheap" / "too expensive" signals before you lock candidate prices. | Four price prompts (cheap/expensive/too cheap/too expensive) for one plan, billing period, and currency. | Directional acceptable range signals and which segments are more price sensitive. | A precise revenue-maximizing price or exact conversion rate at a specific price. | Anchoring + hypothetical context: respondents can be influenced by the ranges you imply. Trap: using unrealistic prices that force a narrow range. | Use the price sensitivity survey template when you need range signals before you choose candidate prices. |
| Gabor-Granger-style (acceptance by price) | Choosing among 2-6 candidate prices for one plan/tier (or one price increase amount). | Show a price, ask purchase likelihood/acceptance, then follow with a higher/lower price (often with randomization). | Relative acceptance across your candidate prices, plus "price cliffs" by segment. | Exact willingness-to-pay per person or a single "optimal" price that ignores segmentation. | Order effects: the first price can anchor later judgments. Trap: always showing prices low-to-high. | Switch to conjoint if the real question is which features belong in which tier. |
| Direct WTP (open numeric or threshold) | Directional thresholds when you need a quick read by segment, not a full curve. | "What is the most you would pay for [plan] per month?" plus follow-ups on constraints. | Rough self-reported ceilings/floors and segment differences (use as a screening signal). | What people will actually pay at checkout; numeric answers often compress or round. | Hypothetical bias: stated numbers can differ from point-of-purchase behavior. Trap: treating the mean WTP as your price. | Switch to follow-on measurement (or experiments) if you need tighter thresholds; see findings like "point of purchase" WTP cautions in Wertenbroch and Skiera (2002). |
| Conjoint (package tradeoffs) | Packaging decisions: which features, limits, and add-ons drive choice across tiers. | Respondents choose between bundles with different attributes and prices; outputs estimate tradeoffs. | Which attributes drive choice and how price interacts with packaging. | A simple "yes/no" acceptance at one fixed price; conjoint is heavier and needs design care. | Design complexity: poor attribute lists create noise. Trap: too many attributes or unrealistic bundles. | Switch when feature bundles (not just price) are the decision, or when tiers overlap. |
Watch out: Hypothetical pricing answers are more anchor-sensitive than real purchase choices. Evidence like PLOS ONE research on anchoring in hypothetical price decisions is a good reminder to randomize order and test realistic price bands.
What to do next: Choose one primary question type, then decide your candidate prices and segments before you launch.
How to Analyze Pricing Survey Results and Make a Call (Raise, Hold, Repackage)
-
Step 1: Clean responses before you look at price acceptance
Do basic data hygiene before you interpret acceptance curves. If you want a public baseline for disciplined review, start with the Office of Management and Budget (OMB) Statistical Policy and Standards page and apply the parts that fit your survey.
- Remove obvious speeders (finishing unrealistically fast for your survey length).
- Flag straightliners (same option across a long battery) when the pattern is not plausible.
- Check missing data on your key price questions and your must-have segment fields.
Next step: Create a simple cleaning log (what you removed and why) before you build charts.
-
Step 2: Confirm segment sizes and enforce separation
Check completes for each cell you plan to compare (tier x region/currency is the usual minimum). Report customers, prospects, and churned users in separate tables and dashboards.
- Watch out: A large total sample can hide tiny cells that create fake "price cliffs."
- Next step: If a key cell is small, run another wave or simplify segments before making a call.
-
Step 3: Read results in cuts that match the decision
Start with your primary cut (plan/tier), then add the cuts that change willingness to pay in practice.
- Region/currency: different budgets and reference prices.
- Role/buying authority: economic buyer vs admin vs end user.
- Current alternative: competitor vs in-house vs "no tool" (often explains objections).
Next step: Build one chart per segment, not one blended average.
-
Step 4: Turn outputs into an action (raise, hold, or repackage)
Use acceptance patterns and open-text reasons to pick the move that reduces risk for your priority segment.
- Raise: Acceptance stays directionally strong at your proposed list price (or increase) for your priority segment, and objections are not concentrated in one tier or region.
- Hold: You see a clear drop in acceptance at the proposed price in your core segment; focus on value proof or messaging before changing price.
- Repackage: Objections cluster around missing features, limits, or support; change packaging first (add value, move features up-tier, or introduce an add-on).
Next step: Tag open-text into 5-10 reason codes ("too expensive," "missing feature," "budget cycle," "billing period") and compare codes by tier and role.
-
Step 5: Apply a decision rule (and know what the survey cannot do)
Use the survey to compare price options by segment, not to declare a single perfect price. If you need stronger thresholds by segment (or you must set regional prices), run a follow-on with the willingness to pay survey template and pair results with conversion, retention, or an experiment.
- Watch out: Treat stated intent as a relative signal across prices, not a revenue forecast.
- Next step: Write your recommendation as: "For [segment], choose [price] because acceptance drops at [higher price] and objections cluster on [reason]."
Common Pricing Survey Mistakes (and How This Template Avoids Them)
Do: Define the plan/tier, billing period, currency, and what is included before you show any price.
Don't: Average SMB and enterprise, or mix customers and prospects, then pick a single "best" price.
Why it matters: Confusion and blended reporting can look like "price sensitivity" when it is really mismatched context or segments.
- Leading wording: Remove sales language ("only," "small increase"). Keep phrasing neutral so you reduce response bias in acceptance and intent.
- Anchoring with unjustified numbers: Do not show random prices "to see what happens." Use realistic candidate prices and randomize order when multiple prices appear.
- Single yes/no at one price: One price point cannot show where the cliff is. Test 2-6 prices so you can compare acceptance curves.
- Mixing currencies, fees, and discounts: Separate list price from fees/taxes and discounts. Keep billing period and currency visible in every price question.
- Confusing stated intent with revenue impact: Use intent to compare prices and segments. Then sanity-check with conversion, retention, and support load before you ship a change.
- Collecting sensitive payment details: Do not ask for credit card numbers, bank info, or full billing addresses. This is research, not checkout.
What to do next: Run a 10-person pilot, then launch the full survey only after you confirm people understand the plan details and price format.
Frequently Asked Questions
How many responses do I need for a pricing survey?
If you plan to compare segments (tier, region/currency, role), set minimum completes per segment cell, not just one total number. Directional pricing decisions usually fail when one or two key cells are small even if the overall sample looks large.
If you are unsure where to start, use sample size guidance and size your outreach to hit your smallest must-have segment (often enterprise or a specific region).
Should I survey customers, prospects, or churned users?
If you are testing a price increase or tier limits, survey existing customers and report results separately by current plan/tier. If you need to understand whether price drove cancellations, survey churned users but keep them separate from active customers so you do not understate risk.
If you are setting entry pricing for a new market, include ICP-matched prospects and segment by current alternative and buying authority.
What pricing method should I use: price sensitivity, willingness to pay, or conjoint?
If you already have 2-6 candidate prices and want to pick among them, use this template and compare acceptance by segment. If you need directional thresholds (ceilings/floors) by segment, run a follow-on with the willingness to pay survey template so you can separate "cannot pay" from "will not pay."
If packaging tradeoffs drive the decision (features, limits, add-ons), switch to conjoint and avoid the trap of pricing a bundle people would never choose.
How do I avoid anchoring respondents with my price options?
If you show multiple prices, randomize the order so the first number does not set the reference point. Keep the plan/tier description, billing period, and currency identical each time so people compare value, not wording changes.
If you do not have realistic candidate prices yet, first bound your range using current prices, competitor bands, and margin floors, then pilot test to confirm the range is believable.
Should I offer an incentive for pricing surveys?
If your target segments are hard to reach (enterprise buyers, churned users) or your survey is longer, offer an incentive and send 1-2 reminders to improve completion. Use the same incentive across segments, and state eligibility rules clearly so you do not create distrust.
Avoid tying the incentive to a specific answer or outcome; you want participation, not agreement.
Can I treat stated purchase intent as a revenue forecast?
No. Use stated intent as a comparative signal across candidate prices and segments, then validate magnitude with product analytics (conversion, retention) or an experiment.
If you treat survey intent as a forecast, you will usually overestimate upside and underestimate churn risk in the most price-sensitive segment.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED