A mutual action plan is a shared document that maps every step from where a deal is now to a signed contract and a successful kickoff. It is the artifact that keeps a buyer and a seller honest about what has to happen, when, and who owns it.
This post walks through a 13 milestone MAP template, how to fill in each row for a real deal, the common mistakes that kill MAPs, and where the template ends and the actual buyer relationship begins. The Excel template is free to download.
What a MAP is, briefly
A mutual action plan is a joint document. The seller drafts it. The buyer agrees to it. Both sides own milestones.
It is not a project plan. A project plan happens after signature. A MAP happens before signature, and it covers both the buying process and the early implementation milestones.
The point of a MAP is not the document. The point is the conversation that builds the document. When a buyer agrees to the steps, you learn whether the deal is real. When the buyer pushes back on a milestone, you learn what is actually getting in the way.
For the conceptual frame on what a MAP is and why it works, read Mutual Action Plan. This post is about the template itself.
The 13 milestone template at a glance
The template walks both teams from late stage discovery through to a successful first 30 days post signature.
- Business case alignment
- Stakeholder map
- Technical evaluation kickoff
- Security review
- Legal review kickoff
- Procurement review
- Pricing and commercial alignment
- Final proposal delivered
- Internal approval
- Contract redline cycle
- Signature
- Implementation kickoff
- First value milestone
Each milestone has the same fields: owner on the buyer side, owner on the seller side, target date, status, dependencies, and notes.
The template is opinionated. You can cut milestones for simpler deals. You should rarely add milestones, because more milestones usually means less signal.
Walking through the template
Here is what good looks like for each milestone.
1. Business case alignment
Owner buyer. The economic buyer or champion. Owner seller. The AE. What it looks like done. A one page business case both sides agree on. Problem, current state, future state, success metric, expected ROI, and the cost of doing nothing. Either party can present it without changing it.
If you cannot get the buyer to align on a business case, you do not have a deal. You have an opportunity that will stall.
2. Stakeholder map
Owner buyer. Champion. Owner seller. AE plus solutions engineer. What it looks like done. A documented buying committee. Names, roles, what each cares about, level of support, and known concerns. Updated through the cycle.
This is where the MAP starts to expose the real shape of the deal. If your stakeholder map only has two names, you are missing four.
3. Technical evaluation kickoff
Owner buyer. Technical lead. Owner seller. Solutions engineer. What it looks like done. Scope of evaluation, success criteria, target completion date, and the people involved. Not a free for all. A scoped exercise.
4. Security review
Owner buyer. Security or IT. Owner seller. Customer engineer or pre sales. What it looks like done. Security questionnaire returned, SOC 2 or relevant docs shared, any required clarifying call held. A clear yes or a clear list of objections.
5. Legal review kickoff
Owner buyer. Legal counsel. Owner seller. AE plus deal desk. What it looks like done. Standard MSA or relevant agreement shared. Initial redlines returned. Both legal teams have made contact.
6. Procurement review
Owner buyer. Procurement. Owner seller. AE plus deal desk. What it looks like done. Pricing rationale provided. Comparable spend benchmarks discussed if asked. Procurement is on a path to approval, not blocking.
7. Pricing and commercial alignment
Owner buyer. Champion plus economic buyer. Owner seller. AE. What it looks like done. Pricing structure agreed. Term length agreed. Any discounts or incentives traded against specific concessions, not given freely.
8. Final proposal delivered
Owner buyer. Champion. Owner seller. AE. What it looks like done. Final order form or proposal sent with all commercial terms. Acknowledged by champion and economic buyer.
9. Internal approval
Owner buyer. Economic buyer. Owner seller. AE. What it looks like done. Whatever internal approval the buyer needs. Steerco vote. Finance signoff. CIO approval. Date confirmed and tracked.
10. Contract redline cycle
Owner buyer. Legal. Owner seller. Deal desk. What it looks like done. Final agreed contract language. No open redlines. Both sides ready to sign.
11. Signature
Owner buyer. Signatory. Owner seller. AE. What it looks like done. Counter signed contract returned. Confirmed by both sides.
12. Implementation kickoff
Owner buyer. Project sponsor. Owner seller. Customer success or onboarding. What it looks like done. Kickoff call scheduled within an agreed window. Implementation team named on both sides. Project plan handed off.
13. First value milestone
Owner buyer. Project sponsor. Owner seller. Customer success. What it looks like done. A specific first value moment defined and dated. First report run. First user trained. First integration live. Whatever a 30 day proof of value looks like for your product.
This last milestone is what separates a sales close plan from a real MAP. The deal is not closed at signature. The deal is closed when the customer gets to the first value milestone.
How to actually fill it in
The first version of the MAP is drafted by the seller. You do not send it to the buyer cold. You walk through it on a call with your champion.
Three things to expect from that call.
The dates will move. That is fine. The structure is what matters.
Some milestones will be unknown. The buyer might not know which security review process applies. That is information. Capture it as a follow up.
Some milestones will be skipped. A small mid market deal might not need a procurement review. Cut what does not apply. Do not pad.
After the call, send the updated MAP to your champion. Ask them to circulate to the broader buying committee. The MAP becomes a shared artifact and a recurring reference point in every working session through the rest of the cycle.
Common mistakes that kill MAPs
A few patterns to avoid.
Sending a MAP without a champion. A MAP needs a buyer side owner. Without one it is just a seller checklist that gets ignored.
Padding with seller side tasks. A MAP is for joint milestones. "Send updated proposal" is a seller task, not a milestone. It does not belong on the MAP.
Treating the MAP as a presentation. The MAP is a working document. It should be ugly, current, and usable. Not a polished slide.
Updating only at the start. The MAP only works if it is updated weekly. If the dates do not move, you are not actually using it.
Storing it only in the seller's drive. The MAP belongs somewhere both buyer and seller can see and edit. A buyer who cannot see the current MAP cannot trust the process.
Where the MAP belongs
A MAP in a shared Excel file works for early adopters. It does not scale.
For a sales team that runs MAPs on every deal, the MAP belongs in the same system as the opportunity record. That is the only way it gets updated, audited, and learned from across deals.
A working MAP system has three properties. It lives next to the deal data. It is shareable with the buyer in a clean view. It rolls up across deals so leaders can see which MAPs are stale, which milestones are most often missed, and where deals tend to slip.
That is the gap between an Excel template and a real MAP practice.
Download the template
Get the free Excel mutual action plan template with all 13 milestones, owner fields, status tracking, and a buyer ready summary view.
Download the mutual action plan template
Related reading
Bring this into Salesforce with ACE
The template gets you started. The MAP earns its keep when it lives where the buyer can see it and the seller can keep it current. That requires more than a spreadsheet.
ACE is the document and content layer for sales inside Salesforce. MAPs, proposals, security packets, and onboarding plans live in one place, are easy to share with the buyer, and stay tied to the opportunity record. The MAP becomes the working document of the deal, not a stale file.
