Mutual Action Plan

Build collaborative close plans with buyers — shared milestones, stakeholder alignment, risk flags, and timeline tracking that keep deals moving and transform vague commitments into binding agreements.

Pre-Work Framework

Before creating a Mutual Action Plan, the AI should ask:

1. What's the current deal stage and how far along are you? — Are you at the beginning of negotiations, deep in the evaluation, or at final contracting? Early-stage MAPs focus on milestone definition and stakeholder identification; late-stage MAPs focus on removing final blockers and securing signatures. The depth of the MAP scales with deal complexity and proximity to close.

2. Have you identified all stakeholders who need to be involved in this deal? — Do you know the champion, economic buyer, technical buyer, procurement contact, legal reviewer, and any other decision-influencers? Incomplete stakeholder mapping is the #1 cause of late-stage deal collapse. If you cannot name all stakeholders who will be involved in the approval process, the MAP becomes your tool to surface missing people before they object at the final hour.

3. What's the buyer's true timeline, not your timeline? — Do not confuse your close date with their decision date. Ask directly: "When does your budget cycle end? When do you need to present to your board? When is your busy season?" The MAP must honor their calendar, not yours. If you do not know their constraint, that becomes your first action item.

4. Is procurement already involved, and if so, what's their typical approval cycle? — Procurement surprises kill more deals than product gaps. If you have not seen a procurement team yet, do not assume you are in the home stretch. Add procurement engagement as an explicit milestone. If procurement is already involved, ask how long their review typically takes and what they will need from you (contract review, security questionnaire, references, etc.).

5. How strong is your champion, and do they have real authority, or are they a liaison? — A champion with authority can move the deal forward unilaterally; a liaison needs their own internal alignment before they can sell on your behalf. Your MAP strategy changes completely based on this. Strong champions mean you can move fast and iterate the MAP with them. Weak champions mean the MAP becomes your tool to help them build consensus internally.

Core Principles

Principle 1: Mutual Means Mutual Rule: Both you and the buyer commit to specific actions by specific dates, with equal accountability.

A one-sided action plan is not mutual—it is a wishlist. A real MAP has actions for both parties. Your actions: deliver contracts, run technical validations, connect with references, coordinate integrations, secure executive sign-off. Buyer actions: gather stakeholder feedback, run internal security review, confirm budget allocation, schedule approval meetings, return signed agreements. Neither side should have significantly more actions than the other. If you are doing 8 things and the buyer is doing 2, the MAP is not balanced, and the deal will likely slip because the buyer has not invested in it. Mutual accountability keeps both parties aligned and drives urgency.

Principle 2: Milestones Not Tasks Rule: Every entry in the MAP is a meaningful buyer milestone, not a tactical task disguised as a milestone.

Do not add "VP of Sales reviews proposal" as a milestone. Instead, add "Economic buyer confirms budget allocation and procurement initiation timeline by March 28." Milestones mark progress toward close and signal buyer investment. Tasks are steps internal to each party. The MAP is for milestones only. This distinction is critical: it forces you to think in buyer terms (what does their process require?) rather than seller terms (what do I need to do?).

Principle 3: Buyer's Timeline First Rule: The MAP timeline is anchored to the buyer's fiscal calendar, approval cycle, and decision process—not your quarter-end.

Your quarter ends March 31, but the buyer's budget cycle ends June 30 and their board approvals happen quarterly. Forcing a close by March 31 violates the buyer's natural approval rhythm and creates either a false commitment or a slip. Start with the buyer's hard constraint (their approval deadline), then work backward to define milestones. This approach is more reliable than starting with your close date and hoping the buyer can fit you in. If there is tension between your close date and their timeline, surface it explicitly in the MAP. Hiding this mismatch guarantees disappointment.

Principle 4: Document Assumptions Explicitly Rule: Every milestone includes the assumption that makes it achievable, not just the action.

Bad entry: "Procurement review contract by March 22." Better entry: "Procurement review contract by March 22 (assuming no new questions from IT security team)." Best entry: "Procurement review contract by March 22 (assumes no new questions from IT security, and that customer has completed SOC2 audit prep)."

Assumptions make hidden risks visible. If the assumption is not met, the milestone is unrealistic and should be renegotiated. Documenting assumptions transforms the MAP from a static plan into a dynamic risk-management tool. When you share a MAP with assumptions, you are saying "I have thought this through, and here is what needs to be true for this to work." That honesty builds credibility.

Principle 5: The MAP Is a Qualification Tool Rule: A buyer who will not commit to a shared MAP is not as ready to close as they claim.

