MAP. The artifact that turns "maybe" deals into "when" deals.
A Mutual Action Plan is a shared document — usually a Google Doc, Notion page, or Salesforce Quip — that maps every step from the buyer's current state to a signed contract, with explicit owners, dates, and dependencies on both sides. It is the most under-used close-stage artifact in modern B2B sales and one of the few that consistently produces measurable cycle compression. AEs who run a MAP on every deal above $25K close 30-40% faster on average than AEs who don't, and the deals they lose, they lose earlier (and cheaper) instead of in the late-stage indecision phase. The framework's hidden mechanism: asking a buyer to co-author a MAP surfaces hidden objections, missing stakeholders, and unrealistic timelines that would otherwise stay invisible until they killed the deal in week 8. This essay covers the anatomy of a working MAP, the moment in the cycle to propose one, the social-engineering reason buyers co-author MAPs they would refuse to sign as commitments, the without-MAP vs with-MAP comparison, and the rollout playbook for adding MAPs to an existing sales motion.
01What a MAP is
A Mutual Action Plan is a shared document — typically a Google Doc, Notion page, Salesforce Quip, or dedicated deal-room tool — that explicitly maps every step from the buyer's current evaluation state to a signed contract. The document is co-authored by the seller and the buyer's primary contact, with explicit owners, dates, and dependencies on both sides.
The structural components of a working MAP:
- Goal statement at the top. What outcome both parties are working toward, with a target date. "Sign annual contract for [product] by [date], with [implementation milestone] complete by [date]."
- Stakeholder list. Every person involved in the decision on either side, with their role. The act of listing them surfaces missing stakeholders.
- Step table. Every action needed between today and signature, with: week/date, action, owner, dependency, status. This is the bulk of the document.
- Open questions section. Things that aren't yet resolved — pricing, scope, security questions. Living section that gets resolved as the deal advances.
- Decision criteria. What the buyer is evaluating and how they'll decide. Often combined with MEDDIC's Decision Criteria field.
The document lives shared in a tool both sides can access. It's reviewed at the start of every check-in call. Status updates happen async between calls. By the close stage, the MAP has typically been iterated 4-8 times — each iteration surfacing new information and refining the path to signature.
02Anatomy of a working MAP
A real MAP for a typical $80K ACV enterprise deal, mid-cycle:
Notice what the MAP makes visible that would otherwise be hidden:
- InfoSec was missing from the original plan. Adding Priya in W1 caught a 4-week security-review process that would have surprised the team in W7.
- Procurement takes 2 weeks. The MAP forced this conversation in W1 instead of discovering it in W11 when it would have pushed the close date by 2 weeks.
- The CFO is the Economic Buyer. Listed explicitly in W4; the AE knows to engage them before the pilot review, not after.
- The pilot exists as a deliberate de-risking step. Both sides agreed to it upfront rather than having the buyer propose it at week 6 as a stalling tactic.
- Every date is real, not aspirational. The buyer agreed to the dates by co-authoring; missing dates becomes a conversation rather than a surprise.
Each of these visibility-improvements is worth more than the operational cost of the MAP — they collectively explain the 30-40% cycle compression that disciplined MAP practitioners see.
03Why MAPs compress cycles
Four mechanisms drive the cycle-compression effect:
1. Hidden stakeholders surface in week 2 instead of week 7. The MAP's "stakeholder list" section forces the buyer to think about who else needs to be involved. The stakeholders that get added — Security, Legal, Procurement, CFO — would otherwise have surfaced as last-minute surprises that delay the close.
2. Realistic timelines get negotiated upfront. Most deal slippage comes from underestimating the time required for security review, procurement, legal redlines, and integration setup. The MAP makes these explicit upfront. A buyer who says "we want this in 30 days" but whose internal procurement takes 45 will negotiate the date during MAP creation, not discover the mismatch in week 5.
3. Objections surface earlier. Co-authoring the MAP often surfaces objections the buyer wasn't going to raise spontaneously: "we'd want to see a security audit," "the CFO would want a pilot first," "we'd need a one-year term not three-year." These objections are easier to address in week 2 than in week 8. Most deals that die in the late stage die to objections that could have been resolved months earlier if anyone had asked.
4. The buyer's internal commitment is captured in writing. When the buyer agrees to a date in a co-authored doc, they're operationally committed in a way verbal "yeah that should work" doesn't capture. The doc is something they can show their boss; it carries the weight of a written commitment without the legal heaviness.
The combined effect is operational: MAPs don't make deals close that wouldn't have closed; they make winnable deals close faster and dead deals die earlier. Both effects compound to substantial cycle compression and pipeline efficiency.
04Why buyers co-author them
The most counterintuitive thing about MAPs is that buyers actively participate in creating them. The same buyer who would resist "commit to signing by date X" willingly co-authors a project plan that contains exactly that commitment. Three reasons:
"Sign this commitment to purchase by X" is a request for concession. The buyer is being asked to commit before they have full information. The framing positions the parties as adversaries with opposing interests.
The substantive content is identical. The social framing produces dramatically different responses. Skilled AEs use this difference deliberately — they get the operational benefit of a written commitment without triggering the resistance an explicit commitment would.
Three additional reasons buyers co-author:
1. It makes the buyer look organized internally. When the buyer's manager asks "where are we with [vendor]?", being able to share a structured project plan is much better than saying "I'm still evaluating." The MAP becomes the buyer's tool for managing up.
2. It clarifies the buyer's own thinking. Many buyers don't actually know what their internal process looks like until they're forced to write it down. The MAP makes them confront the realities (yes, security takes 4 weeks; yes, the CFO will want a pilot) that they hadn't internalized. The clarity is valuable to them.
3. It distributes accountability. Owners on both sides means the buyer isn't bearing all the project-management weight alone. Distributed accountability feels lighter than concentrated accountability.
The combined effect: buyers don't resist MAPs because MAPs aren't asks. They're collaborative artifacts that produce value for the buyer too.
05When to propose the MAP
The timing of MAP introduction matters substantially. Too early (in cold outreach) feels presumptuous; too late (after technical demos and pricing) misses the cycle-compression opportunity. The sweet spot is the end of the first qualified discovery call, after value has been established and the buyer has signaled real interest.
The ideal proposal moment + framing:
"Great call — I think we have a real fit here. Based on what you've described, getting this in place by [their target date] would require a few internal steps on both sides. I'd love to put together a shared project plan with you — just a Google Doc — that lays out the path from here to a signed contract with the owners and dates on each step. That way we can both stay aligned on what needs to happen when. Want me to draft a first version after this call?"
The framing achieves three things at once: positions the MAP as a collaboration aid (not a commitment request), names the buyer's own target date (making the MAP serve their interest), and offers to do the drafting work (lowering the buyer's effort). Most qualified buyers say yes.
If the buyer resists: that resistance itself is diagnostic. A genuinely qualified buyer with real interest will engage with the MAP; a buyer who resists has reservations about the deal that need to surface. Treat MAP-resistance as a signal to dig into qualification rather than to push through.
06Without-MAP vs with-MAP
What the same deal looks like managed two different ways:
The difference isn't that MAP-managed deals do different things — they do the same things, but earlier, in parallel rather than serial, and without surprises. The compression compounds because nothing waits on something else that hadn't been planned for.
07The rollout playbook
Adding MAPs to an existing sales motion. The 7-step rollout:
- Build a templated MAP starter for each deal-size band. $25K deals don't need the same structure as $250K deals. Create 2-3 templates (mid-market, enterprise, strategic) with the appropriate level of detail. Reps customize from templates rather than starting from scratch.
- Train AEs on the proposal framing. The "collaborative project plan" framing is non-obvious; reps left to invent it themselves often propose MAPs in ways that feel commitment-asking and damage rapport. Train the exact language.
- Make MAPs required for deals above a threshold ($25K-$50K depending on org). Without the requirement, reps will skip MAPs on deals they "think will be easy" — exactly the deals where MAPs would catch the surprises. Require them.
- Tie MAP creation to a CRM stage gate. A deal cannot advance to "Proposal" or "Negotiation" stage without a linked MAP. Forces the discipline without managers having to police it.
- Review MAPs in weekly deal reviews. Manager 1:1s with reps include MAP review. Surfaces the "this date is slipping" conversation 4 weeks earlier than waiting for the close-date slip.
- Measure cycle time before vs after rollout. The metric to track: median time from "first qualified discovery" to "signature" for deals above the threshold. Cut by 20-40% within 90 days of disciplined MAP rollout, if the program is real.
- Iterate the template based on what surfaces. The first few months of MAP usage will surface recurring patterns — security always takes 4 weeks; procurement always wants a specific clause; CFO involvement always happens at a specific stage. Bake those patterns into the template for future deals.
08Common mistakes
The MAP needs signal context to be credible.
The conversation that earns the right to propose a MAP starts with a discovery call that demonstrates real understanding of the buyer's situation. Mama's signal-anchored briefs are what make that discovery call land — funding, hiring, tech-stack, and exec-move context delivered before you walk in so the buyer sees you as informed rather than fishing.