Mutual action plan builder

Purpose

A Mutual Action Plan (MAP) is a shared roadmap that helps the buyer work through their own buying process toward value. It is not a close plan. A close plan tracks what the seller does to push the deal to signature, and buyers ignore it. Built properly, a MAP turns skepticism into partnership and forces one honest question at every step: what has the buyer actually achieved, not what did we send them?

When to use

Run this on a live deal when any of these are true:

• The champion asks what the next steps are, or how to get this over the line.
• You are entering scoping, POC, security review, legal, or procurement.
• The deal has slipped once, or stalled with no written, mutual timeline.
• You cannot name who on the buyer side owns each decision gate.
• The buying committee is larger than your one champion.
• You are about to send a "next steps" email and want the buyer to co-own a plan instead.

Do not run this on a deal whose need and value are not yet validated. A MAP only lands when both sides work toward value the buyer has agreed to. On an unqualified deal it produces a document nobody believes.

Route elsewhere when:

• The question is pipeline hygiene, coverage, or stage aging across deals. Use pipeline-review.
• One deal is stuck, ghosted, or blocked by an objection. Use deal-blocker-maneuvers.
• You need to map and widen the buying committee itself. Use multi-threading-coach.

Inputs

Collect these first. Where something is missing, do not fill it in. Mark it [CONFIRM WITH BUYER] and make confirming it the first buyer task.

• Deal context: company, champion (name and role), stage, expected or contracted close date, and deal value if known.
• The business problem and the desired outcome, in the buyer's words. A direct quote or close paraphrase from a call is best.
• Everyone involved: every stakeholder you know of (security, legal, procurement, finance, executive sponsor, end users, IT or RevOps), with name, role, and sentiment if known.
• The buyer's timeline and its driver: the reason behind the date (board commitment, fiscal year, launch, cost pressure).
• The buyer's internal process: the security, procurement, and approval steps they must run, and any board or signature gates.
• Your seller-side steps: what you, your SE, legal, CS, and your executive sponsor must do to support them.
• Success criteria: what the buyer expects after close, such as onboarding time, cost saved, or revenue enabled.

If the value summary, the buying committee, or the timeline is missing, treat confirming them as the first buyer-evidence milestone (see Step 6).

Procedure

Step 1: Write the value summary in the buyer's words

Write two or three sentences on the benefit to the buyer. Describe what they get, not what you sell. Where you can, lift the buyer's own phrasing from the call. If you only have your own pitch, label it as a draft and schedule its confirmation.

• Weak (seller voice): "Aligned helps you manage deals with digital sales rooms and mutual action plans."
• Strong (buyer voice): "We want to cut enterprise deal cycle time by about 30%, and give our AEs one room where every stakeholder can self-serve, so we stop losing momentum to email and missing executives."

Keep it concrete and tied to an outcome the buyer cares about. Use no adjectives the buyer would not use themselves. Where a figure appears, it must come from the buyer or a source you can cite. Never invent one.

Step 2: Map the full buying committee

List every stakeholder in the purchase decision, not only the champion. For each person record:

• Name, role, and the buyer job they own.
• Current stance: supportive, neutral, skeptical, blocker, or unknown.
• What this person needs to say yes, and what buyer evidence would show they are on board.

You usually influence a committee, not a single person. Unknown names become [CONFIRM WITH CHAMPION] items. Confirming them is a buyer task, because only the buyer knows their own organization.

Step 3: Write milestones as buyer evidence, not seller activity

This is the core of the method. Rewrite every milestone as evidence the buyer can point to, a state they have reached.

• Seller activity (wrong): "Demo done," "Proposal sent," "Follow-up call completed."
• Buyer evidence (right): "Problem agreed across the team," "Vendor shortlisted," "Timeline and its driver agreed," "Impact validated by multiple stakeholders," "Executive sponsor has assigned a team," "Security review passed," "Procurement terms approved," "Signature authority confirmed."

If a milestone starts with a seller verb ("we send," "we deliver," "we follow up"), rewrite it. Seller actions still exist. They become the supporting tasks under a buyer milestone (Step 5).

Step 4: Work backward from the buyer's timeline

Anchor the plan to the buyer's target date and the reason for it, then work backward through the milestones. The sequence:

1. Confirm the need and the value.
2. Work backward from the buyer's timeline.
3. Share your process and align it with theirs.
4. Identify all stakeholders.
5. Agree expectations for the partnership.
6. List the tasks.
7. Set a timeline and an owner for every task.
8. Set up tracking, then review regularly.

If there is no firm date, or no reason behind it, that is a red flag. The deal is not yet a real MAP candidate. Make "timeline and its driver agreed with the champion" the first buyer-evidence milestone.

Step 5: Give every task one owner and one date, on both sides

Under each buyer-evidence milestone, list the tasks needed to reach it. Give each task one named owner and a target date. Owners come from both sides: buyer stakeholders and your own team. Shared ownership is the point. A task without an owner or a date is a wish.

