Customer-Discovery Interview Scripts That Surface Willingness to Pay (2026)

Most founders I talk to have done customer discovery interviews. They’ve scheduled the Zoom calls, asked open-ended questions, and walked away with notebooks full of “people love this idea.” Then they build for six months and find out nobody will pay. The problem isn’t that they skipped the interviews — it’s that their customer discovery interview questions willingness to pay never made it past the surface. This post gives you the verbatim scripts I’ve used and tested to move from problem exploration to budget reality, without leading your prospect toward the answer you want to hear.

I’ve run or reviewed more than 200 of these interviews across B2B SaaS, productized services, and marketplace founders over the past four years. The scripts here are the version I’d hand a founder the night before their first call — not the version I started with. That earlier version got me a lot of enthusiastic conversations and zero paying customers.

Why Most Discovery Interviews Confirm Instead of Challenge

Rob Fitzpatrick’s The Mom Test identified the core failure mode a decade ago: founders ask questions that feel like research but function like fishing for compliments. “Would you use this?” and “Would you pay for this?” are the most common offenders. The research community calls this hypothetical bias — people are reliably optimistic about what they’ll do in an imagined future. Fitzpatrick put it plainly: “The world’s most deadly fluff is ‘I would definitely buy that.'”

Jobs-to-be-Done (JTBD) theory adds another layer. Customers don’t buy products — they hire solutions to make progress on a specific outcome in a specific context. That means the question isn’t “how much would you pay?” but “what are you already paying, in money and time, to make progress on this outcome right now?” The budget signal is embedded in existing behavior, not in hypothetical intent.

The fix isn’t a new framework. It’s a sequenced script that earns the right to ask about money by first establishing the real cost of the problem.

Finding Your First 10 Interviewees

Before the script matters, you need people to run it with. For pre-revenue founders with no warm pipeline, this is the #1 practical blocker. Three tactics that work without a network:

1. Cold DMs in niche Slack and Discord communities. Find communities where your target persona actually spends time — not generic startup Slacks, but industry-specific ones. Write a transparent ask: “I’m not selling anything. I’m spending 20 minutes learning how [target persona] handle [specific problem]. Happy to send a $25 Amazon or Starbucks gift card for your time.” Transparency converts better than vague “research” framing. Expect a 10–20% response rate in communities where you’ve been a genuine contributor.
2. LinkedIn first-degree connections in the target role. Filter your connections by job title and company size. You have more warm contacts than you think — and a first-degree connection is far more likely to say yes than a cold stranger. A short message: “I know you work in [domain]. I’m trying to understand how [role] handle [specific problem] before I build anything. Would you spare 20 minutes on a Zoom call? No pitch, ever.” works well.
3. Subreddit posts on r/entrepreneur, r/SaaS, or niche subreddits. A post titled “I’m a founder doing research on [specific problem] — would 5 people in [role] be willing to do a quick call?” often generates 10–20 responses, especially if you’re transparent about your stage. Be specific about the problem domain; vague posts get ignored.

Budget $200–$300 for gift cards across your first 10 interviews. It’s the cheapest due diligence you’ll ever do.

The 20-Minute Discovery Script: Phase by Phase

Phase 1 (Minutes 0–3): Set the Contract

Before you ask a single question, you need to neutralize the social dynamic. Prospects will try to be helpful. They will sense what you want to hear. The opening sets expectations that prevent this.

“Thanks for making time. Quick note before we start — I’m not pitching anything today, and there are no right or wrong answers. I’m trying to understand how you currently handle [domain], not validate a specific solution. The most useful thing you can do is correct me when I’m wrong about how your world works.”

That last sentence is key. It gives permission — even implicit instruction — to push back. Prospects who feel like they’re teaching you are far more honest than prospects who feel like they’re evaluating your idea.

Phase 2 (Minutes 3–12): Anchor on Specific Past Behavior

This is the core discovery phase. Every question targets what actually happened, not what might happen.

• “Tell me about the last time you ran into [problem]. Walk me through what that day looked like.”
• “What did you do first? Then what?”
• “What tools, services, or people were involved in that situation?”
• “How did you decide to handle it that way versus another approach?”
• “What was the outcome? Was that acceptable, or did you have to do something else afterward?”
• JTBD framing question: “If you think about the outcome you were trying to reach — not the tool or the process, but the actual result — what does success look like for you in that situation? And what does failure cost you?”

The goal is a detailed incident narrative, not a general opinion. General opinions (“this is a big pain point”) are noise. Incident narratives — with actors, timelines, tools, and outcomes — are signal. You will learn more from one specific incident story than from 20 minutes of “yes this is a real problem.”

Phase 3 (Minutes 12–18): Quantify the Problem Before You Touch Price

This is where most founders rush to pitch. Resist it. The quantification questions here are doing double duty: they reveal the real cost of the problem and they build the anchor that makes your eventual pricing conversation honest.

• “Roughly how often does this come up — weekly, monthly, quarterly?”
• “When it happens, how long does it take your team to deal with it?”
• “What does that time cost you — either in your own hours or in staff time?”
• “Are you currently paying for any tools or services to handle this? What does that run you?”
• “What would you estimate this costs the business per year, all in?”

That last question is where many prospects will hesitate. That hesitation is data. If a prospect says “I’ve never really thought about it,” that tells you the problem doesn’t have budget gravity — it’s an annoyance, not a priority. If they give you a number — even a rough one like “probably $15,000–$20,000 a year when you factor in the time” — that’s your economic envelope.

This connects directly to what I covered in why most first products fail before launch: founders skip the step of establishing financial pain before assuming a market exists.

Phase 4 (Minutes 18–20): The Budget Probe

Only after you’ve established the cost of the problem do you move to the budget probe. And even here, you’re not asking “would you pay for this” — you’re asking about existing behavior.

For B2B prospects with organizational budgets, use these questions:

• “Has your team ever evaluated a solution to this specific problem? What happened?”
• “If a solution existed that reliably fixed this — what’s the conversation look like internally to get it approved? Who’s involved?”
• “What budget line would this come from — operations, software, headcount?”
• “When you’ve approved software or services in this range before, what’s the typical ceiling before you need a second signature?”

Note what you’re not asking: “How much would you pay for my product?” That question activates anchoring bias and social performance. Instead, you’re asking about existing approval processes and budget categories. The answer to “what’s your typical ceiling before you need a second signature” is far more useful than any answer to a hypothetical pricing question.

Customer Discovery Interview Questions Willingness to Pay: The Signal Table

After 10 interviews, five signals reliably separate a real buyer segment from a polite audience. Here is what weak and strong looks like for each.

This isn’t a scoring system designed to make you feel good about a weak signal. It’s a forcing function. I’ve seen founders with 10 interviews, all positive, who couldn’t fill in a single “strong” column because they never asked the right questions. One founder I worked with in the HR-tech space ran 12 glowing interviews, hit zero strong signals on the table, and pivoted the segment before writing a line of code. That decision saved her roughly six months of build time.

Common Mistakes That Kill the Budget Signal

Mistake 1: Pitching During Discovery

The moment you describe your solution, the interview becomes a sales call in the prospect’s mind. They shift from informing to evaluating — and evaluating means being polite. Save the pitch for a separate call. I’ve made this mistake more times than I want to admit: I’d get excited when someone described a pain point I’d been building for, and I’d slip into demo mode. In one case, a B2B SaaS interview I ran in 2024 went sideways the moment I mentioned my product name — the prospect spent the remaining eight minutes telling me how much she liked the concept rather than describing her actual workflow. Every time I’ve slipped into pitch mode, interview quality has collapsed.

Mistake 2: Accepting Vague Positive Signals

Phrases like “this is definitely a problem,” “I would totally use something like this,” and “we’ve been looking for a solution” are the discovery interview equivalent of fake applause. They feel good. They mean nothing. The antidote is a follow-up question every time: “Can you tell me more specifically about the last time that came up?” Force the conversation back to a specific incident. If they can’t name one, the pain isn’t sharp enough to buy.

This is exactly what I explored in why friend feedback quietly kills customer validation — social proximity creates a bias toward encouragement that has nothing to do with purchase intent.

Mistake 3: Asking About the Future

Any question in the future tense — “Would you use…,” “Could you see yourself paying…,” “Do you think your team would want…” — is measuring optimism, not willingness to pay. Fitzpatrick’s rule applies here absolutely: only past behavior predicts future behavior. Anchor every question in the past or present tense.

Mistake 4: Interpreting Interest as Commitment

