Mutual Action Plan (MAP) Template

# Mutual Action Plan — {{Customer name}} × {{Vendor name}} — {{Target close date}}

## Deal summary
- Solution: {{what you're buying}}
- Business outcome: {{one-line quantified outcome}}
- Investment: $___ ({{term}}, {{payment terms}})
- Target signature: __/__/__
- Target go-live: __/__/__

## Executive sponsors
- **Customer sponsor:** {{Name}} ({{Title}}) — signs off on business case
- **Vendor sponsor:** {{Name}} ({{Title}}) — signs off on partnership

## Core team
| Role | Customer | Vendor |
|------|----------|--------|
| Executive sponsor | | |
| Project owner | | |
| Technical owner | | |
| Procurement / legal | | |
| Security / compliance | | |
| Finance / budget | | |

## Timeline & milestones

### Phase 1 — Business case validation (Weeks 1–2)
| # | Step | Owner | Due | Status | Notes |
|---|------|-------|-----|--------|-------|
| 1 | Discovery / requirements confirmed | Customer PM | | | |
| 2 | ROI / business case aligned | Vendor AE + Customer sponsor | | | |
| 3 | Reference call (if needed) | Vendor AE | | | |
| 4 | Executive alignment meeting | Both sponsors | | | |

**Success criteria:** Both sponsors align on business case and target outcomes.

### Phase 2 — Technical validation (Weeks 3–5)
| # | Step | Owner | Due | Status | Notes |
|---|------|-------|-----|--------|-------|
| 5 | Technical scoping call | Vendor SE + Customer tech | | | |
| 6 | Security review (SOC 2, DPA, questionnaire) | Customer security | | | |
| 7 | POC / trial (if applicable) | Both | | | |
| 8 | Integration validation | Both tech teams | | | |

**Success criteria:** Security approved, technical fit confirmed, POC success criteria met.

### Phase 3 — Commercial (Weeks 6–8)
| # | Step | Owner | Due | Status | Notes |
|---|------|-------|-----|--------|-------|
| 9 | Pricing proposal delivered | Vendor AE | | | |
| 10 | Budget approval | Customer finance | | | |
| 11 | MSA / order form redlines | Both legal | | | |
| 12 | Legal review complete | Both legal | | | |
| 13 | Procurement sign-off | Customer procurement | | | |
| 14 | Signature | Customer signatory | | | |

**Success criteria:** Contract signed and countersigned.

### Phase 4 — Onboarding (Weeks 9–12)
| # | Step | Owner | Due | Status | Notes |
|---|------|-------|-----|--------|-------|
| 15 | Kickoff | CS + Customer PM | | | |
| 16 | Configuration + integration | Both | | | |
| 17 | Training | Vendor CS | | | |
| 18 | Go-live | Both | | | |

**Success criteria:** In production use with adoption > __%.

## Risk register
| # | Risk | Impact | Likelihood | Owner | Mitigation |
|---|------|--------|------------|-------|------------|
| 1 |      |        |            |       |            |
| 2 |      |        |            |       |            |

## Weekly sync
- Standing time: {{day}} at {{time}}
- Format: review status of open steps, flag blockers, adjust dates if needed
- Attendees: {{list}}

## Sign-off
- Customer champion / sponsor: {{Name}} — {{Date}}
- Vendor AE: {{Name}} — {{Date}}

*This plan represents our mutual commitment to complete the above steps in the timeline shown. It is not a contract — the executed order form is the binding commitment.*

Why a MAP actually shortens sales cycles

It sounds counterintuitive — adding process shortens things? — but MAPs work for three reasons. First, they force the buyer to think through their own process (they usually haven't). Second, they surface hidden steps (security review, procurement, budget approval) 6 weeks earlier than they'd otherwise appear. Third, they create a joint commitment — pulling out of a MAP is socially harder than 'going quiet' on an AE.

How to introduce a MAP without spooking the buyer

Don't call it a 'mutual action plan' — that sounds sales-y. Call it a 'joint project plan' or 'implementation timeline'. Introduce it as a service to them, not a tool for you:

• 'To make sure we hit your Q3 go-live target, I've drafted the steps I know from other similar deals. Can we walk through it together and mark what's realistic on your side?'
• 'I want to make sure I'm not surprising you with anything. Here are the typical steps for a deal this size — let's confirm what applies.'
• 'Legal and procurement usually take 3–4 weeks. Should we start those in parallel with the technical validation?'

The five steps buyers always forget

• Security review / SOC 2 questionnaire — often 2–3 weeks; needs to start EARLY.
• Data Processing Agreement (DPA) for EU/UK — extra 1–2 weeks.
• Procurement approval — often gated by dollar thresholds; the buyer's champion may not know their own threshold.
• Budget re-approval — if the deal size changed, budget may need to go up the chain again.
• Vendor onboarding forms — payment terms, W-9, banking, insurance certs.

Weekly cadence with the champion

Once the MAP is signed, hold a 15-minute weekly sync with your champion. Structure:

1. Review what closed since last week (completed steps).
2. Flag anything at risk of missing its date.
3. Confirm this week's actions and owners.
4. Ask: 'Is there anything I should know about that's not on this plan?'

When to escalate a stuck MAP

If a step misses its date by more than 5 business days without a clear reason, escalate to the executive sponsor. Escalation is not confrontation — it's a re-alignment:

Subject: Quick alignment on {{project}} timeline

Hi {{Sponsor}},

Thanks for the alignment we set on {{original date}}.

We're currently at {{current step}} — {{X}} business days behind the plan we mapped together. Not a crisis, but I want to flag it now so we can course-correct rather than surprise the {{go-live}} date.

Two things would help:
1. {{Specific ask #1}} — expected impact: {{X}} days recovered.
2. {{Specific ask #2}} — expected impact: {{X}} days recovered.

Happy to jump on a 15-min call this week if easier. Otherwise the champion team is aligned on next steps.

Thanks,
{{Your name}}

FAQs

Related tools & templates