The Mutual Action Plan Co-Build — 60-Min Training

Why late-stage deals slip when nobody maps the path

The most expensive failure in B2B selling is not the lost deal — a loss frees the rep's time and sharpens the forecast. The expensive failure is the deal that neither closes nor dies: it sits in "commit" for three quarters, distorts the forecast, and finally either closes far too late to count or evaporates into "no decision." Sales-effectiveness research has documented for years that "no decision," not a competitive loss, accounts for a large share of stalled pipeline.

Deals slip because the buyer's journey is mostly invisible. Gartner's B2B buying research finds a typical buying group now spans 6 to 10 stakeholders, and buyers spend only about 17% of the purchase journey actually meeting with potential suppliers. That means for every hour a rep spends with a buyer, roughly five hours of buying activity — internal alignment, a security questionnaire routed to an analyst the rep has never met, a finance review tied to an approval threshold nobody asked about — happen with the rep nowhere in the room. Security reviews, legal redlines, procurement intake, and signature routing live only inside the buyer's organization, and a rep who cannot see them cannot forecast them.

A Mutual Action Plan attacks exactly this gap. It does not give the rep a seat in those internal meetings; it does something nearly as good — it names them, dates them, and assigns them, so that when one stalls, the rep knows within a week instead of within a quarter. The MAP is the cheapest intervention available: it costs roughly ten minutes on a verbal-yes call, requires no budget, and converts the most uncertain category in the forecast into something a manager can actually inspect. That is why it earns 60 minutes of a team's week.

The five-step CO-BUILD motion

A MAP is not a document you write — it is a conversation you facilitate. The mnemonic CONFIRM, CHART, COMMIT, CADENCE, CLOSE is built so a rep can hold the whole motion in their head on a live call.

CONFIRM — before you build anything, confirm there is a real deal to plan: a compelling reason to act by a date, a measured outcome, and someone who can commit their side. This maps to the MEDDICC elements Metrics, Decision Process, and Champion. Building a MAP on a soft yes just produces a tidy document attached to a dead deal.

CHART — co-build the milestone list on a shared screen, working backward from the go-live date the buyer cares about. Back-casting is the technical heart of the step: if go-live is October 1, then onboarding starts mid-September, which means signature by early September, redlines finished in August, security review started in July. The buyer suddenly feels a July deadline for a step they had not even mentioned — the rep did not create urgency, the rep made the buyer's existing urgency visible. Write milestones in the buyer's vocabulary, not methodology jargon.

COMMIT — every milestone gets a named human owner and a date, spoken out loud by the buyer. Not "legal" — a person. Not "next week" — a date. Reframe the date as the buyer's protection: "if procurement intake doesn't start by the 15th, your October go-live is at risk." There is a hierarchy of owner quality: best is a named individual the rep has met, acceptable is a named individual with a path to them, weak is a role, unacceptable is a team.

CADENCE — agree a recurring 15-minute weekly review to walk the plan, color each milestone green/yellow/red, and re-date anything that moved. A MAP reviewed once is a document; a MAP reviewed weekly is a process. Frame it to the buyer as a "go-live tracking review," never a "sales check-in."

CLOSE — use the MAP as the closing instrument. You never "ask for the close" again; you ask "are we still on track for milestone 6?" When the last milestone before signature is green, the signature is the natural next line. Reps who run a real MAP describe the close as anticlimactic — which is exactly the goal.

The two "No" branches are the most valuable outputs. A "No" at CONFIRM sends the rep back to discovery before any planning time is wasted. A "No" at the COMMIT gate — a buyer who will not date their own milestones — is a slip signal arriving weeks or months early. Teach the room to want those answers: an early "No" is cheap, a quarter-end "No" is expensive.

What belongs on a real MAP

Most slipped deals stall on the same five hidden steps, and reps consistently under-estimate how long each takes. Security or InfoSec review typically surfaces after the verbal yes and runs 2 to 6 weeks. Legal and MSA redlines run 1 to 4 weeks and usually cannot finish until security clears, because security findings sometimes change contract language. Procurement or vendor intake runs 1 to 3 weeks and can often run in parallel with legal. Budget or finance sign-off runs 1 to 2 weeks, tied to an approval threshold. Signature and routing take 2 to 7 days.

