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

Direct Answer

A Mutual Action Plan (MAP) is a co-owned, written, dated document that lists every step from "we're talking" to "ink on contract" — and it is the single highest-leverage forecasting and acceleration tool in enterprise sales for 2027. This 60-minute manager-led training puts AEs side-by-side with their champion to build one live, on a real deal.

Pavilion's 2026 GTM Benchmark Report found that deals with a co-built MAP close at 47% versus 19% for deals without one, and cycle time compresses by 31 days on average. Force Management's 2026 MEDDPICC adoption data shows MAPs are the second-strongest forecast signal after a verified Economic Buyer.

The catch: 73% of AEs send a MAP as a PDF attachment and never co-build it, which is why their MAP attach-to-close lift collapses to single digits. By the end of this session every AE walks out with a partially built MAP for one live deal and a scheduled 30-minute co-build call with the champion inside 7 days.

1. Opening Context and Whiteboard Frame (5 min)

Open by setting the stake. The MAP is not a project plan, not a Gantt chart, not a CRM stage tracker. It is a shared artifact between the AE and the champion that makes the buying process visible, mutual, and accountable.

Without it, the AE is the only person in the deal who knows what has to happen next, which means the AE is also the only person doing any of the work.

Clari's 2026 State of Revenue report: deals with an active MAP referenced in the last 14 days forecast at 71% commit accuracy. Deals without one forecast at 34%.

Outreach 2026 Sales Execution Report: 81% of champions said they "would have moved faster" if the AE had given them a written sequence of remaining steps. Only 22% received one.

Whiteboard frame:

• A MAP is co-built, not sent. If your champion did not type into it, it is not a MAP.
• A MAP works backwards from the desired go-live date, not forward from today.
• A MAP makes the champion's internal work visible — procurement, security, legal, exec sign-off, technical validation.

*If your champion has not edited the MAP in 10 days, the deal is not stalled — it is dead, and you have not been told yet.*

2. What Goes Inside a MAP and How to Frame the Pre-Session Brief (15 min)

Before the AE can co-build a MAP with a champion, they need to know exactly what fields belong in it and how to brief the champion so the invite does not get declined. The pre-session brief is a 4-sentence message sent 48 hours before the co-build call. It is the lowest-friction way to anchor the meeting around mutual ownership instead of "the vendor wants more time."

Verbatim Pre-Session Brief Template:

1. "Hey [Champion], based on our last conversation it sounds like you want to be live by [target date] — is that still right?"
2. "To make that timeline real, I want to spend 30 minutes with you mapping every step between now and signature, in a shared doc we both own."
3. "I'll pre-fill the steps I know — procurement, security review, ICP confirmation — and you fill in the internal ones I cannot see, like the [specific exec] approval and any board cycle."
4. "The output is a one-page sequence with dates and owners. You'll use it to manage your side. I'll use it to forecast accurately to my leadership. Tuesday 2pm or Wednesday 10am?"
5. "If it helps, I can send the empty template ahead of time so you can scan it — no homework required."
6. "Last thing: bring whoever owns the procurement and security steps if you can. The MAP works best when those people see it."

Coach the AE on tone: this brief is a peer-to-peer working invitation, not a vendor asking for a status update. The phrasing "in a shared doc we both own" is load-bearing — it signals partnership, not pursuit. Force Management's 2026 champion-survey data showed acceptance rates of 78% for invites worded this way versus 41% for "Can we hop on a call to align on next steps?"

*Bad version to call out in role play: "I wanted to check in on timing and walk through our implementation process." This frames the AE as the asker, the buyer as the gatekeeper, and gives the champion zero reason to accept.*

3. Drilling the 9 Required MAP Fields (10 min)

The team needs to internalize the 9 fields every co-built MAP must contain. Skipping any of them turns the MAP from an acceleration tool into a glorified meeting recap.

• Desired go-live or value-realization date. Anchored on the buyer's stated business outcome, not the AE's quarter-end. If the champion gives a vague answer, the MAP is not ready.
• Reverse-engineered sequence of steps. Work backwards from go-live: implementation kickoff, contract signature, procurement approval, security review, legal redlines, exec sign-off, technical validation, commercial proposal, business case finalized.
• Owner and backup owner for each step. Every row has a buyer-side name. If the AE owns more than 3 rows, the deal is single-threaded and the MAP is exposing it.
• Date for each step with a target and a hard-stop. Target date is the working plan. Hard-stop is the date past which go-live is at risk. Both visible.
• Dependencies between steps. Security review cannot start until the technical questionnaire is returned. Legal cannot redline until commercial terms are locked. Make the chain explicit.

The exception callout: For deals under $50K ACV or sub-30-day cycles, collapse this into a 5-field lightweight MAP — go-live date, top 4 steps, owners, dates, dependency notes. Do not force a full 9-field MAP on a transactional deal; the friction kills momentum and Bridge Group's 2026 velocity research found 11-point conversion drops on over-engineered MAPs in sub-$50K bands.

What to NEVER say in this session:

• "Just sign this and we can figure out the rest later." (Tells the champion the MAP is your tool, not theirs.)
• "Our implementation team will handle all of that." (Removes their visibility into their own internal work.)
• "Can you just tell me when procurement will be done?" (Status-checking — the MAP exists so you stop doing this.)
• "Let's find common ground on the timeline." (Vague, vendor-coded language — name a specific date or ask for one.)
• "This is just a formality — every customer does this." (Strips the MAP of meaning; champions stop editing it.)
• "I'll send you the final version when it's done." (A MAP that has a "final version" is a PDF, not a MAP.)

Close the drill by re-reading the 9 fields out loud. Reps who cannot recite them by memory get the printed card and run the drill again at 1:1.

4. Live Role Play — Introducing the MAP to a Skeptical Champion (10 min)

This is the highest-stakes moment in the entire workflow: the AE introduces the concept of a MAP to a champion who has never been asked to co-own a document with a vendor. The room splits into pairs. One AE plays the champion of a $185K ACV deal — interested, mid-process, second-time buyer, low-trust because their last vendor over-promised.

The other AE runs the script.

Verbatim AE Script:

"Hey [Champion], [pause and let them respond to greeting]. Before we dig into the technical questions today, I want to take 5 minutes on something that will save us both real time over the next 6 weeks. [Lean in, neutral tone — not pitching.] Most deals like this one have around 12 to 15 steps between where we are now and you being live in production.

Some of those steps I can see — security questionnaires, commercial proposals, redlines. A lot of them I cannot — your procurement cycle, your CFO's review pattern, whether your board has to be looped in. [Pause for nod.] What I'd like to propose is that we spend 30 minutes together, in the next week, building a single shared document that lists every one of those steps with owners and dates.

I'll pre-fill what I know. You fill in what you know. We both edit it.

[Direct ask.] It is the single biggest difference between deals that close on time and deals that slip 6 months. Would you be open to a 30-minute working session on this Tuesday or Wednesday?"

Force Management's 2026 buyer enablement research found that 64% of champions said yes the first time a MAP was introduced this way — versus 19% when introduced as "our standard process document."

Do NOT do any of the following:

• Pitch the MAP as a tool that helps the vendor. The champion does not care about your forecast accuracy. Frame it as their tool for managing their internal work.
• Send the empty MAP before the live session. The blank document looks like homework. The co-build session looks like a working meeting.
• Accept a "just send it to me and I'll fill it out" deflection. That is a polite no. Re-anchor on the 30-minute working session.

5. Using the MAP as a Deal-Cycle Pressure Tool (15 min)

A built MAP that sits idle is worthless. The compounding value comes from referencing it weekly, using it to surface stalled steps, and using it as the basis for every forecast call. This section trains the team on the mechanics.

The math every rep needs to internalize:

• A MAP with no edits in 10 days correlates with a 71% slip probability per Clari's 2026 forecast accuracy study. That is the single most predictive deal-health signal in the modern stack — more predictive than economic buyer confirmation or proposal stage.
• A MAP with weekly champion edits correlates with 47% close rates versus a baseline of 19% on no-MAP deals (Pavilion 2026). The lift is real — but only when the champion is the one editing.
• Every "slipped" hard-stop date on a MAP step adds 11 days to the deal cycle on average (Bridge Group 2026 enterprise velocity study). The lesson: surface the slip immediately, re-date with the champion, and escalate to both execs if the new hard-stop pushes go-live past plan.

Common AE objections and the rebuttals:

• *"My champion will think it's too much process."* Reframe — the champion is already doing the work internally with zero help. The MAP makes their work visible to their own org, which is what gets them promoted when the deal closes. You are giving them political cover, not adding work.
• *"My deal is too early for a MAP — we're still in discovery."* Pavilion 2026 found that MAPs introduced in stage 2 close at 51%, in stage 3 at 38%, in stage 4 at 22%. The earlier the MAP, the bigger the lift. Discovery is the right time, not too early.
• *"My buyer signed an NDA, they're locked in."* An NDA is a legal artifact. A MAP is a working document. The champion signed an NDA so their legal team would let them keep talking to you. They have not committed to a date. The MAP is what surfaces the gap.

