What is a mutual action plan, and how do you get a buyer to agree to one?
A mutual action plan, or MAP, is a short, dated list of every step between today and a signed contract, with a named owner on the buyer's side or yours for each one, built backwards from the date the buyer needs to go live. You get a buyer to agree to one by anchoring it to their deadline, not your quarter: ask when they need the result, work back from that date together, and let them edit every line before you call it theirs. A plan the buyer hasn't touched is a sales checklist with a nicer name.
Updated
What counts as a mutual action plan?
Dock's template page, read 2026-10-06, calls it "a collaborative document that outlines all the steps, deadlines, and responsibilities." Salesforce's blog (Molly Clarke, April 12, 2024) calls it "a document shared between the seller and the buyer." Vendor wording, not a standard. Both boil down to what, when, who.
In MEDDPICC terms, the MAP is two letters written down. The Decision Process is "the series of steps that the buyer will follow to make a decision." The Paper Process is how you "go from decision to signature." Both phrases are MEDDICC Ltd's, a training company; the framework is in BANT vs MEDDIC.
Our three-line test: every row has a date, every row has a named person, and the buyer does the work on at least a third of the rows. Fail one and it's a close plan in disguise.
Why would a buyer want one?
Because buyers stall, and rarely see it coming. Forrester's December 4, 2024 release on its State of Business Buying 2024 says "86% of B2B purchases stall during the buying process" (no sample size given, and a stall is not a loss). Dixon and McKenna (HBR, June 24, 2022) say 40% to 60% of deals die with a buyer who said they'd buy and then never moved, based on 2.5 million-plus recorded sales calls they studied. Broad range, one research team; the types are in why B2B deals end in no decision.
Gong's 8,382-deal analysis on its own platform (20% close rate with next steps discussed, 5% without) is a correlation that never mentions MAPs; a MAP is simply next steps for the whole deal, buyer's steps included.
Our pitch: the plan guards their go-live date against their own legal queue, security review and budget calendar. Say "so you hit your date," never "so I can forecast."
What goes in the plan, and what stays out?
The core is a table: Step, Their person, Our person, Date, Why this date. Typical rows: success criteria, security questionnaire, pilot, business case, legal, vendor setup, signature, go-live.
The last column does the heavy lifting: every date traces to something the buyer said, a duration ("legal took three weeks last time") or a deadline. If you made it up, mark it "to confirm."
Keep out your internal stages, discount deadlines and anything the buyer did not say. Keep the boring rows: MEDDICC's Paper Process page names legal review, security sign-offs, vendor questionnaires and MSA negotiation as stall points. Reps skip them; they kill the date.
Our owner rule: a buyer owner is a name, not a department. "IT" is not an owner. Get names via how to find the decision maker, and expect several, per B2B buying committee size.
Worked example: a plan built backwards from the signing date (invented)
Invented example, for illustration: we sell a claims-billing tool to Larkspur Therapy, an invented 300-person chain of physical-therapy clinics. Lena, the revenue-cycle director and our champion, says their fiscal year starts Tuesday, January 5, 2027, and she wants billing on the new tool that morning. Omar runs IT, Rita is legal, Ben is the CFO. Our onboarding takes 14 calendar days (invented figure). Lena says legal held their last software contract three weeks; Omar says a security questionnaire takes two. Today is Tuesday, October 6, 2026.
Backwards, in calendar days: go-live Tue Jan 5, minus 14 days of onboarding, is signature Tue Dec 22; minus 21 days of legal is contract-out Tue Dec 1; minus a 7-day buffer is Ben's meeting Tue Nov 24; minus 14 days for the business case is pilot results Tue Nov 10, so the 14-day pilot starts Tue Oct 27. The questionnaire runs Oct 20 to Nov 3; kick-off is Oct 13.
| # | Step | Their person | Our person | Date | Why this date |
|---|---|---|---|---|---|
| 1 | Success criteria agreed (denied-claim rate target, measured in the pilot) | Lena | AE | Oct 13 | Kick-off |
| 2 | Security questionnaire completed | Omar | SE answers | Oct 20 out, Nov 3 back | Omar: two weeks |
| 3 | Sandbox pilot in two clinics (de-identified claims) | Lena | SE | Oct 27 to Nov 10 | Two weeks of claim volume |
| 4 | Business case written from pilot numbers | Lena reviews | AE writes | Nov 17 | A week before Ben's meeting |
| 5 | CFO decision meeting | Ben | AE presents | Nov 24 | 14 days after pilot results |
| 6 | Contract through legal | Rita | AE sends MSA | Dec 1 to Dec 22 | Last contract: three weeks |
| 7 | Signature | Ben | AE | Dec 22 | 14 days before go-live |
| 8 | Onboarding to go-live | Lena | Onboarding lead | Dec 22 to Jan 5, 2027 | Fiscal year starts |
Kick-off to signature is 70 days: Oct 13 to Nov 13 is 31, Nov 13 to Dec 13 is 30, Dec 13 to Dec 22 is 9.
What the plan tells you. The buyer does the work on six of the eight rows (all but the business case and onboarding): 6 ÷ 8 = 75%, well above our one-third floor. Legal is the longest step, at 21 days. Not every slip hurts: if the questionnaire comes back Nov 10, seven days late, nothing moves, because it only had to beat the Nov 24 meeting. If legal takes 28 days instead of 21, signature moves to Dec 29 and go-live to Jan 12, 2027, a week into Lena's fiscal year. Raise that risk on Dec 8, a week into legal, not on Dec 22.
How do you get the buyer to agree to it?
- Ask for the go-live date and the reason behind it.
- Ask what each step took last time: "How long did legal take on your last vendor?"
- Build the first draft on the call, not after it.
Prompt for an AI first pass from your notes (ours):
You are helping me build a mutual action plan from a sales call. Use only facts in my notes. The buyer's go-live date is [DATE] because [REASON]. Durations the buyer gave me: [e.g., legal 3 weeks, security 2 weeks]. Our onboarding takes [N] days. Build a table with columns Step, Their person, Our person, Date, Why this date, working backwards from the go-live date. Where I have no buyer-stated duration, write "to confirm" in the date column instead of guessing, and do not run two steps in parallel unless my notes say so. Finish with the three questions I should ask the buyer to fill the gaps. Notes: [PASTE NOTES]
- Send it the same day as a draft, "to confirm" on every date they didn't give you, linked from the recap email (timing: how long to wait to follow up after a demo).
- Ask your champion to own the buyer-side names before the next call.
- Open every call by reviewing it.
Who signs off: the economic buyer sees the plan before the paper process starts, and the champion keeps it current. Salesforce's post also suggests giving it a dedicated meeting and getting the buyer's sign-off.
Opening line: "Can we sketch the steps from here to your go-live date? You edit it, I'll chase my side." If they say "we don't do that here": "Fine, just tell me what has to happen before you could sign, and I'll write it down."
| They push back with | Your move |
|---|---|
| "We don't need all this." | Shrink it to five rows on the call. |
| "I can't commit the legal team." | Ask for the duration, not the commitment. |
| "Just send the contract." | Ask who reads it first and how long that took last time. |
| "The date might move." | Ask what moves it; mark the date "to confirm." |
What do you do when a date slips?
Our slip rule: a slipped step moves the signature date by the same number of days, unless slack before a later step absorbs it. Say it out loud, with the new signing date. Buyers fix slips when they see their go-live move; they ignore slips you quietly absorb.
Two slips on one step, or a buyer who stops opening the plan: move the deal out of commit (forecast categories). If your champion goes quiet, the plan is your record of what was agreed (when your champion leaves). If the buyer vanishes after the contract goes out, see prospect ghosted after proposal.
Track two numbers (our guidance): share of forecast deals with a buyer-edited plan, and slip days per deal, which feed cycle length in the sales velocity formula.
When should you skip a mutual action plan?
- One person decides and pays from their own card: a dated next step is enough.
- The deal closes in under two weeks: skip the document, keep the "why this date" question.
- The buyer hasn't named a date or a problem: a plan with no buyer deadline is your timeline in a costume.
Sources
Research and vendor pages accessed October 6, 2026.