The One-Page Mutual Action Plan for Closing Enterprise Deals
A mutual action plan, sometimes called a MAP, is a shared document listing every remaining step to close, who owns it, and by when. It exists because "let's stay in touch" is not a plan, and most enterprise deals that slip do so on steps nobody wrote down: a legal review nobody scheduled, a budget sign-off nobody chased.
Here's how to build one that a buyer will actually keep using, not just sign once and forget.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
How do you build a mutual action plan with the buyer?
Build the first draft on a call with your champion, live, rather than sending a finished document for them to react to. Ask directly: "What has to happen between now and a signed contract on your end, step by step?" Write down exactly what they say, including steps you didn't expect, like an internal security questionnaire or a specific approver who's traveling next week. A plan they helped build feels like theirs, which matters when you need them to chase their own colleagues later.
Keep It to One Page, on Purpose
Every step gets three columns: the action, who owns it (name, not just "legal"), and a target date. Resist the urge to add a project-management level of detail. The point of a MAP is that a busy VP can glance at it in ten seconds and know exactly what's next and who's behind. A dense multi-page plan gets opened once and ignored. A one-pager gets referenced in every check-in call.
Should the buyer's steps have dates too?
Sellers are usually comfortable committing to their own dates: sending a contract, scheduling a technical call, delivering a security packet. The MAP only earns its name when the buyer's steps get dates as well, such as when their legal team will return redlines or when their budget owner will confirm sign-off. If a buyer resists putting a date on their own step, that hesitation is itself useful information about how real the timeline actually is.
Revisit It Every Time a Step Slips
A missed date on a MAP isn't a failure, it's information. When a step slips, don't quietly extend the date and move on. Go back to the buyer and ask what changed: was it a genuine scheduling conflict, or did priorities shift underneath the deal? A pattern of slipping dates without a clear reason is often the earliest honest signal that a deal is at risk, well before it shows up as a stalled stage in your pipeline.
Use It to Justify Your Own Escalations Internally
A dated, buyer-agreed MAP is also useful evidence when you need to pull in your own manager or an executive sponsor, because it shows exactly where the deal stands against a plan the buyer signed off on, not just your read of the situation. "We agreed legal would return this by the 12th and it's now the 20th" is a much stronger reason to escalate than a vague sense that things feel slow.
A Common Mistake That Makes a MAP Feel Like a Formality
The mistake that undermines a mutual action plan fastest is treating it as a document to produce once and file away, rather than a living reference both sides actually return to. If a rep builds the plan, sends it, and never mentions it again until the deal is already off track, the buyer reasonably concludes it wasn't a real commitment either, just paperwork.
The fix is simple but easy to skip under time pressure: reference the plan by name in every subsequent call. "Looking at our plan, we're on track for the security step, but legal's date moved, let's talk about why." That habit is what turns a one-page document into an actual shared accountability tool, rather than something that gets attached to an email once and forgotten by both sides within a week.
The same mistake shows up when a rep builds the plan alone and sends it for a signature-style acknowledgment instead of walking through it live. A buyer who never had input on the dates has less reason to feel accountable to them, and is more likely to let a step slip quietly rather than flag it early, which is exactly the failure a MAP is supposed to prevent.
Build and maintain the plan with these steps:
- Draft it live with your champion by asking what has to happen on their side, step by step, between now and a signed contract.
- Give every step an action, a named owner and a target date, and keep the whole plan to one page.
- Put dates on the buyer's steps as well as yours, such as legal redlines and budget sign-off.
- Revisit it at every check-in, and ask what changed whenever a step slips instead of quietly extending the date.
- Use the dated plan as evidence when you need to escalate internally.
What Good Looks Like
A working mutual action plan has a date and a named owner on every remaining step, on both sides, and gets updated within a day whenever a step slips, not reviewed only at the next scheduled call.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Frequently Asked Questions
When in the sales cycle should I introduce a mutual action plan?
As soon as you've confirmed real buying intent and a rough timeline, usually right after the deal moves past initial evaluation into a defined path to close. Introducing it too early, before the buyer has committed to moving forward at all, can feel presumptuous and stall the relationship instead of helping it.
What if the buyer won't engage with the plan at all?
Low engagement with a MAP is a warning sign worth taking seriously. It often means the deal isn't as prioritized on their side as it sounds on calls. Keep it simple, keep asking for their input, and if they still won't engage after a couple of tries, treat the deal as lower confidence in your forecast.
Should the mutual action plan include pricing details?
Generally no. Keep it focused on process steps and dates, such as legal review, security sign-off, and PO issuance, rather than commercial terms. Mixing pricing into the same document can slow down updates to the plan every time a number is still being negotiated.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
How to Build a Mutual Action Plan With Your Buyer
How to build a mutual action plan a buyer will use: when to introduce it, the columns it needs, a worked example, common mistakes and where to keep it.
Putting Mutual Action Plans Inside the CRM, Not a Doc
Why a mutual action plan in a shared Google Doc goes stale after the kickoff call, and what changes when it lives on the opportunity record instead.
How Enterprise Deal Cycles Are Actually Changing
What's genuinely changing enterprise deal velocity right now, from AI-assisted buying committees to procurement automation, and what hasn't changed at all.
Executive Sponsorship: When to Put Your CEO on a Late-Stage Deal
When bringing in your own CEO or a senior executive actually helps close an enterprise deal, and the specific situations where it backfires instead.
How to Multi-Thread an Enterprise Deal Before Your Champion Goes Quiet
How to map an enterprise buying committee and build relationships with more than one stakeholder, so a reorg or a quiet champion doesn't stall your deal.
Getting Sales-Ready for an Enterprise Procurement Review
What to have prepared before an enterprise procurement or security review reaches your deal, so it becomes a formality instead of a two-month delay.