What is a Mutual Action Plan (MAP) — and how do you get the buyer to actually sign it?

Direct Answer

A Mutual Action Plan, or MAP, is a jointly-owned, dated timeline that runs from first discovery through signed contract and kickoff. The AE and the buyer-side champion build it together, then list every step that has to happen — security review, legal review, procurement, executive sign-off, DocuSign, implementation kickoff — with a named human owner on each side and a real due date.

It originated in the MEDDPICC/Force Management world and was popularized by Gong and DealHub templates between 2020 and 2024. Gong Labs data shows deals with a shared MAP close 38% more often and 25% faster.

TL;DR

• A MAP is a shared, dated timeline from discovery through kickoff, co-authored by the AE and the buyer's champion, with named owners on both sides for every step.
• The mechanism is commitment: writing dates next to the buyer's name forces internal coordination and exposes phantom approval steps weeks before they would have surprised you.
• The format that actually works is a live shared Notion page, Google Doc, or DealHub workspace with columns for step, owner, due date, status, and blockers — not a one-way PDF the AE sends over.
• Gong Labs research across thousands of opportunities found shared MAPs increase win rate roughly 38% and shorten cycle time roughly 25% versus deals managed without one.
• MAPs die three ways: the AE writes it alone, it never gets updated after week one, or it omits the procurement, legal, and IT rows where deals actually stall.

The Anatomy of a MAP That Closes

A MAP that actually moves a deal looks nothing like the sanitized "buying journey" diagrams vendors put in their pitch decks. It is a working document — messy, frequently updated, full of real names and real dates. The best ones live in a Notion page or DealHub workspace the buyer can edit, with a header like "Acme + Vendor — Path to March 31 go-live." Every row is a concrete step with a verb.

Every owner is a person, not a department. Every date is a Tuesday or Thursday, not "early Q2."

Here is the spine senior AEs use, refined from Force Management's MEDDPICC field guides and the DealHub template library:

Two things separate this from the project plan you might write in your CRM. First, every owner row has a buyer-side name — not just yours. Second, the durations are honest.

Tell a buyer that security review takes three days because your last deal closed that fast, and the first real CISO who sees the doc will write you off as someone who has never sold to an enterprise.

How to Get the Buyer to Sign It (without using the word "MAP")

The biggest mistake AEs make is calling it a Mutual Action Plan in front of the buyer. The buyer hears vendor jargon and assumes a script. Introduce the artifact, not the acronym.

After a strong second meeting — usually the technical demo or business case session — say: "I want to make sure we hit your March 31 go-live. Can we spend ten minutes mapping backward from that date so we both know what has to happen and when?" Then open a blank shared doc, type the go-live date at the bottom, and walk backward together.

That reframe puts the buyer's deadline at the top, not your quarter close. The doc becomes their plan to hit their goal — with you as a resource — rather than your plan to close them. Champions love this because it gives them something to send their executive sponsor.

When the VP asks "how serious is this vendor?", the champion forwards the MAP. That is when the deal stops being a one-on-one conversation and becomes a project an executive tracks.

Two tactics make signature inevitable. First, fill in the buyer-side owners with the champion, live, during that ten-minute session. The instant the champion types "Priya — InfoSec" into a row, the deal moves from selling to implementing.

Second, propose a recurring fifteen-minute Friday sync. Most champions agree because it is shorter than anything else on their calendar, and once that invite is on the books the MAP self-updates. If a buyer refuses both, you do not have a champion — you have a curious manager, and the deal is at far higher risk of slipping than your forecast suggests.

The 3 Ways MAPs Die

The first death is the solo MAP. The AE builds a beautiful timeline in Notion, fills every row with their own name, sends it over, and asks the champion to "review." The champion never opens it. This is a project plan with the buyer's logo at the top, not a MAP.

Mutuality comes from the buyer typing their own owners and dates into rows with you in the room.

The second death is the send-once MAP. AE and champion build it in week one, both feel great, and nobody updates it. By week four the doc is stale, the champion is embarrassed to look at it, and the AE stops bringing it up because pointing at missed dates feels confrontational.

The fix is the Friday cadence — short, lightweight, champion-driven. A MAP not updated weekly no longer exists.

The third death is the sanitized MAP — the version that lists discovery, demo, proposal, and signature but quietly omits security review, legal redlines, procurement, and IT change management. Those four steps are where 80% of enterprise deals actually stall. If they are not on the MAP with named owners, you will discover them as surprises in weeks five through eight, and your close date slips a full quarter.

The MAP's job is to surface those steps in week one, while there is still time to parallel-path them.

Frequently Asked Questions

MAP vs Close Plan — what is the difference? A Close Plan is internal. The AE writes it for their manager and forecast call, with their own dates and assumptions. A MAP is external and jointly owned.

Both can exist at once; mature AEs keep a private Close Plan that mirrors the MAP but adds forecast probability, competitor notes, and internal risk language they would never share with the buyer.

When in the cycle do you propose a MAP? After the second substantive meeting — usually the technical demo or business case session — never on the first call. Proposing one on the first call feels presumptuous and signals you are chasing your quota. Proposing one after the buyer has demonstrated real pain and a real timeline feels like a service.

What if the buyer refuses to engage with the MAP? Treat the refusal as the most valuable data point of the cycle. A real champion will engage because they want the deal too. A polite contact who refuses is telling you they have no authority, no urgency, or no real intent to buy.

Downgrade the forecast, ask one clean question — "is there a different timeline that would work better?" — and either re-qualify or move on.

Sources

• Force Management — MEDDPICC field guides and Command of the Message playbooks, 2022 to 2024
• Gong Labs — Mutual Action Plan win-rate and cycle-time research, 2024
• Sales Hacker — Mutual Action Plan templates and AE playbooks, 2023
• DealHub — Mutual Action Plan template library and digital sales room guidance, 2024
• Pavilion — RevOps and Enterprise Sales community benchmarks, 2024
• OpenView Partners — SaaS Benchmarks Report on enterprise sales cycle length, 2024
• Bessemer Venture Partners — State of the Cloud and enterprise sales motion guidance, 2024
• Winning by Design — SPICED framework and deal execution curriculum, 2023 to 2024