Comparing by fit
Two ways of thinking, side by side. There is no winner here — read across each row and choose the one that fits your situation.
Sales
Four kinds of question that let a buyer talk themselves into the size of their problem.
By 6days
Sales
Lead with a commercial insight that reframes the buyer's problem, rather than asking what keeps them up at night.
By 6days
When to use — SPIN Selling
Use it in considered, higher-value sales where the buyer has a real problem they have not fully priced, and where the purchase requires internal justification. It is especially strong when your advantage is genuine but not obvious in a feature comparison.
When to use — Challenger Selling
Use it in complex B2B sales where you have genuine cross-customer data the buyer lacks, where the competition is undifferentiated on features, and where the real enemy is the buyer's inertia rather than another vendor.
When not to use — SPIN Selling
Avoid it in low-value transactional selling, where the buyer knows what they want and the questioning reads as an obstacle between them and a purchase. It fails when the buyer has already diagnosed themselves and wants a price — implication questions asked of a decided buyer feel like manipulation, because at that point they are. It also requires real preparation; run cold it produces an interrogation.
When not to use — Challenger Selling
Avoid it when you have no real insight — performed without substance it is just contrarianism, and buyers detect it immediately. Avoid it with sophisticated buyers who know their domain far better than you, where a reframe reads as condescension. It also demands enablement most sales organisations do not have: the insight must be built centrally, because individual reps cannot see across the customer base.
A seller who explains why their product is excellent gets polite agreement and no purchase. Buyers do not act because a solution sounds good; they act when a problem feels expensive enough to be worth the disruption of fixing. Telling someone their problem is expensive rarely persuades them. They have to arrive there themselves, and most sales conversations never create the conditions for that.
Relationship-led selling assumes the buyer knows what they need and the seller's job is to be trusted, responsive, and pleasant. In complex purchases that assumption often fails. Buyers have partial views of their own problem, committees that disagree, and a strong pull toward doing nothing. A seller who only responds to stated needs ends up competing on price against everyone else who responded to the same stated needs.
SPIN structures discovery around four question types asked in rough sequence: situation questions to establish facts, problem questions to surface difficulties, implication questions to expose what those difficulties cost, and need-payoff questions that invite the buyer to articulate the value of solving them. The engine is the implication stage — it converts a mild annoyance into a quantified business problem, and it does so in the buyer's own words, which is why it survives their internal review after you leave the room. The corresponding discipline is restraint: the seller's job is to ask, not to pitch.
Challenger selling argues that the strongest performers in complex sales teach rather than serve. They bring the buyer a perspective on their business the buyer did not have — usually about a cost or risk they are carrying without knowing it — tailor it to the specific stakeholder, and are willing to create constructive tension rather than agree with everything. The insight has to lead somewhere: it should point naturally at a strength that is genuinely yours, or you have improved your competitor's chances by educating the buyer for free.
Establish the facts you genuinely need — scale, current tools, process, who is involved. Research everything you can beforehand. Situation questions bore buyers and buy you no credit, so the fewer you need, the better prepared you look.
Probe for what is not working: where things break, what is slow, what is manual, what people complain about. You are looking for dissatisfaction, not gaps in your feature coverage. Resist the reflex to solve the first problem you hear.
Take a surfaced problem and follow it outward. What does that delay do downstream? Who else is affected? What has it cost this year? This is the step sellers skip because it feels uncomfortable — and it is the step that does the actual work.
Invite the buyer to describe what solving it would be worth: what changes if this goes away? A benefit you assert is a claim to be checked. A benefit the buyer articulates is a position they will defend to their own colleagues.
An ordered process with 4 phases.
Establish the facts you genuinely need — sparingly.
Surface the difficulties, gaps, and dissatisfaction.
Develop what those problems actually cost.
Worked example — SPIN Selling
A field-service software rep meets an operations director. Situation: 40 engineers, paper job sheets, manual scheduling. Problem: sheets arrive late and some never arrive. Implication: how long until an unbilled job is noticed? Six weeks. What share never get billed? Perhaps 3%. On what revenue? £8m. Who chases them? Two admins, most of a week each month. The director has now said, unprompted, that paper is costing roughly £240k a year plus most of two salaries. Need-payoff: what would same-day billing be worth? The rep has still not mentioned the product, and the business case is already written — by the buyer.
Worked example — Challenger Selling
A workforce management vendor meets a retail chain that has asked for help with scheduling efficiency. Rather than answering the brief, the rep opens with data from comparable chains showing that most scheduling savings are eaten by the cost of staff turnover that erratic schedules cause — the fix for the stated problem makes the unstated one worse. It reframes the conversation from a scheduling purchase to a retention one, an argument the CFO cares about far more, and it points at the vendor's stability features rather than its scheduling engine, where every competitor is equal.
The model was published by Neil Rackham in the late 1980s, drawing on a large observational study of sales calls conducted by his research organisation. It is unusual among sales methods in having been derived from recorded behaviour rather than from a successful practitioner's intuition. The named method and its book are the author's commercial work; this description is our own.
The approach was popularised in the early 2010s by Matthew Dixon and Brent Adamson, based on segmentation research conducted through the Corporate Executive Board on the behaviour of sales representatives. Its central claim — that teaching outperforms relationship-building in complex sales — has been both influential and contested, and the underlying study has drawn methodological criticism. The named framework is the authors' commercial work; this description is our own.
Present your solution against the problem they have now sized, in their language and their numbers. Everything you say here lands against a need they built, which is why it is heard as relevant rather than as a pitch.
Develop a point of view from data across your customers that this buyer cannot see from inside their own organisation — an unrecognised cost, a coming risk, a wrong assumption. It must be commercially specific. A trend report is not an insight.
Trace the insight to its conclusion. If acting on it favours a competitor, you have done their discovery for them. The insight must terminate somewhere you are differentiated — this is the discipline that separates the method from thought leadership.
The same insight has to land differently for the CFO, the operations lead, and the end user, because their metrics differ. Reframe it in each stakeholder's terms without changing the substance.
Open by challenging how they currently understand the problem, and earn the right to your solution by making the problem legible. Do not lead with product; the reframe is what makes the product interesting.
When the buyer pushes back, do not immediately concede. Ask why, and hold the position if the evidence supports it. Assertiveness is the part practitioners drop first because it is uncomfortable, and dropping it turns the method back into a pleasant conversation.
Let the buyer state the value of solving it.
Not specified