Even after a great interview with solid budget signals, you haven’t validated a buyer. You’ve identified a prospect. The validation step that actually counts is a commitment — a letter of intent, a signed pilot agreement, a pre-order, a deposit. Most indie projects stall not from bad ideas but from mistaking encouragement for commitment — the same failure mode in a different phase.

When You Have 10 Interviews: What to Do With the Data

Ten interviews is a minimum viable signal set for a single segment. Practitioner resources — including GrowthRamp’s customer discovery guide — put the full market validation number at 30 interviews, but 10 is enough to decide whether you have signal worth pursuing. After 10 interviews, look for convergence on three things:

1. Problem homogeneity: Are they describing the same specific problem, or five loosely related things? If five different problems are surfacing, you’re probably talking to five different segments.
2. Budget range convergence: Do the numbers cluster? B2B SaaS products priced at $200–$500/month tend to surface from problems costing $15K–$50K/year. If your interviewees are describing $2K/year problems, a $300/month solution won’t make the math work for them.
3. Organic pull: Did any prospect ask what happens next before you did? Did anyone offer to pay before you named a price? That’s the strongest signal in discovery — demand that precedes the offer.

Frequently Asked Questions

How many customer discovery interviews do I need before I can start building?

Ten interviews is the minimum to detect a pattern, but not enough to confirm one. Run 10 interviews with prospects who all match your target persona, then assess whether the budget signals converge — at least 6 of 10 naming a similar range. If they do, you have enough to build a narrow MVP and run a second round with paying pilots. If they don’t, run 10 more with a refined segment definition before you write a line of code.

What if a prospect says they’d pay but won’t commit to a pre-order or pilot?

That gap is your most important data point. The distance between “I would pay for this” and “here is money” reveals the actual friction — budget approval process, timing, trust deficit, or a problem that isn’t painful enough to act on yet. Ask directly: “What would need to be true for you to move forward in the next 30 days?” If they can’t answer specifically, the problem doesn’t have purchase urgency right now. Note it, don’t dismiss it, but don’t count it as a validated buyer.

Should I share pricing during discovery, or wait?

Don’t introduce pricing first. Let the prospect’s answers about existing spend and problem cost establish the anchor. Then, if they ask or if the budget signal is strong, test a price point by framing it as a question: “If something like this were available at $X/month, where would that land relative to what you’re currently spending on this?” That framing keeps you in research mode and surfaces their reaction without triggering a negotiation dynamic. Introducing price before you understand their cost frame is one of the fastest ways to kill an honest conversation.

What questions should I avoid asking in customer discovery interviews?

Avoid any question in the future tense or hypothetical framing. The Fitzpatrick model flags three categories as particularly destructive: (1) compliment-fishing questions (“Do you think this is a good idea?”), (2) hypothetical-use questions (“Would you use something like this?”), and (3) hypothetical-price questions (“How much would you pay for this?”). All three invite optimism rather than honest signal. Replace them with past-tense behavior questions: “What have you done to solve this?” “What have you spent on this problem in the last 12 months?” “When was the last time you tried a new tool or service to address this?”

What is willingness to pay and how do you surface it without asking directly?

Willingness to pay (WTP) in customer discovery is the maximum a prospect would actually spend to solve a specific problem — as revealed by behavior, not by what they say they’d spend. You surface it indirectly by anchoring on past behavior: “What are you currently spending on tools or services to handle this?” and “What did the last solution in this space cost you?” The gap between what they’re already paying and the size of the pain they describe tells you more about WTP than any direct price question ever will.

Run the Script, Then Decide

The real purpose of these customer discovery interview questions willingness to pay scripts is to make the go/no-go decision on building as rigorous as any other business decision. You wouldn’t commit six months and $50,000 to a business acquisition without financial due diligence. Customer discovery is financial due diligence on a segment — and the budget probe is the income statement.

Run 10 interviews with this script. Fill in the signal table. If you hit the 3-of-10 threshold on named budget ranges, keep going. If you don’t, treat that as a pivot signal, not a failure. The founders who build things people actually buy don’t have better ideas — they have better questions.

Note: Pricing benchmarks and budget thresholds cited here are based on practitioner experience and published resources including GrowthRamp and ProblemSifter. The 3-of-10 threshold and SMB pricing ranges reflect the author’s own interview practice and are not published academic benchmarks. This post is for informational purposes only and is not professional financial, legal, or business advice.