60 Product Survey Questions to Ask, Grouped by Goal

Muhammad Khawaja
Muhammad Khawaja
Updated

Good product survey questions start from the decision you need to make: whether to build a new product, what to fix in a prototype, which features to improve, how to price, or why customers leave. Below are 60 product survey questions grouped by those goals, each with the answer format to use. Pick 5 to 10 questions from one group for a single survey instead of sending all of them, and use the sample survey near the end as a starting structure.

Product survey questions at a glance

Goal When to ask Core question
Concept testing Before you build How likely would you be to use a product that [does X]?
Product testing and beta During a prototype, pilot or beta Were you able to [complete the main task]?
Usage and satisfaction After a few weeks of real use Overall, how satisfied are you with [product]?
Feature feedback Right after someone uses a feature How satisfied are you with [feature]?
Pricing and value Before launch or a price change How would you rate the value for money?
Product-market fit Once people have used it regularly How would you feel if you could no longer use [product]?
Churn and cancellation At cancellation or after inactivity What is the main reason you are cancelling?

New product and concept testing questions

Use these before you build or commit to a launch. Show a short description or mock-up first, then ask. You are testing whether the problem is real and whether this solution appeals to the people who have it.

  1. How do you currently handle [problem]? Multiple choice with the common workarounds, competitors, "I don't" and an "Other" option.
  2. How big a problem is [problem] for you today? Opinion scale 1-5, "Not a problem" to "A major problem".
  3. Based on this description, how likely would you be to use [product]? Opinion scale 1-5, "Very unlikely" to "Very likely".
  4. What, if anything, would stop you from trying it? Long text.
  5. Which part of this idea appeals to you most? Multiple choice listing the main benefits, randomized, with "Other".
  6. What is unclear or unappealing about it? Long text.
  7. Compared with how you handle this today, would [product] be better or worse? Opinion scale 1-5, "Much worse" to "Much better".
  8. Which of these names or designs do you prefer? Multiple choice with a short description of each option, randomized.
  9. Would you like early access when it launches? Yes/no, then an email question for those who say yes.

Product testing and beta questions

Use these once people have a prototype, sample or beta in hand. Ask about specific tasks, and send the survey within a day of the test while details are fresh.

  1. What did you try to do first with [product]? Short text.
  2. Were you able to [complete the main task]? Multiple choice: "Yes", "Partly", "No".
  3. How easy or difficult was it to [complete the task]? Opinion scale 1-7, "Very difficult" to "Very easy".
  4. Where did you get stuck? Long text, shown only to people who answered "Partly" or "No".
  5. Did anything work differently from what you expected? Yes/no, then long text: "What did you expect instead?"
  6. Did you run into any bugs or errors? Yes/no, then long text for steps and a file upload for a screenshot.
  7. How would you rate the overall quality of [product] so far? Rating, 5 stars.
  8. For physical products: how would you rate the [taste, fit, comfort, packaging, durability]? Rating, one question per attribute.
  9. What is the one thing we must fix before launch? Long text.

Product usage and satisfaction questions

These form the core of a product evaluation survey. Send them after a few weeks of real use, not on day one.

  1. How often do you use [product]? Multiple choice: "Daily", "A few times a week", "Weekly", "Monthly", "Less often".
  2. What do you mainly use [product] for? Multiple choice with your main use cases and "Other".
  3. Overall, how satisfied are you with [product]? Opinion scale 1-5, "Very dissatisfied" to "Very satisfied".
  4. How well does [product] meet your needs? Opinion scale 1-5, "Not at all well" to "Extremely well".
  5. How would you rate the reliability of [product]? Rating, 5 stars.
  6. How easy is [product] to use? Opinion scale 1-7, "Very difficult" to "Very easy".
  7. What do you like most about [product]? Long text.
  8. What frustrates you most about [product]? Long text.
  9. How likely are you to recommend [product] to a friend or colleague? Opinion scale 0-10 (the Net Promoter Score question).
  10. What is the main reason for your score? Long text.

Feature feedback and feature request questions

