
You have confirmed a real problem in discovery. The buyer acknowledges it but treats it as a minor irritation, not a priority. You need to help them feel the full weight of it before you say a word about your solution.
A buyer who sees a problem as small will not move. Implication questions - asking what the problem causes downstream - are the mechanism that shifts a problem from 'annoying' to 'urgent'. Neil Rackham's research across tens of thousands of sales calls found implication questions to be the single strongest predictor of success in complex sales. They work because the buyer is doing the math, not you. When they say the number out loud, it lands harder than any figure you could put in a slide.
Skip this step and you pitch into a vacuum. The buyer nods, says it sounds interesting, and does nothing. You lose not to a competitor but to inertia - the buyer decides the problem is not big enough to justify the disruption of changing.
After this lesson you can take a surface-level complaint and, through a short sequence of questions, help the buyer calculate the real cost themselves - in time, money, or deals - so urgency is their conclusion, not your claim.
Confirm the problem first. Do not jump to implications before the buyer has clearly admitted the issue. A quick restatement - 'So the handoff between SDR and AE is where things fall apart?' - gets a clean yes before you go deeper.
Ask what happens downstream. 'When that breaks down, what does it cause for the rest of the team?' or 'Who else feels the knock-on from this?' opens the ripple effect without you asserting it.
Put a rough number on it together. 'Roughly how many deals a quarter do you think get affected by that?' then 'And what is the average deal size?' Let them do the arithmetic. Your job is to hold the silence after the question.
Widen the time horizon. 'So over a full year, what does that add up to?' A quarterly number feels manageable; an annual one often does not.
Aim the heaviest questions at the economic buyer. They feel the aggregate cost across the business. An end user feels their own pain; the economic buyer feels the total.
Rep: 'It sounds like the handoff process is a bit painful.' Buyer: 'Yeah, it is not ideal.' Rep: 'Got it. So let me show you how we handle that...' - The rep accepts the buyer's framing, moves to pitch, and leaves the problem feeling small.
Rep: 'When that handoff breaks down, what actually happens next?' Buyer: 'The AE goes into the call cold, has to re-qualify everything.' Rep: 'How often does that happen?' Buyer: 'Probably half our deals.' Rep: 'And when an AE goes in cold like that, what does it do to close rates?' Buyer: 'Honestly? We probably lose a third of those.' Rep: 'So half your pipeline, losing a third of those deals - what does that add up to in a quarter?' Buyer: '...that is probably four or five deals.' Rep: 'At your average deal size, that is a meaningful number over a year.' - The buyer has done the maths. The rep has said nothing about the product.
After this lesson you can take a surface-level complaint and, through a short sequence of questions, help the buyer calculate the real cost themselves - in time
You have got it when the buyer, not you, names the cost of the problem - in a real number or a concrete consequence - before you have mentioned your solution.
A buyer who sees a problem as small will not move. Implication questions - asking what the problem causes downstream - are the mechanism that shifts a problem from 'annoying' to 'urgent'. After this lesson you can take a surface-level complaint and, through a short sequence of questions, help the buyer calculate the real cost themselves - in time, money, or deals -
Skip this step and you pitch into a vacuum. The buyer nods, says it sounds interesting, and does nothing.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment