The Mutual Action Plan Co-Build: Building a Written Plan-to-Close WITH the Buyer So Late-Stage Deals Stop Slipping — a 60-Minute Sales Training

Direct Answer

Late-stage B2B deals do not slip because the buyer went cold. They slip because nobody wrote down — and nobody owned — the steps between "yes" and "signed." Security reviews, legal redlines, procurement intake, budget thresholds, and signature routing live only inside the buyer's organization, and a rep who cannot see them cannot forecast them.

The fix is a Mutual Action Plan (MAP): a jointly owned, written, date-stamped plan that lists every milestone from verbal agreement to signed contract to first value, with a named human owner and a due date on each line. The discipline that produces a real MAP — not an emailed PDF the buyer never agreed to — is the 5-step CO-BUILD motion: CONFIRM, CHART, COMMIT, CADENCE, CLOSE. This is a 60-minute sales training that teaches a manager to install that motion in one room: an 8-minute cold open contrasting a slipped deal with a co-built one, a 22-minute teach of the motion plus the three failure modes, a 12-minute discussion auditing live deals, a 15-minute role-play under genuine buyer resistance, and a 3-minute debrief where every rep commits to co-building one MAP this week.

Run it and your "commit" category stops being a wish and starts being a forecast.

TL;DR

• The problem: the buyer's journey is mostly invisible to the rep — Gartner's research finds buyers spend only ~17% of the purchase journey with suppliers, and buying groups now run 6-10 stakeholders. The hidden 83% is where deals slip.
• The artifact: a Mutual Action Plan — written, date-stamped, milestone-by-milestone, with a *named* owner and date on every line, co-owned by the buyer.
• The motion: CO-BUILD — CONFIRM (real deal?), CHART (back-cast milestones live), COMMIT (named owner + date on every line), CADENCE (weekly 15-min review), CLOSE (signature is the last green milestone).
• The three failure modes: the *emailed MAP* (buyer never agreed out loud), the *single-threaded MAP* (one buyer name on every line), the *frozen MAP* (built once, never reviewed).
• The agenda: 60 minutes — Intro 8, Teach 22, Discussion 12, Role-Play 15, Debrief 3.
• The counter-case: a MAP is wrong for transactional single-signer deals, unqualified deals, buyers who read it as vendor process, hyper-relational founder sales, and deals overtaken by a procurement RFP.
• The outcome: every rep leaves having committed to co-build one MAP, name one buyer-side owner, and set one review cadence — checked at next week's pipeline review.

THE PULSE TRAINING

📋 The Pulse Training

Who this is for: B2B account executives, sales managers, and RevOps leaders running mid-market and enterprise deals that keep slipping a quarter. This is a process training — it works for SaaS, services, manufacturing, and any considered B2B purchase with multiple stakeholders and a 60-to-180-day cycle.

What teams leave with: A repeatable way to co-build a written Mutual Action Plan (MAP) with the buyer — a jointly owned, date-stamped, milestone-by-milestone plan that runs from verbal agreement to signed contract to go-live. Teams leave able to run the 5-step CO-BUILD motion (CONFIRM → CHART → COMMIT → CADENCE → CLOSE), plus the three failure modes that turn a MAP into a dead document.

Manager brings: (1) Three slipped deals from last quarter with their original close dates. (2) A blank MAP template. (3) The team's current stage-conversion and slip-rate numbers.

This entry sits in the deal-execution wing of the Pulse Sales Trainings library. It is the structural complement to the forecast-inspection training in (st0037): one training builds the plans, the other inspects them. If your team's "commit" category has a credibility problem — if the number the team forecasts and the number that closes diverge quarter after quarter — this is the training that closes the gap.

It does not require new tooling, a new CRM field, or a methodology overhaul. It requires one disciplined conversation, run the same way every time, on every late-stage deal.

Why this training, and why now

The single most expensive failure in B2B selling is not the lost deal. A lost deal is a known quantity — it frees the rep's time, it sharpens the forecast, it teaches a lesson. The expensive failure is the deal that *neither closes nor dies* — the deal that sits in "commit" for three quarters, consumes pipeline reviews, distorts the forecast, and finally either closes far too late to count or quietly evaporates into "no decision." Sales-effectiveness research from CSO Insights (now part of Korn Ferry) has documented for years that "no decision" — not a competitive loss — accounts for a large share of stalled pipeline.

The deals are not lost to a rival. They are lost to inertia, to the buyer's own internal complexity, to a path nobody mapped.

A Mutual Action Plan is the cheapest, most direct intervention against that failure. It costs ten minutes on a verbal-yes call. It requires no budget.

And it converts the most uncertain category in the forecast — late-stage "commit" deals — into something a manager can actually inspect. That is why this training earns 60 minutes of a sales team's week.

MEETING AGENDA — 60 MINUTES

Agenda math: 8 + 22 + 12 + 15 + 3 = 60 minutes. The blocks are sequenced so energy peaks in the role-play, when the room is applying the motion under pressure, and lands on a concrete commitment. Do not let the teach overrun — every minute stolen from the teach is stolen from the role-play, and the role-play is where the skill actually transfers.

