Mutual Action Plan
Mutual Action Plan (MAP) is a jointly built timeline between seller and buyer that lists every step, owner, and date required to reach a purchase decision.
Also known as: close plan, mutual close plan, joint execution plan
Mutual Action Plan (MAP), sometimes called a close plan, is a jointly built timeline that maps every milestone from current stage to signed contract, with named owners and target dates on both the seller and buyer sides. The artifact itself is less important than the act of building it together, which forces hidden complexity to the surface and turns a deal from an act of faith into a project with a critical path.
What Mutual Action Plan Means
A Mutual Action Plan is a shared document that lists the steps required to reach a purchase decision on both sides: discovery completions, technical evaluations, business case build, legal review, procurement, security review, and final approval. Each step has an owner, a date, and a dependency. It is similar in structure to a project plan but narrower in scope: it covers only the steps needed to reach a purchase decision, not the implementation work that follows the signed contract. The implementation project plan is a separate artifact built by customer success or services, usually starting from the close plan’s end date.
How Mutual Action Plan Works
A Mutual Action Plan works by making the buying process explicit and collaborative, so neither side is guessing about next steps. It also exposes hidden stakeholders, approval steps, and procurement gates early, which improves forecast accuracy and gives marketing-supplied enablement content a clear place in the journey. Most reps build the plan after the second or third substantive meeting, when both sides agree there is something to plan. The plan should be a shared document the buyer can edit, comment on, or push back on. Google Docs, shared spaces in deal-room tools, or even a co-edited PDF outperform a seller-controlled spreadsheet for adoption. Marketing supports the plan by providing the proof points, ROI tools, and stakeholder-specific content that map to each milestone.
Common Pitfalls and Misconceptions
A frequent mistake is treating the Mutual Action Plan as a seller-only checklist. Its value comes from genuine buyer agreement; if the buyer never edits or commits to it, it is just a wish list with the seller’s logo on it. The strongest indicator that a plan is working is that the buyer adds steps the seller had not anticipated. Another pitfall is introducing the plan too early or too late: too early can feel presumptuous before the buyer is committed, while too late means key steps are already rushed. The right moment is usually after the second or third substantive meeting, when both sides agree there is something to plan.
Mutual Action Plan in Practice
The practitioner-level discipline is using the Mutual Action Plan as a forecasting instrument, not just a project plan. When a buyer-side milestone slips, the forecast adjusts in the same conversation, not weeks later when sales realizes the deal will not close on time. Mature teams build the close plan into their CRM as discrete deal milestones and tie forecast probability to milestone completion. The plan becomes a forecast input, not a slide. Reluctance from the buyer is also a useful signal: soft resistance, will look at it later, is usually a no in slow motion, and hard refusal is information worth acting on by adjusting the forecast or re-qualifying the deal.
Common questions.
When should a mutual action plan be created?
How does a mutual action plan improve forecasting?
Is a mutual action plan the same as a project plan?
How does marketing support a mutual action plan?
What if the buyer refuses to engage with the plan?
What goes in a mutual action plan?
Should the plan be a shared document or seller-owned?
Related Terms
More from Sales Alignment.
Let’s Talk
Let’s talk about what your next quarter could look like.
Tell us what you’re working on. A senior practitioner reads it, not an SDR queue, and replies, usually within one business day.
- Reviewed personally, not routed through a queue.
- A conversation about what you’re actually working on, not a generic pitch.
- No pressure, just a chance to talk it through.