A 320k deal slipped on me last quarter. Three weeks before the contract date, the champion went dark. The CFO had a "few more questions". Legal pulled in privacy. Then procurement showed up with a vendor questionnaire we had not seen, and the close pushed two months.
We had a mutual action plan on that deal. I had built it myself. A nice PDF with milestones, owners, and target dates. The buyer thanked me for it, told me it was helpful, and then never opened it again.
That is the problem with most mutual action plans in B2B sales. They look like project plans. They get treated like marketing collateral. And when the deal stalls, nobody on the buyer side feels accountable to the document.
This guide is what I have learned about MAPs after running them on 200 plus B2B deals across HubSpot and Salesforce orgs. I will cover what a working MAP looks like, when to introduce it, how to wire it into HubSpot, and the specific reasons most of them fail.
What a mutual action plan actually is
A mutual action plan, sometimes called a MAP or a close plan or a joint execution plan, is a shared document between seller and buyer that maps every step from the current sales stage to a signed contract. It lists what needs to happen, who owns each step, and when each step is due.
That is the textbook answer. It misses the part that matters.
A working MAP is a commitment device. It is the only artifact in the B2B sales cycle where the buyer signs up, in writing, to specific actions on specific dates. It moves the conversation from "we are interested" to "you will get us a security review by November 14, and I will deliver the signed MSA by November 21". Without that explicit commitment, a MAP is just a checklist that lives in your CRM.
According to Gartner's 2023 B2B buying study, the average enterprise software deal now has 11 buyer-side stakeholders. A 2024 Forrester report found that 67% of B2B buyers say the purchase process is harder than three years ago. The MAP is the only seller-controlled tool that gives the buyer a way to coordinate their own internal mess.
A MAP is a commitment device, not a project plan.
If the buyer has not agreed to specific dates and owners in writing, you do not have a MAP. You have a wishlist with deadlines.
Why most mutual action plans fail
I have audited dozens of MAPs across HubSpot deals. The same failure patterns show up.
The MAP is one-sided
The seller fills out every row. Every owner is "AE" or "Customer Success". The buyer never edits a thing. This is the most common pattern, and it is the worst. If the buyer has not put their name next to a task, they are not on the hook for it.
It reads like a Gantt chart
Twenty rows, eight columns, three swimlanes, color codes. Buyers do not want to read your project plan. They want to know the next two things that need to happen and what each will cost them in time.
No business case at the top
The MAP lists tasks but never restates why the buyer is doing this. When the deal hits friction at week six, the champion has no anchor to remind themselves and their CFO what problem they were solving. The deal evaporates because the original pain is no longer top of mind.
No procurement and legal in the plan
In my data, 70% of slipped Series B and enterprise deals slipped on procurement or legal steps that were not in the MAP. The seller built a plan that ended at "contract signed" and forgot that "contract signed" has 12 substeps the legal team owns.
No escalation path
When a deadline slips, the MAP does not say what happens. Does the AE escalate to the VP? Does the CEO call the CFO? Without an escalation rule, slippage compounds.
The 22% win rate number is from a 2024 study by RAIN Group on complex B2B deals. My own number across audited HubSpot pipelines is closer to 18% win rate lift, but only on deals where the MAP was co-edited by the buyer in the first four weeks. Static PDFs showed zero lift.
The structure that actually works
After a lot of trial, here is the structure I now use. It fits on one screen. It has seven sections. Every working MAP I have run uses some version of this.
1. Business case
Two to four sentences. What problem is the buyer solving. What is the cost of doing nothing. What outcome are they buying. This sits at the top of the document and gets read first in every internal meeting on the buyer side. If the champion has to defend the project to the CFO, this is the language they will use.
I write this with the buyer in week one. We literally co-author it on a call. The act of writing it together is more important than the words.
2. Success criteria
Three to five measurable outcomes the buyer expects in the first 90 days post-signature. This anchors success metrics before the deal closes, so when the customer success team picks up the account, they are not guessing.
3. Decision criteria
What the buyer is using to choose between vendors. Often a vendor comparison sheet they built internally. If you cannot get this in writing, you do not understand the deal.
4. Decision process
The internal steps the buyer has to take. Security review, procurement, legal redlines, board approval if it applies, budget reallocation if the budget did not exist. This is where most MAPs break. Every step on the buyer side, with the buyer-side owner and the date, lives here.
5. Implementation plan
What happens after signature. Kickoff, data migration, training, go-live. This is the part the buyer side cares about most, because they are paying for the outcome, not the contract.
6. Risk register
Three to five things that could kill the deal. Procurement slowness, the CFO budget freeze, a competing internal project. Naming the risk on the MAP makes it easier to handle when it shows up.
7. Key dates and owners
The actual schedule. Every row has a date and an owner. Half the owners are on the buyer side. If they are not, you do not have a MAP.
When to introduce the MAP
This is where I see most AEs get it wrong. They either drop the MAP in stage one, before the buyer is qualified, or they wait until stage four when the deal is already supposed to be predictable.
The right moment is right after the second discovery call, when you have a clear champion, a verified pain, and you are about to scope or demo. At that point the MAP becomes the structure for the next four to eight weeks.
If you introduce it earlier, the buyer treats it as a sales tactic. If you introduce it later, you are trying to plan a deal that is already running on momentum.
A good intro line: "To make sure we both stay on track for your November 21 board meeting, I want to map out the steps you and I will both need to hit. Can we spend 15 minutes putting together a plan we both edit?" That framing makes the MAP feel like a service the seller is offering to keep the deal on schedule, not a control mechanism.
The tooling question
There are three options. Dedicated tools, your CRM, or a generic doc.
Dedicated MAP tools
Accord, Recapped, DealHub, Aligned, and a handful of others. They give you templates, version control, buyer-side notifications, and analytics on what the buyer is looking at. Accord and Aligned are the strongest right now for SMB and mid-market. Pricing runs from 50 to 150 per seat per month.
These tools are great if you are running 50 plus open deals across multiple reps and need consistency. They are overkill if you have five AEs and 30 open opps.
HubSpot deal property checklist plus Notion
This is what I use for most of my Series A and Series B clients. A custom HubSpot deal property called "MAP link" pointing to a Notion page, a Google Doc, or a Coda doc. The doc has the seven sections I listed above. HubSpot fires automated reminders when MAP dates slip past today.
Cheap, flexible, and it works. The downside is no buyer-side analytics. You do not know if the champion opened it yesterday or three weeks ago.
Generic shared doc
A Google Doc with a basic template. Fine for teams under 1M ARR. Once you are past that, the lack of structure starts to hurt new rep onboarding.
Wiring the MAP into HubSpot
If you are running HubSpot Sales Hub Pro or Enterprise, here is the setup I recommend. It takes a couple of hours and pays back inside a quarter.
Custom deal properties
Add four properties to the deal object:
- MAP link, a single line text field for the Notion or Google Doc URL
- MAP status, a dropdown with values Draft, Active, Stalled, Closed
- MAP target close date, a date picker the buyer agrees to
- MAP last buyer activity, a date that gets updated when the buyer edits the doc (manual or via Zapier if you use Notion)
Required field by stage
Use HubSpot's required properties feature to block deals from advancing past stage three without a MAP link and an active status. This forces reps to actually build the doc instead of advancing on hope.
Pipeline view
Add MAP status as a column on your kanban view. Now you can see at a glance which open deals are running an active MAP and which are limping along without one.
Automated reminders
Build a HubSpot workflow that fires when the MAP target close date is less than 14 days away and the MAP status is not Active. The workflow assigns a task to the AE with the deal name and a link to the doc. This is the single highest-impact automation in this whole setup.
Reporting
A weekly dashboard with two reports. Win rate by MAP status. Average days to close by MAP status. Inside a quarter you will have data on whether the MAP is moving your numbers, or just looking pretty.
The KPIs that tell you it is working
Vanity metrics around MAPs are easy to game. Number of MAPs created, percentage of deals with a MAP, that kind of thing. The metrics that matter are harder to fake.
Buyer edit rate
What percentage of MAPs got at least one edit from the buyer side in the first four weeks. Target above 60%. Below 40% means your reps are creating MAPs as a checkbox, not as a real artifact.
Win rate delta
Win rate on deals with an active MAP versus deals without. Run this segmented by deal size. My benchmark from audits is a 15% to 22% win rate lift on deals above 25k ACV. Below 25k, the lift is smaller because deals are simpler and a MAP is overhead.
Slippage variance
Average days between MAP target close date and actual close date. If this is more than 21 days, your MAPs are not being maintained.
Stage-to-stage conversion
Conversion rate from late discovery to proposal. A working MAP lifts this number because it surfaces buyer-side blockers earlier.
Minimum buyer edit rate that signals a MAP is actually being used. Below this, your reps are doing checkbox compliance and the deal data will not move.
Where MAPs go wrong even when you do this right
Two failure modes I keep seeing on teams that have done the setup correctly.
The MAP becomes the deal review
Some sales leaders start using the MAP as the deal review document. So now the AE is updating the MAP for the buyer and the VP at the same time. The buyer-facing language gets stripped out, the internal commentary creeps in, and the document stops being usable by the customer.
Keep your internal deal review separate. The MAP is the buyer-shared artifact. Internal deal review notes live on the HubSpot deal record or in your forecast tool.
Champion change destroys it
The original champion leaves, gets a new role, or just goes quiet. The new contact has never seen the MAP. If you have not built a habit of getting the MAP in front of multiple stakeholders by week three, it dies with the champion.
My fix: explicit MAP review meetings with the buyer's internal team by week three. Even if it is a 15-minute call. The MAP gets mentioned by name in front of three people on their side, which makes it survive a champion change.
It becomes a contract
In legalese-heavy industries, buyers sometimes get nervous that the MAP creates obligation. A simple disclaimer at the top of the doc handles this: "This document is a working plan to coordinate the procurement process. It is not a contract and creates no legal obligation between the parties."
I add this to every MAP I build. No buyer has ever pushed back.
The MAP and the renewal motion
One more thing nobody talks about. The MAP from the first sale is the best artifact you have for the customer success team during onboarding and renewal.
The success criteria you co-wrote in week two become the QBR talk track in month nine. The business case becomes the renewal pitch. If your sales-to-CS handoff is broken, the MAP is often the missing piece.
In my B2B SaaS renewal motion playbook I cover how to use the original MAP as the foundation for the renewal conversation. The work the AE did before signature pays compounding returns through year two and three of the customer relationship.
This is also why the MAP needs to live somewhere the CS team can find it post-close. A Notion page they can read works. A PDF buried in an email thread does not. If you are doing CRM migration work, the MAP storage location is one of the things to standardize. See my CRM migration playbook for the field mapping side of this.
What I would do if I were starting from zero
If I were taking over a Series A or Series B sales team tomorrow with no MAP discipline in place, here is the 30-day plan.
Week one: pick a template. Either Accord, Aligned, or a Notion template I would write myself. Train all AEs on the seven-section structure.
Week two: add the four custom properties to HubSpot. Make MAP link and MAP status required to advance past stage three. Run an audit of all open deals over 25k and tag which have a real MAP versus which do not.
Week three: every open deal without a MAP gets one. The AE has a one-hour block to co-write it with the champion. If the champion will not get on a call to co-write, that is a leading indicator the deal is colder than the rep thinks.
Week four: build the reporting. Win rate by MAP status. Average slippage. Buyer edit rate. Review weekly with the sales leader.
By day 60, you will know which reps are using the MAP as a tool versus which are filling it out for compliance. By day 90, the win rate delta data will tell you whether your team needed this or not. In my experience, every team I have run this on did.
Want help wiring this into your HubSpot?
We build MAP workflows, deal stage requirements, and forecast dashboards into HubSpot for B2B teams. Book a 30-minute audit and we will show you what we would fix first.
Book an audit →FAQ
What is the difference between a mutual action plan and a close plan?
In practice, nothing. Different vendors prefer different names. Salesforce-aligned tools often say "close plan". HubSpot-aligned tools say "mutual action plan" or "MAP". The structure and intent are the same. Pick the name your buyer will react to best.
When in the sales cycle should I introduce the MAP?
Right after the second discovery call, when you have a clear champion and verified pain. Earlier feels like a sales tactic. Later means the deal is already running on momentum and the MAP becomes paperwork.
Do I need a tool like Accord or can I use a Google Doc?
For under five AEs and sub-1M ARR, a structured Google Doc or Notion page works fine. For larger teams or 50 plus open deals at any time, dedicated tools like Accord or Aligned pay back through buyer-side analytics, version control, and notifications.
What if the buyer refuses to co-edit the MAP?
That is a qualification signal. A real champion will spend 30 minutes co-writing the document because it helps them coordinate their own internal mess. If they will not, you do not have a champion, you have a contact. Forecast the deal accordingly.
How do I avoid the MAP looking like a control mechanism?
Frame it as a service to the buyer. "I want to map out the steps so we both stay on track for your November 21 board meeting." Have the buyer write at least three sections themselves, including the business case. Add a one-line disclaimer that it is a working plan, not a contract. The buyer will treat it as a tool, not a tactic.