How to Build a Mutual Action Plan — With Template
The short answer
A mutual action plan (MAP) is a shared checklist of every step — on both sides — required to get from "we're interested" to signed contract. The goal is to surface the buyer's timeline, identify hidden blockers, and give your champion a tool to navigate their own procurement process.
Mark Jacobs
Director of Commercial Partnerships & Growth, Vista · December 3, 2025
Most AEs think they control the deal timeline. They don't. The buyer's fiscal calendar, procurement process, and internal approval chain control it. A mutual action plan is how you get visibility into that process before it surprises you.
What a MAP actually is
A simple shared document that answers three questions:
- What has to happen before this deal can close?
- Who owns each step?
- What's the realistic timeline?
It's not a sales tactic. It's a project plan for the decision. When it works, both sides are working from the same list of what's left to do.
Standard B2B SaaS MAP Template
| Step | Owner | Target Date |
|---|---|---|
| Share security documentation | You | Day 1–2 |
| Technical review / security Q&A | Buyer IT lead | Week 1 |
| Expanded stakeholder demo | You + buyer champion | Week 1–2 |
| Legal review of MSA | Buyer legal | Week 2–3 |
| Procurement / vendor setup | Buyer ops | Week 3–4 |
| Final budget approval | Economic buyer | Week 4 |
| Contract signature | Both | Week 4–5 |
Why AEs avoid building MAPs
It feels presumptuous to hand a buyer a project plan at call two. The reality is the opposite — buyers who are serious appreciate the structure. The ones who push back hard on a MAP are usually signaling something about their actual level of interest or internal readiness.
How to introduce it without it feeling like a sales tactic
Don't call it a “mutual action plan.” Say: “I want to make sure I'm not creating any surprises on your end. Can we walk through what your team's process looks like between here and a signed contract?”
Then build the MAP from their answers in real time. Share it in the follow-up after that call.
The compounding value
When the deal evolves — new call, new stakeholder, new objection — update the MAP. It becomes the living record of where the deal is. Your champion can share it internally to answer “where are we with this vendor?” without digging through email threads.
Vista generates a MAP automatically from your call transcript — extracted from what was actually said on the call, not filled in after the fact from memory. Paste the transcript and the MAP is already structured with named owners and dates before you close your laptop.
Frequently Asked Questions
At what stage of the deal cycle should I introduce a MAP?
After the demo, before legal. The MAP conversation is a natural continuation of "okay, we're both interested, what does moving forward actually look like?" — which is the question you should be asking after every strong demo.
What if the buyer doesn't want to commit to a timeline?
That's data. A buyer who won't engage with a MAP often doesn't have real budget, internal alignment, or urgency. It's better to know at call three than at month three.
Should the MAP be visible to the entire buying committee?
Yes. The MAP's value is that it aligns both sides on what's left to do. Keeping it AE-only removes the accountability that makes it work.
Can AI generate a mutual action plan from a call transcript automatically?
Yes. Vista extracts the MAP from your call transcript — pulling out named commitments, owners, and timelines from what was actually said on the call. You paste the transcript and the MAP is already structured before you close your laptop. No blank template, no memory required.
10 free rooms. No credit card. No setup.
Try Vista free →