Complex B2B deals do not stall because sellers are bad at selling. They stall because nobody wrote down who does what by when, on both sides.
A mutual action plan fixes that. It is a shared, co authored document between seller and buyer that lists every step required to get from current state to signature, with owners and dates on each step.
Simple idea. Enormous impact on deal velocity. This post covers what a MAP is, why it works, how to build one, and how to operate it inside Salesforce. Free template at the bottom.
What a mutual action plan is
A mutual action plan, sometimes called a mutual close plan or a joint success plan, is a living document co owned by the buyer and seller that captures:
Every step required to get from this moment to signed contract and successful go live.
The owner of each step, on both sides.
The target date for each step.
The status of each step.
Any dependencies between steps.
The key word is mutual. A close plan the seller writes in isolation and emails to the buyer is not a MAP. It is a wish list. A real MAP gets co authored in the same meeting where the buyer confirms they actually want to buy.
Why MAPs matter
Three specific reasons, backed by what the data consistently shows.
Deal velocity. Forrester and other research consistently find that deals with a mutual action plan close 20 to 30 percent faster than deals without. The mechanism is not mysterious. Written dates create accountability. Accountability removes the "I thought you were handling that" dead weeks.
Single threading risk. When the only person on the buyer side is your champion, the deal dies if they get promoted, fired, or pulled to a bigger priority. A MAP forces the champion to name the economic buyer, the legal reviewer, the IT security contact, and the procurement owner. The moment those names are on the plan, you are multi threaded whether you realized it or not.
Buyer accountability. The cleanest signal a buyer is serious is whether they will co author a MAP with dates. A buyer who will not commit to internal dates is telling you the deal is not real. Better to learn that in week four than in week sixteen.
When to build a MAP
Not every deal. MAPs are overhead. Use them where the overhead pays back.
Build a MAP when the deal is worth more than your team's median ACV, or involves more than three stakeholders on the buyer side, or has a cycle longer than 60 days, or has a hard go live date the buyer cares about.
Skip the MAP when the deal is transactional, when the buyer is a single champion buying on a credit card, or when the cycle is under 30 days and the next step is just a contract.
For deals in the MEDDPICC zone, MAPs are the single best operational artifact to enforce discipline around decision criteria, process, and paper. See our MEDDPICC sales methodology post for how the two fit together.
The anatomy of a good MAP
Five columns, minimum. Anything more is optional.
Step. The specific action that has to happen. "Legal reviews MSA" is a step. "Get through legal" is not.
Owner. The named human. "Procurement" is not an owner. "Sarah Chen, Senior Procurement Analyst" is.
Target date. The specific day the step needs to be complete. Not "week of June 3." Specific day.
Status. Not started, in progress, complete, blocked.
Dependency. If this step cannot start until another step finishes, name it.
Optional additions that help. A risk flag for high risk steps. A success criteria field for steps that are not just "done" but have to achieve a specific outcome. A notes field for context that would otherwise get lost.
A MAP with 15 rows is about right for a 200 thousand dollar deal. A MAP with 40 rows is about right for a 2 million dollar enterprise deal. A MAP with 80 rows is a Gantt chart pretending to be a MAP and the buyer will never read it.
How to co author a MAP with a buyer
The most common mistake is sellers writing the MAP alone and emailing it to the buyer asking for sign off. That turns the MAP into a document the buyer did not ask for and feels no ownership of.
The right move is to build it in a working session.
Set the meeting after a discovery call where the buyer has confirmed they want to move forward. Invite the champion and ideally one other stakeholder from the buyer side.
Open with the framing. "If everything goes right, what does success look like and when does it happen." Get a target go live date on the table.
Work backwards from the go live date. Every step required. Let the buyer name steps you would not know about, like internal security review cycles or board approval windows.
Assign owners as you go. The champion will volunteer for some steps. Ask who owns the others. You will learn names you did not know.
Set dates. Push for specificity. "We need this done in June" becomes "target June 18."
Close the meeting with the MAP as a shared artifact. Both sides have a copy. Both sides commit to updating it weekly.
A MAP built this way is not a sales tool. It is a project plan the buyer happens to have co authored with the seller. That distinction changes how the buyer treats it.
Running a MAP inside Salesforce
The MAP has to live somewhere. Most teams put it in Google Docs or a shared spreadsheet. That works until the rep forgets to update it or the buyer stops opening the link.
A better answer for Salesforce shops is to run the MAP on the Opportunity record. Each step is a Salesforce task tied to the opportunity. Owners are Salesforce users or contacts. Dates are due dates. Status is the standard task status field.
Benefits. The MAP rolls up into Salesforce reports automatically. Manager can see all active MAPs at once and flag the ones with slipping dates. Champions can be given guest access through Salesforce Experience Cloud so they update their own rows. The MAP becomes part of the forecast hygiene, not a side artifact.
For teams running this at scale, tying the MAP to the account plan means the same system tracks both the account strategy and the individual deal execution.
Common MAP anti patterns
The things that kill MAPs in practice.
Seller only MAP. The seller writes it alone. The buyer never looks at it. The MAP is decoration.
Vague ownership. "Legal" is an owner. It is also nobody. Name the human.
Date compression. The seller sets all dates based on what is needed to close by end of quarter rather than what is actually realistic. The buyer smells it and disengages.
No updates. The MAP is built once and never revisited. Within three weeks the dates are wrong and the steps are out of order. Useless.
Too long. The seller adds every possible step to look thorough. The MAP becomes unreadable. The buyer stops opening it.
Too short. The seller lists five steps for a sixteen step deal. The buyer knows the MAP is incomplete and loses trust in the seller's process literacy.
Half of MAPs in the wild have at least one of these problems. The fix is discipline, not software.
Example MAP: 500k enterprise SaaS deal
A simplified example for a 500 thousand dollar annual SaaS deal with a Q2 close target.
Week 1. Technical discovery call completed. Champion confirms economic buyer name. Both sides.
Week 2. Demo to economic buyer and two direct reports. Seller and champion co host.
Week 3. Security questionnaire received from buyer IT. Seller completes and returns.
Week 4. Reference call completed. Seller arranges, champion attends.
Week 5. Pricing proposal delivered. Seller and buyer review live in meeting.
Week 6. Procurement kickoff call. New contact named, added to MAP.
Weeks 7 to 9. Legal review. Redlines exchanged. Named legal contacts on both sides.
Week 10. Security review completed. Named security contact on buyer side.
Week 11. Final sign off from economic buyer. Contract routed for signature.
Week 12. Contract signed. Kickoff scheduled for go live two weeks later.
Twelve weeks. Twelve named steps. Named owners on both sides throughout. That is a working MAP.
Download the MAP template
A free Excel template with the five columns, conditional formatting for status, and a starter list of the twenty most common steps in an enterprise B2B deal. Customize for your product and your motion.
Download the mutual action plan template
Bring it into Salesforce with CRUSH
Prolifiq CRUSH lives on the Salesforce Account and Opportunity records. Mutual action plans run as structured objects tied to the deal, with tasks automatically syncing to Salesforce and shared views for your buyer's champion. No second login. No separate tool.
If your team is running MAPs in Google Docs today and the updates are slipping, see how CRUSH operationalizes them inside Salesforce.
FAQ
What is a mutual action plan? A mutual action plan is a shared document between buyer and seller that lists every step required to close and go live, with owners and target dates on both sides. The word "mutual" means it is co authored, not written by the seller alone.
What is the difference between a mutual action plan and a close plan? Often used interchangeably. Close plan tends to be seller only. Mutual action plan explicitly means co authored. The mutual version is stronger because buyer ownership drives accountability.
When should I introduce a MAP? After the buyer has confirmed intent to move forward, typically after technical discovery and before pricing. Introducing a MAP too early feels presumptuous. Introducing it too late loses the velocity benefit.
Where should a MAP live? For Salesforce teams, on the Opportunity record. The MAP steps become Salesforce tasks so they roll up into existing reporting and forecasting workflows. Google Docs works for one off deals but does not scale.
How long should a MAP be? Roughly one row per week of expected cycle, plus one row per additional stakeholder. A 60 day deal with five stakeholders is about 10 to 15 rows. Fewer and you are missing steps. More and the buyer stops reading.
