Mutual Action Plans (MAPs)
The single most effective deal-control instrument in enterprise selling — when the customer signs it, when it lives in the deal, and when it surfaces slips early.
A is a jointly-owned, dated plan from current state to signed contract or value milestone, signed off by the buyer. It operationalizes 's and and converts into execution. Without a , sellers manage deals by hope; with one, slips become visible the day they happen.
Why MAPs work
- They surface the full and in writing — no late surprises
- They the publicly to specific actions, which is itself a
- They give , legal, and security visibility before they become the bottleneck
- They convert 'we'll get back to you' into a dated, owned action
- They turn deal slippage from a quarter-end shock into a week-1 conversation
Structure of an effective MAP
A useful is one to two pages and includes:
- Outcome statement — the business outcome the customer is buying, in their words
- Target signature date — the date that drives every milestone backward
- Workstreams — typically: , technical evaluation, , , , executive approval, signature
- Milestones per workstream — date, deliverable, owner on each side
- Decision gates — the named meeting where each workstream is reviewed
- Risks and dependencies — what could slip and who owns the mitigation
- Sign-off line — 's name and date
Keep it scannable. A 12-page no one updates is worse than a one-page everyone references weekly.
Co-creating the MAP with the customer
Never email a draft cold. The standard motion:
- Earn the right by completing strong and validating at the level
- Frame: 'For deals like yours we typically run a joint plan — it keeps everyone aligned and surfaces risks early. Worth 30 minutes to build it together?'
- Walk the through a starter draft on a screen-share, editing live
- Ask the to circulate it internally and bring back edits — this is itself a
- Once aligned, capture the 's written sign-off (email is enough)
- Reference the in every subsequent meeting; update visibly when dates move
Driving accountability and momentum
A signed is leverage; an unused is paperwork. Operationalize:
- Open every customer call with a 60-second review
- When a milestone slips, ask 'what changed and what does it imply for signature?' — never silently roll dates
- Use the in internal deal reviews — it is the source truth for stage and
- Mirror the in your next-step fields
- Escalate visible slips early; vendor-side can break ties
Common failure modes
- Vendor-only plans — the seller writes a 'plan' and shares it once; the customer never engages. Not a .
- No buyer sign-off — the 'agrees verbally' but never confirms in writing. Easily disowned later.
- No dates — workstreams without dates are aspirations, not commitments.
- No / legal / security workstreams — the most common cause late-quarter surprise.
- No enforcement — slips are ignored politely; the becomes decorative.
- One-time artifact — built at Stage 3, never referenced again.
MAP and MEDDPICC
The is where becomes operational. is the spine; is a workstream; is named in the executive-approval gate; is the signatory; is the target date. A deal with a strong MEDDPICC score and no is still exposed; a deal with a weak score and no MAP is fiction.
Real-world example
An a $1.6M deal as , expecting signature by quarter-end. No existed. The customer's queue was 6 weeks; the seller learned this in week 4 the quarter. The deal slipped two quarters. A peer team on a similar deal had built a at Stage 3 that surfaced the security queue immediately; they front-loaded the security questionnaire and pre-aligned with the customer's security architect. Their deal closed in-quarter at the same value. The product was identical; the discipline was not.