Mutual Action Plan (MAP): Template and Playbook

Deals slip when milestones live in a rep's head, not on paper. A mutual action plan aligns you and the buyer on a specific path to signature — with dates.

Mutual Action Plans: The Shared Document That Closes Enterprise Deals

A mutual action plan (MAP) is a shared document listing every milestone required to close the deal — with owners, dates, and status. It's not project management theater; it's a commitment device. Buyers who agree to a MAP close at 2-3x the rate of those who don't. Buyers who refuse to co-own a MAP are telling you the deal isn't real, even if they say the right words on the demo.

When to introduce the MAP

After the discovery call, before the technical evaluation. Frame: 'To make sure we hit your target go-live date, let's map the milestones between now and then — I'll draft it, you refine it.' Introducing too early feels pushy; introducing too late (post-verbal-yes) is too late to prevent slippage. The MAP is the artifact that transforms 'we're interested' into 'we've committed to a process.'

The template

Columns: milestone, owner (customer name or your name), target date, status (green/yellow/red), notes. Standard milestones: discovery complete, technical evaluation complete, security review complete, procurement package submitted, legal review complete, order form signed, kickoff scheduled. Each with a specific date and named owner. The document is a shared Google Doc or Notion page updated live during meetings.

Getting the customer to co-own it

The magic word: 'What am I missing?' After drafting the MAP, share it with your champion: 'Does this reflect your internal process? What milestones am I missing? Who owns each step on your side?' The customer edits, adds, and signs off — making it their plan, not yours. A MAP written by the vendor and forwarded is a rep artifact. A MAP co-edited becomes shared reality.

Using the MAP in weekly calls

Every weekly touchpoint opens with the MAP: 'Where are we vs plan? What's yellow? What's red?' If procurement is 2 weeks behind, the MAP surfaces it before it becomes a 6-week slip. If the security review hasn't started, the MAP forces the conversation ('who owns kicking that off?'). Deals without MAPs slip silently for 6 weeks; deals with MAPs surface slips immediately and stay on track.

The escalation lever

When a milestone slips, the MAP is your escalation tool: 'We agreed to have security review complete by the 15th. It hasn't started. If we don't kick it off this week, we'll miss the March 1 go-live. Who can help move this forward?' The written commitment gives you cover to escalate without seeming pushy. Without a MAP, escalation feels like nagging; with a MAP, it's holding the mutual plan.

Common mistakes

Vendor-only MAP: rep updates it, customer never opens it. It's a rep tracker, not a mutual plan. Too generic: 'evaluation complete' with no sub-steps hides the real work. Too detailed: 50 milestones no one reads. No dates or dates only ('sometime in March'): the point is the specific commitment. Not reviewed weekly: the MAP has to be a live artifact, not a snapshot.

Frequently asked questions

Does the MAP replace the SOW or contract?
No. It's a process artifact that runs alongside legal documents. The SOW describes what you're delivering; the MAP describes how the deal will get done.
What if the customer refuses to co-own a MAP?
Warning sign. It usually means they're not the true champion, or the deal isn't real. Move the deal to a lower forecast category until you have MAP alignment.
Should we use a MAP for renewals?
Yes — especially at-risk renewals. The renewal MAP covers the 90-day pre-renewal timeline (value review, terms discussion, paper, signature).

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database