The Gap Between Knowing Your Product and Knowing Your Customer
Most managers who are new to sales or client-facing roles make the same mistake: they lead with what they know best. They explain features, walk through specifications, and recite benefits they’ve memorized from internal training. The product pitch is polished. The customer still doesn’t buy.
The problem isn’t the product. It’s that the manager is selling to a version of the customer that exists only in their own head. They’ve assumed what the customer wants instead of finding out. And no amount of product knowledge closes that gap.
Understanding your customer well enough to sell to them means knowing what they actually care about, what’s standing in their way, and what a good outcome looks like from their side of the table. This article shows you how to build that understanding systematically, not by guessing.
Start With the Job the Customer Is Trying to Do
A useful frame for customer understanding comes from the idea of “jobs to be done.” Customers don’t buy products or services in the abstract. They hire them to accomplish something specific in their work or life. When you understand the job they’re trying to do, you can speak directly to that instead of describing your offering in a vacuum.
Ask yourself: what problem is this person trying to solve today? What does success look like for them once that problem is gone? What happens if they don’t solve it?
These questions shift your thinking from product-out to customer-in. A procurement manager buying software isn’t looking for features. They’re trying to reduce manual work, reduce errors, and make a defensible decision they won’t have to explain to their CFO in six months. If you understand that, you know exactly what to address.
How to Find Out What the Job Actually Is
- Ask open questions early. Before any pitch, ask the customer to describe their current situation and what they’re hoping to change. “Walk me through how you’re handling this today” reveals more than any survey.
- Listen for friction words. Phrases like “it’s a bit of a pain,” “we usually just,” or “the workaround we use” signal the real problem areas. Those are the jobs your solution needs to address.
- Ask about the last time they tried to solve this. Prior attempts reveal what failed, what they valued, and what they won’t tolerate again.
Build a Clear Picture of Who You’re Actually Talking To
Customer understanding isn’t just about the problem. It’s about the person. Two customers with identical problems may need completely different approaches depending on their role, experience, priorities, and risk tolerance.
Before a sales conversation or proposal, get clear on three things:
- Their role and responsibility. A CEO cares about strategic outcomes and risk. A department head cares about team capacity and budget. A frontline user cares about ease of use and not having their day disrupted. Tailor your message to the person in the room, not to a generic buyer.
- Their decision-making context. Are they the final decision-maker, or are they recommending to someone else? If they’re presenting your solution upward, you need to give them language they can use. If they decide alone, you need to address their personal concerns directly.
- What they’ll be judged on. People make purchasing decisions partly based on how the outcome will reflect on them. A manager who champions a new tool that fails looks bad. Understand their professional stakes and you’ll understand their hesitation.
Use Research Before Every Significant Conversation
Walking into a customer conversation cold is a missed opportunity. Spending 20 minutes on research before a meeting changes the quality of every question you ask and every point you make.
What to Look For
- Their company’s recent news. A new product launch, an acquisition, or a shift in leadership all change priorities. Reference something current and they’ll see you’ve paid attention.
- Their industry’s pressures. If their sector is facing regulatory changes, talent shortages, or margin compression, your solution may be relevant in ways you haven’t mentioned yet.
- Their LinkedIn or professional background. Understanding how long they’ve been in role, where they came from, and what they’ve worked on gives you context for how they think.
- What existing customers in similar situations have said. If you have case studies or outcomes from comparable companies, a brief mention shows you’ve seen this problem before and know how to solve it.
Research doesn’t mean scripting the conversation. It means arriving with enough context to ask smarter questions and make more relevant points.
Separate What Customers Say From What They Mean
Customers don’t always articulate their real concern directly. Sometimes they don’t know exactly what’s bothering them. Sometimes they’re protecting a position. Sometimes they’re testing you.
A common example: a customer says the price is too high. That might mean the price is genuinely beyond their budget. But it might also mean they don’t yet see enough value to justify the cost, they’re comparing you to a cheaper alternative they don’t fully trust, or they’re looking for a reason to negotiate. The right response depends entirely on which one it is.
How to Dig Beneath the Surface
- Reflect the objection back. “When you say the price is a concern, help me understand what you’re comparing it to.” This opens the door without being confrontational.
- Ask about the consequences of not acting. If they downplay urgency, ask what happens if things stay the same for another six months. Their answer tells you whether the problem is real enough to justify a purchase.
- Name the hesitation you sense. If a customer seems reluctant but isn’t saying why, try: “I get the sense there’s something you’re weighing up here—what am I missing?” Most people will tell you.
Map the Outcome They’re Buying, Not the Product They’re Getting
Your customer is not buying your product. They’re buying what your product enables them to do or avoid. This distinction sounds small but it changes everything about how you frame your offer.
Instead of: “Our platform has automated reporting and real-time dashboards.”
Try: “Your team gets back about four hours a week that’s currently going into manual reporting, and your manager sees live data instead of waiting for the Monday update.”
The second version sells the outcome. The first version sells the feature. Customers respond to outcomes because outcomes are what they actually want.
To make this shift, ask yourself before any pitch: what does their work or life look like after they start using this? Be specific. Attach numbers where you can. The more concrete the outcome picture, the easier it is for the customer to see themselves in it.
Know What Makes Your Customer’s Situation Unique
Generic solutions feel like they were built for someone else. Even if your product is the same for every customer, the way you present and apply it should reflect that customer’s specific situation.
This means paying attention to details: the size of their team, how long they’ve had the problem, what they’ve already tried, what constraints they’re working within. Then referencing those details back to them throughout the conversation.
“Given that you’re running a team of twelve across two locations, the way this would work for you is…” lands very differently than “here’s how the product works in general.”
Personalisation signals that you’ve listened, that you understand, and that you’re not just running a script. All three things build trust. And trust is what customers buy before they buy anything else.
Build Understanding Over Time, Not Just Before a Sale
The managers who consistently sell well don’t treat customer understanding as a pre-sales activity. They treat it as an ongoing discipline.
After every customer interaction, note what you learned. What did they care about that you didn’t expect? What did they push back on? What language did they use to describe their problem? Over time, these notes build a picture that makes every subsequent conversation sharper.
Simple Habits That Compound
- Keep a brief record after each customer conversation. Three bullet points is enough: what they want, what’s in the way, what the next step is.
- Review your notes before following up. Reference something specific from the last conversation. It shows continuity and signals that you’re paying attention.
- Ask for feedback when a deal doesn’t close. “I’d find it really useful to understand what we could have done better” gives you data that improves every future conversation.
- Talk to your existing customers regularly. They’ll tell you things that prospects won’t. What almost made them not buy, what surprised them, what they’d change. All of it is signal.
What Good Customer Understanding Looks Like in Practice
A manager walks into a sales conversation with a potential client who runs a mid-sized operations team. Before the meeting, they’ve checked the company’s recent press release announcing a new logistics contract. They know the operations leader’s team is likely stretched. They open with: “I saw you’ve just taken on a significant new contract—congratulations. What does that mean for your team over the next few months?”
The customer says their team is under pressure and onboarding is slow. The manager doesn’t immediately pitch their onboarding tool. They ask three more questions: what’s slowing the onboarding down, what’s the cost of that delay in real terms, and what have they tried so far.
Now they know the specific bottleneck, the financial and operational stakes, and what hasn’t worked before. When they finally describe their solution, it’s in the customer’s language, addressing the customer’s exact situation, with an outcome the customer has already said they want.
That is what customer understanding looks like when it’s working. It’s not a personality trait. It’s a set of habits anyone can develop.
The One Question That Unlocks Everything
If you remember nothing else from this article, remember this question: “What does a good outcome look like for you?”
It’s deceptively simple. But it cuts through assumptions, surfaces priorities, and gives you a target to aim at. Customers who answer this question are telling you exactly what they want to buy. Your job from that point is simply to show them you can deliver it.
Customer understanding isn’t a sales technique. It’s the foundation that makes every other technique work. Build it deliberately, practise it consistently, and it will show up in your close rate, your relationships, and your reputation as someone worth doing business with.
Frequently Asked Questions
Why do customers not buy even when I explain all the product features?
Customers don’t buy because you’re selling to a version of them that exists only in your head, not their actual needs. Leading with features and specifications addresses what you know best, not what they actually care about. The gap isn’t closed by more product knowledge—it’s closed by understanding what job they’re trying to accomplish and what success looks like from their perspective.
How do I find out what my customers actually want as a manager?
Start by asking open questions about their current situation before any pitch: ‘Walk me through how you’re handling this today.’ Listen for friction words like ‘it’s a bit of a pain’ or ‘the workaround we use’—these reveal the real problem areas your solution needs to address. Also ask about their previous attempts to solve the problem, which shows what failed and what they valued.
What is jobs to be done in customer management?
Jobs to be done means understanding that customers don’t buy products in the abstract—they hire them to accomplish something specific in their work or life. Instead of describing your offering in a vacuum, you focus on the actual job they’re trying to do, what success looks like when that problem is solved, and what happens if they don’t solve it. This shifts your thinking from product-out to customer-in.
What’s the difference between knowing your product and knowing your customer?
Knowing your product means understanding features, specifications, and benefits from internal training. Knowing your customer means understanding what they actually care about, what’s blocking them, and what good outcomes look like from their side of the table. Product knowledge focuses on what you’re selling; customer knowledge focuses on what job they’re trying to accomplish and why it matters to them.
How do I avoid making assumptions about what customers need?
Replace assumptions with systematic discovery by asking specific questions about their current process and desired changes. Focus on understanding the job they’re trying to do rather than leading with what you think they should want. Listen actively for pain points and friction in their current workflow, and ask about their previous solution attempts to understand what didn’t work and why.