Ask about a feature right after someone uses it, ideally inside your product, and pass the feature name in the survey link.

  1. Which of these features do you use regularly? Multiple choice, multiple selection.
  2. Which feature is most valuable to you? Multiple choice, single selection.
  3. Which features have you never used, and why? Multiple selection, then long text.
  4. How satisfied are you with [feature]? Opinion scale 1-5.
  5. How easy was it to [do the job the feature is for]? Opinion scale 1-7.
  6. Did [feature] do what you expected? Yes/no, then "What did you expect instead?" for "No".
  7. If you could change one thing about [feature], what would it be? Long text.
  8. If you could add one feature, what would it be, and what would it help you do? Long text.
  9. Which of these would be most useful to you next? Pick up to three. Multiple choice, multiple selection. Limiting the picks forces a priority.
  10. How are you working around the missing feature today? Long text. The effort of the workaround tells you how badly it is needed.

Pricing and value questions

Pricing questions work best with people who understand the product, so show a short description and state the billing period and currency. Questions 40 to 43 are the Van Westendorp price sensitivity meter, introduced by Peter van Westendorp in 1976. Ask all four together, in this order, and plot the answers to find an acceptable price range.

  1. How would you rate the value for money of [product]? Opinion scale 1-5, "Very poor" to "Excellent".
  2. At what price would [product] be so expensive that you would not consider buying it? Number.
  3. At what price would it be so cheap that you would doubt its quality? Number.
  4. At what price would it start to feel expensive, but still worth considering? Number.
  5. At what price would it feel like a bargain? Number.
  6. Which of these plans would you choose? Multiple choice with two to four plan descriptions.
  7. How would you prefer to pay? Multiple choice: "Monthly", "Yearly", "One-time".
  8. Compared with alternatives you have considered, is our price lower or higher? Opinion scale 1-5, "Much lower" to "Much higher".

Product-market fit questions

Question 47 is Sean Ellis's product-market fit test. Ellis compared results across startups and found that products where at least 40% of users answered "Very disappointed" tended to have strong traction (summary of the test). Send it only to people who have used the product recently and more than once.

  1. How would you feel if you could no longer use [product]? Multiple choice: "Very disappointed", "Somewhat disappointed", "Not disappointed", "I no longer use it".
  2. What type of person do you think would benefit most from [product]? Long text.
  3. What is the main benefit you get from [product]? Long text.
  4. What would you use instead if [product] were no longer available? Multiple choice with alternatives and "Other".
  5. How can we improve [product] for you? Long text.

The answers to 48 and 49 from "Very disappointed" users are the most useful: they describe who your product is really for and the words they use for its value.

Churn and cancellation questions

Show these during cancellation or send them to accounts that have gone quiet. Keep it to two or three questions; people leaving owe you nothing. For a deeper guide, see cancellation and churn surveys.

  1. What is the main reason you are cancelling? Multiple choice: "Too expensive", "Missing features I need", "Hard to use", "Switching to another product", "No longer need it", "Technical problems", "Other".
  2. Which product are you switching to? Short text, shown only to people who chose "Switching to another product".
  3. What could we have done to keep you? Long text.
  4. What will you miss most about [product]? Long text.
  5. How likely are you to come back in the future? Opinion scale 1-5.
  6. May we contact you to learn more? Yes/no, then email.

Context questions to segment your answers

Add one or two of these to any product survey so you can compare groups. If you already know a customer's plan, account ID or signup date, pass it in the survey link instead of asking.

  1. What best describes your role? Multiple choice.
  2. How long have you been using [product]? Multiple choice: "Less than a month", "1-6 months", "6-12 months", "More than a year".
  3. How did you first hear about [product]? Multiple choice with "Other".

Which answer format to use

Answer format Best for Example
Opinion scale (1-5 or 1-7) Satisfaction, ease, agreement, likelihood How easy was it to set up?
0-10 scale Net Promoter Score How likely are you to recommend us?
Star rating Quick quality ratings of one attribute Rate the packaging
Single choice Reasons, frequency, segments What is the main reason you are cancelling?
Multiple selection Feature usage, "pick up to three" priorities Which features do you use?
Yes/no Screening and branching Did you run into any bugs?
Number Prices and quantities At what price would it feel expensive?
Long text The "why" behind a score What could we have done better?
File upload Screenshots of bugs, photos of products in use Attach a screenshot

