Why Most MAPs Are Wishes with Columns
A Mutual Action Plan the customer never confirmed isn't mutual — it's a wish with columns. Customer-confirmed dates, backward from go-live, or it's fiction.
Open any CRM in any enterprise sales organization and you will find them: Mutual Action Plans, dozens of them, each a tidy grid of milestones and dates marching confidently toward a close date that happens to land three days before quarter end.
Look closer. Who wrote the dates? The seller. Who confirmed them? Nobody. What direction were they planned in? Forward from today, stacked end to end until they reach the number the seller needed. Whose deadline anchors the whole thing? The vendor's fiscal calendar.
That document is not a Mutual Action Plan. A MAP the customer never confirmed is a wish with columns. And a pipeline full of wishes with columns is why your forecast slips in the last two weeks of every quarter — the plans were never load-bearing, and you found out at the worst possible time.
What "mutual" actually requires
A real Mutual Action Plan establishes agreement between buyer and seller about the steps each will take to progress the buying journey. The structure is simple; the standard is not:
- Every step across three tracks — technical, business, and paper — including the customer's internal steps: approvals, review boards, committee dates. If your MAP contains only vendor activities, you've written a project plan for yourself and labeled it mutual.
- A named owner for every task, on both sides. Names, not teams. "Legal" is not an owner; a specific attorney is.
- Mutually agreed start and end dates — which means the customer said yes to each one, in writing.
- Exit evidence for every milestone. Not "security review — done" but the artifact that proves it: the assessment issued, the redlines returned, the PO executed. A milestone without exit evidence is a feeling with a date on it.
- Weekly status review with the champion, in a countdown format that makes slippage visible the week it happens, not the week it becomes fatal.
The single test that separates a MAP from a wish: customer-confirmed dates, or it is not mutual. Not "we sent it and they didn't object." Confirmed. In writing. Silence is not agreement; silence is a customer who hasn't read your document.
Work backward from their go-live, not your quarter end
The direction of planning matters more than the plan. A MAP built forward from today is an optimistic stack of vendor tasks. A MAP built backward from the customer's go-live date is a shared logistics problem — and shared logistics problems get solved by both parties, because both parties own the deadline.
In the flagship deal I use to teach this, the MAP was built backward from a February 2 production go-live — seven weeks ahead of the regulator's March 31 deadline, because the champion insisted on runway. Six representative rows: model-risk documentation submitted November 3, risk-committee readout November 10, third-party risk assessment issued November 14, MSA redlines returned November 21, order form and PO executed December 1, implementation kickoff December 8. Every row: a date, a named owner on the right side of the table, a status.
Notice what backward planning does to urgency. The vendor never once had to say "we need this by quarter end." The customer's deadline drove every date, and the vendor's quarter — engineered deliberately — happened to align. Urgency framed as their outcome is a shared deadline; urgency framed as your quarter is a lever they will use against you in the final negotiation.
The coaching move for leaders follows directly: in forecast reviews, replace "when will it close?" with "walk me backwards from the customer's go-live." Sellers who can only narrate forward from today are describing momentum. Sellers who can narrate backward from the customer's date — if signature is December 1, what must be true November 10, and is it? — are describing a plan. Momentum slips. Plans have named failure points you can fix.
The MAP is a qualification instrument disguised as a project plan
Here is the part that transforms the MAP from admin work into intelligence: the resistance it meets is the diagnosis.
In that same deal, when the seller first proposed the MAP, the buyer's sourcing lead declined to commit dates — for two weeks. The sales leader's read in the deal review was exact: "Either the case is weak or our contact can't get it approved — find out which." It was neither; sourcing was simply under-resourced. The champion escalated, the Economic Buyer assigned a named sourcing owner, and every date filled within a week.
Every one of those outcomes was worth knowing, and the MAP surfaced the question weeks before it would have surfaced itself. A customer who won't confirm dates is telling you something — the case isn't compelling enough, your contact lacks authority, a competing priority you haven't discovered is consuming the calendar, or an internal process you've been assuming doesn't work the way you think. All four are deal risks. All four are invisible in a MAP you wrote alone, because a wish with columns never gets pushback. It never gets read.
This is the general principle: an empty field is a finding, not a formality. An unconfirmed date isn't missing paperwork. It's the deal telling you where to work this week.
Two failure smells for leaders
Every customer-side owner is the champion. One name in every row means one thread — and one thread means you are one resignation letter away from a lost quarter. A healthy MAP has four or five distinct customer names: the champion, yes, but also the committee presenter, the security owner, the sourcing lead, the Economic Buyer on the signature line. If your champion is carrying every row, your MAP has just diagnosed a single-threaded deal — act on it.
The customer's internal steps are missing. Which committee, review board, or sign-off are you assuming rather than seeing? The steps that kill Q4 deals are almost never vendor steps. They're the buyer's internal ones — the risk committee that meets monthly, the vendor-registration process nobody mentioned, the second legal review triggered above a spend threshold. If those steps aren't rows in the MAP with owners and dates, they are landmines with no map.
Three questions to ask out loud in any deal review:
- What percentage of the next 30 days of MAP dates has the customer confirmed in writing?
- Which customer-internal step are we assuming rather than seeing?
- If signature is December 1, what must be true on November 10 — and is it?
That first question is worth making mechanical: in the deal-health scoring system I run, confirmed-MAP-dates is a standing component of every deal's weekly score, computed as the percentage of next-30-day dates the customer has confirmed. It decays automatically when the customer goes quiet — which makes it a slippage seismograph. The close date is a lagging indicator; the confirmation rate is a leading one.
The wish, converted
The fix costs one conversation. Take your best "committed" deal, open its MAP, and send it to your champion with a single ask: "Can you confirm these dates work on your side — and add the internal steps I'm missing?"
If it comes back confirmed and corrected, you have a real plan and probably a real deal. If it comes back silent, you have your answer too — earlier and cheaper than the last week of the quarter would have delivered it. Either way, the columns finally contain something better than wishes: evidence.
This essay is adapted from Chapter 9 of The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli. The book shows the full MAP and close plan run across a live enterprise deal, escalations included. The free Field Toolkit includes the Mutual Action Plan template — with the exit-evidence column — and nine more fill-in templates. Get the book and the Toolkit at the link in the footer.