Mutual Action Plan Template: 3 Copy-Paste Examples (SaaS, Enterprise, SMB)

Key takeaways:

• A mutual action plan template is a shared, table-based close plan—not a seller's checklist. Every row should name an owner (seller or buyer) and a date.
• Three templates fit most B2B motions: a lean SaaS plan (3 milestones), a enterprise plan (5+ milestones for security, legal, and budget sign-off), and a stripped-down SMB plan (3 milestones, 6 tasks max).
• The fastest way to make a MAP stick is to build it with the buyer in the first call and host it in a Digital Sales Room so both sides see live progress.
• The three most common fill-in mistakes—no buyer-side tasks, seller-imposed dates, and a "set and forget" plan—are also the easiest to fix.

If you have already read our mutual action plan guide and just want something you can copy, paste, and send today, this is the page. Below are three field-tested templates, a fully filled-in example, and the mistakes that quietly kill a MAP before it does any work.

A MAP works because it turns "next steps" from a vague promise into a shared, dated commitment. Forrester's State of Business Buying 2024 found that B2B purchases now involve an average of 13 stakeholders, with 89% spanning two or more departments—which is exactly why an informal "I'll follow up next week" no longer holds a deal together.

---

The 5 building blocks every MAP template needs

Before the copy-paste tables, here is the skeleton all three share. Keep these five blocks and you can adapt the rest to any deal.

The single rule that separates a real MAP from a glorified to-do list: every task names an owner—seller or buyer—and a date the two of you agreed on. A plan with only seller tasks is a project plan; a MAP is mutual by design.

---

Template 1 — SaaS deal (lean, 3 milestones)

Best for transactional-to-mid SaaS deals with a 30–90 day cycle, a clear champion, and 2–4 stakeholders. Copy this Markdown table directly into your CRM note, email, or DSR.

Deal:    [Customer] × [Your Product]
Goal:    Sign by [date] and complete onboarding by [date]
Created: YYYY-MM-DD   Updated: YYYY-MM-DD

Success criteria
- [N] users complete the trial and create ≥1 workspace
- ROI clears [threshold] over [period]
- Security review passes with no blockers

Timeline (reverse-engineered)
[go-live] ← Sign  →  -1wk Procurement  →  -2wk ROI review  →  -4wk Trial  →  -6wk Demo (start)

---

Template 2 — Enterprise deal (5+ milestones)

Best for deals above your enterprise ACV threshold, with multi-layer approval (security, legal, finance) and a 3–6 month cycle. The difference from the SaaS template is that each gate becomes its own milestone, so a stall in legal does not hide behind "in progress."

Deal:    [Customer] × [Your Product] — Enterprise rollout
Goal:    Executed MSA by [date]; phase-1 go-live by [date]
Sponsor: [Exec sponsor]   Champion: [Champion]

Success criteria
- IT confirms [integration] and [scalability requirement]
- InfoSec approves with no high-severity findings
- Legal accepts liability + data-residency terms
- Finance approves budget within [fiscal period]

Stakeholders
| Name | Dept | Role | Phase |
| ____ | IT   | Technical eval | Evaluation |
| ____ | InfoSec | Security sign-off | Review |
| ____ | Legal | Contract redlines | Contracting |
| ____ | Finance | Budget approval | Approval |
| ____ | Exec  | Final approver | Negotiation–Signature |

For enterprise deals, also list the likely objectors, not just supporters—the InfoSec or legal reviewer who joins late is the most common reason a "committed" deal slips a quarter. Mapping each stakeholder's concern early is the same discipline that powers MEDDIC.

---

Template 3 — SMB deal (stripped down)

Best for sub-$10K ACV, 1–2 decision-makers, and a 2–4 week cycle. Here the goal is less structure: three milestones, six tasks maximum. Over-engineering a small deal makes the buyer feel managed and slows it down.

Deal:    [Customer] × [Your Product]
Goal:    Start by [date]

---

Filled-in example (SaaS deal)

Templates are abstract until you see one completed. Here is the SaaS template with real-looking values, so you can see the level of specificity that makes a MAP work.

Deal:    Acme Inc. × Terasu — Sales-room rollout
Goal:    Sign by 2026-06-30, complete onboarding by 2026-07-15
Created: 2026-05-15   Updated: 2026-05-29

Success criteria
- All 5 AEs create ≥1 room and share ≥3 documents
- ROI shows ≥4 hrs/week saved per rep
- Security review passes (SSO + audit log confirmed)