🎯 Bottom Line

Late-stage deals do not slip because the buyer went cold. They slip because nobody wrote down what has to happen between "yes" and "signed" — and the steps that live only in the rep's head (security review, legal redlines, procurement intake, budget sign-off) surface one at a time, each one a fresh surprise.

A Mutual Action Plan drags those steps into daylight and puts a date and an owner on every one. Co-built with the buyer — not emailed at them — it becomes the deal's shared source of truth. Run the 5-step CO-BUILD motion and your forecast stops being a guess.

SECTION 1 — INTRO + COLD OPEN (0:00-0:08)

The cold open exists to do one thing: make the room *feel* the cost of an unmapped deal before they hear a single tactic. Do not open with theory. Open with two deals — ideally two real ones from the manager's own team, named only by initials — that started in nearly identical positions and ended in completely different places.

1.1 — The two-deal cold open

Deal A — the unmapped deal. A rep got verbal approval from a VP in week 6 of a 90-day cycle, said "great, I'll send the contract," and went quiet. The contract sat in a security review nobody mentioned for five weeks, then hit legal, then procurement opened a new vendor intake.

The deal closed — eleven months later, in a different fiscal year, after being forecast as "commit" three times. The rep was not lazy and the buyer was not dishonest. The rep simply could not see the path, so the rep could not forecast it, and every hidden step arrived as a surprise that reset the clock.

Deal B — the mapped deal. Same deal size, same buyer seniority, same product, same competitive context. The rep, on the verbal-yes call, said: "Let's spend ten minutes mapping what happens between now and go-live so neither of us gets surprised." They built a MAP together — eight milestones, dates, named owners on both sides.

Security review was milestone 3. It surfaced on day one, not day forty. The InfoSec analyst's name was on the line, and the rep had a contact to chase.

The deal closed inside the quarter, on the date the MAP predicted within four days.

The difference was not effort or charisma or discounting. It was that one rep made the path visible and the other guessed. Put both deals on the whiteboard side by side and ask the room a single question: *"Which of these two reps had a better quarter — and which one had a better forecast?"* The answer is the same rep, and that is the entire point of the training.

1.2 — Naming the discipline

The MAP is not a Pulse invention. It is a long-recognized discipline that appears under different names across every major sales methodology, which is itself a signal of how fundamental it is:

• The "close plan" and "Paper Process" in MEDDICC / MEDDPICC — the second P explicitly stands for *Paper Process*, the sequence of legal, security, and procurement steps a contract must traverse.
• The "Mutual Plan" in Force Management's Command of the Message practice.
• The "Mutual Action Plan" as a recurring-revenue artifact in Winning by Design's SPICED framework.
• The "compelling event" back-casting taught in The Challenger Sale, where the rep teaches the buyer their own path.

When a discipline shows up independently in four serious frameworks under four names, it is not a fad. It is load-bearing. The training's job is to make the room *do* it, consistently, not just nod at it.

1.3 — Why deals slip: the numbers

The slip problem, quantified. Gartner's widely cited B2B buying research finds the typical buying group now spans 6 to 10 stakeholders, and that buyers spend only about 17% of the purchase journey actually meeting with potential suppliers — the rest is internal work the rep cannot see.

Gartner also reports that customers who perceive the information they receive as helpful in advancing the purchase are 2.8x more likely to close a high-quality, low-regret deal. Separately, sales-effectiveness studies (CSO Insights / Korn Ferry, and CRM-pipeline analyses published by Salesforce and others) have repeatedly shown that roughly half of forecasted deals fail to close in the quarter they were committed, and that "no decision" — not a competitive loss — accounts for a large share of pipeline that simply stalls.

A MAP attacks exactly this gap: it converts the invisible 83% of the buyer's journey into a dated, owned, inspectable list.

Read that 17% number to the room slowly. It means that for every hour a rep spends with a buyer, roughly five hours of buying activity happen with the rep nowhere in the room — internal alignment meetings, security questionnaires routed to an analyst the rep has never met, a finance review tied to an approval threshold the rep has never asked about.

The MAP does not give the rep a seat in those 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.

A Mutual Action Plan is a jointly owned, written, date-stamped plan listing every milestone from verbal agreement to signed contract to first value — with an owner and a due date on each line. The word that matters is *mutual*: the buyer has their own milestones, their own due dates, and they agreed to them out loud.

🟡 Coach Note

Do not let the room call this "a glorified to-do list." A to-do list is one-sided and private. A MAP is two-sided and shared — the buyer can see their own commitments and the rep can see the buyer's. That visibility is the entire mechanism. Ten minutes, hard stop at 0:08.

1.4 — The forecasting cost of an unmapped deal

Before leaving the cold open, make one more point explicit, because it is the point that earns the training its place on the calendar. An unmapped deal does not just risk slipping — it actively *corrupts the forecast*, and a corrupted forecast costs the whole company, not just the rep.

Walk the room through the chain of consequences. When a rep forecasts a verbal-yes deal as "commit" for the current month with no MAP behind it, the manager rolls that number up. The director rolls the manager's number up.

