What is a mutual action plan?
A mutual action plan (MAP) is a written agreement between a buying team and a selling team about how a purchase decision will get made. It turns vague intent ("we hope to decide this quarter") into named steps with owners and dates. The word that matters is mutual: the buyer helps write it, owns their own steps and can see the seller's.
Complex purchases involve far more than choosing a vendor. Gartner describes six "buying jobs" that B2B buyers work through and revisit: problem identification, solution exploration, requirements building, supplier selection, validation and consensus creation (Gartner, B2B buying journey, accessed 2026-10-15). A MAP gives the later jobs, especially validation and consensus creation, an owner and a date, so they do not happen by accident.
Sellers also use close plans and mutual success plans. They overlap with a MAP, but differ in who sees them and where they end, as the table below shows.
When should you introduce a mutual action plan?
- Discovery has confirmed a real problem, a budget path and a reason to act by a date (a compelling event).
- More than one team must sign off: finance, IT and security, procurement or legal.
- The buyer has a fixed date to hit, such as a contract renewal, a fiscal year-end or a launch.
- A deal has stalled and you need to agree, in writing, what happens next and who does it.
- Skip it for small, single-decision-maker purchases where a short email recap is enough.
Mutual action plan vs close plan vs mutual success plan
The names are often used interchangeably. The practical differences are who can see the document and when it ends.
| Plan | Who sees it | Ends at | Main purpose |
|---|---|---|---|
| Mutual action plan | Buyer and seller | Signature and go-live | Agree the steps, owners and dates to a decision |
| Close plan | Usually the seller's team only | Signature | Forecast and manage the deal internally |
| Mutual success plan | Buyer and seller (often customer success) | First value and beyond | Agree the outcomes the customer expects after purchase |
| Implementation project plan | Customer and delivery team | Go-live | Detailed delivery tasks once the contract is signed |
The mutual action plan template
Fill in the header first, then adjust the milestones to your sales process. Keep owners as named people, not teams. The "Done when" column is pre-filled with suggested exit criteria you can edit.
Plan header
| Field | What to write |
|---|---|
| Buyer / seller | [Buyer company] and [seller company] |
| Shared goal | [The business outcome the buyer wants, in their words] |
| Success criteria | [How the buyer will judge the evaluation a success] |
| Compelling event and target date | [Why this must happen by when, e.g. renewal or launch] / [date] |
| Buyer lead / seller lead | [Champion name and title] / [account executive name] |
| Last updated | [Date and who updated it] |
Plan milestones
| Phase | Milestone | Buyer owner | Seller owner | Target date | Status | Done when |
|---|---|---|---|---|---|---|
| 1. Align | Problem, goals and success criteria agreed | [Name] | [Name] | [Date] | Not started | Buyer confirms the summary in writing |
| 1. Align | Buying group identified | [Name] | [Name] | [Date] | Not started | Every role on the stakeholder map has a name or a plan to find one |
| 1. Align | Mutual action plan reviewed together | [Name] | [Name] | [Date] | Not started | Buyer has edited and accepted the plan |
| 2. Evaluate | Tailored demo or workshop | [Name] | [Name] | [Date] | Not started | Evaluators confirm their use cases were covered |
| 2. Evaluate | Technical validation or pilot | [Name] | [Name] | [Date] | Not started | Agreed pilot criteria met, or gaps documented |
| 2. Evaluate | Business case drafted with the champion | [Name] | [Name] | [Date] | Not started | Champion can present it without the seller |
| 3. Validate | Security and IT review | [Name] | [Name] | [Date] | Not started | Questionnaire answered and reviewer signs off |
| 3. Validate | Reference conversation | [Name] | [Name] | [Date] | Not started | Buyer has spoken to a comparable customer |
| 3. Validate | Executive sponsor meeting | [Name] | [Name] | [Date] | Not started | Economic buyer confirms priority and budget |
| 4. Decide | Commercial proposal | [Name] | [Name] | [Date] | Not started | Proposal accepted or redlined |
| 4. Decide | Procurement and vendor onboarding | [Name] | [Name] | [Date] | Not started | Vendor set up in the buyer's systems |
| 4. Decide | Legal review of contract and data terms | [Name] | [Name] | [Date] | Not started | Final terms agreed by both legal teams |
| 4. Decide | Signature | [Name] | [Name] | [Date] | Not started | Contract signed by the authorised signer |
| 5. Launch | Kickoff and onboarding plan | [Name] | [Name] | [Date] | Not started | Implementation owners and dates agreed |
| 5. Launch | First value review | [Name] | [Name] | [Date] | Not started | Buyer confirms progress against the shared goal |
Prefer a file? Both downloads are free and ungated.
Mutual action plan example
Example: fictional company
Here is the template filled in for an invented deal. Dates are written as weeks from the first meeting so the example stays readable.
Ferncastle Analytics (seller) is helping Marlow & Finch Logistics (buyer) replace spreadsheet-based sales forecasting before the buyer's new fiscal year.
Plan header
| Field | Example entry |
|---|---|
| Shared goal | Run the regional forecast call from one live view instead of five spreadsheets. |
| Success criteria | Two regional managers run a forecast call in the pilot without help from sales operations. |
| Compelling event | New fiscal year planning starts in week 12; the tool must be live before then. |
| Buyer lead / seller lead | Dana Okafor, Director of Revenue Operations / Sam Whitley, Account Executive |
Plan milestones (status at week 5)
| Phase | Milestone | Buyer owner | Seller owner | Target date | Status | Done when |
|---|---|---|---|---|---|---|
| 1. Align | Goals and success criteria agreed | Dana Okafor | Sam Whitley | Week 1 | Done | Dana confirmed the recap by email |
| 1. Align | Buying group identified | Dana Okafor | Sam Whitley | Week 2 | Done | Stakeholder map shared in the deal room |
| 2. Evaluate | Pilot with two regions | Luis Moreno, Regional Sales Manager | Priya Nair, Solutions Engineer | Weeks 3-5 | In progress | Two forecast calls run in Ferncastle |
| 2. Evaluate | Business case with the champion | Dana Okafor | Sam Whitley | Week 6 | Not started | Dana presents it to the CFO |
| 3. Validate | Security review | Grace Lindqvist, IT Security Manager | Priya Nair | Week 6 | At risk | Questionnaire signed off (waiting on SSO details) |
| 3. Validate | CFO meeting | Martin Hale, CFO | Ferncastle VP Sales | Week 7 | Not started | CFO confirms budget for next fiscal year |
| 4. Decide | Procurement and legal | Aisha Bello, Procurement Lead | Sam Whitley | Weeks 8-9 | Not started | Terms agreed and vendor onboarded |
| 4. Decide | Signature | Martin Hale | Sam Whitley | Week 10 | Not started | Contract signed |
| 5. Launch | Kickoff and rollout | Dana Okafor | Ferncastle onboarding lead | Week 11 | Not started | All regions trained before planning starts |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to create a mutual action plan
Draft it before you propose it
Arrive at the post-discovery call with a draft based on what the buyer told you. A blank template asks the buyer to do your job; a draft gives them something to correct.
Work backward from the buyer's date
Start with the compelling event and the go-live date, then place signature, legal, procurement and security review before it. If the dates do not fit, say so now rather than in week nine.
Name a buyer owner for every buyer step
Security, procurement and legal steps need a named person on the buyer's side. A milestone with no buyer owner is a risk you should raise with your champion.
Define "done" for each milestone
Write the exit criteria in plain language, such as "questionnaire signed off" rather than "security". It stops a milestone from being marked complete when it is only started.
Agree it live and let the buyer edit
Walk through the plan on a call, invite changes and confirm it in writing. A plan the buyer has changed is a plan the buyer believes in.
Keep one shared version and inspect it
Store the plan where both sides can see the latest version, update it after every meeting, and review slipped buyer milestones in your deal and forecast reviews.
Common mutual action plan mistakes
A seller plan with a mutual label
If only the seller has tasks, the buyer has not committed to anything. Every phase needs buyer-owned steps.
Introducing it too early
Before the buyer agrees there is a problem worth solving, a plan to close feels like pressure. Earn it in discovery first.
Stopping at signature
Buyers care about go-live and results, not your quarter. Ending the plan at first value makes it about their outcome.
Turning it into a project plan
Fifty rows of tasks will not be read. Keep the plan to the milestones that move the decision, roughly one screen.
Hiding legal and procurement until late
Contract, data-protection and vendor-onboarding steps often take longer than the evaluation. Put them on the plan from the first draft.
Emailing static copies
Attachments create competing versions. Keep one live plan in a shared space and link to it.
How Revspire runs mutual action plans in Digital Sales Rooms
A spreadsheet MAP works, but it lives apart from the content, people and conversations of the deal. In Revspire Digital Sales Rooms, the mutual action plan sits inside a branded room the buyer and seller share, with owners and due dates on each step, next to the proposal, security documents and other shared content.
The same room includes buying-committee stakeholder mapping and buyer-engagement analytics, so the seller can see how each stakeholder is engaging and spot milestones that depend on people who have gone quiet.
Mutual action plan template FAQs
What is the difference between a mutual action plan and a close plan?
A close plan is usually an internal seller document for managing and forecasting a deal, and it ends at signature. A mutual action plan is shared with the buyer, includes steps the buyer owns, and normally continues to go-live or first value.
When should you introduce a mutual action plan?
After discovery confirms a real problem, a reason to act by a date and more than one person involved in the decision. Introduce it as a way to save the buyer time ("let's make sure nothing surprises us before your deadline"), not as a closing tactic.
How long should a mutual action plan be?
Short enough to review on one screen. We suggest roughly 10 to 20 milestones grouped into phases. Detailed implementation tasks belong in a separate project plan after signature.
How do you get a buyer to agree to a mutual action plan?
Bring a draft built from their own words, anchor it to their deadline, ask them to correct it and let them own their steps. Champions often welcome a MAP because it helps them explain the process to their own leadership.
Do mutual action plans improve win rates?
We have not found an independent, methodology-backed study that measures this; most published figures come from vendors describing their own customers. The reliable way to know is to track it in your CRM: compare win rate and cycle length for deals with and without an agreed MAP.
Related templates and reading
- Free templateSales battlecard templateA one-page card per competitor: why you win, where they are strong, landmine questions, objection responses and pricing guardrails.
- Free templateStakeholder map templateEvery person in the buying group on one page, with buying role, influence, stance, priorities and a next action.
- Blog: making MAPs stickHow mutual action plans shorten the B2B sales cycle
- Blog: room layouts that hold a MAPDigital sales room templates and examples
- Blog: tools that host MAPsBest digital sales room software
Sources
- Gartner, The B2B buying journey (2026-10-15 (accessed))