If the buyer resists creating a MAP, resists committing to dates, or pushes back on milestones, that is a yellow flag disguised as a timeline issue. A truly ready buyer wants clarity on next steps and will engage in building the plan with you. A buyer who says "I'll get back to you on timing" or "Let's not over-plan this" is either not a real opportunity or is missing internal alignment. Use the MAP creation process as a discovery tool. Their resistance tells you what is really blocking progress.

The Process

Phase 1: Stakeholder Mapping (Entry: Deal info and contacts; Exit: Complete org chart with roles and buy-in status)

Before the MAP itself comes stakeholder alignment. List every person who will be involved in evaluating, approving, or implementing your solution:

• Champion (your internal advocate)
• Economic buyer (controls the budget)
• Technical buyer (validates the solution works)
• Procurement (approves contracts and terms)
• Legal (reviews agreements)
• Implementation lead (owns the integration plan)
• Executive sponsor (executive-level approval)
• End users (who will use the product)

For each stakeholder, document:

• Name, title, and function
• Their primary concern (speed? security? ROI? ease of implementation?)
• Buy-in status: "already onboard," "neutral," "needs convincing," "likely objector"
• How you will involve them: "included in technical deep-dive," "gets a financial summary," "needs legal review," etc.
• When they need to be engaged: early, mid-deal, late, or only at signature

If you cannot name a stakeholder in any category, that is a gap. Add "Identify and engage [title]" as a milestone.

Phase 2: Milestone Definition With Buyer (Entry: Stakeholder map; Exit: Negotiated list of 6-8 shared milestones with specific dates)

Schedule a working session with your primary champion and ask: "Let's build a shared plan to get this deal across the finish line. What does your approval process look like from today to signature?" Take them through their process step by step:

• Do they need technical validation? Timeline?
• When does procurement get involved? How long do they typically take?
• When are board approval meetings? Quarterly? Monthly?
• Are there budget cycle deadlines or fiscal year constraints?
• What happens if you need legal review? How much time does that take?

From their answers, define 6-8 key milestones. Examples:

1. Technical deep-dive and security review completed: March 20
2. Procurement initial review and questions submitted: March 25
3. Economic buyer approves budget allocation: April 2
4. Legal review complete with no major objections: April 5
5. Implementation readiness confirmed (IT infrastructure, user access): April 10
6. Final contract execution: April 15
7. Implementation kickoff: April 22

Do not make milestones a week apart. Space them realistically based on the buyer's actual process. A procurement review takes 5-7 days typically. A legal review takes 7-10 days. Budget allocation requires stakeholder meetings, which might be scheduled weeks out. Use real timelines.

Phase 3: Risk Identification & Mitigation (Entry: Milestones; Exit: Risk register with mitigation actions)

For each milestone, ask: "What could prevent this from happening on schedule?" Examples:

• Technical deep-dive milestone at risk because: "IT team is heads-down on infrastructure project until March 18"
  • Mitigation: Schedule the deep-dive for March 19-20 to align with their availability
• Procurement review at risk because: "Procurement team is unfamiliar with your vendor category"
  • Mitigation: Provide a procurement packet in advance with reference customers in their industry
• Budget allocation at risk because: "The CFO reviews quarterly budget requests in a single meeting on April 5"
  • Mitigation: Get CFO briefing by March 28 to ensure budget is on the April 5 agenda

Risk identification converts vague concerns into specific, actionable mitigation plans. It also signals to the buyer that you have thought through their internal constraints and are helping them navigate them.

Phase 4: Shared Document Creation (Entry: Milestones, risks, actions; Exit: Formal MAP document signed by both parties)

Create the MAP in a shared format (email-friendly, Google Docs, or structured template). Format:

MUTUAL ACTION PLAN
Deal: [Company Name] - [Solution Category]
Period: [Today] through [Close Date]
Prepared by: [Your Name] and [Buyer Champion Name]

STAKEHOLDERS
[Table with name, title, concern, status]

MILESTONES & ACTIONS
| Milestone | Target Date | Buyer Actions | Seller Actions | Assumptions | Risk |
| Technical review | Mar 20 | Schedule security team, review SOC2 | Conduct technical deep-dive, answer questionnaire | No scope changes | IT team availability |
| [continue for all milestones] |

RISKS & MITIGATIONS
- Risk: Procurement unfamiliar with category
  Mitigation: Provide vendor packet and customer references by March 22

TIMELINE SUMMARY
Commit Date (both parties commit): April 15
Next Review Date (plan check-in): March 27

SIGN-OFF
[Buyer Champion]: _________________ Date: _________
[Your Name]: _________________ Date: _________

The physical act of both parties signing (or typing names and dates in email) creates commitment. It transforms the plan from a suggestion into an agreement. This is critical.