The VP of Sales presents the rolled-up number to the CFO. The CFO uses it to make hiring, spending, and investor-communication decisions. Then the deal slips — not because anyone lied, but because a security review nobody mapped consumed five weeks — and every decision built on that number is now wrong.

The rep's single act of optimistic, unmapped forecasting propagated all the way to the company's financial planning.

This is why "no MAP, no commit" is not a bureaucratic rule. It is a *data-integrity* rule. A forecast is a promise the sales organization makes to the rest of the company, and a promise with no plan underneath it is not a forecast — it is a hope wearing a forecast's clothing.

The MAP is the evidence that converts a hope into a promise. A manager who internalizes this stops treating the MAP as the rep's busywork and starts treating it as the price of admission to the commit category.

🟡 Coach Note

If anyone in the room is a sales manager or RevOps leader, ask them directly: "How many times last quarter did a 'commit' deal slip and surprise you?" Whatever the number, it is the size of the problem this training solves. Write it on the board and leave it there for the next 52 minutes.

SECTION 2 — THE TEACH (0:08-0:30)

This is the 22-minute core of the training. The goal is not for reps to *understand* the CO-BUILD motion — it is for reps to be able to *recite* it and *run* it. By 0:30, every person in the room should be able to name the five steps in order and explain the slip-test without notes.

2.1 — The 5-step CO-BUILD motion

A MAP is not a document you write. It is a conversation you facilitate. The motion has five steps, and the mnemonic — CONFIRM, CHART, COMMIT, CADENCE, CLOSE — is built so reps can hold it in their heads on a live call.

Step 1 — CONFIRM. Before you build anything, confirm there is a real deal to plan. Confirm the buyer wants to move forward, confirm a compelling reason to act by a date, and confirm you are talking to someone who can commit their side of the plan. This maps directly to the MEDDICC elements *Metrics*, *Decision Process*, and *Champion* — if you cannot confirm those three, you are not ready for a MAP, you are still selling.

Building a MAP on a soft yes just produces a tidy document attached to a dead deal. The CONFIRM step is also a courtesy to the buyer: it asks, in effect, *"are we both sure this is happening?"* before either side invests time in planning. A buyer who hesitates at CONFIRM has just told you something true and valuable.

The CONFIRM script the room should leave able to run is short and direct: *"Before we map out the path to go-live, let me make sure I've got this right — the reason you want this in place by [date] is [compelling event], the outcome you're measuring is [metric], and you're the right person to commit your side of the plan — or is there someone else I should have on this call?"* Three sentences.

Each one tests one MEDDICC element. If all three land cleanly, you have a deal worth mapping. If any one wobbles, the wobble is the most useful information you will get all week — and the right move is to pause the MAP and go back to discovery, not to plough ahead and build a document that papers over the gap.

Step 2 — CHART. Co-build the milestone list on a shared screen, live. Start from the end — the go-live or first-value date the buyer cares about — and work backward. This back-casting technique is the same one The Challenger Sale authors describe as making the buyer's path explicit and teaching the buyer to buy.

Ask the buyer: *"Walk me through what has to happen on your side."* Their answer reveals the hidden steps: security questionnaires, legal review, procurement intake, budget approval thresholds, board or committee dates. You add your side: order form, implementation kickoff, onboarding.

The chart is built together, in their words, on their screen. The physical fact of *their* screen matters — a plan the buyer is typing into is a plan the buyer owns.

Back-casting is the technical heart of CHART, and reps consistently get it backward — they start from "today" and ask "what's next?" That forward-walk produces a vague, open-ended list with no deadline pressure. The back-cast starts from a fixed point the buyer already cares about — "you said you need this live before the fiscal-year planning cycle in October" — and works in reverse: *if* go-live is October 1, *then* onboarding must start by mid-September, *which* means the contract must be signed by early September, *which* means legal redlines must finish in August, *which* means security review must start in July.

Suddenly the buyer is looking at a July deadline for a step they had not even mentioned, and they feel the urgency themselves. The rep did not create urgency; the rep made the buyer's *existing* urgency visible by anchoring it to the buyer's own date. That is the Challenger move — a constructive tension the buyer experiences as help, not pressure.

A second CHART discipline: write the milestones in the *buyer's* vocabulary, not the methodology's. The MAP should say "Riya's team reviews the data-security questionnaire," not "MEDDPICC Paper Process — security gate." The buyer should be able to forward the document to their own CFO without a single line reading like vendor jargon.

If a milestone on the MAP would embarrass the buyer to forward, it is written wrong.

Step 3 — COMMIT. Every milestone gets a named owner and a date. Not "legal" — a person. Not "next week" — a date.

The buyer commits to their lines out loud. This is the step reps skip, and skipping it is why MAPs fail: an unowned, undated milestone is a wish. The Sandler Selling System's "no mutual mystification" principle applies — vague is the enemy, and an up-front contract on who-does-what-by-when removes it.

When the buyer says "procurement usually takes two weeks," you write the date two weeks out and ask "who is our contact there?" The discomfort of pinning a name to a line is exactly the discomfort that surfaces a soft deal early.

