Survey questions to ask about a new product (before and after launch)

There is a temptation to treat product feedback as something you collect once, usually after the fact. But the questions you need answered before a launch are fundamentally different from those you need answered after it.

Before launch, you are trying to validate. You want to know whether the product concept resonates, whether the pricing sits right, and whether your target audience sees the problem you are solving. These are market research questions for a new product, and they inform decisions that are still open.

After launch, you are trying to measure. Did the product deliver on its promise? Where is the experience falling short? These product evaluation survey questions close the feedback loop and drive continuous improvement.

Both phases require a clear set of questions and survey software that handles distribution, logic branching, and analysis without friction.

The goal of pre-launch research is to reduce the guesswork that kills products before they reach the market.

Understanding the problem and the audience

Before asking what people think of your product, establish that the problem you are solving is real and felt.

• "How often do you experience [problem your product addresses]?" (Daily / Weekly / Monthly / Rarely / Never)
• "How do you currently manage [this problem]?" (Open text)
• "How satisfied are you with your current solution for this?" (Scale of 1 to 5)
• "What does your current approach cost you in time or money each month?" (Open text or range options)

These questions do more than simply confirm demand. They give you the words customers use to describe their problems, which should feed directly into your positioning.

Concept validation

Once you have established the problem, introduce the product concept and test the reaction.

• "Based on this description, how likely are you to try [product name]?" (Very unlikely / Unlikely / Neutral / Likely / Very likely)
• "What would you expect [product name] to do that is not mentioned here?" (Open text)
• "What concerns, if any, do you have about this product?" (Open text)
• "Who else in your organization or household would use this product?" (Multiple choice or open text)

The last question is particularly useful for B2B products, where buying decisions often involve more than one person.

Pricing and value perception

Pricing is one of the most common places where launches go wrong, and one of the easiest things to test in advance.

• "What price would you consider reasonable for a product like this?" (Open range)
• "At what price would this product start to feel too expensive?" (Open text)
• "At what price would this product start to feel suspiciously cheap?" (Open text)
• "Compared to what you currently use, how would you rate the value of this product?" (Scale of 1 to 5)

The first three questions form a basic Van Westendorp pricing model , one of the most practical tools in product research, delivered through a simple survey for new product launch planning.

Competitive awareness

Understanding what alternatives exist in your customers' minds helps you sharpen differentiation before launch.

• "What other products or tools have you used for this problem?" (Open text or multiple choice)
• "What do those alternatives do well?" (Open text)
• "What would make you switch to a new product?" (Open text)

Messaging and positioning

Before you write your launch copy, find out which aspect of the product your audience finds compelling.

• "Which of these benefits matters most to you?" (Rank or select up to two)
• "How would you describe this product to a colleague in one sentence?" (Open text)

The second question is a quiet goldmine. The answers show how customers naturally frame the product, and they often produce more useful positioning than anything written in isolation.

A Gartner survey of product managers found that 45% of product launches are delayed by at least one month, and among those delayed, 20% on average fail to meet internal targets. The pressure around launch day can cause teams to shift attention away from listening. That is precisely when a structured post-launch survey matters most.

Overall satisfaction and first impressions

• "Overall, how satisfied are you with [product name]?" (Scale of 1 to 10)
• "How well does [product name] match what you expected based on how it was described?" (Not at all / Slightly / Mostly / Completely)
• "What was your first impression after using the product?" (Open text)

Product quality and usability

These product testing questions get specific about the experience of using the product.

• "How would you rate the overall quality of [product name]?" (Scale of 1 to 5)
• "How easy is [product name] to use?" (Very difficult / Difficult / Neutral / Easy / Very easy)
• "Have you run into any issues or limitations while using [product name]?" (Yes / No, with open text follow-up if yes)
• "Are there features you expected to find that are missing?" (Open text)
• "Which parts of [product name] do you use most often?" (Multiple choice or open text)

Value and willingness to continue

• "Do you feel [product name] is worth what you paid for it?" (Yes / No / Somewhat)
• "How likely are you to continue using [product name] in the next three months?" (Scale of 1 to 5)
• "What would need to improve for you to use this product more regularly?" (Open text)

Net Promoter Score

• "How likely are you to recommend [product name] to someone with a similar need?" (Scale of 0 to 10)

Post-launch NPS gives you a fast read on advocacy potential and when tracked over time, tells you whether the experience is improving or slipping after initial excitement fades.

Open discovery

End with at least one question that gives customers space to tell you something you did not think to ask.

• "Is there anything about your experience with [product name] that we have not covered here?" (Open text)
• "If you could change one thing about [product name], what would it be?" (Open text)

Keep each survey focused on one stage. Mixing pre-launch concept questions with post-launch satisfaction questions in the same form creates confusion and dilutes the data.

Write questions in the customer's language, not yours. Internal teams develop shorthand for features and product names that customers have never heard. Every question should read as if a real person wrote it in conversation.

Also, use logic branching. A customer who says they have not encountered any issues does not need to see a question about bug severity. Good survey software handles this automatically, keeping the experience short and relevant.

Send the post-launch survey within the first two to four weeks of use, when first impressions are sharpest. A new product survey sent three months later captures habit but misses the initial reaction that shapes long-term perception.

Zoho Survey lets you build multi-format surveys with logic branching, distribute them through email, links, QR codes, or embedded forms, and track responses in real time through reporting dashboards. For teams using Zoho CRM, the integration links survey responses directly to customer records, turning product feedback into something that feeds into sales, support, and development workflows without manual handling.