Walk the room through the arithmetic: even when nothing goes wrong, the gap between "verbal yes" and "signed" can realistically run seven to sixteen weeks. A rep who forecasts a verbal-yes deal to close "this month" without a MAP is not optimistic — they are uninformed. A subtle CHART skill is teaching the buyer which milestones can run in parallel and which must run in series; a rep who helps parallelize the independent steps can compress a sixteen-week path to ten, which is real deal acceleration the buyer thanks you for because it is their timeline you protected.

A real MAP carries: the buyer's target outcome and go-live date; every milestone from today to first value; a named human owner and a date on each; a status field; and the review cadence. It does not carry your CRM forecast category, your commission math, or marketing boilerplate — those would make the buyer feel managed. The test is simple: a working MAP is a document the buyer would be comfortable forwarding to their own CFO without a single line reading like vendor jargon.

Consider a representative $90K annual mid-market SaaS deal, verbal yes in week six, go-live wanted before the buyer's Q4 planning cycle. A well-built MAP lists roughly eight milestones and the buyer owns six of them — correct, because most of the path is the buyer's internal work. One line may honestly read "owner TBD"; that is a flag telling the rep exactly what the next cadence review must resolve, not a failure. The buyer-side milestones spread across three different named people — the InfoSec analyst, in-house counsel, and the procurement specialist — so that if the champion leaves, the plan survives. Tooling from Salesforce, HubSpot, DocuSign, and deal-collaboration platforms like DealHub, Aligned, GetAccept, and Recapped ships MAP templates natively, but the tool is not the point: a MAP built in a shared Google Doc with genuine two-sided ownership beats the most sophisticated platform emailed at the buyer.

The three failure modes and the 60-minute agenda

If reps learn nothing else, they should learn to recognize the three artifacts that look like a MAP and function like nothing. The emailed MAP is built alone and sent as a PDF — the buyer never agreed out loud, so they own nothing; the tell is asking "did the buyer say any of these dates out loud?" The single-threaded MAP puts one buyer-side name on every line, so a single resignation, leave, or reorg orphans the whole plan; with buying groups of 6 to 10 people, a real MAP names the security, legal, and procurement contacts separately. The frozen MAP is built right and then never reopened — it is stale within two weeks and is the most insidious failure because the build was genuine before the cadence lapsed and all its value evaporated.

The training installs the motion in one room across five blocks totaling exactly sixty minutes. An 8-minute intro and cold open contrasts two real deals — one that slipped three quarters unmapped, one co-built that closed on the date the MAP predicted within days — so the room feels the cost before hearing a tactic. A 22-minute teach covers the CO-BUILD motion, the milestone durations, and the three failure modes, with the goal that every rep can recite the five steps without notes. A 12-minute discussion audits at least three live deals against a MAP-discipline scorecard written on the whiteboard. A 15-minute role-play has an AE co-build a MAP live with a VP who says "just send me the contract" and later deflects on the security date. A 3-minute debrief closes with each rep committing to one deal, one buyer-owned milestone, and one review cadence.

The scorecard scores each commit-stage deal 0-5, one point each for: a written MAP the buyer co-built live, a named owner on every milestone, a date on every milestone, the buyer owning at least three milestones, and a weekly cadence being honored. Four or five is legitimately forecastable, two or three is at-risk and coached this week, zero or one is not a commit deal at all. This scorecard is the bridge to forecast-call discipline: the rule "no MAP, no commit" is only enforceable when there is an objective test of what counts as a real MAP.

When a MAP is the wrong move

A MAP is a powerful tool, not a universal one, and a training that teaches "always build a MAP" produces reps who run the motion mechanically and lose the trust of sophisticated buyers. Coach the room on when to skip it, scale it down, or wait.

