Stop Presenting Information. Start Helping Customers Decide.

Most technical salespeople give presentations that are accurate, well-prepared, and genuinely impressive in terms of the knowledge they contain.

And yet, when the meeting ends, the customer often leaves without a clear sense of what they are supposed to do next. They found it interesting. They appreciated the detail. But they are no closer to a decision than they were before they walked in.

The problem is rarely the content. It is almost always the structure.

The Presentation That Informs Versus the Presentation That Influences

There is a fundamental difference between a presentation designed to inform and one designed to influence a decision.

An informative presentation transfers knowledge. It covers the product, the features, the specifications, the results. It is thorough. It leaves nothing out. And it is built around what the presenter knows.

A presentation designed to influence a decision is built around something different: what the customer needs to understand in order to move forward.

Those two things are not the same. And most technical presentations are built for the first purpose while being used in situations that require the second.

Why technical salespeople default to information transfer

Technical salespeople often know their subject deeply. That knowledge is genuinely valuable. But it can also create a particular kind of trap.

When you understand something well, it is tempting to share all of it. You want to be thorough. You do not want to leave anything important out. You are aware that the customer might have questions you have not anticipated, and you want to be prepared.

So you add another slide. And another. And before long, the presentation is comprehensive in a way that works against you.

The customer is not trying to become an expert in your product. They are trying to work out whether it is worth their time and money. Those are different problems, and they require different presentations.

Start With the Customer's World, Not Your Own

The most effective change most technical salespeople can make to their presentations is to stop starting with their product.

Start with the customer instead.

What is happening in their business? What problem are they dealing with? What is the risk or opportunity they are facing? Why does it matter now, and what happens if nothing changes?

When you open a presentation by describing the customer's situation accurately, something shifts in the room. The customer stops being a passive audience and starts paying attention in a different way. They are not waiting to see what you are going to sell them. They are recognising their own situation in what you are saying.

Once that recognition is in place, your solution has somewhere to land.

The structure that follows the customer's thinking

A presentation built around the customer's decision follows a straightforward sequence.

Their situation. The problem or opportunity within it. Your solution and why it is relevant. Evidence that it works. A clear recommendation about what to do next.

That structure mirrors the way a decision-maker actually thinks. It moves from context to problem to solution to action. It does not require the customer to hold a large amount of technical information in their head before they understand why any of it matters.

Compare that to the structure most technical presentations follow: company overview, product features, technical specifications, case studies, pricing. That structure is built around the presenter's knowledge, not the customer's decision. It asks the customer to do the work of connecting the information to their own situation. Many of them will not bother.

The Problem With Trying to Tell Them Everything

There is a version of over-preparation that is particularly common in technical sales, and it is worth naming directly.

The salesperson knows their product inside out. They have spent months or years developing that knowledge. They are proud of it, and rightly so. And when they get in front of a customer, they want to demonstrate it.

The result is a presentation that covers everything, just in case. Every feature. Every use case. Every technical detail that might conceivably be relevant.

The customer experiences this as a flood of information they cannot process. They do not know what is important and what is background. They do not know what they are supposed to take away. And by the end, they are more confused than they were at the start.

The one question to ask before you build any presentation

Before you put a single slide together, ask yourself one question: what do I want this audience to understand, believe, or do differently as a result of this presentation?

Write the answer down. Then build the presentation around it.

Every slide should earn its place by contributing to that outcome. If a slide does not help the customer understand the problem, believe in the solution, or decide what to do next, it probably does not belong in the deck.

The technical detail can always come later. In a follow-up document. In a separate technical session. In a conversation with the customer's technical team. The presentation is not the place for all of it.

Making Complexity Easier to Understand

Selling something complex does not mean the customer needs to understand all of the complexity. They need to understand the part that is relevant to their decision.

The most effective tool for achieving this is analogy. A well-chosen analogy gives the customer a mental picture they can work with, without requiring them to understand the underlying technical detail.

When explaining a complex insurance proposition, for example, you might say: "Think of it like a building. Your standard policy covers the ground floor. What we are looking at is what happens on the floors above, because that is where the bigger exposure tends to sit."

That is not a complete technical explanation. It is not meant to be. It gives the customer a framework for understanding the concept. Once they have that framework, you can add the specific detail they actually need.

Clarity first, precision where it matters

The instinct in technical sales is often to lead with precision. To get the numbers right. To use the correct terminology. To make sure nothing is oversimplified.

That instinct is understandable, but it can work against you in a presentation context.

