15 Customer Discovery Questions That Reveal Buying Intent (2026)

The most dangerous customer interview ends with praise. “I love it,” “I would definitely use this,” and “keep me posted” feel encouraging, but they cost the customer nothing. They predict very little about what happens when price, switching effort, security review, team politics, or a busy calendar enters the decision.

Customer discovery should reveal evidence, not collect approval. The strongest evidence comes from recent behavior, consequences the buyer already feels, resources they have already spent, and commitments they are willing to make next.

The fifteen questions below help uncover that evidence without turning the interview into an interrogation or a disguised product pitch. You will not ask all fifteen in every conversation. Pick the ones that match what you still need to learn, probe the answers, and record the buyer's words before interpreting them.

Use an Intent Ladder, Not a Yes-or-No Label

Buying intent is not one signal. It is a ladder of increasingly costly evidence:

1. Opinion: The person agrees the idea sounds useful.
2. Recognition: They can describe the problem in their own context.
3. Behavior: They recently experienced it or tried to solve it.
4. Resources: They spent time, money, reputation, or team capacity on it.
5. Process: They know who decides, what constraints apply, and when action can happen.
6. Commitment: They offer access, data, an introduction, a scheduled next step, a deposit, or payment.

No single answer closes a sale. The ladder helps you compare interviews without pretending that enthusiasm and commitment are equivalent.

For broad validation work, the customer validation guide provides the surrounding process. The questions here focus specifically on whether the problem is moving toward a buying decision.

Questions 1-4: Establish Recent Behavior

1. “Tell me about the last time this problem happened.”

This question moves the conversation from general beliefs to an event. Ask when it happened, where the work started, who was present, and what the person did next.

Strong signal: The buyer recalls a recent example with concrete steps, people, and consequences.

Weak signal: They can only imagine how the problem might happen to someone else.

Useful probe: “What did you do in the first ten minutes after you noticed it?” A detailed sequence often reveals workarounds and product requirements that an abstract discussion misses.

2. “What changed that made this a problem now?”

Problems become purchases when a trigger raises urgency. A team grows, a contract renews, errors become visible, a regulation changes, a manager arrives, or a workaround breaks.

Strong signal: A dated event created a new cost or deadline.

Weak signal: The problem has been “annoying for years” with no reason to address it now.

Useful probe: “If that change had not happened, would you be looking for a solution?” This separates a persistent irritation from an active buying window.

3. “Walk me through how you handle it today.”

Current behavior is your real competitor. Ask the buyer to describe the workflow from the first input to the final outcome. Note tools, handoffs, waiting, approvals, manual checks, and places where work returns for correction.

Strong signal: The buyer has an established workaround and can point to its friction.

Weak signal: The job is so rare or unimportant that nobody owns a process.

Useful probe: “Could you show me the blank template or a redacted example?” Access to an artifact is stronger than another description and may reveal a viable concierge MVP.

4. “How often has this happened in the last month or quarter?”

Frequency affects value and product shape. A painful daily workflow may support recurring software. A high-stakes annual event may support a premium service but poor weekly retention.

Strong signal: The buyer can estimate frequency from a calendar, ticket log, report, invoice, or repeated routine.

Weak signal: Frequency expands only after you explain why the problem should matter.

Useful probe: “What is the busy-period version?” Peak conditions can reveal urgency that averages hide.

Questions 5-9: Measure Consequence and Existing Spend

5. “What happens when this is late, wrong, or not done?”

Do not force every consequence into money. The cost may be delay, customer trust, employee frustration, compliance exposure, missed revenue, or a senior person's attention.

Strong signal: A named person or metric is affected, and the buyer can recall a consequence.

Weak signal: Nothing changes when the job is ignored.

Useful probe: “Who notices first?” The answer often identifies the problem owner or an overlooked stakeholder.

6. “Which part consumes the most time or attention?”

This question locates the expensive moment inside the workflow. The most disliked step is not always the most valuable one to solve. Waiting for approval may create more delay than the manual task people complain about.

Strong signal: The buyer can identify a bottleneck and quantify it with hours, handoffs, or delay.

Weak signal: Every step is described as equally painful.

Useful probe: “If you could remove only one step, which would change the outcome?” That forces a tradeoff and helps you find a narrow wedge.

7. “What have you tried to fix this?”

Past attempts reveal motivation and evaluation criteria. Include tools, contractors, internal projects, process changes, templates, training, and decisions to postpone.

Strong signal: The buyer invested effort and can explain why an attempt failed or was abandoned.

Weak signal: They have never searched, asked a colleague, created a workaround, or allocated time.

Useful probe: “What did you hope that option would change?” This reveals the desired outcome without asking the buyer to design your product.

8. “What do you currently spend on the problem?”

Ask about total resources, not only software subscriptions. Include employee hours, agency fees, error costs, duplicate tools, rush work, and management review.

Strong signal: There is an existing budget line or costly allocation of time.

Weak signal: The buyer calls the issue critical but cannot name any resource devoted to it.

Useful probe: “Which part of that spend could move to a better solution?” Existing spend does not guarantee accessible budget, but it shows how the company values the job today.

9. “Why did you stop, reject, or replace the last solution?”

Switching history reveals hidden requirements. A product may have failed because of workflow mismatch, implementation burden, trust, price, internal ownership, or a missing result.

Strong signal: The buyer names a specific failure and the condition a replacement must meet.

Weak signal: Every alternative is dismissed with vague adjectives such as “clunky” or “not great.”

Useful probe: “What would have needed to be true for you to keep it?” This exposes the real evaluation standard and warns you against repeating the same failure.

Questions 10-13: Understand the Buying Process

10. “By when would this need to improve to matter?”