Structure each milestone block as:

• Milestone: a buyer-evidence statement.
• Why it matters: one line linking it to the value summary or a decision gate.
• Buyer-side tasks: each with an owner and a date.
• Seller-side tasks: each with an owner and a date.
• Milestone owner: the one buyer accountable for declaring it done.
• Target date for the milestone.

Step 6: Handle gaps honestly

Expect to run this mid-deal, when information is incomplete. For each gap, do one of three things:

• If the gap undermines the plan's credibility (value summary, timeline, executive sponsor, security or procurement process), make confirming it the first buyer-evidence milestone and the first buyer task.
• If it is a stakeholder you cannot name, write the role and mark it [CONFIRM WITH CHAMPION]. The buyer supplies the name.
• If it is an unknown date or dependency, mark it [TBD] and add a task to confirm it before the dependent milestone can be scheduled.

Never invent a stakeholder name, a date, or a buyer quote. A MAP built on guesses does more damage than no MAP, because it spends the trust the plan is meant to build.

Step 7: Frame it for co-creation

Present the plan as a draft for the buyer to edit, not a finished document. Flag the sections you want them to change:

• Value summary: "Is this how you would describe the win?"
• Stakeholder list: "Who are we missing?"
• Timeline and driver: "Is this the real date, and what sits behind it?"
• Every [CONFIRM] and [TBD] item.

An opening message to the champion should state the intent plainly. For example: "I've drafted a shared plan so we both know how this gets done on your side. It's a draft, not a prescription. Can you tear it apart and tell me what I've got wrong about your process?"

The message is an external send. It goes to the approver first.

Step 8: Set the tracking and review cadence

A MAP is a living document. State the review cadence: a recurring check-in, typically weekly and tied to milestone completions, where both sides update status, raise slippage early, and adjust. Record where the plan lives and who can edit it. Deals rarely follow the first version of the plan. Regular review keeps it accurate. Put the recurring check-in in the calendar as part of the deliverable.

Output

A single MAP document containing:

• Value summary: two or three sentences in the buyer's words.
• Stakeholder list: the full committee with roles, buyer jobs, stances, and one milestone owner per person.
• Timeline and driver: the target date and the reason for it, worked backward.
• Milestones: each written as buyer evidence, with buyer-side and seller-side tasks, owners, and dates.
• Co-creation prompts: the sections flagged for the buyer to edit, and the opening message to the champion.
• Review cadence: where the plan lives and how often both sides review it.

Quality bar

A strong MAP reads as if the buyer wrote half of it. The value summary sounds like something their executive would say in a budget meeting, not like your landing page. The stakeholder list names people you have actually spoken with; where it does not, it asks the champion to fill the gap instead of hiding it. Every milestone is something the buyer can point to and say "yes, that happened." Nothing reads "proposal sent" or "demo delivered" as progress.

Check that:

• Every milestone is written as buyer evidence, not seller activity.
• The value summary uses the buyer's words, and every figure traces to the buyer or a cited source.
• Every task has one owner and one date, drawn from both sides.
• Every unnamed stakeholder, missing date, and open dependency carries a [CONFIRM WITH CHAMPION] or [TBD] marker.
• The plan is framed as an editable draft with explicit co-creation prompts.
• A recurring review check-in is named and calendared.

Signs it is working

• The champion edits the draft and sends it to people you have never heard of. The buying committee is showing itself, which is the purpose.
• You hear dates and constraints you did not know about, because the plan made them safe to share.
• Slippage appears as a milestone moving, not as silence. You see the risk weeks before the close date disappears.
• Both sides hold tasks with their names on them. The buyer does real work, not only receives yours.

Anti-patterns

• A close plan in disguise. Every milestone is something the seller does. Rewrite each one as buyer evidence. If you cannot, the buyer is not really engaged yet, so go back and validate value before drafting.
• Only the champion is listed. A committee of one dies when that person goes on leave or changes role. Map the wider group, and treat unknown members as the first milestone.
• No timeline, or no driver behind it. A date without a reason is a guess, and without the reason you cannot protect the date or re-anchor it when it slips.
• Too complex. A plan that looks daunting is built for the seller's comfort, not the buyer's ease. Cut it. A MAP should simplify the buying process.
• Set and forget. A plan nobody reviews is dead on arrival. If there is no recurring check-in, add one.
• No co-creation framing. A document presented as finished reads as your sales tool, and the buyer ignores it. It arrives visibly as a draft with clear invitations to edit. The method depends on that.
• Invented details. A fabricated stakeholder, date, or quote is a trust problem. Leave the markers in place and let the buyer fill them.

Rules

• Never invent a stakeholder name, a date, or a buyer quote. Leave the marker in place and let the buyer fill it.
• Use business contact data only. Do not record personal emails, phone numbers, or private account details.
• Nothing leaves the building without a named approver. The opening message to the champion is an external send; stage it and get approval before any send.

Before you send the plan or the opening message, ask: who is the named approver releasing this?