By 6days · v1.0 · Updated 7/20/2026
Lead with a commercial insight that reframes the buyer's problem, rather than asking what keeps them up at night.
Fill this in for your own situation — a private worksheet only you can see.
When to use
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
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.
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.
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.
Framework by 6days on 6days — https://6days.apexaion.ai/framework/challenger-selling
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.
Worked example
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 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.
Related ways to think about this.
A jointly owned, dated plan from here to live — so the deal has no invisible middle.
Use when Use it on complex deals with long cycles, multiple approval gates, and implementation work after signature — especially where you have been burned by late-stage procedural slippage or where the buyer has a hard date they must hit.
Avoid when Avoid it on small or fast transactions, where it is bureaucratic overhead the buyer will resent. It is worthless if it becomes a seller-authored document emailed for agreement — that is a project plan with a friendly name, and it will not predict anything. And it cannot fix a deal with no genuine urgency; it will simply document the drift precisely.
Four kinds of question that let a buyer talk themselves into the size of their problem.
Use when 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.
Avoid when 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.
A checklist for whether a complex deal is real, before you spend a quarter finding out.
Use when Use it on high-value B2B deals with several stakeholders and a long cycle, especially where forecast accuracy matters and pipeline reviews have become exercises in optimism. It is most useful as a shared vocabulary that lets a manager ask 'what don't we know?' without it reading as an attack on the rep.
Avoid when Avoid it in transactional or self-serve sales, where the overhead exceeds the deal value and there is no committee to map. Applied mechanically it becomes a CRM compliance ritual that reps fill in after the fact, which produces the paperwork and none of the thinking. It also qualifies deals; it does not create them.