Pair every scale with an optional "why" question, because a score without a reason rarely tells you what to change. And keep scales consistent within a survey: if one satisfaction question runs 1-5, they all should, with the same end labels.

If you need a true ranking question (drag options into order), some survey tools offer one; see how ranking questions work in Google Forms and other tools. A "pick up to three" question is often enough and is easier to answer on a phone.

How to write a product survey people finish

  1. Start from one decision, such as "Should we build X?", and cut every question that doesn't help answer it.
  2. Keep it short. Five to ten questions is enough. A single in-app question with an optional follow-up often beats a long email survey.
  3. Ask at the right moment: feature questions right after use, satisfaction after a few weeks, churn questions at cancellation. See when in-app surveys beat email.
  4. Branch on answers. Ask "What went wrong?" only after low scores. For a general feedback form, start with "Is this about a bug or an idea?" and give each path its own follow-ups: steps to reproduce and a screenshot for bugs, use case and impact for ideas.
  5. Pass context instead of asking for it. Plan, account ID and the screen someone came from can travel in the survey link, so every response arrives tagged.
  6. Write neutral, single questions. "How would you rate the new editor?" not "How much do you love it?" "How fast and reliable is it?" is two questions.
  7. Randomize long option lists so the first option doesn't win votes just for being first.
  8. Close the loop. Tell people what you changed because of their feedback.

A sample product feedback survey you can copy

This eight-question structure works for an existing product and takes about two minutes:

  1. Statement screen: "We're improving [product] and want to hear from you. This takes about two minutes."
  2. How often do you use [product]? (single choice)
  3. Overall, how satisfied are you with [product]? (1-5)
  4. Logic: if the score is 1-3, ask "What is the main thing we should fix?"; if 4-5, ask "What do you like most?" (long text)
  5. Which of these features do you use regularly? (multiple selection)
  6. Which of these would be most useful to you next? Pick up to three. (multiple selection)
  7. How likely are you to recommend [product] to a friend or colleague? (0-10)
  8. Anything else you'd like us to know? (long text, optional)

End with a thank-you screen, and, if you like, a second ending for promoters that asks for a review or testimonial.

How to build it in FlowyForm

FlowyForm shows one question at a time, which suits short product surveys shared by link, embedded in your app or site, or printed as a QR code for product testers.

  • Start from the product feedback survey template, the feature request form or the beta tester signup form for recruiting testers.
  • Use opinion scale blocks for 1-5, 1-7 and 0-10 questions, rating blocks for stars, multiple choice with "Other" and randomized options, number blocks for the pricing questions, and file upload for screenshots.
  • Add logic rules on scores or answers to show follow-ups and send people to different endings.
  • Add hidden fields such as ?plan=pro&feature=export to the link so each response is stored with that context.
  • Send each response to a Slack channel or a Google Sheet. To create tickets in tools like Jira or GitHub, use webhooks with Zapier, Make, n8n or your own backend; there is no direct Jira or GitHub integration.

The free plan includes unlimited responses, logic and the Slack, Google Sheets and webhook integrations.

FAQ

What is a product survey?

A product survey is a short questionnaire that asks current or potential customers about a product: whether the problem it solves is real, how they use it, how satisfied they are, which features matter, what they would pay and why they leave.

What questions should I ask about a new product?

Ask how people solve the problem today, how big the problem is for them, how likely they would be to use your product based on a description, what would stop them, and what feels unclear. Questions 1 to 9 above cover this. Once people have tried a prototype, switch to task-based testing questions (10 to 18).

How many questions should a product survey have?

Usually five to ten. One focused goal per survey keeps it short. If you need more, split it into two surveys sent at different moments, or use logic so each person only sees the questions that apply to them.

What is the difference between a product survey and a customer satisfaction survey?

A product survey focuses on the product itself: features, usability, value and fit. A customer satisfaction survey measures the whole experience, including buying, delivery and support. Many teams include one overall satisfaction question in their product surveys so the two can be compared.

When should I send a product feedback survey?

Right after a meaningful action (using a feature, finishing onboarding, completing a test), a few weeks into regular use for satisfaction and product-market fit, and at cancellation for churn. Avoid sending the same customer several surveys in a short period.