Clarity and precision are not the same thing. A clear explanation is one the customer can follow and act on. A precise explanation is one that is technically accurate. In a presentation, clarity matters more.

You can always add precision later, in response to specific questions. But if the customer has not understood the concept, the precise detail is useless to them.

Use Stories to Give Data Meaning

Data tells people what happened. Stories help them understand what it means.

Most technical presentations include statistics. Percentage improvements. Cost reductions. Time savings. These numbers are often genuinely impressive. But presented without context, they do not land the way the presenter hopes.

A customer who hears "our clients have reduced processing time by 40%" has a piece of information. A customer who hears the story behind that number has something they can relate to.

What was the situation? What problem were they experiencing? What did they change, and what happened as a result? What would have happened if they had not changed anything?

Now the customer can picture it. They can start asking themselves whether the same thing could be true for them. That is the real value of a customer story: it turns a statistic into something a decision-maker can use.

Choosing the right story for the right audience

Not every customer story is relevant to every customer. The most effective stories are the ones that reflect the specific situation of the person in the room.

If you are presenting to a finance director, the story that will resonate is one about a finance director who faced a similar problem. If you are presenting to an operations team, find a story about an operations team.

The closer the match between the story and the customer's own situation, the more useful it is. Generic case studies are better than nothing. Specific, relevant stories are significantly more powerful.

Read the Room

A presentation is not a performance where your job is to get from slide one to the end without deviation.

Watch what is happening in the room. Are people asking questions? Are they engaged? Are they pushing back on something? Good. Explore it. A customer who challenges your thinking is a customer who is paying attention.

Are people becoming distracted? Looking at their phones? Having side conversations? Do not simply carry on because the next slide says you should.

Stop and ask: "How does this relate to what you are dealing with?" Or: "I want to make sure this is landing in the right way. What questions do you have so far?"

Being prepared does not mean being trapped by your preparation. The best presenters are willing to adapt because they are focused on the audience, not on delivering their content.

Questions are signals, not interruptions

When someone asks a question during your presentation, it is almost always a sign that they are thinking. That is what you want.

You do not always need to answer immediately with a full explanation. Sometimes "That is a good point. I am going to come to that in a moment" is enough. Sometimes the question is better explored than answered: "That is an interesting question. What is prompting it?"

And if you do not know the answer, say so. "I do not know. Let me find out and come back to you" is more credible than attempting to bluff your way through it. Customers notice the difference, and they remember it.

Before Your Next Presentation

It is worth asking a few questions before you build your next deck.

• Who is in the room, and what do they actually need to understand?
• What decision are they trying to make, and what would help them make it?
• What is the single most important thing I want them to take away?
• Does every slide contribute to that outcome?
• Where can I replace a feature with a business consequence?
• Where can I replace a statistic with a story?
• What is the clearest possible recommendation I can make at the end?

A great technical presentation is not about demonstrating how much you know. It is about helping your customer understand why something matters to them, and making it as easy as possible for them to decide what to do next.

That is the shift from presenting information to influencing a decision. It is not a small shift. But it is the one that makes the difference.

---

Shift the Needle works with salespeople and technical specialists who want to present with more impact. Find out more about our programmes or get in touch.

Related reading: Why Customers Stop Returning Your Calls · Discovery Should Feel Like a Useful Conversation, Not an Interrogation

---

Frequently Asked Questions

Why do technical presentations often fail to lead to a decision?

Because they are built around what the presenter knows rather than what the customer needs to understand. A presentation that covers everything accurately can still leave the customer with no clear sense of what to do next. Structure matters as much as content.

What is the most effective structure for a technical sales presentation?

Start with the customer's situation, not your product. Move from their problem or opportunity to your solution, then to evidence that it works, and finish with a clear recommendation. That sequence follows the customer's thinking rather than the presenter's knowledge.

How do you make a complex product easier to understand in a presentation?

Use analogy to give the customer a mental picture before you add technical detail. Clarity matters more than precision in a presentation context. The detail can come later, in response to specific questions or in a follow-up document.

How much detail should a technical presentation include?

Only the detail that helps the customer make a decision. Before building any presentation, ask what you want the audience to understand, believe, or do differently as a result. Every slide should earn its place by contributing to that outcome.

What should you do when a customer asks a question during a presentation?

Treat it as a signal that they are thinking, which is what you want. You do not always need to answer immediately. Sometimes exploring the question is more useful than answering it. And if you do not know the answer, say so. Credibility matters more than appearing to know everything.