The Mutual Action Plan Co-Build

A 60-Minute Team Working Session Where Reps Draft Buyer-Aligned MAPs Before Legal or Procurement Stalls the Deal

Why Run This Session

Late-stage deals stall when the only plan in the system is the seller's. Reps email "next steps" lists that procurement ignores because no buyer owner, no buyer date, and no proof step ever appeared on the buyer's calendar.

A mutual action plan (MAP) nobody co-authored with the champion is a wish list. It creates false confidence in forecast calls until legal or security adds six weeks the rep never modeled.

This session installs a shared MAP template—milestone, buyer owner, seller owner, target date, exit criteria—and forces every rep to draft one on a live late-stage deal, pressure-test it in pairs, and store it where managers inspect pipeline before the next forecast.

Managers who skip this ritual pay for it in forecast calls: reps defend numbers they cannot tie to buyer-side evidence or CRM artifacts. Running the session quarterly keeps new hires from inheriting bad habits from shadow pipeline—and gives RevOps a consistent field to audit when conversion or stage velocity drops.

The hour is not enablement theater; it is the minimum viable discipline before you scale headcount or raise quota.

What Reps Will Walk Out With

• A five-column MAP drafted on one live late-stage opportunity
• At least two rows with named buyer owners (not "TBD" or "legal")
• Champion review script practiced with peer feedback
• MAP linked or pasted in CRM on the opportunity record
• Clear rule for when a lightweight email plan replaces a full MAP (ACV threshold)

Who Should Be in the Room

Account executives and managers; include deal desk or RevOps if they own stage definitions. Each rep brings one deal past solution confirmation—verbal yes or strong champion commitment—but not yet signed. Sub-$15K velocity deals can observe but should use the simplified MAP variant in Block 5.

Before the Meeting (Manager Prep — 15 Minutes)

1. Share the MAP row template (worksheet below) and a screenshot of where MAPs live in your CRM (note, object, or attached doc).
2. Manager selects two example MAPs from won deals—one good, one missing buyer owners—as teaching anchors.
3. Ask reps to confirm champion name and next meeting date before the session.
4. Legal or deal desk optional: provide average durations for security and legal rows for your company.

The 60-Minute Agenda

This session runs 0:00 to 1:00. The agenda blocks below sum to exactly 60 minutes.

Frame — Seller Plans vs. Mutual Plans (0:00–0:07, 7 minutes)

Show a stalled deal where the rep had internal tasks but no buyer dates. Manager says: "Procurement did not go dark—they were never on the plan." Rule: no buyer owner, no MAP row.

Facilitator script: Poll: how many late-stage commits lack a shared doc the champion has seen? Those are today's priority fixes.

CRM setup (first two minutes): Reps open late-stage opps and add a note "MAP draft — [date]" before teaching starts.

Close this block: Volunteer shares one missing buyer step that killed a past deal (security, board, budget freeze).

Timer and room mechanics (Frame — Seller Plans vs. Mutual Plans): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion.

Facilitator circulate: Walk the perimeter; sit with the quietest pair first. Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack.

Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing. These norms keep the block dense and protect the sixty-minute boundary.

Teach MAP Anatomy (Five Columns) (0:07–0:18, 11 minutes)

Walk each column with examples. Exit criteria must be observable: "MSA countersigned," not "legal progressing." Show how seller-only tasks (internal pricing approval) sit in a separate internal tab if needed—but buyer-facing MAP stays buyer-visible.

Facilitator script: Read a champion-forwardable email intro: three sentences, link to MAP, explicit ask for edits by date.

Live demo in CRM: If your CRM has a Mutual Plan object, create one live; otherwise attach Google/Word link in the opportunity.

Manager checkpoint: RevOps confirms forecast stage requires MAP link at Stage 4+ if that is your policy.

Timer and room mechanics (Teach MAP Anatomy (Five Columns)): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Solo Draft on a Live Deal (0:18–0:34, 16 minutes)

Sixteen minutes: minimum six rows, at least two buyer names, all dates within the fiscal period or marked at-risk.

Facilitator script: Ask "Who loses their job if this date slips?" on the riskiest row—surfaces real buyer owners.

CRM action (required before timer ends): Paste table into CRM note; link mutual doc in the opportunity header field if available.

Circulate and challenge: Flag any row where exit criteria is vague; rep rewrites before pair block.

Timer and room mechanics (Solo Draft on a Live Deal): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Pair Pressure-Test — Champion vs. Skeptic (0:34–0:48, 14 minutes)

Partner A plays skeptical champion ("legal is six weeks, you assumed two"). Partner B defends dates with evidence or moves dates. Swap.

Facilitator script: Interrupt optimistic dates: Manager says: "Evidence or move it right on the MAP."

Pair exercise rules: Skeptic must cite realistic durations from your company's last three similar deals when possible.

CRM action after swap: Update target dates in the MAP and CRM before leaving the pair.

Timer and room mechanics (Pair Pressure-Test — Champion vs. Skeptic): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion.

Facilitator circulate: Walk the perimeter; sit with the quietest pair first. Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack.

Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing. These norms keep the block dense and protect the sixty-minute boundary.

Champion Review Script & ACV Rules (0:48–0:56, 8 minutes)

Group writes the exact ask: "Here is our shared plan—what did we get wrong?" Reps with sub-$15K deals outline a three-line email MAP instead of six rows.

Facilitator script: Two reps read champion scripts aloud; room flags jargon and feature language.

Capture on whiteboard: Post ACV threshold for full MAP vs. Lightweight plan; RevOps aligns with stage definitions.

Each rep commits: Schedule champion MAP review meeting on the calendar before anyone leaves.

Timer and room mechanics (Champion Review Script & ACV Rules): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Commit — Publish and Forecast (0:56–1:00, 4 minutes)

Round-robin: deal name, next MAP milestone, buyer owner, date. Manager logs who published in CRM.

Facilitator script: Manager says: "Unpublished MAPs are not in Commit for this week's forecast."

Forecast / pipeline tie-in: Pipeline review agenda adds MAP checkpoint column starting next Monday.

Manager records in CRM or tracker: Manager runs report: late-stage opps without MAP link; assigns fix owners by EOD.

Timer and room mechanics (Commit — Publish and Forecast): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Agenda check: 7 + 11 + 16 + 14 + 8 + 4 = 60 minutes.**

Worksheet / Artifact

How to Use This With the Buyer

1. Send the MAP as a living doc before the call: "What did we get wrong?" invites edits and ownership.
2. Ask the champion to add rows you cannot see—procurement and InfoSec steps they know exist.
3. Use exit criteria as agenda items—each meeting advances one row to done with proof attached.
4. When dates slip, co-edit the MAP with the buyer instead of hiding slippage in private notes.

Manager Coaching Notes

• Rows without buyer owners are fiction—challenge them in pipeline review.
• Match MAP ceremony to ACV; do not bury small deals in enterprise process.
• Inspect CRM weekly: MAP date must move or the deal is not truly advancing.
• Celebrate champion edits; no edits often means no multi-threading.
• Pair with buying-process mapping (st0073) when blind spots appear in MAP rows.

The Bottom Line

A MAP is a forecast instrument, not a pretty slide. Reps who co-build buyer-owned steps see stalls before procurement goes dark—and managers who inspect MAPs in CRM stop confusing seller activity with buyer progress.