A MAP turns a sales cycle into a shared project. The buyer sees exactly what has to happen, when, and who owns it. The seller gets honest commitment from the champion and real visibility into stall. Both sides stop guessing.
A Mutual Action Plan, often shortened to MAP, is a shared document that a seller and a buyer write together to agree on every milestone, owner, and date required to go from discovery to signed contract to go-live. It is a core artifact of the MEDDPICC and MEDDICC sales methodologies. Unlike an internal close plan, a MAP is visible to the buyer, co-edited by the buying committee, and treated as the project plan for the purchase itself.
The six things to understand about a Mutual Action Plan before you build the template, teach the team, or ship it into the CRM. The buyer owns at least half the rows, or it is not actually a MAP.
A Mutual Action Plan is a single shared document, co-authored by the seller and the buying committee, that lists every step required to evaluate, approve, sign, and launch the purchase. Each row has an action, an owner, and a date. The buyer sees the plan, edits the plan, and signs off on the plan.
In MEDDPICC the P stands for Paper Process, which is the full sequence of approvals, procurement, legal, security, and signatures the buyer has to run. The MAP is where that process gets written down with dates. Without a MAP, Paper Process is a conversation. With a MAP, it is a dated schedule the champion has agreed to.
A close plan is an internal document that lives in the CRM for the manager and the forecast. A MAP is visible to the buyer and co-edited by the buyer. The two can share rows, but if the buyer has never seen it, it is a close plan, not a MAP. The buyer visibility is what gives a MAP its force.
A good MAP is scheduled backward from the date the buyer wants to be live. Go-live anchors onboarding, which anchors contract signature, which anchors legal review, which anchors security review, which anchors final technical validation. The compounding slippage from any one slip becomes visible immediately when the dates work backward.
The MAP forces the champion to put their name on buyer-side rows: who runs the security review, who gets procurement engaged, who schedules the executive readout. A champion who will not take an owner column on any row is not a real champion. The MAP exposes that weakness while there is still time to fix it.
The MAP lives in a shared location both sides can edit, and a copy of the current state lives on the opportunity record. Rows that slip write to the stage history. The forecast reads the MAP, not the rep's optimism. The MAP is the artifact the pipeline review opens, not a slide the rep rebuilds for every meeting.
A MAP is not a two-row checklist of "demo scheduled, contract signed." It is the full project plan for the purchase, which on an enterprise cycle can be twenty to forty rows. The sections below are the real work categories every MAP has to cover before go-live. Any one of them missing is where a deal stalls.
Rows for discovery calls with each stakeholder, a documented use case, a quantified pain, and a technical validation session. The buyer agrees that the problem is worth the project before anyone commits to legal review. Skipping this section is why late-stage deals suddenly go dark on price.
A tailored demo against the buyer's real workflow, a technical deep dive with the owners who will integrate, and any proof of concept with success criteria written down in advance. The buyer signs off that the product does what they need before procurement gets involved.
The buyer co-authors a one-page business case: the quantified pain, the expected outcome, the investment, and the timeline. The seller supplies the template and the comparable customers. The buyer owns the numbers. The business case is what the champion carries to the executive readout.
A row for every item the security team will ask for: SOC 2 report, data processing addendum, penetration test summary, privacy review, vendor questionnaire. The dates are set from the security team's actual queue, not the champion's wish. This is where cycles slip when the row is missing.
Procurement adds the vendor, legal reviews the MSA, both sides exchange redlines, finance approves the spend. Each is its own row with the actual owner on the buyer side named. The default queue times for procurement and legal in that organization are the biggest unknown. The MAP forces the champion to go find them.
Final contract approvals, signature routing, PO issuance, and the handoff to customer success. The kickoff meeting is booked on the calendar before signature, not after. The onboarding plan starts from the signed go-live date. Nothing in this section is optional and nothing moves without the signature it is waiting on.
Teams often ship a close plan, call it a MAP, and wonder why cycles still slip. The distinction is small on paper and huge in practice. A close plan is a tool for the seller and the manager. A MAP is a tool for the seller and the buyer. The audience change is what forces the discipline that makes it work.
A close plan lives in the CRM and the forecast review. The buyer never opens it. A MAP lives in a shared document and the buyer edits it in real time. If a seller cannot send the link to the champion without rewriting half the rows, it is a close plan with a MAP label, not a MAP.
A close plan has the rep as owner on nearly every row because the manager wants to know what the rep is doing. A MAP has the champion, legal counsel, security lead, procurement, and executive sponsor as owners on half the rows. Buyer-side ownership is what makes a MAP a project plan rather than a monologue.
A close plan uses stage names, forecast categories, and MEDDPICC letters. A MAP uses plain English the buyer can read: "security review scheduled," "procurement engaged," "executive readout," "redlines returned." The language shift forces the seller to translate the sales process into project terms the buyer can defend.
On a close plan, a slipped row means the rep updates the forecast category. On a MAP, a slipped row means the buyer-side owner has to explain the slip to their own executive sponsor. Shared visibility converts an internal risk signal into a conversation the champion has to lead on their own side.
A close plan ends when the deal is signed. A MAP ends when go-live is confirmed and the kickoff is complete. The last third of the MAP is often the first third of customer success. That overlap is deliberate: it is what turns a signed contract into a working customer instead of a stalled implementation.
A mature team runs both. The MAP is the buyer-facing project plan. The close plan is the internal forecast artifact that captures metrics, decision criteria, pain, champion strength, and competition. The two share the dated milestones, but the audiences and the fields are different.
A MAP is simple to describe and surprisingly hard to run. The template is not the hard part. The hard part is getting the buyer to co-own it, keeping it current, and letting the dates tell the truth when they slip. These are the six moves mature teams drill into every rep who runs a serious cycle.
The rep introduces the MAP in the second or third conversation, framed as the way serious buyers run a purchase. Waiting until legal review to introduce the MAP wastes the leverage. Early introduction gives the champion the structure they need to run their own side of the project.
The MAP is built in a working session with the champion, not emailed as a draft. The seller shares a screen, lists the milestones, and asks the buyer to fill in the dates and owners for their side. Building it live surfaces exactly where the buyer does not know their own process, which is where the sales cycle actually lives.
The first row the buyer fills in is the target go-live date. Every other row is scheduled backward from there. Working backward exposes impossible timelines before procurement does: if the buyer wants to be live in six weeks and security review takes eight, that conversation happens in week one, not week seven.
The MAP is reviewed with the buyer-side executive sponsor as a formal checkpoint. The sponsor either confirms the dates, pushes back on them, or exposes that they do not actually support the project. All three outcomes are useful. A MAP never reviewed with the sponsor is a MAP without authority.
The MAP is opened at the top of every scheduled meeting. The question is always the same: what slipped, what moved up, what is at risk. Rows that slip are turned red in real time. The ritual itself is what keeps the MAP alive. A MAP that only gets reviewed in the final two weeks of the cycle is a MAP that no longer tells the truth.
When a row slips, the original date stays and the new date is added next to it. The buyer sees the slippage. Rewriting dates to hide the slip is the single most common way a MAP goes from a tool that works to a tool that produces false confidence. Honest dates are the only reason the forecast built on top of them can be trusted.
Strkr keeps the Mutual Action Plan on the opportunity record, with buyer-side and seller-side owners, dated rows, and visible slip. Strkr AI reads the MAP against the stage, flags the rows that are overdue, and surfaces the deals where the champion has not taken ownership of a single row. The forecast reads the plan, not the rep's optimism.
A Mutual Action Plan is a single shared document that a seller and a buyer write together. It lists every step required to evaluate, approve, sign, and launch a purchase, with an owner and a date for each row. Half the rows have buyer-side owners (legal, security, procurement, executive sponsor), and half have seller-side owners. Both sides open it on every call to see what slipped and what is at risk.
A close plan is an internal document that lives in the seller's CRM for the forecast and the manager. The buyer never sees it. A Mutual Action Plan is visible to the buyer, co-authored by the buying committee, and treated as the project plan for the purchase itself. The audience is the entire difference. A plan the buyer never opens is a close plan with a MAP label, not a MAP.
In MEDDPICC the P stands for Paper Process, the full sequence of approvals, procurement, legal, security, and signatures the buyer has to run before signing. The MAP is where Paper Process is written down with dates. Without a MAP, Paper Process is a conversation that gets rediscovered in week ten. With a MAP, it is a dated schedule the champion has agreed to in week two.
Early, in the second or third conversation, framed as the way serious buyers run a purchase. Waiting until legal review to introduce the MAP wastes the leverage. Early introduction gives the champion the structure they need to run their own side of the project and surfaces missing information (procurement queues, security review times) while there is still time to work around it.
At minimum: a target go-live date, discovery and validation rows, demo and technical fit rows, a business case, a security and compliance block, procurement and legal rows, signature and onboarding, and a buyer-side executive readout. Each row has an action, an owner on the correct side, a target date, and a status. On enterprise cycles a serious MAP runs twenty to forty rows across those blocks.
Both sides. Seller-side owners show up on discovery, demo prep, business case drafting, security questionnaire responses, and kickoff planning. Buyer-side owners show up on scheduling stakeholders, running the internal security review, engaging procurement, routing legal redlines, and the executive readout. If every row has the rep as owner, it is a close plan, not a MAP.
Open it at the top of every scheduled call, so the ritual is non-negotiable. Keep the original dates visible when rows slip, do not quietly rewrite them. Have the buyer-side executive sponsor review the MAP as a formal checkpoint. Store it in a shared location both sides can edit live. A MAP that only gets opened in the final two weeks of a cycle is a MAP that has already stopped telling the truth.
No. Mature teams run both. The MAP is the buyer-facing project plan with shared ownership and plain-English rows. The close plan is the internal CRM artifact that captures forecast category, decision criteria, metrics, pain, champion strength, and competitive position. The two share the dated milestones, but the audiences and the fields are different. One for the buyer, one for the manager.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
