A mutual action plan (MAP) is a shared document that defines the specific steps, decision-makers, timelines, and success criteria that both the seller and buyer need to complete for a deal to close. It is sometimes called a mutual success plan, a joint execution plan, or a close plan. The critical difference between a MAP and a seller-only close plan is the word "mutual": the buyer champion co-creates and co-owns the MAP, which means they are committing to the steps and timeline, not just receiving them from the seller. A MAP that the buyer helped build is far more likely to be followed than a plan the seller emailed over without discussion.
When to introduce a mutual action plan
Introduce a MAP after you have confirmed two things: the prospect has identified a genuine problem that your product solves, and there is a real project with a real decision-making process (not a casual evaluation with no champion and no budget). Introducing a MAP too early (before confirming budget or sponsor) wastes the effort; waiting too long misses the opportunity to shape the evaluation process. Typically a MAP is introduced after the initial demo and first expression of interest, when the prospect says "this looks relevant -- what are the next steps?" That question is the natural opening for a MAP conversation.
What a mutual action plan includes
- Goal and success criteria: what the buyer is trying to achieve and how they will evaluate whether they achieved it -- agreed in the buyer's language, not the seller's
- Key milestones: the major decision points and stages in the evaluation (security review, technical POC, legal review, executive sign-off)
- Action items: each specific task with a clear owner (buyer or seller), due date, and dependency on other items
- Stakeholders: all people involved in the decision, their role in the process, and their primary concern
- Timeline: the target decision date, working backward from any hard deadline (contract renewal date, budget cycle, launch date)
- Dependencies and risks: items that could delay the timeline and how they will be managed
How to build a MAP with the buyer
Do not send a pre-built MAP and ask the buyer to review it -- this is a seller plan, not a mutual plan. Instead, schedule a 30-minute session with the buyer champion specifically to build the MAP together. Open with the buyer's goal and decision date ("we want to make a decision by September -- what needs to happen between now and then?") and fill in the plan together. The buyer's version of the steps will often reveal requirements the seller did not know about (a security review step, a procurement process, a technical review board) and will generate buyer buy-in that a seller-authored plan cannot.
Using the MAP to maintain momentum
A MAP is most valuable as a live tracking tool, not a one-time document. Reference it in every follow-up communication ("based on our MAP, the next step is X by [date] -- are you on track?"). When a step slips, use the MAP to have a direct conversation about whether the overall timeline is still realistic. A MAP that is not being followed is a signal that the deal has stalled or the champion has lost internal support -- it surfaces problems early when there is still time to address them.
Frequently asked questions
- What is a mutual action plan in B2B sales?
- A mutual action plan (MAP) in B2B sales is a shared document co-created by the seller and buyer champion that defines the specific steps, owners, timelines, and success criteria for completing a buying evaluation and reaching a decision. It is also called a mutual success plan, joint execution plan, or close plan. The "mutual" element is what makes it work: a MAP the buyer helped build has buyer buy-in; a plan the seller wrote and emailed over is a seller close plan, not a mutual plan. MAPs are most commonly used in complex B2B enterprise deals with long sales cycles and multiple stakeholders, where the biggest risk is that the deal loses momentum or stalls because neither side has a shared picture of what needs to happen next. A MAP addresses that risk by making the evaluation process explicit, shared, and tracked.
- How is a mutual action plan different from a close plan?
- A close plan is a seller-side document that maps out what the seller needs to do to close a deal by a target date. A mutual action plan (MAP) is a shared document co-created with the buyer that maps out what both the seller AND buyer need to do to complete the evaluation and reach a decision. The practical difference: a close plan is an internal sales tool; a MAP is a collaborative contract between buyer and seller. A close plan can be built without buyer input; a MAP requires a conversation with the buyer champion. A close plan tracks seller milestones; a MAP tracks both seller actions (completing a security questionnaire, providing references) and buyer actions (scheduling a technical review, getting IT approval, completing procurement). MAPs are more powerful for enterprise deals because they create shared accountability and explicit buyer commitment to the timeline.
- When should you introduce a mutual action plan in B2B sales?
- Introduce a mutual action plan (MAP) in B2B sales after you have confirmed: (1) there is a genuine problem your product solves (not just curiosity); (2) there is a real project with a real sponsor and budget (or clear path to budget); (3) the buyer has expressed interest in moving forward ("what are the next steps?"). The right moment is typically after the initial demo when the prospect shows genuine interest, or after a discovery call confirms strong problem-solution fit. Introducing a MAP too early (before confirmed sponsorship and budget) wastes effort -- the deal is not serious enough for the buyer to commit to a joint plan. Waiting too long risks the evaluation moving forward without your influence on the process design. A useful test: if the buyer is willing to co-create a MAP with you, the deal is real. If they resist ("we'll just evaluate and get back to you"), you are dealing with a non-committed evaluator.