A $4K single-signer renewal on a credit card has no hidden procurement or security path; a full eight-milestone MAP there is theater, and a two-line email confirming the close date is the entire plan. When CONFIRM fails — no compelling event, no economic buyer, no metric — a MAP does not manufacture urgency or authority; it just attaches a neat document to a deal that was never real, so stay in discovery. In procurement-led organizations, a MAP presented as "our standard close plan" and driven from the vendor's screen in vendor language reads as forecast management and adds friction; if you cannot get genuine two-sided ownership, a quietly tracked internal plan is more honest than a fake "mutual" one.

In hyper-relational or founder-led sales, pulling out a structured milestone grid mid-conversation can break the rapport that is the buying process; capture the same discipline conversationally — "you'll loop in your ops lead Thursday, I'll have the order form over by Friday" — and follow up in writing without the formal artifact. And occasionally a clean champion-built MAP gets yanked into a procurement RFP that resets the rules; do not cling to the obsolete plan, rebuild a new one with the procurement owner as a named participant. A MAP earns its place when a deal has a real multi-stakeholder buying process, genuine qualification behind it, and a buyer willing to co-own the plan. The skill is not "always build a MAP" — it is knowing which deals need one, and a rep who can name the deal on their list where a MAP would be wrong actually understands the tool.

Making the skill transfer: role-play and follow-through

Understanding the motion and running it under live resistance are different competencies, and only the second one closes deals — which is why the role-play block is protected and never compressed. The buyer resists twice: first "we really don't need a formal plan," second "I can't give you a date for security, that's not my team." The first is a framing test — a passing rep reframes instantly ("ten minutes now protects your go-live date, because I've watched deals this clean lose six weeks to a security review nobody flagged"), recasting the MAP as the buyer's insurance policy rather than the vendor's tracking sheet. The second is a multi-threading test — a passing rep does not need the date from the VP, only a name: "you wouldn't own that date; who would? Introduce me to whoever runs InfoSec intake and I'll bring the realistic timeline back to this plan." That converts a dead end into a new named owner, the direct defense against the single-threaded failure mode.

Three failure patterns recur. The rep who lectures the MAP for two minutes while the buyer's eyes glaze — fix: build by asking ("walk me through what has to happen on your side"), not telling. The rep who accepts "TBD" and moves on — fix: TBD on a date is acceptable, TBD on an owner is not, so always convert the deflection into a name. And the rep who builds a beautiful MAP then reverts to habit with a cold "so, are you ready to move forward?" — fix: the close is the MAP, "milestone 7 is signature and 1 through 6 are green, so shall we target the 14th?"

The training's value is realized in the following week's pipeline review, not in the room. The manager opens that review by reading the commitments back verbatim and asking each rep to show the MAP; a "commit" deal with no co-built MAP gets moved out of commit on the spot, no debate. The first time a manager actually does that, the team learns the rule is real, and the next round of MAPs gets built without being asked. The three-part commitment — one deal, one milestone, one cadence — is deliberately small, because a too-big ask ("MAP your whole pipeline by Friday") is just a polite no, and a commitment that cannot be verified next week is a commitment that did not happen.

Related questions

How is a MAP different from an internal close plan?

An internal close plan is one-sided and private — the rep's own to-do list. A MAP is two-sided and shared: the buyer sees their own dated commitments and the rep sees the buyer's, and the buyer agreed to each line out loud. That mutual visibility is the entire mechanism; a plan the buyer never co-owned is just the rep's homework.

Who should own each milestone on the MAP?

A named human, never a team. "Legal," "procurement," or "security" is a line with no real owner. Walk every line up a hierarchy — best is someone you've met, acceptable is someone with a path to them, unacceptable is a role or a team — until each names an individual who can move that step.

What does it mean when a buyer won't commit a date?

It is data, and good data. A buyer who genuinely intends to buy will give a rough date for their own internal step because the date costs them nothing. A refusal signals the internal commitment behind the verbal yes is not there yet. Don't push for the date — go back to CONFIRM and find what's missing.

How often should the MAP be reviewed?

