Builds a mutual action plan (MAP) with shared milestones, named owners, and buffer-padded dates that drives a qualified deal from verbal intent to signature and go-live. Use when someone asks "build a mutual action plan for this deal", "how do I keep this deal from stalling", "the buyer said yes but nothing is moving", or once a prospect is qualified and has expressed intent to move forward. Do NOT use for preparing the qualification call itself - use discovery-call-prep instead. Do NOT use for scripting the negotiation and close conversation - use closer-sales-script instead.
Click to play with sound.
---
name: Mutual Action Plan
description: Builds a mutual action plan (MAP) with shared milestones, named owners, and buffer-padded dates that drives a qualified deal from verbal intent to signature and go-live. Use when someone asks "build a mutual action plan for this deal", "how do I keep this deal from stalling", "the buyer said yes but nothing is moving", or once a prospect is qualified and has expressed intent to move forward. Do NOT use for preparing the qualification call itself - use discovery-call-prep instead. Do NOT use for scripting the negotiation and close conversation - use closer-sales-script instead.
---
# Mutual Action Plan
A mutual action plan is a shared document that aligns 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 a vendor's wishlist, and the deal it was supposed to protect will stall in legal, procurement, or a budget cycle nobody mentioned. The costly mistake this skill prevents is discovering a six-week security review three weeks before the quarter ends.
## Operating procedure
Steps run in this order because dates cannot be set before milestones are known, and milestones cannot be known before the buyer has contributed theirs.
### Step 1: Gather inputs
Collect before drafting anything. Label guesses as guesses.
1. Deal stage and evidence of intent - a MAP before clear evaluation intent is premature. Default assumption: qualified with verbal intent.
2. Buyer's desired go-live date, or the business event driving urgency. If neither exists, that absence is a finding (see Step 3).
3. Known buyer-side steps: security review, legal, procurement, budget approval, board sign-off. Default: unknown, to be elicited from the buyer.
4. Deal size and cycle length. A sub-30-day, low-complexity deal gets the lightweight variant (see Escape hatch).
5. Names or roles for owners on both sides.
### Step 2: Introduce the MAP to the buyer
… load the full skill through Skill Me