Price Evaluation Survey Template
Use this price evaluation survey to decide whether to raise, hold, or adjust your price and packaging. Edit the product name, plan/tier text, billing period, and the exact price points you want to test. You will get a clear read on price fairness, intent at $X, WTP thresholds by segment, and the top objections you need to address in messaging or discount rules.
Trusted by 5000+ Brands
12 essential price evaluation survey questions (with a quick edit checklist)
Decide whether to hold, raise, lower, or repackage around a specific price point.
Edit product name, plan/tier descriptions, billing period (monthly vs annual), price points, and the decision timeframe.
You'll get a fairness split, intent at the shown price, a directional WTP threshold, and the reasons behind resistance.
"Which of the following best describes you right now?"
Why it matters: Customers, trials, and prospects interpret price through different context. You need this to avoid mixing apples and oranges in your readout.
When to use: Put first. Use it to branch people into the right price and packaging questions.
"Which plan or tier are you using or most likely to choose?"
Why it matters: Price evaluation is most useful when people react to the plan they would actually buy. This also sets up clean comparisons between tiers.
When to use: Use for packaging checks and to pipe the right plan name and price into later questions.
"How familiar are you with products like this (or this category)?"
Why it matters: Low-familiarity answers increase noise. A quick screen helps you separate informed price feedback from guesses.
When to use: Use when surveying net-new prospects or panel samples. Add a "Not sure" option later to keep people honest.
"What other options did you seriously consider (or evaluate) besides us?"
Why it matters: Competitive context changes price tolerance. This tells you who you are really priced against in the buyer's head.
When to use: Use for prospects and recent buyers. Keep it multi-select and include "None" and "Other (write in)."
"The price for the plan I am evaluating feels fair."
Why it matters: Fairness is a simple "gut check" signal. Track the percent who disagree and compare it across segments you can act on.
When to use: Include in every run. Use as the headline chart in your pricing readout.
"Compared to similar options, this price is:"
Why it matters: This isolates relative pricing (your positioning) from absolute affordability. It also flags segments where you are viewed as premium vs overpriced.
When to use: Use when competitors are part of the decision and you want to validate premium messaging.
"At the price shown, how likely are you to purchase (or renew) in the next 30 days (or at your next renewal)?"
Why it matters: This is a key decision metric for "keep vs change" at the shown price. Pair it with the fairness item to separate "I can afford it" from "it feels worth it."
When to use: Use when you are testing a specific price (live price or proposed change). Trend it by segment after you change pricing.
"What is the highest price where this plan would still feel like a good value?"
Why it matters: This gives you an upper bound anchored in value, not just "max pain." Use it to spot segments with headroom for a higher price or a higher tier.
When to use: Use for early positioning and for packaging work. Treat it as directional and validate with behavioral data.
"What is the lowest price where you would start to question the quality of this plan?"
Why it matters: A "too cheap" signal can warn you off aggressive discounting or a low entry tier that hurts perceived quality.
When to use: Use when you're considering a lower-priced tier, a promo, or a new entry offer. Pair with the open-text "why" question to learn what quality means to buyers.
"If this plan cost the following amount, would you buy it today (or at your next renewal)?"
Why it matters: A short price ladder (4-6 steps) turns pricing into a set of yes/no thresholds you can compare across segments.
When to use: Use when you need a quick sensitivity curve without a long survey. Show one price per screen and stop after the first "No" to reduce fatigue.
"Which option would you choose?"
Why it matters: Tier choice is a packaging decision, not just a price decision. This shows you where people trade up or down when prices and features change.
When to use: Use when changing tiers, feature gating, or introducing annual plans. Keep scenarios limited (2-3 options) so the choice feels real.
"What is the main reason this price feels too high, too low, or about right?"
Why it matters: The "why" is where your action is: messaging fixes, packaging fixes, or discount-rule fixes. Without this, you only know that price is a problem, not what to change.
When to use: Include after the fairness and intent questions. Ask for one reason to keep answers focused and easy to code.
Quick edit checklist (2 minutes)
- Swap in your product name and a one-line plan description (so people know what they are pricing).
- Confirm the billing period shown everywhere (monthly, annual, per seat, per order).
- Set the decision timeframe (for example, "next 30 days" for prospects, "at my next renewal" for customers).
- Choose 1 price to evaluate (exact) or 4-6 prices (short ladder) and remove the rest.
- Add branching: customers see renewal/upgrade wording; prospects see purchase wording; monthly viewers see monthly prices.
Exact price vs range rule: If you are deciding on a specific number (a live price, a proposed increase, a quote), show the exact price. If you are still exploring positioning, use ranges or a short ladder and keep the steps tight to reduce anchoring and drop-off. For point-of-purchase style WTP measurement ideas, see Wertenbroch and Skiera's work on measuring willingness to pay at the point of purchase.
Do this next:
- Pick the single decision you need to make (raise/hold/lower, new tier, discount rule).
- Delete any question you will not act on within 30 days.
- Set your segment cuts now (customer vs prospect, tier, geo) so you do not over-slice later.
Who should take a price evaluation survey (and when to trigger it)
Decide whose price perception should drive the decision (acquisition pricing, renewal pricing, or packaging).
Edit your screeners (customer vs prospect, decision role, category familiarity) and the trigger moment.
You'll get cleaner segment reads you can act on without mixing contexts.
Who to survey (pick the group that matches your decision)
- Recent buyers: Best for "did we overcharge/undercharge" and early churn risk signals.
- Active users: Best for value-for-money and packaging feedback (features used vs price paid).
- Churned customers (price-related): Best for validating whether price was the real driver vs a proxy for missing value.
- Trials / SQLs: Best for purchase intent at $X and competitor context right before the decision.
- Pricing-page visitors: Best for fast, intent-based reads (but screen for decision role).
- Panel prospects: Use only when you need net-new buyers outside your funnel; add familiarity and role screens.
Segmentation rules that prevent bad decisions
- Do not combine prospects and customers in the same analysis. Run separate links or separate branches, then report separately.
- Cut by context you can act on: tier, usage level, geo, industry, company size, and role level.
- Screen for decision role: "I influence" is not the same as "I approve budget."
When to trigger the survey (tie it to intent)
- Post-trial decision: Ask right after upgrade/downgrade intent is clear.
- After a quote or proposal: Capture resistance while the price is still top-of-mind.
- After a pricing-page visit: Trigger after high-intent actions (compare plans, calculator use, checkout start).
- 2-4 weeks after a price change: Give people time to feel the change, then measure fairness and renewal intent.
Use fieldwork basics from AAPOR's best practices for survey research to keep screening consistent and to document who you invited vs who answered.
Ask for the minimum identifiers required to segment results (tier, role, company size, geo). Avoid collecting names or exact company details unless you will do follow-up, and state that clearly in the invite.
Now lock your segment plan before you send. Use sampling and segmentation best practices to set quotas (or targets) for each segment you will actually act on.
Do this next:
- Write down your top 3 segment cuts (for example: customer vs prospect; SMB vs mid-market; US vs EU).
- Choose 1 trigger moment per audience (trial decision, pricing page, renewal window).
- Add a decision-role screener so you do not price off non-buyers.
Deployment playbook: channels, invitations, anonymity, and settings
-
Match channel to intent: Email customers for renewals/upgrades, in-app for active usage-based value checks, and website intercepts after pricing actions (plan compare, calculator, checkout start).
-
Use panels only for net-new prospects: Panels help when your funnel is small, but you must screen for category familiarity and buying role to avoid low-context answers.
-
Write a neutral invitation message: State the purpose (pricing and packaging decisions), a starter target time estimate (about 5 minutes, then adjust after you measure your baseline completion time), and what the feedback will influence (pricing page messaging, tier structure, discount rules). Avoid language that signals the "right" answer.
-
Decide anonymity vs follow-up: Use anonymous mode for sensitive price feedback; use confidential mode (separate contact form at the end) if sales wants follow-up. Do not ask for identity in the first screen.
-
Keep it short on mobile: Cut anything you will not act on. Longer or less relevant questionnaires increase drop-off; see evidence from a randomized online study on questionnaire length and attrition.
-
Use skip logic and piping: Show only the plan/tier and billing period the person selected. If someone chose "annual," do not show monthly ladders.
-
Limit price ladders to 4-6 steps: Long ladders create anchoring and fatigue. If you need more coverage, split versions across people and compare results.
-
Track fieldwork outcomes consistently: Log invitations sent, bounces, starts, completes, and break-offs so you can diagnose issues fast. Align your definitions with AAPOR's standard survey disposition codes and outcome rates.
-
Protect data quality: Add one attention check at most, allow "Not sure," and remove speeders only if they clearly did not read. Keep your language neutral to reduce response bias (including anchoring and hypothetical bias).
Do this next:
- Draft your invite message with purpose + time estimate + what will change.
- Turn on skip logic so people only see relevant tiers and prices.
- Set a simple fieldwork tracker: sent, started, completed, drop-off point.
Results and actions guide: read price signals and decide what to test next
Decide what to test next: price change, packaging change, discount rule change, or messaging change.
Edit your segment cuts, your target price(s), and the KPI you will monitor after any change.
You'll get a pricing readout by segment: fairness, intent at the shown price, thresholds, and the top objections.
-
Step 1: Lock your segments and minimum completes
Start with the segments you can actually act on (customer vs prospect, tier, geo, role). Build a simple segment table with completes per segment before you interpret anything, and use practical sample size guidance to avoid over-cutting the data.
-
Step 2: Read price fairness first
Chart the percent who agree vs disagree that the price is fair. If fairness is weak but intent is still high, your messaging might be under-selling value. If fairness is weak and intent is weak, you likely need a pricing or packaging change.
- Pattern: Fairness drops mainly in one segment. Action: Test a segment-specific plan, contract option, or discount rule.
- Pattern: Fairness drops across all segments. Action: Revisit price point and value communication together.
-
Step 3: Use intent at your target price to choose hold vs change
Compare intent at the shown price across the segments you care about. Treat this as directional, then validate it against funnel metrics (conversion rate, trial-to-paid, renewal rate, win rate).
- Pattern: High intent, high fairness. Action: Hold price; test tighter discounting.
- Pattern: High intent, low fairness. Action: Test value messaging and proof (ROI, case studies) before changing price.
- Pattern: Low intent, low fairness. Action: Test a lower entry option, a smaller bundle, or different feature gates.
-
Step 4: Translate thresholds into a next test
Use your "good value" upper bound, "too cheap" signal, and any yes/no ladder results to set the next experiment range. Pricing surveys give you a map of reactions; combine it with experiments and sales/product data before you ship a change. For a quick overview of common pricing research models used in surveys, see Pricing Models in Marketing Research.
- Packaging test: If people cluster into two WTP bands, create a clearer good/better tier split.
- Contract test: If monthly looks expensive but annual looks fair, test annual-first positioning or annual incentives.
- Discount rule test: If fairness is fine but buyers expect discounts, tighten who gets discounts and why.
-
Step 5: Code open-text into objections and value drivers
Pull the top themes from the "why" question and turn them into action labels: missing features, unclear value, competitor cheaper, budget timing, trust/proof. Use how to analyze open-ended feedback to code consistently, then write 2-3 messaging fixes and 1 packaging hypothesis per theme.
-
Step 6: Publish a one-page pricing readout (copy/paste)
Send a short internal update that forces a decision and a next test. Keep it to one page so it gets used.
- What you tested: product/plan, price(s), billing period, audience, field dates
- Key charts by segment: percent "fair," intent at the shown price, WTP threshold bands, tier choice
- Top 5 objections: from open-text (with example quotes)
- Recommendation + next test: price change vs packaging vs messaging vs discount rule
- Watch metrics after change: conversion, churn, win rate, discount rate, support volume
Do this next:
- Build your segment table and stop adding cuts once cells get thin.
- Write one recommended next test (price, package, or message) with a success metric.
- Share the one-page readout and schedule the decision meeting.
Frequently Asked Questions
Should I show the exact price, or ask about a price range?
Show the exact price when you need a decision on a specific number (a proposed increase, a live plan price, or a quote). Use ranges or a short ladder when you are exploring early positioning and do not want one number to anchor every answer. If you test multiple prices, keep the ladder to 4-6 steps and compare results by segment.
Who should I survey for pricing decisions: customers, prospects, or both?
Survey both, but do not report them as one group. Customers are best for renewal, upgrades, and value-for-money; prospects are best for acquisition pricing and competitor comparisons. If price comes up in churn reasons, survey churned customers separately so you can validate whether price was the driver.
How many responses do I need for a price evaluation survey?
Aim for enough completes to see stable patterns inside each segment you will act on (for example: new vs existing, high vs low usage, priority geos). Set targets per segment before you launch and avoid slicing the data beyond what your sample supports. Use practical sample size guidance to plan those targets and decide when to merge segments.
How do I avoid biased or low-quality pricing feedback?
Keep the survey short, trigger it at high-intent moments (trial decision, quote, pricing page), and screen for decision role and category familiarity. Avoid long price ladders because they anchor people and increase fatigue; allow "Not sure" so you do not force guesses. For a deeper overview of common pitfalls, see response bias (including anchoring and hypothetical bias).
What should I report internally after fielding a price evaluation survey?
Send a one-page pricing readout: what you tested (price/plans/audience), the key charts by segment (fairness, intent at the shown price, thresholds), and the top objections and value statements from open-text. Close with one recommendation and the next test you will run, plus the KPIs you will watch (conversion, churn, win rate, discount rate). If segment cells are thin, adjust your cuts using practical sample size guidance before you circulate conclusions.
Can I use this template to evaluate packaging and tiers, not just a single price?
Yes. Ask which tier they would choose, what features are must-haves for that tier, and what they would pay to upgrade. Keep the number of plan scenarios limited (2-3) and use skip logic so each person only evaluates the tiers that fit their use case.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED