The Mutual Action Plan Build Session (60-Min Training)

Live co-build vs. a pre-filled template handoff

There are two dominant ways reps run this 60-minute block, and the choice changes everything about how the plan gets treated afterward. The first is the live co-build: the rep opens a blank shared document or Miro board on screen, and the buyer types their own answers into every field — the timeline, the stakeholder names, the decision criteria — while the rep only supplies structure and follow-up questions. The second is the pre-filled handoff: the rep drafts a MAP in advance based on discovery notes, sends it before the call, and the 60 minutes becomes a review-and-edit conversation rather than a from-scratch build.

The live co-build wins on ownership. When a buyer types "our CFO signs off on anything over $50K" into the document themselves, that statement becomes their commitment, not the rep's assumption. Reps who run pre-filled handoffs consistently report a specific failure pattern: the buyer nods along on the call, then quietly ignores the plan a week later because it never felt like theirs. The psychological mechanism is simple — people defend decisions they authored and discard decisions handed to them. A live session forces at least 70% of the field entries to come from the buyer's own keyboard, which is why most MAP-mature sales orgs (teams running MEDDIC-MC or a similar qualification framework) default to co-build for any deal above their average deal size.

The pre-filled handoff still has a real place. It works better for renewal and expansion motions where the relationship and stakeholder map already exist, or for deals where the buying committee genuinely cannot free up 60 synchronous minutes — common in enterprise deals with five or more stakeholders across time zones. In that case, a rep drafts the skeleton, shares it with a short Loom walkthrough, and uses the "60 minutes" as three or four shorter async check-ins instead of one block. The trade-off is speed for depth: async handoffs move faster on the calendar but surface fewer objections up front, meaning problems with the decision process tend to appear later in the cycle, closer to the deadline, when they are more expensive to fix.

A third, hybrid pattern splits the difference: the rep pre-populates only the sections that are matters of record (contract dates, procurement steps, known technical requirements) and leaves the judgment-call sections — decision criteria, stakeholder support levels, and the target decision date — blank for the live session. This hybrid is what most Training programs teach as the default starting point, because it protects the ownership benefit of live co-build while cutting dead time spent re-explaining context the rep already has. Choosing between the three isn't about rep preference; it should be driven by deal size, stakeholder count, and how much of the buying process is already understood before the call starts.

How to decide between the two approaches

The decision comes down to four questions the rep should answer before scheduling the session. First: how many stakeholders are already identified? Fewer than three names usually means discovery isn't done yet, and a live session should include time to surface the missing names rather than assume a pre-filled map will be accurate. Second: has an Economic Buyer been confirmed? If not, a pre-filled handoff risks enshrining a guess as fact, so live co-build is safer. Third: what is the deal's position in the buying committee's fiscal calendar — is there budget urgency, or is this exploratory? Urgent, budgeted deals tolerate the async speed of a handoff; exploratory deals need the full live build to create urgency in the first place. Fourth: can the rep get 60 synchronous minutes with at least the champion and one additional stakeholder? If the answer is no, forcing a live format wastes the format's main advantage — real-time buy-in from more than one voice in the room.

Reps who skip this decision step and default to whichever format they personally prefer tend to see the same problem repeatedly: a beautifully built MAP that nobody on the buying side references again. The fix is to treat the format choice itself as a five-minute pre-call decision, documented in the CRM opportunity record alongside the MEDDIC-MC notes, so the next rep who touches the deal (in a handoff, territory change, or manager review) understands why that format was chosen.

Concrete numbers behind each approach

The 60 minutes in a live co-build session typically break into six timed segments: a 10-minute warm-up to align on the biggest internal obstacle, a 15-minute MEDDIC-MC pass to capture Metrics, Economic Buyer, Decision Criteria, Decision Process, Identified Pain, and Champion, a 10-minute stakeholder mapping segment, a 15-minute evaluation timeline build, a 5-minute next-actions commitment, and a 5-minute close-and-handoff. That 10/15/10/15/5/5 split adds to exactly 60 and is the structure most Training decks teach, because the two longest blocks (MEDDIC-MC and timeline) are where the plan's substance actually gets created.

Stakeholder maps built in these sessions typically land between three and five named individuals with a role and a support rating (commonly a green/yellow/red scale). Fewer than three names usually signals the deal isn't ready for a MAP session at all — the rep should run one more discovery call first. Evaluation timelines for mid-market and enterprise B2B deals commonly span 45 to 90 days from the build session to a signed contract, with legal review alone frequently consuming 10 or more business days once redlines start, which is why experienced reps insert a legal-review milestone at roughly the halfway point of the timeline rather than at the end.

On the handoff side, async-only MAPs (sent as a document with no live session at all) see materially lower completion rates on assigned action items — reps who track this internally often find that buyer-side action items agreed to live on a call get completed within 48 hours far more often than items simply emailed over. That single number — same-week completion of the buyer's first assigned action — is one of the most useful leading indicators a rep has for whether a deal is genuinely progressing or politely stalling. A pattern worth tracking over a full quarter: deals with a completed live MAP session and at least one on-time buyer action tend to close within the originally forecast window meaningfully more often than deals where the MAP was sent but never walked through live.

