The six reasons people don't buy
The diagnostic sorts your symptoms into one of six root causes. Each one is written out below: what it looks like from the founder's side, what is actually going on, and the three things to do about it.
The Problem Isn't Painful Enough
“People seem interested but nothing happens.”
The pain is real, but it's not sharp enough to drive action.
You've identified a real annoyance, but it's not an acute problem. People acknowledge it exists, but they aren't losing sleep, money, or time over it. Nobody is building workarounds, allocating budget, or complaining to their boss about it. Without urgency, there's no motivation to buy.
Symptoms
- People nod along in conversations but never follow up afterward.
- Nobody can quantify the cost of this problem or recall a specific time it hurt them.
- People aren't doing anything to solve this today. No workarounds, spreadsheets, or budget for it.
- People agree the problem exists but rank it low on their priority list.
- Conversations stay polite and pleasant. Nobody leans in, gets emotional, or shares war stories.
- You've talked to many people and none have asked how to get access or when it will be available.
What to do
- Score your last 5 conversations. Did the person describe a specific moment the problem happened? Did they quantify the cost? Did they mention an existing workaround? If fewer than 3 out of 5 hit those marks, the problem isn't acute enough for this audience.
- Find the sharper edge of the same problem. The problem might be real but you're framing it too broadly. Narrow to the specific moment it hurts most, the specific person who feels it most, and the specific cost that's hardest to ignore. "Professionals waste time on reports" is vague. "Sales managers spend 4 hours every Friday manually compiling pipeline data their VP demands by Monday" is acute.
- Find the people who are already paying to solve it. If no one is spending time, money, or political capital on workarounds, the problem isn't painful enough to build a business around. Look for spreadsheets, manual processes, internal tools, or budget line items as proof of pain.
How you'll know it's working
People tell you stories before you ask. They get frustrated or emotional when describing the problem. They ask "When can I get this?" without being prompted.
Common mistake
Abandoning the idea too quickly. Sometimes the problem is real but you're talking to people who experience it mildly. Try narrowing the audience before killing the idea.
You're Talking to the Wrong People
“Some conversations click, most don't, and I can't tell why.”
The problem is real. You're just not in front of the people who feel it most.
The problem is real, but you're pitching it to people who experience it as a mild inconvenience rather than a burning need. Your ICP is either too broad ("anyone who manages projects") or based on demographics instead of observable pain. When some conversations click and others don't, and you can't explain why, the variable isn't your pitch. It's who you're talking to.
Symptoms
- Some conversations go great, others fall flat, and you can't predict which.
- Your ICP is described with broad labels or job titles rather than specific behaviors and pain signals.
- You can't name 5 specific real people who feel this problem the most.
- Your best conversations came from unexpected people, and interest comes from scattered, unrelated types.
- You struggle to find communities or channels where your target customers naturally gather.
- The people most excited about your idea aren't the ones who would actually pay for it.
What to do
- Find the pattern in your best conversations. Pull out the 3 people who were most engaged, asked the most questions, or showed the most urgency. What do they have in common? Not job titles. Behaviors. Situations. Frustrations. Urgency signals. That pattern is your real ICP.
- Describe your ICP using "People who..." language. Replace demographic descriptions with behavioral ones. Instead of "Marketing directors at mid-size companies," try "People who are manually tracking campaign ROI in spreadsheets because their tools don't talk to each other and their CFO is asking for numbers they can't produce fast enough."
- Find 5 more people who match the pattern and have conversations with them. Use the same questions. If the signal gets stronger with this narrower group, you've found your ICP. If it doesn't, try a different pattern.
How you'll know it's working
Conversations become more predictable. The right people lean in immediately. You can tell within 2 minutes whether someone fits your ICP. Your hit rate on "great conversations" goes from random to reliable.
Common mistake
Narrowing so far that your market can't sustain a business. You're looking for the sharpest pain, not the smallest possible audience. A niche of 50 people isn't an ICP. It's a dinner party.
Your Solution Doesn't Match the Job
“People confirm the problem is real, but they don't want what I've built.”
They want the problem solved. They just don't want it solved the way you're solving it.
The problem is acute. You're in front of the right people. But the thing you've built doesn't match the job they need done. Maybe you're addressing the big picture when they need relief from a specific bottleneck. Maybe your solution adds steps or complexity when they need fewer. Maybe you built what you wish existed, but the way you experience the problem is different from the way your customers experience it. The gap isn't messaging. It's fit.
Symptoms
- People validate the problem enthusiastically, but their energy drops when you show what you've built.
- Feature requests would fundamentally change what the product does, not just improve it.
- The workarounds people use solve a different slice of the problem than your product addresses.
- Your product adds complexity or addresses the big picture when people need help with a specific bottleneck.
- You built what you wish existed, but the people you're talking to experience the problem differently.
- When you ask "What would need to be true for you to switch?", the answer doesn't describe your product.
What to do
- Map the workaround, step by step. Ask your 3 most engaged prospects to walk you through exactly how they handle this problem today. Not the pain. The process. Every step, every tool, every handoff. Where your product replaces that process cleanly, there's fit. Where it doesn't, you've found the gap.
- List every feature request and "we'd need it to..." statement you've heard. Group them. If they cluster around a theme that's different from your product's core, the market is telling you what job they're actually hiring for. Listen to the pattern, not the individual requests.
- Ask the switch question. In your next 3 conversations, ask: "What would need to be true for you to stop using your current workaround and switch to something new?" If the answer doesn't describe your product, you now know exactly what the gap is.
How you'll know it's working
People say "Yes, that's exactly what I need" instead of "That's interesting, but..." Feature requests shift from "it needs to do something completely different" to "it would be great if it also did X" (incremental, not foundational). People start describing your product the way you'd describe it.
Common mistake
Treating every feature request as a mandate to build more. The fix might not be adding features. It might be removing them, simplifying the approach, or solving a smaller, more specific version of the problem really well. Sometimes fitting the job means doing less, not more.
Your Pitch Is About the Product, Not the Pain
“People understand what I do but don't seem to care.”
They understand what you built. They just don't feel why it matters.
The right people have the right problem, and your solution fits. But your message isn't connecting because it leads with what you built instead of what they're suffering from. People understand your product intellectually but don't feel it emotionally. They see a tool. They need to see a painkiller.
Symptoms
- People respond with "interesting" or "cool idea" but never with urgency or a next step.
- People ask "What does it do?" more often than "How does it work?" or "When can I try it?"
- You spend more time explaining features than discussing the customer's problem. Your pitch leads with what you built.
- People say "Send me more info" and then never follow up.
- People ask how you compare to competitors rather than how you eliminate their pain.
What to do
- Rewrite your opening line to start with the customer's cost, not your product. Instead of "We built an AI tool that automates reporting," try "Sales managers spend 4 hours every Friday pulling numbers their VP needs by Monday. We eliminate that." The product is the same. The frame is different. Lead with the bleed.
- Run the "circle test" on your current pitch. Write it out. Circle every word that describes your product (features, tech, capabilities). Now circle every word that describes the customer's problem (pain, cost, frustration, workaround). If the product circles outnumber the pain circles, rewrite until the ratio flips.
- Stop demoing before diagnosing. In your next 3 conversations, don't show the product at all. Spend the entire time asking about the problem. If the conversation naturally leads the customer to ask about your solution, your diagnosis is confirmed and your pitch needs the same flow: problem first, product second. If they never ask, revisit Prescription A.
How you'll know it's working
People start finishing your sentences. They say "Yes, exactly" before you describe the solution. They ask "How does it work?" instead of "What does it do?" The energy shifts from polite to urgent.
Common mistake
Becoming so problem-focused that you never actually describe what you've built. The goal isn't to hide the product. It's to let the problem create the demand for it. Pain first, then solution. Not pain only.
The Price Doesn't Match the Perceived Cost
“People love the product but go silent when I share pricing.”
They want it. They just can't justify the number you're asking.
People want what you're offering, but the price feels disconnected from the value. This usually isn't a pricing problem. It's a cost-discovery problem. You haven't surfaced the full cost of the problem clearly enough for the customer to see your price as a relief rather than an expense. Or you're anchoring your price to competitors instead of to the pain.
Symptoms
- People love the product but go silent, stall, or defer when pricing comes up.
- Your price is based on competitors or gut feeling, and you've changed it multiple times without customer data.
- People ask for a free version or compare your price to cheaper tools that only partially solve the problem.
- You feel anxious saying your price out loud and sometimes discount before being asked.
- You've never asked a potential customer what this problem cost them the last time it happened.
What to do
- Have 3 conversations focused entirely on cost. Don't mention your product or your price. Just ask: "When was the last time this problem came up? What broke? What did it delay? What did it cost you to deal with it?" Map the cost across all four dimensions: money lost, time burned, risk carried, and emotional load. If you can't quantify the cost, you can't justify the price.
- Build a cost-of-inaction statement. Using the evidence from those conversations, write one sentence: "This problem costs [ideal customer profile] approximately [amount] in [cost type] every [time period]." Example: "This problem costs sales managers roughly 16 hours a month in manual reporting and creates a 3-day lag in pipeline visibility for their VP." Your price should feel small next to that number.
- Test the price anchored to the cost. In your next conversation, share the cost of inaction first, then the price. "Most sales managers I've talked to spend 16 hours a month on this. Our tool eliminates that for $X/month." Watch the reaction. If the price feels proportional to the pain, you're calibrated. If not, the cost story isn't strong enough yet.
How you'll know it's working
Customers stop asking "Is there a free version?" and start asking "What's included?" The pricing conversation shifts from negotiation to logistics. People say "That's fair" or "That's less than I expected."
Common mistake
Dropping your price to end the awkwardness. Price resistance usually means the cost of the problem isn't clear, not that the price is wrong. Lowering the price without strengthening the cost story just teaches customers that your value is negotiable.
They Can't Find You
“When I get in front of someone, it works. I just can't get in front of enough people.”
When they find you, it works. The problem is they can't find you.
Your product, pitch, and pricing are working. When you get in front of the right person, they're interested. But you can't get in front of enough people, and the people you do reach are coming through one-off introductions or random encounters. You're relying on luck instead of a system.
Symptoms
- When people find you, they convert. There just aren't enough of them.
- Almost all traction comes from personal introductions or warm referrals.
- Cold outreach (email, DMs, LinkedIn) gets little to no response.
- You don't have a repeatable way to reach new prospects. Your strategy is "launch and hope."
- You can't name the 3 channels where your ICP already spends time looking for solutions.
What to do
- Identify the 3 channels where your ICP already spends time. Not where you think they should be. Where they actually are. Forums, Slack communities, LinkedIn groups, industry events, newsletters, podcasts, subreddits. The people who have your problem are already gathering somewhere and talking about it. Find those rooms.
- Show up in those channels by being helpful, not by pitching. Answer questions. Share insights. Respond to people's problems with genuine value. If your ICP hangs out in a specific Slack community, spend a week being the most helpful person in that channel without ever mentioning your product. Build reputation first. Distribution follows trust.
- Design one repeatable distribution action you can do every day. Not a campaign. A habit. Something like: comment on 5 LinkedIn posts from founders in your ICP every morning. Or send 3 personalized cold DMs per day to people who match your ICP. Or publish one short insight post per week in the community where your ICP gathers. The habit creates the pipeline. The pipeline creates the business.
How you'll know it's working
Inbound interest starts showing up. People reach out to you instead of the other way around. Your weekly pipeline of new conversations becomes predictable. You can say "I talked to X new prospects this week" with a consistent number.
Common mistake
Trying to be everywhere at once. Pick one or two channels and go deep. Spread too thin and you'll be invisible in every room instead of known in one. Depth beats breadth in early distribution.
If buyers are fine but you aren't sure what to ship first, try the V1 readiness assessment. More diagnostics are on the free tools page.