A desired date turns urgency into a planning constraint. It may connect to renewal, budgeting, launch, audit, seasonal demand, hiring, or a customer promise.

Strong signal: The date is tied to an external event and delay has a consequence.

Weak signal: “As soon as possible” is followed by no calendar event or owner.

Useful probe: “What happens if nothing changes by then?” A real deadline survives that question.

11. “How would you decide whether a solution worked?”

Ask for an observable before-and-after. Useful criteria include cycle time, errors, completion, conversion, revenue, workload, response time, or confidence in a decision.

Strong signal: The buyer can define success and has access to the evidence.

Weak signal: Success is “people liking it” with no behavior or outcome attached.

Useful probe: “Which measure would persuade someone skeptical inside the company?” This produces a better pilot criterion than a founder-invented metric.

12. “Who needs to agree before you can buy or test this?”

The person experiencing pain may not own budget, security, implementation, or approval. Map the roles instead of asking only for “the decision-maker.”

Strong signal: The buyer names people, their concerns, and the order in which they become involved.

Weak signal: They promise to “socialize it internally” but cannot explain with whom.

Useful probe: “What would each person need to see?” This turns stakeholder mapping into an evidence plan. It is also a core skill in founder-led sales.

13. “Where would the budget come from?”

Ask calmly and late enough that you understand the problem. You are learning whether the purchase competes with software, labor, consulting, innovation, departmental, or discretionary spend.

Strong signal: The buyer names a budget owner, cycle, or existing line item.

Weak signal: The solution is expected to be “free while we test” with no path to a paid decision.

Useful probe: “When was the last purchase from that budget, and how was it approved?” Past process is more informative than a hypothetical promise.

Questions 14-15: Test Commitment Without Pressure

14. “What would prevent you from taking the next step?”

This invites risk into the open. The answer may concern trust, integration, switching effort, timing, authority, price, policy, or the fact that the problem is not urgent enough.

Strong signal: The buyer names a resolvable concern and agrees on evidence that would address it.

Weak signal: New vague concerns appear each time the previous one is answered. The opportunity may be polite rather than active.

Useful probe: “If we resolved that, what else would stand in the way?” Do not use this as a closing trick. Use it to discover whether the stated blocker is actually decisive.

15. “What commitment would make sense now?”

Offer options appropriate to the evidence: share a redacted artifact, introduce the workflow owner, schedule a technical review, test a manual service, review a one-page scope, place a refundable deposit, or start a paid pilot.

Strong signal: The buyer chooses or proposes a concrete action with an owner and date.

Weak signal: They promise to “circle back” while declining every specific next step.

Useful probe: “What should each of us do before that date?” Commitment is visible in behavior. If you are ready to request payment before building, follow the disclosure and delivery safeguards in the pre-selling guide.

How to Probe Without Leading the Witness

A leading question contains the answer you want: “Would saving ten hours be valuable?” Almost everyone says yes. Use neutral prompts that request evidence:

• “How long did it take last time?”
• “What did that delay affect?”
• “What happened next?”
• “How did you choose that workaround?”
• “What makes you say that?”
• “Could you give me an example?”

Allow silence. Founders often rescue the interviewee from thinking by explaining the idea. The explanation contaminates the answer and makes it harder to tell what the customer already believed.

Do not correct the buyer's language. If they describe your assumed “analytics problem” as a “client trust problem,” record that phrase. Their frame may change your product category, buyer, and message.

Use an Interview Note That Separates Fact From Interpretation

Create one page per conversation:

Context: Role, company type, workflow, and relevant trigger.

Recent event: What happened, when, and who was involved.

Current process: Steps, tools, handoffs, frequency, and owner.

Consequences: Observable cost, delay, risk, or frustration.

Existing action: What they tried and what resources they spent.

Buying process: Stakeholders, budget source, deadline, and success criterion.

Commitment: Next action, owner, and date.

Exact phrases: Three direct phrases worth preserving.

Facts versus inference: Label what the buyer stated and what you concluded. “Report takes six hours” is a stated fact. “They will pay €500 per month” is an inference unless the buyer committed to it.

Copy the fields into one note per interview and add three lines at the top:

Customer and role:
Interview date and trigger:
Decision this interview should inform:

At the bottom, require one sentence for evidence that strengthened the idea, one for evidence that weakened it, and one for the next test. That prevents a polished summary from hiding contradictory facts.

If you record the conversation, get permission and follow applicable privacy and storage requirements. A voice recording is not a substitute for structured notes.

Score Evidence After the Interview

Use a simple 0-2 score across six dimensions:

Do not turn twelve points into fake scientific precision. Use the score to compare evidence and notice gaps.

• 0-4: Problem recognition is weak. Change the segment or investigate a different problem.
• 5-8: There is behavior worth studying, but the buying path is uncertain. Run more focused interviews or a manual test.
• 9-12: The evidence may justify a scoped offer, preorder, or paid pilot—provided the pattern repeats across unrelated buyers.

One high score can be an outlier. Look for repeated combinations: the same trigger, workaround, consequence, buyer, and commitment.

Let the Evidence Choose the Next Step

After a set of interviews, make one decision.

Build a narrow MVP when the workflow and success criterion repeat, buyers provide access, and a small product can reach the desired outcome.

Pre-sell or pilot when urgency, decision process, and willingness to commit are clear enough to define an honest offer.

Continue discovery when the problem is real but buyer, trigger, or budget ownership varies.

Narrow the segment when only one subgroup shows recent action and consequences.

Stop or change direction when praise is abundant but behavior, resources, urgency, and commitment remain absent.

100 Tasks AI can help organize interview notes and keep repeated customer facts connected to later product and sales work. But it cannot improve weak evidence by summarizing it more elegantly. Ask about what customers did, listen for what the decision costs them, and let commitment—not compliments—decide what you do next.