Imagine two people trying to sell the same software.
The first begins with a presentation.
“Our software has a dashboard, automated reports, real-time notifications, advanced analytics, and seamless integration with your existing systems.”
The second begins with a question.
“How much time does your team spend preparing reports every week?”
The first person knows the product. The second is trying to understand the problem.
Perhaps the software really does have an excellent dashboard. Perhaps its automated reports are faster than anything the customer has used before. Perhaps the integrations are genuinely impressive.
But none of those features matters until the customer understands why they should care.
If the customer's biggest frustration is spending ten hours every week preparing reports manually, then the conversation is no longer about dashboards and integrations. It is about those ten hours. What could the team accomplish with that time? What mistakes could be avoided? What would happen if the information were available when it was needed, rather than several days later?
The software has not changed. The conversation has.
And that is the point.
A product is what we offer. The outcome is what the customer hopes to achieve.
When we confuse the two, we spend our time explaining what we have built. When we understand the difference, we begin explaining why it matters.
The Product Is Not the Destination
A person buying a drill does not necessarily want a drill. They want a hole in the wall.
Even that may not be the complete story. Perhaps they want to hang a painting, install a shelf, or make their new house feel like home.
The drill is simply the tool that helps them get there.
The same principle applies to almost every product or service we sell.
A person buying a car may want reliable transportation, but they may also want independence, convenience, or the freedom to travel with their family.
Someone buying a course may want knowledge. But they might really be looking for confidence, a career change, professional recognition, or the ability to pursue an opportunity they have been postponing for years.
A business buying accounting software may want accurate books. But the owner might be seeking something more fundamental: confidence that the business is financially healthy, fewer unpleasant surprises, and more time to focus on running the company.
A company hiring a new employee is not simply purchasing someone's time. It hopes that the person will solve a problem, take responsibility, bring expertise, or help the organisation move forward.
The product or service is the vehicle. The desired outcome is the destination.
This distinction sounds obvious when we describe it in simple examples. Yet it is surprisingly easy to forget when we are the people selling.
We become attached to what we have created. We know how much effort went into building it. We understand its features, its strengths, and the clever decisions behind its design.
Naturally, we want people to appreciate those things.
But the customer is not necessarily interested in the effort behind our product. They are interested in what it can do for them.
That is not selfishness. It is simply how people make decisions. They evaluate new things in the context of their own lives, challenges, ambitions, and responsibilities.
Our job is to connect what we offer with what matters to them.
The Trap of Explaining Everything
When we know a product well, we tend to talk about it in detail.
We explain its features, describe how it works, demonstrate its capabilities, and point out the advantages it has over alternatives.
We may believe that the more information we provide, the more convincing our presentation will become.
But more information does not automatically create more value.
Imagine a small business owner who wants to improve the way customers discover the business online.
You offer a website platform. You could explain the technology, the content management system, the hosting infrastructure, the security measures, the analytics, the integrations, and the flexibility of the platform.
All of these may be important.
But the business owner might have a much simpler concern.
“When someone hears about my business and searches for me online, I want them to understand what I do and know how to contact me.”
That is the conversation worth having first.
ll-designed website could help the business owner present services clearly, share useful information, build credibility, and make it easier for interested people to enquire.
The technical features still matter. They support the result. But they no longer need to lead the conversation.
The customer does not have to become interested in website technology to understand the value of having a useful online presence.
This is a useful discipline for anyone who builds products, whether they are developers, designers, consultants, or founders.
We must learn to distinguish between the things we are proud of and the things the customer needs to hear.
Sometimes they overlap. Sometimes they do not.
The purpose of a sales conversation is not to demonstrate everything we know. It is to help another person understand whether we can make a meaningful difference to their situation.
The Question Behind the Question
Consider a customer who says, “I need a new website.”
We could respond by asking about colours, pages, images, hosting, and functionality. We could begin discussing packages and prices.
Those questions will eventually matter.
But first, we could ask something simpler.
“What would you like the new website to help you achieve?”
The answer may reveal that the customer wants to sell products online. Another may want to establish professional credibility. Someone else may need a place to display a portfolio, while another business owner may want customers to find information without calling the office.
All four customers have asked for a website.
Yet they are not necessarily looking for the same solution.
The person selling a product may need a catalogue, payment integration, and a straightforward buying experience. A professional may need a clear profile, service descriptions, and an easy way to get in touch. An artist may need a portfolio that allows the work to speak for itself. A service business may need to explain its offerings and encourage enquiries.
The word website describes the requested product. It does not fully explain the customer's desired outcome.
This is why the question behind the question matters.
People often describe the solution they have imagined rather than the problem that led them to imagine it.
They say they need an app when they may need a simpler process. They ask for more advertising when they may need a clearer offer. They ask for a new employee when they may need to reconsider how work is organised.
Sometimes their proposed solution is exactly right. Sometimes it is not.
We should not assume that customers are wrong about their own needs. But neither should we assume that the first thing they request tells us everything we need to know.
Our responsibility is to understand enough to make a useful recommendation.
Features, Benefits, and Outcomes
There is a difference between describing a feature and explaining a benefit. There is an even deeper difference between describing a benefit and connecting it to an outcome that matters to a particular customer.
Consider three ways of describing the same capability.
A feature: “The system automatically sends reminders.”
A benefit: “You do not have to remember every follow-up yourself.”
An outcome: “You are less likely to miss an important customer conversation because it slipped through the cracks.”
Each statement moves the conversation closer to the customer's world.
The feature explains what the product does. The benefit explains why that capability may be useful. The outcome explains what difference it could make.
Not every feature needs to be translated into a dramatic promise. Some customers genuinely care about technical specifications. Others need reliability, compliance, speed, or precise functionality. In those situations, the specifications themselves may be central to the decision.
The important thing is to understand why those specifications matter.
For one customer, a fast system means handling more orders. For another, it means less waiting. For a technical buyer, it may be essential to meet a particular performance requirement.
The same feature can serve different outcomes.
And outcomes are not always financial. A customer may want to save money, but they may also want to reduce uncertainty, simplify a routine, protect their reputation, spend more time with family, or feel confident about a decision.
We should resist the temptation to assume that everyone measures value in the same way.
The real question is not simply, “What can this product do?”
It is, “Which of these capabilities makes a meaningful difference to this person?”
Sell the Change, Not Just the Thing
Every meaningful purchase involves some kind of change.
A customer moves from doing something manually to doing it automatically. From being difficult to find to being discoverable. From feeling uncertain to having a clearer picture of the situation. From struggling with a recurring problem to managing it more effectively.
The product makes that change possible.
This gives us a different way to think about selling.
Instead of presenting a product as an object with a list of features, we can describe the journey
from the customer's current situation to the situation they would prefer. Where are they today? What is not working as well as it should? What would they like to be different? What is preventing that change? And how might our offering help? Imagine a business owner who spends every evening responding to repetitive customer questions. The owner explains the same services, prices, operating hours, and processes over and over again. A seller could present a website as a collection of pages. Or the seller could explore how a clear, well-organised online presence might help customers find basic information themselves, understand the services available, and arrive at a conversation better informed. The second explanation connects the product to a change in the owner's working life. It does not guarantee that the owner will receive more customers or save a specific number of hours. Those outcomes depend on many factors. But it helps the customer understand the practical purpose of the solution. That is the difference between selling a thing and selling the change that thing is intended to support.Why Understanding the Outcome Makes Selling Easier
When we understand the desired outcome, several parts of the sales conversation become clearer. First, we know what to emphasise. We no longer need to describe every feature equally. We can focus on the capabilities most relevant to the customer's situation. Second, we can make better recommendations. If the customer needs a simple way to display services and collect enquiries, we may not need to recommend a complex e-commerce system. A smaller solution might serve them better. Third, we can discuss price in a more meaningful way. Instead of comparing only the cost of two products, we can examine what each option offers, what it requires, and whether the expected value justifies the investment. Fourth, we can recognise when we are not the right fit. If the outcome the customer needs is beyond what we can reasonably deliver, we can say so before either side wastes time or money. And finally, we can explain our offering in language the customer understands. This does not mean abandoning technical details or simplifying everything until it becomes vague. It means putting information in the right order. Begin with what matters. Explain how the product helps. Then provide the details needed to make a confident decision. The sequence matters because people need a reason to care before they have a reason to examine every detail.The Danger of Promising Too Much
There is an important caution here. Once we start selling outcomes instead of features, it becomes tempting to promise the outcome itself. A website becomes “more customers guaranteed.” Software becomes “zero mistakes.” A training programme becomes “your dream career.” A marketing service becomes “unlimited growth.” These claims may sound persuasive, but they confuse what we can provide with what we can influence. A product may enable an outcome without guaranteeing it. A website can make a business easier to discover and contact, but it cannot guarantee that every visitor will become a customer. A course can teach valuable skills, but it cannot guarantee a promotion. A reminder system can reduce the chance of forgetting something, but its effectiveness depends on how it is configured and used. Customers deserve to understand this distinction. We should be ambitious about the value we can create, but honest about the limits of our contribution. In fact, understanding the desired outcome should make us more careful with our promises, not less. Once we know what matters to the customer, we also know what would constitute a disappointing result. We should be clear about what our product does, how it supports the desired change, what conditions affect the outcome, and what the customer must contribute. Selling the destination does not mean pretending we control the entire journey. It means showing the customer how our offering can help them move towards it.When the Product Is Not the Answer
Perhaps the most difficult test of this principle comes when we discover that our product is not what the customer needs. Imagine a business owner who believes that a new website will solve a decline in sales. After talking, you discover that customers are already finding the business online, visiting the existing website, and making enquiries. The real difficulty is that enquiries are not being followed up consistently. A new website might improve the presentation, but it may not address the central problem. You could still sell the website. You might even be able to justify several improvements. But if you believe the main issue lies elsewhere, you should say so. Perhaps the business needs a better follow-up process. Perhaps it needs to understand why enquiries are not converting. Perhaps the existing website needs only a few targeted changes. This is where the difference between a transaction and a relationship becomes visible. A transaction asks, “Can I sell this product?” A relationship asks, “Can I help this person make progress?” Those questions sometimes lead to the same answer. Sometimes they do not. Choosing not to sell an unsuitable solution may mean losing immediate revenue. But it can also build credibility, preserve trust, and create the possibility of working together when a genuine need emerges. More importantly, it keeps us focused on the reason we entered the conversation in the first place: to create value for another person.A Different Way to Introduce What You Do
This principle also changes how we describe our own work. Suppose someone asks what your company does. You could begin with a list of technologies, services, and capabilities. You could describe the platforms you build, the systems you integrate, and the tools you use. That may be appropriate when speaking to someone who wants technical details. But when speaking to a business owner, it may be more useful to begin with the challenges you help address. You help businesses present what they offer clearly, become easier for potential customers to discover, and create better ways for people to enquire or buy. The technology supports that work. It is not necessarily the first thing the customer needs to understand. The same principle applies to a freelancer, a consultant, an artist, or an employee explaining their contribution. Instead of asking only, “What do I do?”, ask, “What becomes possible because I do it?” A designer does more than create layouts. Their work may help people understand information and navigate a service. A financial adviser does more than recommend financial products. Their work may help clients make informed decisions about their future. A teacher does more than deliver lessons. Their work helps students develop understanding and capability. A developer does more than write code. Their work can make a process simpler, a service more accessible, or a business more effective. Of course, these descriptions must reflect the actual value delivered. We should not dress ordinary work in grand promises. The point is not to make ourselves sound more important. It is to explain our contribution in terms that connect with the people who benefit from it. When we can do that clearly, our work becomes easier to understand.Start With the Destination
There is nothing wrong with being proud of a product. Products require effort, expertise, imagination, and persistence. Building something useful is an achievement in itself. But the moment we offer that product to someone else, the question changes. It is no longer enough to know what we have built. We must understand why another person might need it. The features are our starting point. The customer's desired outcome gives those features direction. So, before the next sales conversation, pause for a moment. Before explaining the product, ask what the person is trying to accomplish. Before presenting the solution, understand what is not working. Before describing the benefits, discover which benefits matter. And before trying to persuade someone to buy, consider whether what you offer is genuinely suited to the change they want to make. You may discover that your product is exactly what they need. You may discover that a simpler solution would serve them better. Or you may discover that you are not the right person to help them at all. All three are useful discoveries. Because the real purpose of selling is not to persuade people that our product is important. It is to understand what is important to them, and then determine whether our product can help.Stop selling the product. Start helping people reach the destination they care about.