Key takeaways
- A mutual action plan (MAP) is the documented version of the buying process: the exact steps to signature, who owns each one, and when it happens.
- Build it as milestones with next-step actions under each one. The milestone is the outcome; the actions are what make it real.
- A MAP has to cover both lanes: the business decision and the legal and commercial execution. Stopping at 'proposal sent' means you are still forecasting intent.
- Build it live with the buyer, working backwards from the compelling event, share it right away, and review progress weekly. Progress is a completed action, not a stage change.
On this page
What Is a Mutual Action Plan?Why a MAP Matters: The Two LanesWhat Goes in a Mutual Action PlanHow to Build a Mutual Action Plan With Your BuyerWhen to Introduce a MAPThe Most Common MAP MistakesMAPs and Your ForecastColor Code Your Buying ProcessThe Bottom LineHere’s a pattern I’ve watched kill more forecasts than any competitor:
- A champion says, “We’re ready.”
- The seller forecasts the deal: “They said they were ready.”
- The deal disappears into a black box of steps the seller never mapped.
Security review. Legal. Vendor onboarding. Procurement. Redlines. A signer who takes a month-long sabbatical right before signature. (Yes, that happened to me.)
The mistake isn’t optimism. Sellers forecast business intent, not operational reality.
Businesses don’t buy when they feel excited. They buy when their internal process is complete.
The tool that closes that gap is the mutual action plan.
What Is a Mutual Action Plan?
A mutual action plan (MAP) is the documented version of the buying process.
It turns “we’re ready” into “here are the exact steps to signature, who owns each one, and when it happens.”
A good MAP has one job: make the path visible, so it can be managed.
It’s called mutual for a reason. It’s built with the buyer, agreed by the buyer, and referenced by the buyer. If it isn’t co-created, it’s just your internal notes.
This is the point in a deal where I shift from seller to project manager. Most of the selling is done. Now we’re managing an agreed-upon project together, and the project is getting the deal signed and implemented on an agreed timeline to achieve agreed business results.
Why a MAP Matters: The Two Lanes
The buying process has two lanes, and most sellers only track one.
1. The business buying process: the internal sequence that leads to the business “yes.”
- Who’s involved
- What steps must occur
- What criteria will be used
- What priorities this attaches to
- What event forces timing
- Who signs off on the case for change
- Any budget or commercial considerations
2. The legal and commercial execution process: the path that turns a yes into a signed agreement.
- Security review
- Legal review
- Vendor onboarding forms
- InfoSec, DPA, MSA and SOW
- Procurement negotiation
- Payment terms
- Redlines
- PO creation
- Signature authority
If you don’t know the business process, you can’t effectively get to “yes.”
If you only know the business process, you’ll drift in procurement.
“Ready to go” means the business likes the idea. “Ready to sign” means every internal step is mapped, owned and in motion.
That gap is where forecast accuracy goes to die. By making the path from business “yes” to signature visible, documented and managed, I’ve helped organizations move forecast accuracy from roughly 50 percent to 90 percent quickly. Not by pressuring buyers. By mapping the path.
The deal that taught me this
The largest deal of my career was thirty million dollars. Years of work. The business had said yes. We were in contracting.
Then the redline came back requiring us to accept unlimited liability.
We escalated through every layer of both exec teams. We proposed caps and alternative structures. They wouldn’t move, and our executive team made the call they had to make. I had to close-lose a deal that was already in commit, with C-level eyes on it.
The requirement was a dealbreaker no matter when I found it. But when paper went out, I stopped asking hard questions and started celebrating. Two questions would have kept it out of commit:
- “Before we start the redline process, are there any terms in your standard agreement that other vendors have pushed back on or found unusual?”
- “What’s caused your legal reviews to run longer than expected in the past?”
Paper opens a new lane with its own requirements, its own timeline and its own potential dealbreakers. That lane deserves the same discipline as everything before it. A MAP forces it.
What Goes in a Mutual Action Plan
Build your MAP as a series of milestones, with next-step actions under each milestone.
The milestone is the outcome. The next-step actions are the prerequisites that make the outcome real.
This is where most deals drift: sellers track milestones in their head, but the actions that unlock them never get written down, owned or dated.
Every line needs four things:
- The action
- An owner (theirs or yours)
- A date
- A status
Here’s the structure I use in the DealDoc MAP template:
The header: both teams, named.
| Your company | Buyer company | ||
|---|---|---|---|
| Account Executive | Name and email | Champion | Name and email |
| Sales Engineer | Name and email | Executive Sponsor | Name and email |
| Customer Success | Name and email | Project Lead | Name and email |
| Executive Sponsor | Name and email | Technical Lead | Name and email |
The plan: milestones and the actions under them.
| Due date | Next step | Type | Stakeholders | Status | Notes |
|---|---|---|---|---|---|
| Solution and buying process alignment | |||||
| Solution criteria alignment | Meeting | Complete | |||
| Buying process alignment | Meeting | Scheduled | |||
| Approval: goals, requirements and evaluation | Approval | In progress | |||
| Pilot planning | Meeting | Not scheduled | |||
| POC, technical validation and stakeholder review | |||||
| POC kick-off | Kick-off | ||||
| Technical checkpoint | Meeting | ||||
| Stakeholder solution alignment | Meeting | ||||
| InfoSec review | Doc review | ||||
| End POC | Meeting | ||||
| Results and recommendations | Meeting | ||||
| Business case | |||||
| Business case review | Meeting | Champion | |||
| Buying team business validation review | Meeting | Buying team | |||
| Executive business validation review | Meeting | Executive Sponsor | |||
| Contracting | |||||
| Contracting kickoff | Meeting | ||||
| Redlines and legal | Task | ||||
| Redline review 1 | Meeting | ||||
| Redline review 2 | Task | ||||
| Final negotiation | Meeting | ||||
| Execution (signature) | Meeting | ||||
| Implementation and onboarding | |||||
| Kick-off call | Meeting | ||||
| Onboarding step 1 | Task | ||||
| Onboarding step 2 | Task |
Notice two things.
First, it runs past signature into implementation. The buyer isn’t buying a contract. They’re buying an outcome on a date. Tie the plan to go-live and the buyer has a reason to care about every row above it.
Second, the business case has three reviews, in order: your Champion, then the buying team, then the Executive Sponsor. That’s how the story travels to the top instead of dying in the middle.
Adjust the milestones to fit your deal. Smaller deals need fewer rows. The rule that doesn’t change: both lanes, every step, an owner and a date.
Get the free Mutual Action Plan template (a Google Sheet).
How to Build a Mutual Action Plan With Your Buyer
1. Start from the date that matters and work backwards
Start with the target date, usually the compelling event or go-live date. Then map every required step to get there, business steps and paper steps, with owners and dates.
Here’s roughly how that sounds on a call:
“It sounds like you want to be live in four months. To make that date real, can we work backwards for two minutes? Implementation is usually about a month. Contracting is often a few weeks. Security and vendor onboarding can add another week or two. So we’re probably staring at six to eight weeks of ‘stuff’ before we even start implementation. That means the next eight weeks are where we need to lock solution alignment, build the business case, and line up the decision meetings. How does that compare to how it works in your company, and what would you change?”
That last question is what makes it mutual.
2. Build it live, then share it immediately
Build it with the buyer, not for them. Share it right after the call and ask for edits. Then treat it as the source of truth in every deal update.
3. Run a short weekly check-in on the plan
Set a short weekly check-in focused only on plan progress: completed steps, blockers, next actions, owners and dates. No fluffy status calls. You catch stalls while you can still fix them.
4. When something slips, update the plan, don’t debate optimism
Surface what moved and agree on the next actions to get back on track. Escalate professionally:
“Hey, we’re drifting off the timeline we agreed to. I need help keeping us on pace. What changed, and what do we need to do to get back on track?”
Sometimes the buyer says it’s fine to slip. Sometimes they pull in the people needed to make it happen. Either way, you know exactly where you stand.
5. Put a price on delay
Convert the cost of inaction into a daily number and reference it in plan updates. Take the agreed business value and divide by 250 working days. A million-dollar ROI is $4,000 lost per day. Every slipped date now has a price tag.
When to Introduce a MAP
Don’t force a buying conversation before the buyer has chosen to buy. It can sound like you’re trying to close a deal that doesn’t exist yet.
But don’t wait until the end, either.
Early, ask about the process as history. It informs requirements without pressure:
- “When decisions like this were made before, what was the process?”
- “Who was involved?”
- “Where did it get stuck?”
- “Was a business case required?”
- “What issues showed up late that you wish you’d planned for?”
Later, when the decision is leaning your way, get specific:
- “What are the exact steps from here to signature?”
- “Who owns each step?”
- “How long does each step usually take?”
- “What could delay this?”
Then document it. That’s your MAP.
Early is scouting. Late is project management.
One nuance: inbound buyers often already have an evaluation and procurement process. Your job is to uncover it, document it and stress-test it, because steps get added that nobody mentioned. Outbound buyers rarely have one, because they weren’t planning to buy. Your job is to help them build it. If you don’t, it will surprise you later.
The Most Common MAP Mistakes
Treating it like a seller checklist. If it isn’t co-created, agreed and referenced by the buyer, it’s just internal notes.
Stopping at “proposal sent.” If your MAP doesn’t include security, legal, procurement, vendor onboarding and signature authority, you’re still forecasting intent, not execution.
Tracking stages instead of actions. Progress is not a stage change. Progress is a completed action that moves a milestone forward. That’s why MAPs work. They force you to track reality, not hope.
Keeping it verbal. If the plan lives in your head, it doesn’t exist.
MAPs and Your Forecast
If a deal is in upside or commit, it should have a mutual action plan in writing. If you can’t articulate and track milestones, owners and dates, it’s nearly impossible to hold anyone accountable.
Commit is earned: green across all criteria, the timeline nailed down, and milestones tracked with mutual owners and dates. And one rule keeps it honest: downgrade fast. Commit moves back to upside the moment an agreed milestone is missed and there’s no plan to get it back on track. Missed milestones aren’t neutral. They’re data. (More on this in Sales Forecast Accuracy: Why You Keep Missing the Number.)
Color Code Your Buying Process
- Red: You can’t explain how this gets bought. “They asked for a proposal.” “They said decisions are fast.” “Procurement should be quick.”
- Yellow: You have a rough idea or a verbal agreement, but nothing is documented or co-created, or you’re tracking but slipping without a recovery plan.
- Green: A co-created MAP with both lanes mapped, owners and dates confirmed, the compelling event and signature authority confirmed, and progress tracked by completed actions.
Green sounds like: “Here are the steps, here are the people, here are the dates, here’s what could delay us, and we’re managing it together.”
If you only understand the decision process but haven’t mapped legal, you’re still yellow.
The Bottom Line
A mutual action plan isn’t paperwork. It’s how “we’re ready” becomes “we’ll sign this quarter, by this date.”
Build it with the buyer. Cover both lanes. Put an owner and a date on every step. Review it weekly. And when it slips, update the plan instead of your hopes.
Grab the free MAP template. The full Buying Process chapter, including every play above, is in the book.