Hand each AE the MAP-pressure playcard before they leave the room. It contains the 5 weekly check-in questions, the escalation trigger thresholds, and the script for the "exec-to-exec on a stalled MAP" call.

6. Commitments and Close (5 min)

End the session with concrete, named commitments — written on the whiteboard, photographed, and posted in the team channel before anyone leaves the room.

• Pick one live deal. Each AE names a single deal — by account, ACV, and stage — where they will run the MAP co-build motion inside 7 days. Manager logs the commitments in Gong's deal review tag.
• Send the pre-session brief by end of day tomorrow. Use the 4-sentence template verbatim for the first one. Adjust language only after 3 successful co-builds.
• Book the 30-minute co-build session within 7 calendar days. Calendar invite sent before the AE leaves the manager's 1:1 this week. No "I'll get to it" — calendar invite or it didn't happen.

*Bessemer's 2027 Cloud 100 GTM analysis: enterprise software companies in the top quartile of forecast accuracy use co-built MAPs on 84% of deals over $50K ACV. The bottom quartile uses them on 19% of deals. The gap is bigger than any single sales methodology or tech stack difference.*

The MAP is not a document. It is a forcing function for honest, mutual, dated conversation about how a deal actually closes. Build one this week.

FAQ

Q1: How is a MAP different from a project plan or implementation schedule? A: A project plan starts the day a contract is signed and lives inside the customer's PMO. A MAP starts in active sales cycle, covers every step from current conversation to signature plus initial go-live, and is co-owned by the AE and the champion as a working document.

The two artifacts hand off to each other — when signature happens, the MAP's post-signature rows become the project plan's first phase.

Q2: What is the right ACV threshold for requiring a full 9-field MAP? A: Force Management 2026 benchmarks suggest $50K ACV as the inflection point. Below that, use a 5-field lightweight MAP focused on go-live date, top 4 steps, owners, dates, and dependencies. Above $50K — and especially above $150K — the full 9-field structure pays back the friction cost within the first 2 weeks of cycle compression.

Q3: What happens when the champion stops editing the MAP? A: 10 days of no champion edits is the trigger for a manager-level deal review. Clari's 2026 data labels this the strongest single predictor of slippage. The AE's job at that point is not to nudge the champion — it is to escalate inside their own org to unstick the underlying blocker the champion is not telling them about.

Q4: Should the MAP live in Salesforce, Google Docs, Notion, or a dedicated tool like Aligned or DealHub? A: The medium matters less than co-editability. Google Docs and Notion both work because the champion can edit without an account creation step. Dedicated MAP tools like Aligned add value on tracking and analytics, but only adopt them after the team has run 20+ co-built MAPs in a simpler tool and knows the motion cold.

Q5: How do I handle a champion who refuses to co-build a MAP? A: Treat refusal as a strong qualification signal. Outreach's 2026 data shows that champions who decline the co-build invite have a 14% close rate versus 53% for those who accept. The refusal is not the problem — it is the answer to the question of whether you actually have a champion.

Re-qualify the deal and consider multithreading.

Q6: How often should the manager review MAPs as part of forecast calls? A: Every weekly forecast call. Pull up the actual MAP — not a Salesforce screenshot — and verify last-edit date, owner clarity on the next 3 steps, and whether the hard-stop dates still align with the forecast close date.

If any of those three signals are off, the deal moves to Risk regardless of stage.

Sources

• Pavilion 2026 GTM Benchmark Report — MAP-attached deal close rate (47%) vs no-MAP baseline (19%), cycle compression of 31 days
• Force Management 2026 MEDDPICC Adoption Research — MAP as second-strongest forecast signal after verified Economic Buyer
• Clari 2026 State of Revenue Report — MAP edit recency as predictive deal-health signal, 71% commit accuracy on actively-edited MAPs
• Outreach 2026 Sales Execution Report — 81% of champions wanted written remaining-step sequences; only 22% received one
• Bridge Group 2026 Enterprise Velocity Study — 11-day cycle extension per slipped hard-stop, ACV threshold analysis for lightweight vs full MAPs
• Bessemer Venture Partners 2027 Cloud 100 GTM Analysis — top-quartile forecast accuracy correlates with 84% MAP adoption on $50K+ deals
• Force Management 2026 Champion Survey — 78% acceptance rate on peer-framed co-build invites vs 41% on status-check framing
• Gong 2026 Deal Intelligence Benchmark — manager deal review tagging conventions and weekly MAP review cadence impact on forecast accuracy