Why most B2B pitches talk past the problem

In pitch reviews I almost always see the same pattern: slide one is the company, slide two the product, slide three a feature list. The customer's problem shows up — if at all — as a subordinate clause. The effect is predictable. The other side listens, nods politely, and files what they heard into a drawer they already had: "another vendor".

A pitch is not a talk about your offering. It is an attempt to describe the customer's situation more precisely than they could describe it themselves right now. Do that and attention is given to you for free. Fail at it and you end up selling on price.

The four most common mistakes

1. The problem stays abstract. "Inefficient processes", "lack of transparency", "competitive pressure" — any vendor could use those phrases for any customer. They create no recognition. A problem only becomes tangible when it is described in the customer's own language: at which point in the month, in which role, with which consequence.

2. Value is phrased as a feature. "Modular architecture" is a feature. "You can connect one department without touching the rest" is value. Many pitches leave that translation from feature to outcome to the listener — and the listener does not make it.

3. Proof is missing or doesn't fit. Proof is what turns a claim into an argument: numbers, references from the same industry, a method someone can follow, a guarantee. A logo slide is not proof as long as nobody knows what actually happened at those customers.

4. The pitch is written for the wrong role. The business unit, procurement and the management board care about different things. Running the same script past all three hits one of them at best.

A structure that puts the problem before the product

• Situation: a description of the customer's daily reality they recognise instantly.
• Consequence: what that situation costs — in time, money, risk or lost deals.
• Turning point: what has to change for the consequence to disappear. Still without your product.
• Solution: your offering as a concrete answer to exactly that turning point.
• Proof: why anyone should believe you.
• Next step: one small, clearly named step instead of a big yes.

The decisive break with the usual structure sits between points three and four. Formulate the turning point cleanly and you often get agreement right there — and from then on you are no longer selling against scepticism but along a shared diagnosis.

An example

Before: "We are a leading provider of software solutions for technical sales and support our customers with a modular platform for digitising their quoting processes."

After: "In most technical sales organisations, a week passes between enquiry and quote because three departments have to supply numbers. During that week the customer often decides anyway — for whoever got there first. We shorten exactly that stretch by generating the calculation from data you already hold."

Both sentences describe the same company. The second one invites a conversation; the first one ends it.

How you notice it is working

A good pitch does not primarily change your win rate — it changes the type of questions you get. Instead of "What does it cost?" you hear "How would this run at our place?". Instead of a postponement you get an invitation to bring in the next stakeholder. Those two signals are the most reliable early indicator that the argument holds, long before it shows up in the forecast.