COMMIT is also where the rep's own discipline is tested, because COMMIT is uncomfortable on both sides of the table. Pinning a buyer to a date feels, to an inexperienced rep, like pushing — and so the inexperienced rep softens it: "no rush, whenever procurement gets to it is fine." That kindness is a trap.

An undated milestone is not a kindness to the buyer; it is a quiet agreement between rep and buyer to let the deal drift. The skilled rep reframes the date as the buyer's protection: *"Let's put a date on it not because I'm chasing you, but because if procurement intake doesn't start by the 15th, your October go-live is at risk — and I'd rather we both see that now than discover it in September."* The date serves the buyer's deadline.

Said that way, the buyer rarely resists, because the rep is on the buyer's side of the table.

There is also a hierarchy of owner quality the room should learn. Best: a named individual the rep has met or been introduced to. Acceptable: a named individual the rep has not yet met but has a path to.

Weak: a named role with no individual ("the InfoSec lead, whoever that is"). Unacceptable: a team ("legal," "procurement," "security"). A MAP line whose owner is a team is a MAP line with no owner, and the rep's job in COMMIT is to walk every such line up the hierarchy until it names a human.

Step 4 — CADENCE. Agree how the MAP gets reviewed. A MAP reviewed once is a document; a MAP reviewed every week is a process. Set a recurring checkpoint — fifteen minutes weekly — to walk the plan, mark milestones green or red, and re-date anything that moved.

The cadence is itself a milestone on the MAP. CSO Insights' research on deal planning makes the same point structurally: dynamic, regularly revisited plans outperform static ones. A MAP without a cadence is a static plan, and static plans go stale.

The CADENCE meeting has a structure, and the room should learn it because an unstructured "MAP check-in" decays into a status update with no teeth. The fifteen-minute review runs the same way every week: open the MAP on a shared screen, walk it top to bottom, and color every milestone — green if on track, yellow if at risk, red if blocked or slipped.

For every yellow or red, ask one question: *"What does this line need to go green, and who owns making that happen?"* Then re-date anything that moved and book the next fifteen-minute slot before hanging up. The cadence is also the rep's early-warning system: a milestone that goes from green to red between two reviews is a one-week-old signal, not a one-quarter-old surprise.

That compression of detection time — from a quarter to a week — is the entire forecasting payoff of the CADENCE step.

A practical note on framing the cadence to the buyer: never call it a "sales check-in." Call it a "go-live tracking review," because that is what it is — fifteen minutes a week protecting the buyer's launch date. Buyers say yes to protecting their own date. They say no, politely, to fifteen minutes a week of being sold to.

Step 5 — CLOSE. Use the MAP as the closing instrument. You never have to "ask for the close" again — you ask *"are we still on track for milestone 6?"* The MAP makes the close a status update, not an event. Jeb Blount's writing on closing (in *Sales EQ* and *Inked*) makes the same point: the close should be the unsurprising sum of every earlier micro-commitment.

When the last milestone before signature is green, the signature is the natural next line, not a confrontation.

This reframes what "closing" even means. In the unmapped deal, the close is a discrete, high-stakes event: the rep works up the nerve, "asks for the business," and the buyer either says yes or introduces a surprise — "oh, this still needs to go through security." The close becomes a moment of maximum tension and maximum risk.

In the mapped deal, there is no such moment. The close is the last green line on a plan the buyer co-built and reviewed every week. By the time signature arrives, the buyer has already said yes — out loud, on the record — to the seven milestones before it.

The signature is not a decision; it is the documentation of decisions already made. Reps who have run a real MAP describe the close as "anticlimactic," and anticlimactic is exactly the goal. A dramatic close is a symptom of a deal that was never mapped.

The CO-BUILD mnemonic is built so a rep can hold the whole motion on a live call: CONFIRM there is a deal, CHART the path, COMMIT owners and dates, CADENCE the review, CLOSE on the last green line. Five C's, one motion, every late-stage deal.

2.2 — The CO-BUILD motion as a flow

The motion is a sequence with two decision gates — one at CONFIRM, one inside COMMIT — and both gates are where the deal's real health is exposed.

The two "No" branches are the most valuable outputs of the motion. A "No" at CONFIRM sends the rep back to discovery before any time is wasted on planning. A "No" at the COMMIT gate — a buyer who will not date their own milestones — is a slip signal arriving weeks or months before it would otherwise have surfaced.

Teach the room to *want* those "No" answers. An early "No" is cheap; a quarter-end "No" is expensive.

2.3 — The typical late-stage milestone list

Most slipped deals stall on the same five hidden steps. Build the room's awareness of how long each really takes — and note that these durations are *typical ranges*, not promises; the rep's job in CHART is to ask the buyer for the real number, not assume one.

A deal with a verbal yes and *none* of these dated is not a "commit" deal — it is a hope. Walk the room through the arithmetic: if security is 2-6 weeks, legal is 1-4, procurement is 1-3, finance is 1-2, and signature is up to a week, then the gap between "verbal yes" and "signed" can realistically run seven to sixteen weeks even when nothing goes wrong.