Notice three things: the goal is a dated outcome (not "evaluate Terasu"), buyer-side tasks (rows 2, 5, 7) carry as much weight as seller tasks, and the success criteria are measurable enough that no one can stall on "we need more time to think."

---

The 3 most common fill-in mistakes (and the fix)

Most MAPs fail not because the template is wrong, but because of how it gets filled in. These are the three we see most often.

Mistake 1 — No buyer-side tasks

A plan with only seller tasks ("we'll send the proposal, we'll prepare the demo") is a project plan, not a mutual one. The buyer reads it as your homework, feels no ownership, and the deal stays exactly as stalled as before.

Fix: every milestone needs at least one buyer-owned task. If you can't name one, the buyer probably isn't ready to advance that milestone yet—which is itself useful information.

Mistake 2 — Seller-imposed dates

When the AE fills in every due date unilaterally, the buyer feels managed and quietly disengages. Dates that the buyer didn't agree to are dates the buyer won't honor.

Fix: set dates with the buyer—"To go live by the 30th, when could security realistically review this?" A date the buyer proposes is a date the buyer defends internally.

Mistake 3 — "Set and forget"

The single biggest failure pattern: the MAP is built once, looks great, and is never updated. Within two weeks it's stale, both sides ignore it, and you're back to "just following up."

Fix: update the MAP weekly, check off completed tasks, and re-share the updated version. A MAP that visibly moves reassures the buyer that the deal is progressing—and a shared Digital Sales Room makes that update a two-minute habit instead of another spreadsheet to maintain.

---

Customizing the template by deal type

A quick reference for which template to start from and what to change.

Keep the structure identical across deals—header, stakeholders, milestones, criteria, timeline—and vary only the depth. Reps who rebuild a MAP from scratch every time burn time and produce inconsistent plans; a small set of standardized templates is what lets a team operate a MAP reliably.

---

Frequently Asked Questions

Can I build a mutual action plan template in Excel or Google Sheets?

Yes. Copy any of the three tables above into a spreadsheet and share it with the buyer. The limitation is that spreadsheets give you no view tracking and clumsy real-time co-editing. A DSR-based MAP lets both sides update live and shows you which stakeholders actually opened it—useful signal a spreadsheet can't provide. Start in Sheets if you must, and move to a DSR once you see the value.

How many tasks should a mutual action plan have?

Aim for 10 or fewer, and no more than three tasks per milestone. Enterprise deals can stretch to ~15, but beyond that the plan becomes admin overhead and the buyer starts to disengage. If the list keeps growing, consolidate tasks or split one milestone into two rather than piling on rows.

When should I introduce the MAP to the buyer?

Right after the buyer signals genuine interest—typically after a strong first proposal or demo. That's when "shall we map out the steps together?" feels natural rather than pushy. Sending a detailed MAP before you've confirmed need can make the buyer feel rushed.

Should I use a different template for every customer?

No—standardize the structure and customize only the details. Keep the same five blocks and adjust milestone count and task content to the buyer's decision process. Maintaining 2–3 templates by deal size (SaaS / enterprise / SMB) is far more efficient than starting from a blank page each time.

What if the buyer won't help keep the MAP updated?

First check whether the plan is too heavy—too many tasks is the usual culprit, so trim it. If the buyer still won't engage after that, low engagement with the MAP often reflects low engagement with the deal itself, which is a signal to re-qualify rather than to push harder.

How is a mutual action plan template different from a close plan?

They overlap heavily. A "close plan" is often an internal, seller-only document used for forecasting, whereas a mutual action plan is explicitly shared and co-owned with the buyer. The template here is built to be mutual—every row has an owner that can be the buyer—so it serves both purposes when shared.

---

Conclusion

A mutual action plan template only works when it's genuinely mutual, specific, and kept alive. Pick the template that matches your deal—lean for SaaS, gated for enterprise, stripped down for SMB—fill it in with the buyer in your next call, and update it every week.

The fastest path from "nice template" to "deals that don't stall" is to stop emailing static files around. Build the MAP once, duplicate it into each new deal, and host it where the whole buying group can see progress in real time.

Next step: Duplicate one of these templates into a Terasu deal room, share it with the buying group, and use the engagement signals to see which stakeholders are actually engaging. Pair it with the mutual action plan guide for the full playbook, and MEDDIC to map the committee behind each milestone.