When Customer Interviews Say Yes but Nobody Buys
When customer interviews say yes but nobody buys, the interviews probably measured interest, not a buying decision. Founders with positive discovery calls and no paid commitments should check whether a specific offer was made, whether the account recently paid to deal with the problem, what the current workaround costs and whether the budget owner took part. Fix the first broken link before changing the product. A fix counts only when buyers complete a step.
The symptom and what it does not prove
This guide is for founders at the idea-to-validation stage who have run a round of customer discovery interviews, heard enthusiastic agreement, made some kind of offer and collected no purchases, pilots or signed commitments. If the interviews are still ahead, start with how to run a customer interview without pitching and the customer discovery questions that reveal buying intent. This guide starts after those conversations, when the results disagree with the notes.
A yes in an interview is a statement about the interview. It shows that the problem sounded familiar, that the participant was polite or that the idea seemed reasonable in the abstract. It does not show that the problem costs enough to replace the current workaround, that the person who agreed controls the money, or that anyone was asked to buy at a specific price by a specific date. The National Science Foundation's Innovation Corps program describes customer discovery as talking to potential customers, partners and other industry stakeholders, and says the interview results allow a team to evaluate the commercial potential of its innovation. A run of positive interviews followed by silence is part of that evaluation, so treat it as evidence rather than bad luck.
The silence does not prove that the problem is imaginary either. It shows that one link between the conversation and a purchase is broken. The work is to find which link, fix that one and check whether buying behavior changes.
Build a yes-to-purchase gap map
Before changing anything, put every positive interview on one sheet, one row per account. Use the same said, seen, done and assumed tags as the customer interview notes template, so that agreement is not mixed up with action. The map below is the interview evidence map adapted for diagnosis: instead of choosing which accounts to pursue, it shows where each yes stopped.
| Column | What to record | The question it answers |
|---|---|---|
| The yes | The participant's exact words, tagged said | What was actually agreed to? |
| The ask | What was offered, at what price and with what decision date | Was a purchase ever requested? |
| Recent purchase | The last time the account spent money or paid staff time on this problem, and on what | Does this problem already get a budget? |
| Current workaround | What the account does today, what it costs and who maintains it | What would the product replace? |
| Budget owner | The title of the person who approves this kind of spending, and whether that person took part | Did the yes come from someone who can buy? |
| What happened | Every step completed after the conversation, tagged done | Where did the account stop? |
Read the map column by column, not row by row. The diagnosis is the first column in which most rows are empty or rest only on said entries. Check the ask first, because it is the cheapest gap to close. If no row records a price and a decision date, the interviews have not yet been tested against a purchase, and the next step is a specific, honest offer to the strongest accounts before diagnosing anything else. If offers were made, work through the next three columns in order and stop at the first one that breaks.
Check recent purchasing behavior
Look at the recent purchase column. An account that has spent money or paid staff time on this problem in recent months already treats it as a cost worth reducing. An account that has spent nothing is showing that the problem is tolerated, however strongly the participant described it. Count the rows in which a recent purchase was seen or done, not only said.
If few rows show one, the gap sits upstream of the offer. Either the problem is real but not costly enough for this segment, or the segment is wrong. A better pitch will not fix that. Go back to the accounts and ask about the last time they paid to deal with the problem, then look for a segment in which that answer comes with an invoice, a contractor, a subscription or a hire. The pillar guide on how to validate a startup idea before building describes the build, narrow or stop decision that this finding feeds.
Investigate current workaround
If recent spending exists but nobody switched, examine the workaround. A spreadsheet, a part-time assistant, a habit of the owner or a free tool can be good enough, already approved and familiar to everyone who touches it. Ask to see it rather than hear about it, and record what it costs in money and hours, who maintains it and what happens when it fails. The Small Business Administration's market research guide lists in-depth interviews among direct research methods and, among the questions to answer about a market, asks what potential customers pay for the alternatives. That price is the comparison the buyer makes, whether or not the founder makes it.
The workaround column usually points to one of three diagnoses. The workaround is cheap and rarely fails, so the product needs a segment in which it is expensive or breaks often. The workaround costs real money, but the cost is spread across people and nobody sees it as one number, so the fix is to measure that cost together with the account before asking for a purchase. Or the workaround is costly and visible, but switching means retraining staff, moving data or changing a supplier, so the offer has to take on that switching work.
Fix the gap in decision-maker and budget owner
If purchases and workarounds hold up, read the budget owner column. A yes from someone who lives with the problem every day and cannot approve the spending is a yes about the problem, not about a purchase. If the approver was absent from most of the conversations, the interviews tested the user's interest and not a buying decision.
Reach the budget owner through the user, not around them. Ask the person who agreed who would need to approve a purchase like this, what that person looks at when deciding and whether the user would join a short conversation with them. Then run a separate conversation with the approver about the cost of the problem in the terms the approver tracks, which may be margin, staff hours, risk or a line in the accounts rather than the daily frustration the user described. Make the offer to the approver, with a price and a decision date.
Daniel's go-to-market mentoring page lists naming the user, the budget owner and the event that makes the problem urgent among the topics a session works through, along with defining a pilot outcome, a buyer commitment and the decision that follows the pilot. That description is self-reported on his site.
A hypothetical worked example from bakery interviews
The following is a hypothetical example with invented details. It illustrates the method and does not describe a real company, customer or measured result.
A founder is building an app that tells independent bakeries how many loaves of each kind to bake tomorrow, to cut the bread left unsold at closing. Over a month the founder interviews head bakers and shift leads at eleven bakeries. Nine say they would use it, several describe throwing away bread as painful, and the founder sends all nine a priced offer for a monthly subscription. Three weeks later no bakery has signed, and two have not replied.
The gap map shows that the ask was made: every row records the price and a reply date. The recent purchase column holds up. Six of the nine bakeries have paid in the past year for something aimed at the same problem, such as extra early-morning hours so that a baker can make a second small batch at midday, or a second daily flour delivery. The workaround column holds up too. At one bakery the founder stays until closing and watches the head baker count the unsold loaves left on the cooling rack, stack them into plastic crates for the food bank driver and write the count in a waste log. The founder sees the same kind of log at four other bakeries, and the head bakers say that the owner reviews it every month.
The budget owner column is where the chain breaks. At all nine bakeries the owner approves software purchases, and none of the owners took part in the interviews or saw the offer. The nine yeses came from people who feel the waste every evening and cannot sign for a subscription.
The founder makes one change and keeps the product, price and segment the same. At each of the six bakeries with recent spending, the founder asks the head baker who approves a purchase like this and whether the owner would join a short conversation. Four owners agree. In those conversations the founder asks about the last month of the waste log in the owner's own terms, the ingredient and labor cost of unsold bread, and then offers a four-week paid trial with a decision meeting booked for the end of it.
The founder sets the evidence in advance. The fix is working if owners bring a cost figure from their own records, if at least two of the four accept a paid trial and put the decision meeting in the calendar, and if each trial bakery uses the suggested quantities on most baking days. If no owner can produce a cost figure, the problem is not visible enough to the people who pay, and the next diagnosis returns to the workaround column. The assumptions behind the fix are written down: that owners, not head bakers, approve this kind of spending; that the waste log captures most of the leftover bread; and that the subscription price is small compared with the monthly cost of unsold loaves.
Evidence that the targeted fix is working
Decide what success looks like before the fix starts, and write it as completed steps, not opinions. A fix aimed at one gap should change the column it targets and the steps after it, while the other columns stay as they were.
| Diagnosed gap | Targeted fix | Evidence the fix is working | Evidence it is not |
|---|---|---|---|
| No specific ask | A priced offer with a decision date to the strongest accounts | Replies that accept, negotiate terms or give a specific reason for declining | Polite agreement and no reply by the decision date |
| No recent purchase | Narrow to a segment in which the problem already gets a budget | New interviews record a seen or done purchase for the problem | Vivid descriptions of pain with no spending behind them |
| Workaround good enough | Target accounts in which the workaround is costly, or measure its cost with the buyer | The buyer states the workaround cost from records and compares it with the price | The buyer cannot name a cost or calls the workaround fine |
| Budget owner absent | Reach the approver through the user and run a separate conversation | The approver joins, discusses the cost in their own terms and agrees to a paid step with a date | The user agrees again, and the approver does not appear |
Give the fix a fixed window, such as the next round of conversations, and judge it on the share of positive interviews that lead to a completed step rather than on the number of positive interviews. If that share does not move, do not add features or widen the segment at the same time. Move to the next column on the map and test the fix for that gap.
Common mistakes and limits
- Fixing the product first. Adding features in response to silence changes everything at once and hides which link was broken.
- Changing several things together. A new segment, price and pitch in the same week leave no way to tell which change mattered.
- Counting more yeses. Additional positive interviews add nothing if the same column on the map stays empty.
- Treating an introduction as a commitment. An introduction to the owner shows access, not willingness to pay.
- Blaming the participants. People who agreed and did not buy usually answered honestly about the problem. The interview asked a different question than the purchase did.
The method has limits. It works with accounts that can be named and revisited, so it suits business sales with an identifiable approver more than consumer products, where usage and purchase data carry more weight than interviews. With a small number of accounts, any diagnosis is a hypothesis for the next round, not a finding. The gap map, the order of checks and the evidence table are an editorial framework, not a measured result.
Related guides and next step
- Running the conversations without selling: How to Run a Customer Interview Without Pitching
- Questions about purchases, workarounds and approvers: Customer Discovery Questions That Reveal Buying Intent
- Recording each interview with evidence tags: Customer Interview Notes Template for Founders
- Deciding whether to build, narrow or stop: Validate a Startup Idea Before Building
Bring your gap map and the replies to your last offer to a free 30-minute strategy session to review your customer discovery interviews with your actual evidence and constraints.
Frequently asked questions
Why do customer interviews say yes when nobody buys?
An interview yes tends to measure interest in the problem rather than a buying decision. The participant may not control the budget, the current workaround may be cheap or already approved, the account may not spend anything on the problem today, or no specific offer with a price and a decision date was made. A gap map that compares each yes with the ask, recent purchases, the workaround and the budget owner shows which of these applies.
What evidence should a founder collect for customer discovery interviews?
For each account, record the participant's exact words, the offer made, the last time the account spent money or paid staff time on the problem, the current workaround and its cost, the title of the person who approves spending and whether that person took part, and every step completed afterwards. Tag each item as said, seen, done or assumed.
What are common mistakes in customer discovery interviews?
Treating agreement as a commitment, interviewing only the people who feel the problem rather than the people who pay for it, skipping the question of recent spending, describing the workaround without seeing it, and responding to silence by adding features or changing several things at once.
How do you know a fix for the interview-to-purchase gap is working?
Decide the evidence before the fix starts. The column the fix targets should fill with seen or done entries, and more accounts should complete the next step, such as a meeting with the approver or a paid trial with a decision date. If the share of positive interviews that lead to a completed step does not change, move to the next gap.