Mutual Action Plan (MAP)

What a Mutual Action Plan Is

Receipts on the buying process. A Mutual Action Plan — MAP — is a written, jointly-owned document that lists every step required to take a deal from verbal commitment to signed contract, with owners and dates attached to each action. The seller and the buyer both commit to it. It exists because enterprise deals don't usually die from rejection — they die from drift. Security review slips three weeks, the CIO requests one more demo, the budget cycle resets in January, the champion goes on parental leave.

The MAP is a project plan dressed as a sales artifact. It includes demo schedule, security review, legal redlines, procurement engagement, executive sponsor sign-off, contract countersignature, and kickoff. It also names the humans responsible on the buyer's side — not just "Acme Corp" but "Jordan Park, VP Engineering, owns security review."

How a Mutual Action Plan Is Built

The seller drafts working backwards from the buyer's stated go-live date. If the buyer wants to be in production by August 1 and onboarding takes 30 days, the contract must be signed by July 1. Working backwards: procurement is 14 days, legal redlines are 10 days, security review is 21 days. That places the security kickoff at May 26.

A complete MAP has five fields per row:

It is sent over email or shared in a live doc, and both sides reference it in every meeting. A MAP that doesn't get opened past kickoff is decorative — it's a stage-progression checkbox, not a working artifact.

A Worked MAP Example

A $380K ACV deal at a mid-market SaaS company. The buyer signs verbal in early March, targets July 1 go-live. The AE builds a MAP with 14 steps: technical demo (March 10), reference call (March 17), security questionnaire returned (April 1), InfoSec call (April 8), redlines exchanged (April 15–29), procurement kickoff (May 1), MSA signed (May 22), order form signed (May 29).

By April 15, the security questionnaire is two weeks late. Because the MAP is shared, the AE doesn't send a chasing "any updates?" email — she sends "the MAP has us at April 1 on the security return; what would help us get back on track?" That's a different conversation. The deal closes May 30, one day past target. Without the MAP, three months of slippage was the realistic alternative.

When Sales Orgs Use Mutual Action Plans

MEDDPICC-driven orgs use MAPs as the artifact behind the "P" — Paper Process. Enterprise AEs use them on every deal above a threshold, often $100K ACV. RevOps teams use the existence of a current, dated MAP as a stage-progression gate — no MAP, the opp can't move to Negotiation. VPs of Sales use it to forecast: a deal without one is not a quarter-end commit, full stop. Sales coaches review MAPs in deal reviews the way pilots review checklists.

Common Mutual Action Plan Failures

The most common failure is unilateral authorship. An AE writes the MAP, emails it once, and the buyer never engages with it. That's not mutual — that's a wish list. A real MAP requires the buyer to add their own dates, push back on the seller's estimates, and identify internal owners the seller couldn't have known.

The second failure is fake mutuality. The buyer signs off on dates they have no power to enforce — the champion commits to a security-review date the InfoSec team never agreed to. The MAP drifts, the AE assumes everything is fine because "we have a MAP," and the deal slips into the next quarter.

The last failure: confusing the MAP for the close. A beautifully built MAP is stage-progression theater if no one references it after week two. The working MAPs are the ones with visible edit history.