A rep who forecasts a verbal-yes deal to close "this month" without a MAP is not optimistic — they are uninformed. The MAP turns that uninformed optimism into a dated plan the manager can inspect.

2.4 — A worked example: the eight-milestone MAP

To make the milestone list concrete, walk the room through a fully built example MAP for a representative mid-market SaaS deal — a $90K annual contract, verbal yes in week 6, buyer wants go-live before their Q4 planning cycle. Put this table on the screen and let the room see what "done right" looks like:

Three things are worth pointing out about this example. First, the buyer owns five of the eight milestones — that is correct; most of the path is the buyer's internal work, and a MAP that the *vendor* owns most of is a MAP that has confused activity with progress. Second, milestone 5 still reads "TBD" for the owner — that is an honest flag, not a failure; it tells the rep exactly what the next CADENCE review must resolve.

Third, milestones 3, 4, and 5 are spread across three different named people — Riya, Marcus, and the procurement specialist — which is the structural defense against Failure Mode 2. If Dana, the champion, leaves the company, milestones 3, 4, and 5 still have owners and the plan survives.

A single-threaded version of this same MAP would list "Dana Okafor" on all eight lines, and one resignation would orphan the entire deal.

2.5 — Sequencing: parallel vs. serial milestones

A subtle skill inside CHART is teaching the buyer which milestones can run in parallel and which must run in series. Security review and procurement vendor intake can often start at the same time; legal redlines usually cannot finish until security has cleared, because security findings sometimes change contract language.

A rep who helps the buyer parallelize the independent steps can compress a sixteen-week path to ten. That compression is real, defensible deal acceleration — and it is acceleration the buyer thanks you for, because it is *their* timeline you protected. This is the difference between a MAP that the buyer experiences as helpful and one they experience as vendor bureaucracy: a helpful MAP makes the buyer's own life faster.

2.6 — What belongs on a MAP

A real MAP has: the buyer's target outcome and date; every milestone from today to first value; an owner on each milestone — a named human, not a team; a due date on each milestone; a status field; and the review cadence. It does not have your internal forecast category, your commission math, or marketing language.

It is a working document the buyer would be comfortable forwarding to their own boss.

Tools like Salesforce (CRM: NYSE: CRM), HubSpot (NYSE: HUBS), and deal-collaboration platforms (DealHub, Aligned, GetAccept, Recapped) ship MAP templates natively, and document-automation vendors such as DocuSign (NASDAQ: DOCU) sit at the signature milestone. But the tool is not the point; the *co-build conversation* is.

A MAP built in a shared Google Doc with genuine two-sided ownership beats a MAP built in the most sophisticated platform on the market and emailed at the buyer.

2.7 — The three failure modes

If reps learn nothing else from the teach, they should learn to recognize and avoid these three failure modes. Each one produces an artifact that *looks* like a MAP and functions like nothing.

Failure mode 1 — the emailed MAP. The rep builds the plan alone and emails it as a PDF. The buyer never agreed to anything out loud, so they own nothing. A MAP the buyer did not help build is just your homework.

The tell: ask the rep "did the buyer say any of these dates out loud?" If the answer is no, it is an emailed MAP regardless of how polished the document looks.

Failure mode 2 — the single-threaded MAP. The MAP has one buyer-side name on every line. When that person goes on leave, gets reorganized, or changes jobs, the whole plan is orphaned. With buying groups of 6-10 people, a real MAP names the security reviewer, the legal contact, and the procurement contact — not just your champion.

This is the exact disaster addressed by the champion-departure training in (st0033): a multi-named MAP is the structural defense against a champion walking out the door.

Failure mode 3 — the frozen MAP. The MAP gets built and then never opened again. Deals are dynamic; an un-reviewed MAP is stale within two weeks. Without the CADENCE step, the document quietly dies and the deal slips anyway.

The frozen MAP is the most insidious failure because it *was* done right at the start — the build was real, the buyer owned it — and then the cadence lapsed and all of that value evaporated.

🟡 Coach Note

Test the room: hand each rep a slipped deal and ask "which of the three failure modes killed it?" Most slipped deals fail mode 1 or 3. Reps who can name the failure mode can prevent it.

2.8 — MAP-discipline scorecard

Score each commit-stage deal 0-5. One point per "yes":

4-5 = legitimately forecastable. 2-3 = at risk, coach this week. 0-1 = not a commit deal, period.

This scorecard is the bridge between this training and the forecast-call training in (st0037). The rule "no MAP, no commit" is only enforceable if there is an objective test of what counts as a real MAP. The scorecard is that test.

A manager who adopts it gives the whole team a shared, un-arguable definition: a deal scoring 0-1 cannot sit in commit no matter how confident the rep sounds.

⚠️ COUNTER-CASE: WHEN A MAP IS THE WRONG MOVE

A MAP is a powerful tool, not a universal one. Forcing the full CO-BUILD motion onto every deal wastes the rep's time and, worse, signals to a buyer that you do not understand their context. 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.

Counter 1 — Transactional, single-signer deals. A $4K annual renewal with one decision-maker and a credit card has no hidden procurement or security path. A full eight-milestone MAP here is theater. Right move: a two-line email confirmation of the close date is the entire "plan." Reserve the MAP for deals with real multi-step buying processes.

