Pricing Discovery: How to Test Willingness-to-Pay Without Leaking Strategy

The Sales Team Cannot Do Your Pricing Research

Most VPs of Product make a fatal mistake: they ask Account Executives to "test out" new pricing tiers on live calls.

This is a disaster. AEs are incentivized to close deals, not collect clean data. If they see a prospect flinch at a $50k initial quote, they’ll discount to $30k to stay in the running for their quarterly quota. You haven't measured willingness to pay; you've just trained your buyers to wait for a price drop.

Willingness to pay research must happen outside the live sales funnel. If your strategy leaks to your current pipeline, you risk resetting the market floor before you’ve even launched the new model.

The Anchoring Trap: Why Direct Questions Fail

If you ask a Director of RevOps at a Series B firm, "How much would you pay for this automated reconciliation tool?" they will lie. They aren't being malicious. It’s a defense mechanism. They want the lowest possible price, so they anchor low.

To get the truth, you have to stop asking for a dollar amount. Instead, focus on the cost of the status quo.

In a recent study for a fintech infrastructure firm, we stopped asking about seat prices and started asking about "error-state recovery time." We found that a four-hour outage cost the prospect roughly $12,000 in engineering overhead and lost transaction fees. That $12k is your ceiling. Only once you establish the cost of the problem can you begin to triangulate a price for the solution.

Four Questions to Map the Value Ceiling

Forget the "What's it worth?" approach. Use these specific prompts during your discovery conversations to find the edges of your pricing power:

• "At what price point would this feel so expensive that you wouldn't even consider it?" This identifies the hard ceiling where the CFO will veto the deal regardless of ROI.
• "At what price point would you consider this a 'no-brainer' purchase that doesn't need C-suite approval?" This tells you the threshold for discretionary department spending (often $10k–$25k in mid-market SaaS).
• "If we charged $X per year, what would you need to see in the first 30 days to feel like you didn't overpay?" This forces the buyer to define their own success metrics and time-to-value.
• "What was the last software purchase your team made that felt like a bargain?" This reveals the buyer’s internal value benchmarks and which competitors they are actually comparing you to.

Testing Value Metrics, Not Just Tiers

Pricing isn't just a number; it’s a metric. Are you charging per seat, per API call, or per "active record"?

Picking the wrong metric can kill a product. A DevOps tool that charges per developer might fail if the engineering lead is currently trying to consolidate head-count. If they are moving toward automation, a "per deployment" metric might feel fairer to them.

I’ve seen a VP of Product at a cybersecurity firm realize mid-discovery that their "per seat" pricing was actually encouraging customers to share passwords to save money. By switching to a "per protected asset" model, they increased the average contract value by 40% because it aligned with how the customer actually grew.

Using BuyerSignal allows you to test these different levers with verified professionals who aren't in your active sales pipeline, ensuring you don't spook your existing customers while you experiment.

The "Substitute Goods" Audit

You aren't just competing against other SaaS vendors. You are competing against "good enough" and "we built it ourselves in a spreadsheet."

In willingness to pay research, you must audit what the buyer would do if your product didn't exist. If the answer is "we'd hire a junior analyst for $65k," that analyst’s salary is your primary competitor. Your pricing needs to be a fraction of that $65k, or your product needs to do work that three analysts couldn't touch.

If the prospect says they would just "ignore the problem for another year," your price isn't the issue—your value proposition is. No amount of pricing optimization can fix a product that solves a "nice-to-have" problem.

Avoid the "Product Marketing" Lean

When conducting these interviews, many founders spend 90% of the time selling the vision and 10% asking for feedback. This is a waste of a conversation.

The goal is to be a neutral observer. Present the product as a fixed set of features. Don't offer "potential future updates" to justify a higher price point. You need to know what they will pay for what exists today, not what might exist in eighteen months.

Keep your workflow clean:

1. Verify the persona (Role, Company Size, Budget Authority).
2. Present a specific use case, not a feature list.
3. Establish the current cost of the problem.
4. Probe the four questions listed above.
5. Document the "tipping point" where the price becomes a non-starter.

Validating Your Model

Strategic pricing is a game of trade-offs. You are looking for the point of maximum revenue, which usually isn't the point of maximum customer volume.

By the time you bring a new pricing model to your sales team, you should already have 15-20 transcripts from non-pipeline prospects confirming that the value-to-cost ratio is balanced. This prevents the "feedback loop of doom" where sales blames the price for every lost deal and product blames the sales team for poor execution.

To get these data points without compromising your current brand reputation, use BuyerSignal to connect with verified experts for structured research. It’s the fastest way to validate your pricing logic before you commit it to a public-facing pricing page.