By 6days · v1.0 · Updated 7/20/2026
A jointly owned, dated plan from here to live — so the deal has no invisible middle.
Fill this in for your own situation — a private worksheet only you can see.
When to use
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 not to use
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.
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 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.
Framework by 6days on 6days — https://6days.apexaion.ai/framework/mutual-action-plan
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.
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.
Worked example
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.
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.
Related ways to think about this.
Lead with a commercial insight that reframes the buyer's problem, rather than asking what keeps them up at night.
Use when 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.
Avoid when 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.
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.