The skill is proportionality — match the weight of the plan to the weight of the buying process.

Counter 2 — The deal is not actually qualified. If CONFIRM fails — no compelling event, no named economic buyer, no real metric — building a MAP does not fix that. It just produces a neat document attached to a deal that was never real. A MAP cannot manufacture urgency or authority that does not exist.

Right move: stay in discovery; do not let a MAP become a way to *feel* like a deal is progressing. A MAP is a *symptom* of qualification, not a *cause* of it — building one on an unqualified deal inverts the logic and produces false confidence in the forecast.

Counter 3 — The buyer experiences it as a vendor process imposed on them. If you present the MAP as "our standard close plan" and drive it from your screen in your language, sophisticated buyers — especially in procurement-led organizations — read it as you managing your forecast, not helping them.

The artifact backfires: it adds friction instead of removing it. Right move: it must be co-built in *their* words, framed around *their* go-live date, and owned by *them*. If you cannot get genuine two-sided ownership, a quietly tracked internal plan is more honest than a fake "mutual" one.

Counter 4 — Hyper-relational or founder-led sales. In some small-business and founder-to-founder deals, pulling out a structured milestone grid mid-conversation breaks rapport and trust that *is* the buying process. Right move: capture the same milestones, but conversationally — "so we're aligned: 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 grid.

The underlying discipline (named owners, dates, a written record) survives; only the formal artifact is set aside.

Counter 5 — Late-arriving procurement that overrides everything. Occasionally a deal with a clean champion-built MAP gets yanked into a procurement RFP or competitive bid that resets the rules entirely. The original MAP is now obsolete. Right move: do not cling to the old plan; rebuild a new MAP with the procurement owner as a named participant, and treat the procurement gauntlet as its own motion — which is exactly the training in (st0036).

The synthesis. A MAP earns its place when a deal has (a) a real multi-stakeholder buying process, (b) genuine qualification behind it, and (c) a buyer willing to co-own the plan. Where any of those three is missing, scale down or wait. The skill is not "always build a MAP" — it is knowing which deals need one.

A rep who can name the deal on their list where a MAP would be the *wrong* move is a rep who actually understands the tool.

SECTION 3 — DISCUSSION (0:30-0:42)

Run these seven prompts. Pull real deals onto the whiteboard — the discussion is worthless if it stays abstract. The manager's job here is to keep the room honest and on the clock: roughly 100 seconds per prompt, and do not let the room theorize when there is a live deal that answers the question.

1. "The buyer says 'just send me the contract — we don't need all this.'" How do you co-build a MAP without sounding bureaucratic? (Hint: frame it as protecting *their* timeline, not yours.)
2. Which of your current commit-stage deals has no written MAP? Why not? Run the scorecard on it live.
3. Single-threaded check: for your top deal, how many buyer-side names are on the plan? If it is one, what happens if that person leaves? (This is Failure Mode 2 — connect it to (st0033).)
4. Procurement and legal are the most common hidden milestones. On your live deals, when do those typically surface — and how late?
5. A milestone went red two weeks running. Is that a slip signal or noise? How do you tell? (Hint: a milestone that is red because a date moved is noise; a milestone that is red because *nobody owns it* is a slip signal.)
6. The buyer will not commit a date to one of their own milestones. What does that refusal tell you about the deal?
7. Counter-case check: name one live deal where a full MAP would be the *wrong* move — and what you would do instead.

🟡 Coach Note

Prompt 6 is the sharpest. A buyer who will not date their own milestones is telling you the deal is not as real as the verbal yes suggested. That is a gift — it is far cheaper to learn it now than at quarter-end.

3.1 — Facilitator guidance for the discussion

The discussion fails in two predictable ways, and the manager should pre-empt both. The first failure is the room treating prompts as trivia — answering in the abstract ("you'd frame it around their timeline") without naming a real deal. Counter it by refusing the abstract answer: "Good — now whose deal?

Pull it up." The second failure is one or two reps dominating. Counter it by directing prompts: "Prompt 4 — let's hear from someone who hasn't spoken yet." The deliverable of the section is concrete: by 0:42 the room should have audited at least three live deals against the MAP-discipline scorecard, with the scores written on the whiteboard.

If that has not happened, the discussion did not work.

3.2 — Model answers the manager should have ready

A manager who runs this discussion cold will get thin answers. Come prepared with a model answer for each of the seven prompts, not to lecture, but to raise the floor when the room stalls.

Prompt 1 — the "just send the contract" objection. The model answer is a reframe, delivered fast and warm: *"Happy to send it today — and before I do, ten minutes to map the path from signature to go-live, because I've watched deals exactly this clean lose six weeks to a security step nobody flagged.

That ten minutes protects your launch date."* The MAP becomes insurance on the buyer's timeline, not paperwork for the rep's forecast.

Prompt 2 — commit deals with no MAP. The honest model answer is usually uncomfortable: there is at least one, and the reason there is no MAP is that the rep is afraid the co-build conversation will surface a soft spot. Name that fear in the room. The fear is rational and the conclusion is exactly backward — the soft spot exists whether or not the rep looks at it; the only choice is whether to find it in week 6 or quarter-end.

