Back to Blog

Should I Ask Users What They'd Pay for My Product?

By George Burgess
7 min read

You've built something valuable. You know it solves a real problem. But when it comes to pricing, you're stuck. Should you just pick a number and hope for the best? Or should you actually ask your potential customers what they'd be willing to pay?

Many creators hesitate to ask users about pricing. It feels awkward, like you're admitting you don't know what your own product is worth. But here's the truth: asking users what they'd pay is one of the smartest moves you can make before launch.

Why Founders Hesitate to Ask

The reluctance to ask about pricing usually comes from a few common fears. First, there's the worry that asking makes you look uncertain or unprofessional. If you don't know what to charge, does that mean you don't understand your own value?

Second, many founders fear the answers they'll get. What if people say they'd pay nothing? What if the numbers are way lower than you hoped? It's easier to avoid the question than face potentially disappointing feedback.

Finally, there's confusion about whether you can even trust what people say. Everyone's heard the stories about customers who claim they'd pay for something, then disappear when it's time to actually buy.

These concerns are valid, but they shouldn't stop you from gathering pricing feedback. The key is understanding when and how to ask the right questions.

The Psychology Behind Asking

When you ask people what they'd pay, you're not just collecting numbers. You're gathering data about perceived value, price sensitivity, and market positioning. This information is incredibly valuable, even if it's not perfectly accurate.

Research shows that while stated willingness to pay isn't always identical to actual purchasing behavior, it's strongly correlated. People might say they'd pay $50 and actually pay $40, or they might say $30 and pay $35. The exact number varies, but the relative positioning stays consistent.

More importantly, asking engages your potential customers in your pricing decision. They feel invested in your product's success. They've thought carefully about the value you provide. This engagement often leads to better customer relationships down the line.

When Direct Questions Work (and When They Don't)

Direct pricing questions work best when you have a clear product concept and you're asking the right audience. If you can show people what you're building and they understand the value proposition, their pricing feedback will be meaningful.

These questions work particularly well with:

  • Beta users who've actually experienced your product
  • Target customers who actively need your solution
  • Community members who already know and trust your work
  • Early supporters who want to see you succeed

Direct questions don't work well when you're asking random people who don't understand your product or aren't in your target market. A developer's opinion on B2B SaaS pricing matters more than their friend's roommate's guess.

How to Ask the Right Way

The way you frame your pricing question makes a huge difference in the quality of feedback you receive. Instead of asking "What would you pay?", try giving people options and seeing which resonates.

Present multiple price points and ask which feels fair. This removes the burden of coming up with a number from scratch and gives you clearer data to work with. You might offer $19, $29, $49, and $79 per month, then see where people cluster.

Context matters too. Explain what features are included, what problem you're solving, and who the product is for. The more clarity you provide, the better the feedback you'll receive.

Make it easy to participate. Long surveys get abandoned. Complex questions get skipped. The simpler and faster you make the feedback process, the more responses you'll collect and the more reliable your data will be.

Tools and Methods for Gathering Pricing Feedback

Traditional approaches include surveys, one-on-one interviews, and landing page tests. Each has its place, but they also have limitations. Surveys get low response rates. Interviews don't scale. Landing pages require significant traffic.

Modern pricing validation platforms solve many of these problems by making it dead simple for users to share their opinions. Instead of filling out forms or scheduling calls, users can vote on different price points in seconds.

The best approach is usually to combine methods. Get detailed qualitative feedback from a few interviews, then validate those insights with broader quantitative data from a larger group.

What to Do With the Answers

Once you've collected pricing feedback, resist the urge to just average the responses and call it done. Look at the distribution of answers. Are people clustered around certain price points? Are there distinct segments with different willingness to pay?

Pay attention to outliers too. If everyone says $29 except for five people who say $99, those outliers might represent an enterprise tier opportunity you hadn't considered.

Compare stated prices against other signals. Do the people who say they'd pay more also engage more with your product? Do they have bigger teams or more complex needs? These patterns help you understand not just what to charge, but who to charge it to.

Use the feedback to test multiple pricing strategies. Maybe you discover you need three tiers instead of one. Maybe you realize your initial price was too low. Maybe you learn that certain features justify premium pricing while others don't.

Making It Easy for Users to Share

The biggest barrier to getting good pricing feedback isn't that people won't share—it's that we make it too hard for them to participate. Long surveys, complicated forms, and time-consuming processes all reduce response rates.

The solution is to remove friction. Let people vote on pricing options with a single click. Show them your product, present a few price points, and ask which feels right. No essays required, no personal information needed, just quick, valuable feedback.

When you make pricing validation this simple, you can gather feedback from hundreds of potential customers instead of just a handful. You get better data, faster insights, and more confidence in your pricing decisions.

So yes, you absolutely should ask users what they'd pay. Just make sure you ask the right people, in the right way, and actually use what you learn. Your pricing will be better for it, and your product will have a much stronger launch.

Ready to validate your pricing?

ProdPoll helps founders get real feedback from their community on pricing decisions. Stop guessing and start making data-driven pricing choices.

Get Started with ProdPoll

Cookie Preferences

We use cookies to enhance your experience and analyze website traffic. Essential cookies are always enabled, but you can choose whether to allow analytics cookies. Learn more

Should I Ask Users What They'd Pay for My Product? | ProdPoll Blog | ProdPoll