Mutual Action Plan Template: The Close Plan Top AEs Actually Use

Search "mutual action plan template" and you'll get a dozen spreadsheets that all say roughly the same thing: send proposal, schedule demo, negotiate terms, get signature, kick off. Those aren't mutual action plans. They're the seller's to-do list with the buyer's name in the header — and they're why so many MAPs get built, shared once, and quietly abandoned by week three. A real mutual action plan is built from the opposite direction: it maps every step the buyer has to take inside their own organization to make this purchase happen, most of which you can't see and none of which appear on your CRM stage list. This guide gives you the anatomy of a buyer-centric MAP, a worked example from an enterprise close, a copyable template, and — the part nobody covers — the actual conversation that produces one.

What is a mutual action plan?

A mutual action plan (MAP) — also called a close plan, joint execution plan, or customer verifier — is a shared, written timeline of every step both the seller and the buyer must complete to get a deal signed and implemented by an agreed date. Each step has an owner (a named person, not a company), a due date, and a status, and both sides can see it.

The word doing the work is mutual. If every row's owner is you, you've written a project plan for yourself. A MAP earns its name when the buyer's rows outnumber yours — because in a complex B2B purchase, they nearly always do. You have to send a proposal and a security questionnaire response. They have to route it through legal, get security sign-off, find budget in a cycle you don't control, brief three stakeholders you've never met, and convince someone that this is worth the disruption. Your list is short. Theirs is the deal.

Why seller-centric MAPs fail

The typical template fails for a reason that goes deeper than laziness. It fails because it describes the part of the deal the seller can see, and deals die in the part they can't.

Think about where late-stage deals actually collapse. Not on "send proposal." They collapse because legal took six weeks and blew the quarter. Because a security review surfaced a SOC 2 question nobody anticipated. Because the buyer's finance team only opens budget in a specific window that closed on the 15th. Because the champion assumed procurement was a formality and it turned out to require three competing bids. Because nobody thought about who would actually run the rollout, so the whole thing stalled on an ownership question at the finish line.

Every one of those is a buyer-side step. None appears on a seller-centric MAP. So the MAP is silent on the exact risks that kill the deal — which makes it a document that inspires false confidence right up until the moment it's useless.

There's a second, subtler failure. Research on late-stage stalls — notably The JOLT Effect by Matthew Dixon and Ted McKenna, which studied recorded sales calls to understand why deals end in "no decision" — points at buyer indecision rather than lack of interest as the dominant killer. Customers stall not because they don't want it, but because they're afraid of getting the purchase wrong. A buyer-centric MAP is a direct antidote to that fear: it takes an intimidating, ambiguous internal process and turns it into a visible, finite list of steps with names and dates on them. It doesn't just track the deal. It makes the buyer feel like the deal is manageable, which is exactly what an indecisive buyer needs.

Your MAP shouldn't describe how you're going to sell. It should describe how they're going to buy — and it should make buying look like something a busy person can actually finish.

The anatomy of a buyer-centric MAP

A good MAP has seven sections. Notice that only one of them is about you.

1. The destination (the agreed outcome and date)

Not "close date: Sept 30" — that's your forecast, not their goal. A MAP starts with a business outcome the buyer actually wants, tied to a date they care about: "New reps productive before the January sales kickoff, which means signed by Nov 15 and rolled out by Dec 10." Anchoring on their date rather than your quarter is what makes the whole document feel like theirs.

2. The people (who has to say yes, and who has to do work)

List every human involved, by name, with their role in the decision — not their job title. Who signs? Who screens? Who has to be trained? This is the same map Strategic Selling's Blue Sheet makes you draw, and it belongs in the MAP because a step with no named owner is a step that won't happen.

3. The buyer's internal gauntlet (the section everyone skips)

This is the heart. Every step the buyer must complete inside their own organization, in order, with their real durations:

• Legal / contract review — who reviews, how long is their queue, what's the standard turnaround, do they use their paper or yours?
• Security / IT review — questionnaire, SOC 2 request, penetration-test results, data-processing agreement, architecture review.
• Procurement — vendor onboarding, competing bids if required, negotiation cycle, PO issuance. (If you're selling upmarket, procurement alone can be a multi-week sub-project.)
• Finance / budget — where does the money come from, is it already allocated, is there a budget window, who approves at this amount?
• Internal socialization — who does the champion need to brief, and does an exec presentation need to happen?

This is the "paper process" — the P in MEDDPICC — and giving it its own section is the single biggest upgrade you can make to a close plan. Most sellers collapse it into one row called "contracts." It isn't one row. It's usually five to ten, and it's where the calendar gets eaten.

4. Your side (the short list)

Proposal, security questionnaire response, reference calls, pricing approval, custom terms. Real, but short. If this section is longer than section 3, you're selling to someone who isn't actually buying.

5. The implementation plan (the part that closes the fear)

What happens after signature: kickoff date, who's trained when, who owns adoption internally, what "working" looks like at 30/60/90 days. Two reasons this belongs in a close plan. First, it's the answer to the buyer's real anxiety — that last time they bought something like this, it died on the vine. Second, discussing rollout in detail quietly assumes the sale, which does more forward motion than any closing technique.

6. Dates, owners, status (the mechanics)

Every row: what, who by name, by when, status. Work backwards from the destination date, not forwards from today — backwards is what exposes the impossible timeline while there's still time to fix it. ("Legal needs four weeks and it's the 20th? Then your January date isn't real unless we start legal now.")

7. The risk row (the honest one)

The best MAPs include an explicit "what could derail this" line, filled in together. It's disarming, it builds trust, and it surfaces the thing your champion is worried about but wouldn't volunteer.

A worked example: a real-shaped enterprise close

Here's what those sections look like assembled, for a $180K deal into a mid-market SaaS company that wants reps ramped before their January kickoff. (Composite example — the shape is what matters.)

Destination: New reps productive before the Jan 12 sales kickoff. Requires: signed by Nov 15, rolled out by Dec 10.

#	Step	Owner	Due	Status
1	Security questionnaire sent	Sam (us)	Oct 2	✅ Done
2	Security questionnaire returned + SOC 2 shared	Priya (IT Security, buyer)	Oct 9	✅ Done
3	Architecture review call with IT	Raj (IT, buyer) + our SE	Oct 14	🟡 Scheduled
4	Business case reviewed with CRO	Dana (champion, buyer)	Oct 17	🟡 In progress
5	CRO meeting — 20 min	Dana → Marcus (CRO, buyer)	Oct 22	⬜ Not started
6	Proposal + pricing sent	Sam (us)	Oct 23	⬜ Not started
7	Legal review begins (their paper, 3-wk queue)	Elena (Legal, buyer)	Oct 27	⬜ RISK: queue
8	Procurement vendor onboarding	Tom (Procurement, buyer)	Oct 27	⬜ Not started
9	Budget confirmed for FY window	Marcus (CRO, buyer)	Nov 3	⬜ Not started
10	Legal redlines resolved	Elena + our counsel	Nov 12	⬜ Not started
11	Signature	Marcus (CRO, buyer)	Nov 15	⬜ Not started
12	Kickoff + admin setup	Dana + our CS	Nov 24	⬜ Not started
13	Rep training sessions (2×)	Dana (buyer)	Dec 3, Dec 8	⬜ Not started
14	Adoption owner named + 30-day check-in	Dana (buyer)	Dec 10	⬜ Not started

Biggest risk: Legal's three-week queue. If step 7 slips past Oct 27, Nov 15 is gone and so is the January kickoff. Mitigation: Dana to ask Elena for a queue slot this week, before the proposal is even sent.

Look at the ownership split: eleven of the fourteen rows belong to the buyer. That's what a mutual action plan looks like. And look at what the document exposed — a legal queue that would have silently eaten the timeline, discovered in week one instead of week six. That single row is worth the entire exercise.

The conversation that creates a MAP

Here's what the template-download crowd never tells you: you cannot write a real MAP at your desk. You can write the seller rows. Everything that matters — the legal queue, the budget window, the procurement rules, who actually signs — lives in the buyer's head, and the only way to get it out is to ask. Which means the MAP isn't really a document. It's the artifact of a conversation, and the conversation is the valuable part.

That conversation has to be earned and framed. Don't open with "can you fill out my close plan." Open with their date:

"You mentioned getting the team ready before January kickoff. Working backwards from that, I want to make sure we don't lose time on something procedural neither of us saw coming. Can I ask you a few boring questions about how purchases like this actually get done at your place?"

Then ask the procedural questions most reps never ask:

• "Walk me through what happens after you decide you want this. Who touches it, in what order?"
• "Whose paper do we use, and how long does your legal team typically take at this size?" (This one question routinely saves deals.)
• "Does security need to review us? Who runs that and what do they usually ask for?"
• "Where does the budget come from, and is there a window when it has to be committed?"
• "Does procurement need competing bids, or are you able to sole-source at this amount?"
• "Who signs — and have they signed something like this before, or is this new for them?"
• "Once it's signed, who inside your team owns making sure people actually use it?"
• "What's the thing most likely to slow this down that we haven't talked about?"

Two things happen when you ask these. You get the information — which alone is the difference between a real timeline and a hopeful one. And you change how the buyer sees you: from a rep chasing a signature to someone who's actually trying to get their project done. That's the Challenger-style "customer verifier" move — you're teaching your champion about their own buying process, which is disarmingly valuable and quietly makes you indispensable. (These questions pair naturally with the broader set in our discovery questions guide.)

The copyable mutual action plan template

Paste this into a shared doc — and the emphasis is on shared: a MAP that lives in your CRM where the buyer can't see it isn't mutual, it's surveillance. Give them edit access. A buyer who edits your MAP has just co-signed the plan.

MUTUAL ACTION PLAN — [Your company] × [Their company]

THE DESTINATION
  Business outcome they want: ..............................
  Their date, and why it matters: ..........................
  Working backwards → signature needed by: .................

THE PEOPLE (name · role in the decision)
  Signs the contract: ......................................
  Champion (drives it internally): .........................
  Users affected: ..........................................
  Screens/can veto (legal, security, procurement): .........
  Owns rollout after signing: ..............................

THE PLAN
  #   Step                          Owner (name)     Due      Status
  1   ...                           ...              ...      ⬜
  2   ...                           ...              ...      ⬜
      (Buyer-side steps to include, if applicable:
       legal review · security review · procurement
       onboarding · competing bids · budget approval ·
       exec briefing · signature · kickoff · training ·
       adoption owner named · 30-day check-in)

BIGGEST RISK TO THE DATE
  What could derail this: ..................................
  Who's mitigating it, and how: ............................

Rule of thumb: if fewer than half the owners above are on
their side of the table, this isn't a mutual action plan yet —
go ask more questions.

Common questions about mutual action plans

What is a mutual action plan? A shared, written timeline of every step both seller and buyer must complete to get a deal signed and implemented by an agreed date, with a named owner and due date on each step. Also called a close plan, joint execution plan, or customer verifier.

What should a mutual action plan include? The buyer's business outcome and date, the named people involved in the decision, the buyer's internal steps (legal, security, procurement, budget, exec briefing), the seller's steps, the post-signature implementation plan, owners and dates on every row, and an explicit biggest-risk line. The buyer's rows should outnumber yours.

When should you create a mutual action plan? As soon as the buyer has agreed they want to solve the problem and there's a date they care about — usually right after a successful demo or business-case conversation, not at the negotiation stage. Building it late means discovering the timeline problems late, which is the whole thing you're trying to prevent.

Who owns the mutual action plan? You draft it and drive it, but it's co-owned — and the ownership shows in the rows. If the buyer never edits it, adds a step, or corrects a date, they haven't actually adopted it, and that's a quiet qualification signal worth paying attention to.

Is a mutual action plan the same as a close plan? Practically, yes — the terms are used interchangeably, along with "joint execution plan." The nuance is that "close plan" often implies the seller's internal document while "mutual action plan" implies a shared one. The name matters less than whether the buyer can see it and edit it.

What if the buyer won't engage with the MAP? That's information, not an obstacle. A champion who won't spend fifteen minutes mapping their own buying process either doesn't have the influence to drive it, or isn't as committed as the forecast assumes. Better to learn that in October than in the last week of the quarter.

The MAP is only as good as the conversation that builds it.

Asking a champion 'whose paper do we use and how long does legal take?' is easy to read and awkward to do — those procedural questions feel intrusive until you've asked them a dozen times. SalesArmor lets you practice the conversation on a live voice call against an AI playing your actual stakeholder, then scores you on whether you surfaced the real process and locked a next step. Rehearse the awkward questions before the deal depends on them.

Practice the close-plan conversation →

A note on sources

This guide draws on the enterprise close-planning literature and practice: the "paper process" discipline formalized in MEDDPICC, the Challenger Sale concept of customer verifiers (teaching the buyer their own buying process), The JOLT Effect by Matthew Dixon and Ted McKenna on buyer indecision as the dominant cause of no-decision losses, and the joint-execution-plan frameworks used by enterprise sales-methodology firms. The buyer-centric emphasis — that a MAP's value is proportional to how many of its rows belong to the buyer, and that its real output is the procedural conversation rather than the document — is the practitioner's read. The worked example is a composite built to show the shape of a real plan, not a specific customer's deal.