Builds a mutual action plan (MAP) with shared milestones, owners, and dates to drive a deal to close. Use once a prospect is qualified and has expressed intent to move forward.
Click to play with sound.
---
name: Mutual Action Plan
description: Builds a mutual action plan (MAP) with shared milestones, owners, and dates to drive a deal to close. Use once a prospect is qualified and has expressed intent to move forward.
---
# Mutual Action Plan
A mutual action plan is a shared document that aligns the buyer and seller on every step between 'we want to move forward' and 'the contract is signed and live.' The word 'mutual' matters — if the buyer has not contributed to and agreed on the plan, it is just a vendor's wishlist.
## When to introduce the MAP
Introduce the MAP after the buyer has expressed clear intent to evaluate seriously — not at the first call. Framing: 'A lot of our customers find it helpful to build a shared timeline so nothing gets stuck waiting on anyone. Would you be open to putting one together?' Never present it as a closing tool — present it as a coordination tool.
## Core structure
The MAP should have exactly these columns: milestone, owner (buyer or seller, by name or role), due date, and status. Keep it in a shared doc the buyer can edit. A MAP that only the vendor can update is not mutual.
Typical milestones for a mid-market SaaS deal:
- Technical review / security questionnaire completed
- Legal review started
- Reference calls completed
- Final business case signed off internally
- Contract redlines exchanged
- Signatures collected
- Kickoff scheduled… install to load the full skillSign in to rate and review this skill.
No reviews yet. Be the first to review this skill.