Phase 5: Progress Tracking & Renegotiation (Entry: Signed MAP; Exit: Weekly status updates and updated timelines as needed)

Weekly or bi-weekly, send a brief status update:

MUTUAL ACTION PLAN STATUS UPDATE
Deal: [Company]
Review Period: [Dates]

COMPLETED MILESTONES (This Week)
✓ Completed: [Buyer Action] - Confirmed budget allocation (ahead of schedule!)

ON TRACK MILESTONES (Next 2 Weeks)
→ On Track: [Buyer Action] - Legal review in progress, expected March 29 (target March 30)
→ On Track: [Seller Action] - Contract redline submitted, awaiting buyer feedback

AT RISK MILESTONES
⚠ At Risk: [Buyer Action] - Procurement review delayed due to vendor evaluation process (target was March 25, now expected April 1)
  Action: Will have interim feedback by March 28; can we advance legal review to March 29 to keep momentum?

COMPLETED ACTIONS
- Seller: Delivered technical documentation (on schedule)
- Buyer: Completed internal security review (ahead of schedule)

UPCOMING ACTIONS
- Buyer: Submit procurement questions by March 22
- Seller: Respond to procurement questions within 24 hours of receipt

REVISED TIMELINE (If Changed)
- Original signature target: April 15
- Revised signature target: April 18 (due to procurement delay, but all other milestones tracking well)

The key is candor. If something is slipping, flag it immediately and propose a revised date. Do not hope that hidden slips will resolve themselves. The buyer already knows about their own internal delays, so transparency builds trust.

If a milestone is at risk, immediately ask: "Do we need to revise the timeline, or do you have a way to accelerate?" Let the buyer decide. This keeps the plan mutual and dynamic.

Anti-Patterns

Anti-Pattern 1: The Seller's Checklist Before: "Here's what I need to do to close this deal..." [list of seller tasks] After: A real MAP with equal buyer and seller actions, clearly labeled as buyer responsibilities.

A MAP that only lists seller actions is a to-do list, not a plan. It also signals that you are not expecting the buyer to do real work, which is why deals with seller-heavy checklists often slip—the buyer has not committed to anything.

Anti-Pattern 2: The Invisible MAP Before: You have a plan in your head, but you have not shared it with the buyer. After: The MAP is a formal document, reviewed and signed by both parties, discussed weekly.

If the buyer does not know your timeline expectations, they will not be held accountable to them. The MAP only works if both parties see and own it.

Anti-Pattern 3: The Optimistic Timeline Before: "We can close this by end of month" (without checking buyer's approval process). After: Working backwards from the buyer's hard constraint (board approval on April 10) to define realistic milestones.

Optimism kills more deals than conservatism. If you set unrealistic dates and miss them, you lose credibility. Start with the buyer's timeline first, then manage expectations from there.

Anti-Pattern 4: The Missing Stakeholder Before: You do not know who procurement is, and suddenly they raise blocking questions at day 29. After: Procurement is identified early, invited into the process, and their review timeline is built into the MAP.

Stakeholder surprises are entirely preventable. Identify everyone who will touch this deal and involve them early. A MAP with missing stakeholders is incomplete and will fail.

Anti-Pattern 5: The Set-and-Forget Before: You create a MAP in week 2, then do not look at it again until week 8. After: The MAP is reviewed and updated weekly. Slips are surfaced immediately and renegotiated.

A MAP that is not actively managed becomes a historical document, not a planning tool. Weekly check-ins keep both parties focused and identify issues before they become crisis.

Output Format

A Mutual Action Plan should be structured and sharable:

MUTUAL ACTION PLAN
Company: [Prospect Name]
Product/Solution: [What you are selling]
Prepared: [Date]
Participants: [Your name], [Buyer champion name], [Other key stakeholders]

BUSINESS CONTEXT
- Company size/industry: [relevant context]
- Current state: [where they are today]
- Desired state: [what they want to achieve]
- Budget commitment: [preliminary, pending approval, approved, etc.]
- Executive sponsor: [if named]

STAKEHOLDER ALIGNMENT
| Name | Title | Role | Buy-in Status | Primary Concern | Engagement Plan |
| [champion] | VP Sales | Internal advocate | Onboard | ROI & Speed | Weekly syncs |
| [economic buyer] | CFO | Budget control | Neutral | Cost & Implementation | Monthly business review |
| [technical buyer] | VP IT | Technical validation | Needs convincing | Security & Integration | Technical deep-dive week of X |

CRITICAL MILESTONES
1. Technical validation complete by [Date]
   - Buyer: Run internal security review, provide environment specs
   - Seller: Conduct technical deep-dive, demo integrations
   - Assumption: No additional scope creep from user feedback

2. [Continue for all milestones]

RISKS & MITIGATIONS
- Risk: Procurement unfamiliar with SaaS vendor category
  Probability: High | Impact: 2-week delay
  Mitigation: Provide SOC2 audit, reference customers, procurement playbook by [Date]
  Owner: [Your name]

TIMELINE SUMMARY
Next Milestone: [Milestone & Date]
Expected Signature: [Date]
Implementation Kickoff: [Date]

NEXT STEPS (This Week)
- Buyer: [Action], owner: [name], due: [date]
- Seller: [Action], owner: [name], due: [date]

SIGN-OFF
[Buyer Champion]: _____________________ Date: _______
[Your Name]: _____________________ Date: _______

Task-Specific Questions

Mode 1: Creating a MAP in Early-Stage Negotiation

• "What does your approval process look like, from where you are today to contract signature?"
• "Who all needs to be involved in the decision, and when do they typically get involved?"
• "What are your hard constraints—budget cycles, board meetings, fiscal year deadlines—that we need to plan around?"

Mode 2: Renegotiating a Slipping MAP

• "This milestone moved from March 20 to April 10. What changed, and what do we need to do to accelerate it?"
• "Is this timeline realistic given your internal processes, or should we revise it together?"
• "Are there any stakeholders who have not been involved yet who could accelerate the process?"

Mode 3: Recovering a Deal With a Broken MAP

• "Let's step back and rebuild the plan together. What would get this back on track for you?"
• "Which stakeholders need to be re-engaged to restore momentum?"
• "Is the timeline still realistic, or do we need to reset expectations?"

MAP Effectiveness in Practice

A well-executed MAP accelerates deals and prevents late-stage surprises. Consider a $500K SaaS deal where the salesperson identified that procurement was unfamiliar with SaaS vendors. Rather than assume procurement would be fast, the MAP built in a 2-week procurement review window with a mitigation plan: the salesperson provided vendor questionnaires, SOC2 audit, and reference customers from procurement's industry a week in advance. Procurement's actual review took 10 days—faster than planned because they were prepared. The deal closed on the revised target date with no final surprises.

Compare this to a similar deal without a MAP: the salesperson assumed a 3-week close, did not identify procurement early, and discovered at day 24 that procurement wanted a security questionnaire completed. That derailed the original timeline, required rushed responses that introduced errors, and the deal slipped 3 weeks. The buyer eventually bought, but lost confidence in the seller's planning capability.

The MAP is a force multiplier. It surfaces risks early, commits both parties, and creates a shared reference point. It also demonstrates to the buyer that you are serious, organized, and thinking through their process—not just your quota.

Another example: a deal where the champion is a liaison (not a decision-maker). Without a MAP, the champion says "I'll check with my team" and disappears for 2 weeks. With a MAP, that champion explicitly commits to "Schedule stakeholder alignment meeting by March 20," forcing them to own the timeline. The accountability of the MAP often reveals whether a champion is truly committed or just a friendly contact.

Quality Checklist

Use these criteria to verify your MAP is effective:

• All key stakeholders are identified by name and title, with buy-in status assessed
• Milestones are buyer-focused, not seller-focused (e.g., "Procurement approval" not "Send contract")
• Each milestone has a specific date based on the buyer's actual process, not your close date
• Each milestone includes both buyer and seller actions
• Assumptions are explicitly documented so hidden risks are visible
• Risks are identified and mitigation plans are assigned
• The MAP is signed or acknowledged by both parties, creating mutual commitment
• Weekly status updates are provided with transparent slip communication
• If milestones change, they are renegotiated, not silently extended
• The MAP is used as a conversation starter for weekly check-ins, not abandoned after creation

Related Skills

• Deal Qualification — Ensure only qualified deals make it to the MAP stage
• Pricing Negotiation — Use the MAP timeline to manage price discussions strategically
• Follow-up Sequences — Coordinate follow-ups with MAP milestone timing
• Pipeline Review — Track MAP progress in forecast scenarios

Example Prompts

• "I'm closing a $250K deal. Help me build a MAP with this company. Here's what I know about their approval process..."
• "This deal is slipping. The buyer keeps saying 'next week' but never commits. Should I create a formal MAP?"
• "My champion is a liaison, not a decision-maker. How do I use the MAP to surface who actually controls the decision?"
• "We're 10 days from close and procurement just got involved. How do I rebuild the MAP to include them without derailing everything?"
• "My buyer is ghosting me. Should I send a MAP refresh to re-engage them?"
• "Generate a weekly MAP status update for my deal. Here are the latest buyer updates..."