Prompt 5 — slip signal versus noise. The model distinction: a milestone that is red because a *date moved for a concrete, owned reason* ("legal is out until Monday") is noise — annoying, but the deal is intact. A milestone that is red because *nobody owns it* or because *the buyer keeps deflecting on who owns it* is a slip signal — the deal is softer than the verbal yes implied.

Red-because-of-a-date is noise; red-because-of-no-owner is a warning.

Prompt 6 — the buyer who will not date their own milestone. The model answer is the sharpest lesson in the training: the refusal is *data*, and it is good data. A buyer who genuinely intends to buy will give you a date — even a rough one — for their own internal step, because the date costs them nothing.

A buyer who will not is telling you the internal commitment behind the verbal yes is not there yet. The right response is not to push for the date; it is to go back to CONFIRM and find out what is actually missing.

The manager should let the room produce its own answers first, then offer the model only as a sharpening tool. A model answer delivered too early shuts the room down; delivered after the room has tried, it lands.

SECTION 4 — ROLE-PLAY (0:42-0:57)

This is where the skill actually transfers. Understanding the CO-BUILD motion and being able to run it under live resistance are different competencies, and only the second one closes deals.

Setup. Pairs. One rep, one buyer. The buyer is a VP who just gave verbal approval on a $90K annual deal and says: "Great, just send me the paperwork and we'll get it signed." The rep's job: co-build a MAP live, on a shared screen, without losing the momentum of the yes.

The buyer should resist twice: first with "we really don't need a formal plan, I'll just push it through," and second with "I can't give you a date for the security review, that's not my team." The rep must run CONFIRM → CHART → COMMIT → CADENCE → CLOSE and get at least one buyer-owned, dated milestone.

Watch for: Does the rep frame the MAP as protecting the buyer's go-live date? Do they build it on the buyer's screen, in the buyer's words? Do they get a *named* security contact when the buyer deflects? Do they set a review cadence? Do they close on a milestone instead of asking for signature cold?

Run 6 minutes, switch, run 6 minutes, debrief 3 minutes. (6 + 6 + 3 = 15.)

4.1 — Coaching the two resistance points

The first resistance — "we don't need a formal plan" — is a *framing* test. A rep who fails it argues for the MAP as a process the rep needs. A rep who passes it reframes instantly: "Totally — and the reason I'm suggesting it isn't paperwork, it's that I've seen deals exactly like this lose six weeks to a security review nobody flagged.

Ten minutes now protects your go-live date." Notice the move: the MAP is recast as *the buyer's insurance policy*, not the vendor's tracking sheet.

The second resistance — "I can't give you a date for security, that's not my team" — is the most common real-world deflection, and it is a *multi-threading* test. The weak rep accepts the non-answer and writes "TBD." The strong rep does not need the date from the VP; the strong rep needs a *name*: "Completely fair — you wouldn't own that date.

Who would? If you can introduce me to whoever runs InfoSec intake, I'll get the realistic timeline straight from them and bring it back to this plan." That converts a dead end into a new named owner on the MAP — exactly the defense against Failure Mode 2.

4.2 — A role-play observation scorecard

Hand each observing rep this five-line scorecard to use while watching their partner. It keeps the observation specific and converts the debrief from vibes into evidence:

A rep who scores five-for-five ran the motion. A rep who scores three or below has a specific, nameable gap — and a specific gap is coachable in a way that "needs to be more consultative" never is.

4.3 — Common role-play failure patterns

Three failure patterns recur in this role-play, and the manager should name them when they appear. Pattern one — the rep who lectures the MAP. Instead of co-building, the rep explains what a MAP is and why it matters for two minutes. The buyer's eyes glaze.

Fix: the MAP is built by *asking*, not *telling* — the rep's first move after the verbal yes should be a question ("walk me through what has to happen on your side"), not a definition. Pattern two — the rep who accepts TBD. The buyer deflects on the security date and the rep writes "TBD" and moves on.

Fix: TBD on a date is acceptable; TBD on an *owner* is not — always convert the deflection into a name. Pattern three — the rep who closes cold anyway. The rep builds a beautiful MAP and then, at the end, reverts to habit: "so, are you ready to move forward?" Fix: the close *is* the MAP — "milestone 7 is signature, and milestones 1 through 6 are green, so signature is just the next line — shall we target the 14th?"

4.4 — The debrief inside the role-play

Use the 3-minute role-play debrief to surface one thing per pair: the single moment the rep either advanced or stalled the co-build. Keep it specific — not "good job building rapport" but "the moment you asked 'who runs InfoSec intake' instead of accepting TBD, that's the rep that gets a forecastable deal." Specific, named moments transfer; general praise does not.

SECTION 5 — DEBRIEF + COMMITMENTS (0:57-1:00)

Each rep commits, out loud: one deal they will co-build a MAP on this week; one buyer-side milestone they will get a named owner and date for; and one review cadence they will set. The manager writes these down and checks them at next week's pipeline review.

