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
A jointly owned, dated plan from here to live — so the deal has no invisible middle.
By 6days
Sales
Four kinds of question that let a buyer talk themselves into the size of their problem.
By 6days
When to use — Mutual Action Plan
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.
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 not to use — Mutual Action Plan
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.
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.
Late-stage deals slip for procedural reasons nobody tracked. A security review nobody scheduled, a legal redline waiting on a lawyer's holiday, a signature authority that turned out to sit two levels up. The seller's forecast says a date; the buyer's organisation has never agreed to that date and often has not been asked. Both sides are surprised, and the surprise is always in the same direction.
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.
A mutual action plan is a shared document listing every step from the current moment to a working deployment, each with an owner on one side or the other and a date both sides accept. It is written with the buyer, not for them. Its value is partly logistical and partly diagnostic: a champion who will not co-author a plan, or cannot get anyone to own a step, has just told you something about the deal that no amount of enthusiasm can offset. It replaces the seller's private forecast with a jointly held commitment.
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.
Start at the business outcome and its date — the quarter they need results by — and work backwards to today. Starting from your close date makes it your plan, and a plan the buyer experiences as yours will not survive contact with their calendar.
Capture the buyer's internal machinery as explicitly as your own: security review, legal, procurement, board approval, data migration, training. The steps you cannot see are exactly the ones that cause the slip.
Every step gets a person, on whichever side. Steps owned by 'the team' do not happen. This is also where you discover whether your champion can actually direct anyone.
Dates must be accepted by the owner, not assigned to them. A date invented by the seller is a wish; a date the buyer's legal counsel agreed to is a commitment you can hold them to without friction.
Not specified
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 — Mutual Action Plan
A vendor and a buyer co-author a plan for a 1 October go-live: security questionnaire returned 12 June (buyer's InfoSec lead), architecture review 26 June (both), redlines returned 10 July (buyer's counsel), procurement submission 24 July (buyer's champion), signature 8 August (the CFO), migration 15 August–15 September (both), training 20 September (vendor). In week three the security questionnaire is four days late and InfoSec is unresponsive. That single visible slip triggers a conversation in June rather than a missed date in October — and it reveals that InfoSec was never told the project existed.
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.
Mutual action plans are a practitioner convention rather than a published methodology, and they circulate under several names including mutual close plans and joint execution plans. The underlying idea is imported from project management, where jointly owned schedules with named owners long predate their use in sales. No individual origin is credibly claimed.
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.
Not specified
Walk the plan in every subsequent meeting and let slippage be visible early. A missed step surfaced in week two is a scheduling problem; the same step surfaced in week ten is a lost quarter.
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.
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.
Let the buyer state the value of solving it.