Nov 14, 2026
12 min read
How to Set Up a Mutual Action Plan for B2B Deals
A mutual action plan (MAP) is a shared, dated document that lists every step both the buyer and the seller must complete for a B2B deal to go from "we're interested" to "contract signed and live." To set one up, work backward from the buyer's go-live date, list every task each side owns (security review, legal, budget approval, signature), give each task a named owner and a deadline, and review it together on a fixed cadence. Done well, a MAP turns a vague verbal commitment into a shared project the buyer actively helps manage.
I've watched many deals stall in the same place: the champion loves the product, the demo went well, and then nothing happens for six weeks. Usually nobody lost interest. Nobody wrote down what had to happen next, who had to do it, or why it mattered by a specific date. This article explains how I set up mutual action plans and when to introduce them. It also covers what to put in them and how to keep them alive without turning them into another ignored spreadsheet.
What is a mutual action plan, really?
A mutual action plan is not a sales forecast, a proposal, or a project plan for implementation. It sits between those things. It is a joint timeline that answers three questions for both sides:
- What has to happen before this deal can be signed and the customer can start getting value?
- Who owns each step, on the buyer's side and on the seller's side?
- By when, anchored to a date the buyer actually cares about?
The word "mutual" is the important part. A plan that lists only your tasks ("send proposal," "follow up") is just your to-do list. A real MAP includes tasks the buyer owns: "IT completes security questionnaire," "CFO approves budget line," "Legal returns redlines." The buyer has to see their own name next to deadlines.
Why do B2B deals need a mutual action plan?
Most B2B purchases involve several people who never attend your sales calls: procurement, finance, legal, IT security, sometimes a board or a parent company. Your champion often doesn't know the full approval path either, especially if their company buys software like yours rarely.
A MAP solves several problems at once:
- It exposes hidden steps early. You learn in week two, not week ten, that a vendor registration process takes three weeks.
- It tests real commitment. A buyer who refuses to put any dates on paper is telling you something about the deal's real status.
- It gives your champion a tool. They can forward the plan internally and use it to push their own colleagues.
- It makes forecasting honest. You can see whether the steps are on track, so you aren't relying only on how a call felt.
If you're working on cycle length in general, a MAP is one of the most practical levers. I cover others in practical methods to shorten the B2B sales cycle.
When should you introduce a mutual action plan?
Timing matters. If you introduce it too early, it feels presumptuous. If you introduce it too late, you've already lost the weeks it was meant to save.
I recommend introducing a MAP right after the buyer has confirmed three things:
- They have a real problem worth solving (pain is confirmed).
- Your solution is a plausible fit (usually after a discovery call and a tailored demo).
- There is some reason to act within a defined window, such as a budget cycle, a contract renewal with a competitor, or a project launch.
In pipeline terms, this usually falls at the transition from "solution validation" to "evaluation" or "proposal." If your stages aren't clearly defined, fix that first. My guide on how to define your B2B sales pipeline stages explains how to set exit criteria. "MAP agreed with buyer" makes an excellent exit criterion for a mid-funnel stage.
For small deals with a single decision-maker and a one-week cycle, a MAP is usually overkill. Use it when a deal involves three or more stakeholders, a cycle longer than about 30 days, or any formal procurement or legal review.
How to set up a mutual action plan: step by step
Step 1: Agree on the target date and the reason behind it
Start with the buyer's date, not your quarter end. Ask questions like:
- "When do you need this running to hit [the goal you mentioned]?"
- "What happens if this isn't in place by then?"
Suppose a logistics company wants its new sales team using your tool before a hiring wave starts on 1 September. The go-live date is 1 September. The reason is "new reps onboard on the platform from day one." Write both at the top of the plan. The reason is what keeps the date real when things slip.
Step 2: Work backward to map the full path
Starting from go-live, ask your champion to walk you through everything that must happen before it. Useful prompts:
- "Who else needs to sign off before a contract is signed?"
- "Has your company bought a tool like this in the last year? What did that process look like?"
- "Does IT or security need to review vendors? How long does that usually take?"
- "Who signs contracts at this value, and do they need a board or holding-level approval?"
In Turkey, I always ask specifically about signing authority. Many companies require signatures that match the authorized signatories in their signature circular (imza sirküleri), and some need two signatures. If the authorized signatory is a general manager who travels constantly, that becomes a step with its own deadline. Also ask early about vendor registration and invoicing requirements, since finance teams may need your company set up in their system before a PO can be issued.
Step 3: List every task with an owner and a date
Now turn the path into rows. Each row needs:
- Task: specific and verifiable ("Security questionnaire returned," not "security stuff")
- Owner: a named person, not "IT team"
- Side: buyer or seller
- Due date
- Status: not started / in progress / done / blocked
Step 4: Add buffer where delays are predictable
Legal review and procurement almost always take longer than people estimate. I usually add 25–50% buffer to any step owned by legal or procurement. In Turkey, plan around public holidays and religious holidays (Ramazan Bayramı and Kurban Bayramı can effectively remove a week or more of decision-making), plus summer periods when senior decision-makers are often away. If your plan runs through August, ask directly who will be available.
Step 5: Review it with the champion before sharing widely
Walk through the draft with your champion in a 20–30 minute call. Let them correct dates and add steps you missed. This is where the plan becomes theirs. Then ask: "Would it help if we shared this with [finance contact / IT lead] so they see where they fit?"
Step 6: Set a review cadence
A MAP that nobody looks at is worse than none, because it creates false confidence. Agree on a rhythm, typically a 15-minute check-in every week or every two weeks, where you go through open items only.
What should a mutual action plan template include?
Here is a simplified example for a mid-sized deal with a target go-live of 1 September:
| # | Task | Owner | Side | Due date | Status | |---|------|-------|------|----------|--------| | 1 | Final demo for sales managers | Ayşe (seller AE) | Seller | 10 June | Done | | 2 | Share business case summary | Ayşe | Seller | 14 June | Done | | 3 | Internal alignment meeting with Sales Director | Mehmet (champion) | Buyer | 18 June | In progress | | 4 | Security questionnaire sent | Ayşe | Seller | 18 June | Done | | 5 | Security questionnaire returned with approval | Emre (IT lead) | Buyer | 2 July | Not started | | 6 | Proposal and pricing sent | Ayşe | Seller | 20 June | Not started | | 7 | Budget approval from CFO | Mehmet | Buyer | 5 July | Not started | | 8 | Contract redlines returned | Legal team (Zeynep) | Buyer | 15 July | Not started | | 9 | Vendor registration in finance system | Finance (Burak) | Buyer | 19 July | Not started | | 10 | Contract signed by authorized signatories | General Manager | Buyer | 25 July | Not started | | 11 | Kickoff and onboarding plan agreed | CSM + Mehmet | Both | 1 August | Not started | | 12 | Go-live for new rep cohort | Mehmet | Buyer | 1 September | Not started |
Above the table, add three lines:
- Goal: New sales reps productive on the platform from their first day.
- Target go-live: 1 September.
- Why it matters: Delayed onboarding means reps start on manual processes and need to be retrained later.
That's enough. You don't need a 40-row Gantt chart. A good MAP fits on one screen.
The proposal sits inside the plan as one step rather than as the end goal. For how to write that step well, see how to write a B2B sales proposal that gets signed.
How do you get a buyer to agree to a mutual action plan?
Some reps hesitate to propose a MAP because it feels pushy. It doesn't have to be. Frame it as help, because it is.
A simple way to introduce it:
"Based on what you've told me, you want this live by 1 September. Companies your size usually have a few approval steps we can't see from the outside, like security, legal, and finance setup. Would it be useful if I drafted a simple timeline of what needs to happen and when, and you tell me what I've got wrong?"
A few things make this work:
- Draft it yourself first. Never ask the buyer to build it from scratch. Bring a 70% version.
- Lead with their date and their goal, not your quarter end.
- Make it easy to share. A shared doc or a simple spreadsheet beats a PDF attachment, and a lightweight shared page is better than a login-gated portal for most mid-market buyers.
If the buyer won't commit to any dates at all, don't argue. Treat it as information. Move the deal back a stage in your CRM and focus on whether there's a real reason to act.
How do you keep a mutual action plan alive?
Most MAPs die in week three, when the first buyer-side task slips and nobody says anything. Some habits that help:
- Address slips immediately and neutrally. "I see the security review was due Tuesday. Is there anything I can do to help Emre, like a call with our technical lead?"
- Re-date honestly. If a step moves two weeks, move everything downstream two weeks and say out loud what that does to go-live. This is often the moment the buyer pushes their own team harder.
- Send a short summary after each check-in. Three lines: what's done, what's next, any risks.
- Bring in executive alignment when needed. If a buyer-side step is blocked for more than two weeks, suggest a short call between your manager or founder and their sponsor.
Price discussions often surface in the middle of a MAP, usually around the budget approval step. Prepare for that moment in advance. My notes on handling price objections in B2B sales calls apply directly here.
How do you roll out mutual action plans across a sales team?
For a founder or sales leader, the value of MAPs multiplies when the whole team uses them consistently.
- Create one standard template. Keep the columns identical across deals so you can review them quickly.
- Define when a MAP is mandatory. For example: any deal above a certain value, or any deal with formal procurement.
- Link MAPs to your CRM. Paste the link into the opportunity record, and track "MAP agreed" as a field or stage requirement.
- Review MAPs in pipeline meetings. Instead of asking "how do you feel about this deal?", ask "which buyer-side task is next, and is it on time?"
- Use MAP status in forecasting. A deal whose buyer-side steps are on schedule deserves more confidence than one with three overdue items, whatever the rep's gut says.
That last point changes forecasting more than any spreadsheet formula. If you're building a forecasting process for a small team, combine MAP status with the approach in how to forecast sales revenue for a small B2B team.
Common mistakes to avoid
- Making it one-sided. If every task belongs to the seller, it's a follow-up schedule, not a mutual plan.
- Using team names instead of people. "Legal" never answers emails. Zeynep does.
- Anchoring on your quarter end. Buyers can tell, and it erodes trust.
- Overbuilding it. Fifty rows signals bureaucracy. Twelve to fifteen is usually enough.
- Stopping at signature. Include at least the kickoff and go-live steps. They remind everyone why the deal matters.
- Never revisiting it. A stale MAP gives false confidence in your pipeline.
FAQ
What is the difference between a mutual action plan and a close plan?
A close plan is usually an internal seller document listing what the rep needs to do to win the deal. A mutual action plan is shared with the buyer and includes tasks both sides own, with named people and dates. The shared ownership is what makes a MAP effective at moving deals forward.
What tool should I use to build a mutual action plan?
A shared Google Sheet, a shared document, or a simple page in a collaboration tool works for most small and mid-sized teams. Dedicated digital sales room tools exist and can help at higher volume, but the format matters far less than the content and the review habit. Choose whatever your buyer can open without friction.
How many steps should a mutual action plan have?
For most mid-market B2B deals, 10 to 15 steps is enough to capture the key approvals without overwhelming anyone. Enterprise deals with heavy security, legal, and procurement processes may need more. In those cases, group related tasks into phases so the plan still reads easily.
What should I do if the buyer refuses a mutual action plan?
Treat the refusal as a signal about deal quality, not as an obstacle to push through. Ask what's making them hesitant. Often the real issue is that there's no internal urgency or the champion lacks authority. Adjust your forecast and your time investment accordingly.
Conclusion
A mutual action plan is one of the simplest tools in B2B sales. Each row is just a task, an owner, a date, and a reason, yet it changes how deals behave. It brings hidden approval steps out early, tests whether the buyer is truly committed, gives your champion something concrete to push internally, and makes your forecast reflect reality rather than optimism. Start with the buyer's go-live date, work backward, put real names next to real deadlines, and review it together every week or two.
If you're building a sales process for your team and want to talk through how mutual action plans, pipeline stages, and forecasting fit together, feel free to [get in touch with me](/). I'm always happy to compare notes with founders and sales leaders.