The three-part commitment is deliberately small. The training does not ask reps to MAP their whole pipeline by Friday — that ask is too big to be real, and a too-big commitment is just a polite "no." It asks for *one* deal, *one* milestone, *one* cadence. That is small enough that every rep can actually do it, and concrete enough that the manager can verify it.

A commitment that cannot be verified next week is a commitment that did not happen.

5.1 — The manager's follow-through

The training's value is realized in the *following* week's pipeline review, not in the room. The manager should open that review by reading back the commitments verbatim and asking each rep to show the MAP. This is where the rule from (st0037) takes hold: a deal in "commit" 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.

🎯 Closing Line

A forecast is only as honest as the plan underneath it. No MAP, no commit. Co-build the plan, name the owners, set the cadence — and watch the quarter stop slipping.

🔗 Related Pulse Content

This is a process training in the Pulse Sales Trainings library — it pairs with the deal-execution and pipeline-discipline entries rather than the industry-specific bid-walk trainings.

• (st0037) — The Forecast Call Reset — the closest sibling. The MAP is the artifact that makes the forecast call honest: a deal with no co-built MAP cannot truthfully sit in "commit." Run st0038 to build the plans, st0037 to inspect them.
• (st0031) — The Expansion QBR — a QBR that produces a six-figure upsell needs its own MAP. The CO-BUILD motion applies directly to turning QBR-identified expansion into a dated, owned plan.
• (st0032) — The Closed-Lost Win-Back Sprint — when a dead deal re-engages, the very first thing to rebuild is a MAP, because the old buying path is stale. CO-BUILD is the re-entry motion.
• (st0033) — The Champion Departure Save — Failure Mode 2 (the single-threaded MAP) is exactly the disaster st0033 addresses. A multi-named MAP is the structural defense against a champion walking out the door.
• (st0036) — Surviving the Procurement Gauntlet — Counter-Case 5 hands off directly to st0036: when procurement overrides the champion-built MAP, that becomes its own motion.
• (st0006) — The Pricing Conversation — pricing is one of the milestones a MAP must sequence; introduce it on the MAP at the right line, not as a surprise at signature.

Hub: /sales-trainings.

Sources & further reading

1. MEDDICC / MEDDPICC — Jack Napoli and Dick Dunkel, original authors of the qualification methodology.
2. Andy Whyte, *MEDDICC* (2020) — the modern codification of the methodology, including the "Paper Process" element.
3. MEDDPICC — the "P for Paper Process" extension covering legal, security, and procurement sequencing.
4. The "close plan" discipline as taught across MEDDICC-based enablement programs.
5. The Challenger Sale — Matthew Dixon & Brent Adamson (2011) — teaching the buyer to buy and making the path explicit.
6. CEB / Challenger research on buyer back-casting and compelling-event anchoring.
7. Gartner B2B Buying research — buying groups of 6-10 stakeholders.
8. Gartner B2B buying journey research — buyers spend ~17% of the journey with any one supplier.
9. Gartner — customers who find supplier information helpful are 2.8x more likely to close a high-quality, low-regret deal.
10. Gartner — the "low-regret purchase" framework for B2B buying.
11. Winning by Design — the SPICED framework (Situation, Pain, Impact, Critical Event, Decision).
12. Winning by Design — the Mutual Action Plan as a recurring-revenue / customer-success artifact.
13. Force Management — *Command of the Message* methodology.
14. Force Management — the "Mutual Plan" and required differentiated value.
15. The Sandler Selling System — the "no mutual mystification" principle.
16. The Sandler Selling System — the "Up-Front Contract" concept governing meeting and milestone agreements.
17. CSO Insights (now part of Korn Ferry) — sales-effectiveness and Sales Performance Optimization studies.
18. CSO Insights / Korn Ferry — research on dynamic deal planning vs. static plans.
19. CSO Insights / Korn Ferry — "no decision" as a leading cause of stalled, lost pipeline.
20. Salesforce (NYSE: CRM) — CRM pipeline and forecast-accuracy analyses; native opportunity-plan templates.
21. HubSpot (NYSE: HUBS) — deal-management tooling and MAP-style templates.
22. DocuSign (NASDAQ: DOCU) — e-signature routing at the final MAP milestone.
23. Jeb Blount, *Sales EQ* (2017) — emotional intelligence in sales and the psychology of the close.
24. Jeb Blount, *Inked* (2020) — closing and negotiation as the sum of micro-commitments.
25. DealHub — deal-collaboration platform with native MAP / digital sales room templates.
26. Aligned — buyer-collaboration "digital sales room" platform with MAP functionality.
27. GetAccept — digital sales room and mutual action plan tooling.
28. Recapped — mutual action plan and buyer-enablement platform.
29. Industry pipeline analyses on forecast slippage — roughly half of committed deals failing to close in the committed quarter.
30. Gartner Future of Sales research — the shift toward digital, seller-free buying activity.
31. General B2B sales-cycle benchmarks for mid-market and enterprise considered purchases (60-180 day cycles).
32. Enablement-practice literature on mutual action plans as a forecast-inspection instrument.