Session cadence matters too. Once a MAP exists, updating it weekly during active evaluation — even a five-minute check-in — keeps both sides accountable; teams that let a MAP go untouched for two or more weeks during an active evaluation should treat that silence as a signal to escalate, not a sign that things are fine.

Implementation details and sequencing

Running the session well is mostly about protecting the time boxes. The warm-up (minutes 0–10) exists to establish the MAP as a partnership tool, not a sales tactic — the rep asks one open question about the buyer's biggest internal obstacle and writes the answer into the shared document verbatim, in the buyer's words. Skipping this step is the single most common reason a MAP session feels like an interrogation instead of a workshop.

Minutes 10–25 cover the MEDDIC-MC pass. The rep walks through each letter as a live prompt rather than a pre-filled assumption: what Metric justifies the investment, who the Economic Buyer is, what the top three Decision Criteria are, what the internal Decision Process and approval steps look like, what pain was Identified in earlier calls, and who the Champion is. Each answer gets a named owner and, where possible, a date attached in the same pass — a MEDDIC-MC field with no owner and no date is not actually complete, just discussed.

Minutes 25–35 build the stakeholder map, ideally as a simple table (name, role, support level, next action) rather than a complex org chart, since complexity here slows the session down without adding accuracy. Minutes 35–50 build the evaluation timeline backward from the buyer's stated target decision date, inserting the standard validation milestones — demo, proof of concept, reference calls, legal review, executive alignment — and assigning an owner to each one before moving on. Minutes 50–55 lock two specific next actions, one per side, each with a hard date; vague commitments like "I'll follow up" don't count and should be pushed back on in the room. The final five minutes close with a verbal recap and a same-day commitment to save the MAP into the CRM opportunity record so it's visible to the full account team, not just the rep who ran the session.

Related questions

How long should a Mutual Action Plan stay active after the build session?

A MAP should be reviewed at least weekly through the full evaluation period. If it goes two or more weeks without an update while the deal is still supposedly active, treat that as a stall signal and escalate to the champion directly.

Who should own updating the MAP after the session ends?

Ownership should be explicit and shared: the rep updates rep-side actions, and the champion or Economic Buyer owns updating buyer-side actions. A MAP that only the rep touches has quietly reverted to a one-sided sales document.

Can a Mutual Action Plan be used before a deal reaches late-stage evaluation?

Yes, though a lighter version works better early — just a rough timeline and one or two decision criteria — reserving the full MEDDIC-MC build for once a champion and Economic Buyer are identified.

What's the biggest reason MAP sessions fail to change outcomes?

The rep fills in more than 30% of the fields themselves instead of letting the buyer type their own answers, which strips the plan of the ownership effect that makes it work in the first place.

FAQ

What if the prospect refuses to schedule a 60-minute session? Offer a shorter 20-minute version covering just the timeline and decision criteria, and frame it as risk reduction rather than a sales step — most refusals soften once the rep positions it as protecting the buyer's own internal timeline, not the rep's quota.

How do I handle vague answers during the MEDDIC-MC pass? Push with a specific follow-up rather than accepting a vague label — "who exactly signs the purchase order over $50K" gets a better answer than "who's the buyer." If the buyer still can't answer, that's useful information: the deal isn't as far along as it looked.

Should the Mutual Action Plan live in a shared doc or inside the CRM? Build it live in a shared doc or whiteboard tool during the Session for real-time co-editing, then copy the finalized version into the CRM opportunity record within the same day so the rest of the account team can see it.

Can this format work for renewal or expansion deals, not just new logos? Yes — swap the evaluation milestones for a current-contract review and an expansion-criteria section, but keep the same 60-minute structure and the live co-build discipline, since ownership matters just as much on a renewal as a new deal.

What happens if a stakeholder map turns up a blocker rated "red"? Don't skip past it. Assign a specific action — usually a direct 1:1 between the rep (or a technical resource) and that stakeholder — with a date, rather than hoping the blocker resolves itself as the timeline progresses.

Is a Mutual Action Plan the same thing as a sales forecast? No. A forecast is the rep's internal prediction; a Mutual Action Plan is a document the buyer co-owns. A healthy MAP can inform a more accurate forecast, but treating them as interchangeable is what causes reps to overstate deal confidence.

Sources

• Gartner: Sales insights
• Salesforce Blog
• Gong Blog
• Outreach Resources
• Winning by Design Blog
• Force Management: MEDDIC Sales Methodology
• Clari Blog
• Harvard Business Review: Sales

Related on PULSE

• [The Mutual Action Plan: Template for Aligning Sales Reps and Prospects on Next Steps](/knowledge/st0691)
• [The Mutual Action Plan Co-Build — 60-Min Training](/knowledge/st0075)
• [The Territory Plan Build — 60-Min Training](/knowledge/st0048)
• [The Multi-Thread and Champion Build Reboot — 60-Min Training](/knowledge/st150)
• [The Referral Engine Build — 60-Min Training](/knowledge/st0062)