A recurring 15-minute weekly review during the active deal, framed to the buyer as a go-live tracking session, not a sales check-in. Walk the plan top to bottom, color each milestone green, yellow, or red, ask "what does this line need and who owns it," re-date what moved, and book the next slot before hanging up.

Does a MAP work for small transactional deals?

No. A single-signer deal with a credit card and no hidden security or procurement path does not need an eight-milestone plan; that is theater. Reserve the MAP for multi-stakeholder deals with a real 60-to-180-day buying process. The skill is proportionality — match the weight of the plan to the weight of the buying process.

FAQ

How long should this training run? Sixty minutes is the default: 8 for the cold open, 22 to teach, 12 to discuss, 15 to role-play, 3 to commit. For a quarterly kickoff you can extend to 90 minutes with a longer role-play, but never compress below 60 — the role-play is where the deal-quality lift actually happens, and it is the first thing a rushed session sacrifices.

Should the AE or the manager facilitate? The manager facilitates and the AEs participate. The manager brings three slipped deals from last quarter with their original close dates, a blank MAP template, and the team's current stage-conversion and slip-rate numbers, so the discussion audits real pipeline rather than staying abstract.

What is the single biggest mistake running it? Letting it decay into a status meeting. The minute the manager opens with "let's go around the room with updates," the training collapses. Hard-anchor on the written agenda, keep the discussion tied to live deals on the whiteboard, and end with a recorded, verifiable commitment from every rep.

How do you measure whether it worked? Track three metrics weekly: rep adoption of co-built MAPs on commit-stage deals, forecast-accuracy delta versus baseline, and win-rate lift on the relevant deal segment. The leading indicator is simpler — how often a "commit" deal slips and surprises the manager. That number is the size of the problem, and it should fall.

What if the buyer says "just send me the contract"? Reframe it as protecting their timeline, not yours: "Happy to send it today — and before I do, ten minutes to map the path from signature to go-live, because deals this clean still lose weeks to a security step nobody flagged." The MAP becomes insurance on the buyer's launch date, not paperwork for the rep's forecast.

How does this fit alongside an LMS certification? They are complementary. Use a self-paced LMS for the theory of what a MAP is; use this 60-minute live working session for the practice, where reps run the motion under genuine buyer resistance. Theory learned alone does not survive first contact with a VP who deflects — the role-play is what makes the skill transfer.

Sources

• Gartner — B2B Buying Journey research (buying groups of 6–10 stakeholders; ~17% of the journey with suppliers): https://www.gartner.com/en/sales/insights/b2b-buying-journey
• Korn Ferry (formerly CSO Insights) — Sales Performance and buyer-engagement research: https://www.kornferry.com/capabilities/sales-effectiveness
• Matthew Dixon & Brent Adamson, *The Challenger Sale* — teaching the buyer to buy and back-casting the path: https://www.challengerinc.com/
• Andy Whyte, *MEDDICC* — the qualification methodology and the "Paper Process" element: https://meddicc.com/
• Winning by Design — the SPICED framework and Mutual Action Plans: https://winningbydesign.com/
• Force Management — Command of the Message and the Mutual Plan: https://www.forcemanagement.com/
• Sandler Training — the Up-Front Contract and "no mutual mystification": https://www.sandler.com/
• Salesforce — opportunity and forecast management: https://www.salesforce.com/products/sales-cloud/
• HubSpot — deal management and pipeline tooling: https://www.hubspot.com/products/sales
• DocuSign — e-signature and agreement workflow: https://www.docusign.com/

Related on PULSE

• [Sales Forecasting Accuracy: Template for a Team Meeting Focused on Data Hygiene](/knowledge/st0796)
• [The Sandler Selling System: Ready-to-Run Mini-Training for New Hires](/knowledge/st0794)
• [Overcoming Call Reluctance: Coaching Template for a Weekly Morning Huddle](/knowledge/st0793)
• [Selling with Stories: Narrative Structure Template for a 45-Minute Sales Workshop](/knowledge/st0792)
• [Account Planning for Enterprise Deals: Template for a Collaborative Team Exercise](/knowledge/st0791)