The buyer never opened your mutual action plan.

The plan looked tidy.

It had a target signature date, a security review, legal approval, procurement, and kickoff. Every row had an owner. The seller had even colour-coded the status column.

There was one awkward detail: the buyer had never seen it.

The account executive had built the entire thing after a call, uploaded it to the opportunity, and described it in the forecast meeting as a mutual action plan. It was really a private theory about how the deal might close.

That distinction matters. A seller can write tasks for a buyer, but the act of writing them does not create agreement. If the buyer has not corrected the dates, added the missing people, or taken responsibility for a milestone, the document records hope with impressive formatting.

A mutual action plan is a buying plan

A mutual action plan, often shortened to MAP, is a shared document that lays out the work required for a buyer to evaluate, purchase, implement, and start getting value from a product or service.

Salesforce describes a MAP as a document shared between buyer and seller that sets expectations across the sales cycle. It usually starts with a repeatable template, then changes to fit the opportunity. Close puts the emphasis on objectives, actions, responsibilities, and timelines.

Both descriptions point to the part that gets lost in practice: the plan is shared.

The useful version helps the buyer coordinate a decision. The weak version helps the seller defend a close date.

A buyer may need to involve security, finance, legal, operations, and an executive sponsor. Some of those people will join late. Some will have requirements that neither the seller nor the first contact knows yet. A shared plan gives that group one place to correct the sequence and see what is waiting on them.

The seller benefits too, but that comes second. When a buyer will not help set the path, the opportunity may be less mature than the CRM stage suggests. Finding that out in August is better than finding it out on the final afternoon of September.

Begin with the date the buyer cares about

Most weak plans begin with the seller's quarter.

"We would like to get this signed by 30 September" may be important inside the selling company. It gives the buyer no reason to spend political capital, chase a lawyer, or squeeze a security review into an already crowded week.

Start with the change the buyer wants to make and the date by which it needs to be working.

Perhaps a new sales team starts on 1 November. A contract expires in December. A territory launch needs clean CRM data before the first campaign. A finance team needs a new process in place before annual planning.

Now work backward together.

If onboarding needs two weeks, the account must be configured before onboarding. Security and legal must finish before configuration. The business owner must approve the scope before the contract reaches legal. Each dependency earns its place because it protects the buyer's outcome, not because it appeared in the seller's template.

If the buyer has no operational date and no consequence for delay, leave the date blank. A fictional deadline will make the plan look complete while hiding the most important thing you have learned.

Use a plan small enough to update

A MAP does not need project-management software. For many deals, a shared table is enough.

The "evidence it is done" column does more work than a percentage-complete field. "Security review at 80%" can remain at 80% for three weeks. "Security approved in writing" is either true or it is not.

The "why it matters" column keeps the plan from turning into vendor homework. It should be written in the buyer's language. "Complete procurement" is a seller task. "Keep the November rollout on schedule" explains why someone inside the account should care.

Keep the status choices plain: not started, in progress, blocked, done. If the plan needs a legend to explain nine colours, it has become another admin system.

Draft it before the call. Finish it on the call.

Do not open a blank spreadsheet in front of a buyer and ask them to design your process. Bring a first draft based on deals that have gone well.

Then give the buyer permission to disagree with it.

That sentence shows preparation, acknowledges that the buyer knows their company better than you do, and makes editing the document part of the meeting.

Move through the plan slowly enough for the buyer to react. Who owns security? Does procurement start before or after legal? Is the executive sponsor actually available that week? Is the go-live date real, or merely preferred?

Watch what the buyer changes. An added stakeholder, a longer review window, or a deleted milestone may tell you more about the deal than a polite "looks good."

Send the updated version while the conversation is still fresh. The meeting notes should capture each commitment, owner, date, and concern. Those same details should update the CRM so the shared plan, follow-up tasks, and forecast do not drift into three different stories.

Make ownership genuinely mutual

A plan with twelve seller tasks and one buyer task is a project checklist. A plan with twelve buyer tasks and no seller obligations is an assignment.

Both sides should own work.

The seller may owe a security package, reference call, revised scope, commercial response, implementation plan, or answer from a product specialist. The buyer may owe introductions, usage data, internal feedback, approval, or access to a review process.

Name a person rather than a department whenever possible. "Legal" cannot miss a date because "Legal" never accepted one. "Maya to introduce us to Dan in Legal by Thursday" can be discussed, changed, and completed.

There will be rows where the owner is unknown. Keep them visible. "Security owner: to be confirmed by Friday" is more honest and more useful than assigning the row to your contact because their name is the only one you have.

A buyer's no improves the forecast

Salespeople sometimes avoid sharing a plan because they worry it will create friction. It can. That is part of its value.

A buyer may say the target date is unrealistic. They may refuse to involve finance yet. They may explain that legal will not review anything before a technical evaluation. They may not know who signs.

None of those answers damages a healthy opportunity. They replace assumptions with facts.

The harder signal is a buyer who likes the product but will not spend fifteen minutes correcting the route to a decision. That does not mean the deal is dead. It does mean the close date deserves less confidence.

Managers can review a MAP without turning the forecast call into document theatre. Ask:

• Dates: Which dates did the buyer provide or confirm?
• Ownership: Which milestone does the buyer own next?
• Evidence: What will show that milestone is complete?
• Access: Who is missing from the plan?
• Change: What changed after the last meeting?
• Disagreement: Where has the buyer corrected us?

The last question is especially useful. A plan that never changes may be perfect. More often, nobody outside the sales team is using it.

Do not force a MAP onto every deal

A straightforward purchase with one buyer and a short cycle may need only a recap email and a dated next step. Introducing a formal plan can add ceremony without reducing risk.

Use one when the decision has enough moving parts to benefit from a shared sequence:

• Several stakeholders or departments are involved.
• Evaluation, security, legal, or procurement can run at different speeds.
• Implementation must meet a real operational date.
• A missed dependency will hurt both sides.
• New decision-makers are likely to enter late.

The plan can start small. Three agreed milestones are better than twenty guessed ones. Add detail as the buyer reveals how the decision works.

The plan belongs in the conversation

A useful MAP is the document people refer to when something changes, regardless of how plain the file looks in the opportunity record.

Open it during the meeting. Ask who needs to be added. Change the date when security needs another week. Record the reason. Turn each commitment into a follow-up task, and keep the CRM aligned with what both sides have agreed.

That is when the plan becomes useful for forecasting. The close date no longer depends only on a rep's confidence. It sits beside a trail of buyer-owned work, completed evidence, and named risks.

If the buyer never opens the plan, you still learned something. Just do not call it mutual.

Quick answers

What is a mutual action plan in sales?

A mutual action plan is a shared document that lists the milestones, owners, dates, and completion evidence required for a buyer to evaluate, purchase, implement, and start using a solution. Buyer and seller build and update it together.

When should a sales rep introduce a MAP?

Introduce it once the buyer has a meaningful outcome and the decision involves enough people or dependencies to need coordination. A good moment is near the end of discovery, when both sides understand the problem but still have time to shape the evaluation and approval process.

Who owns the mutual action plan?

The rep usually maintains the document, but ownership of the work is shared. Each milestone should name the person responsible on the buyer or seller side. The buyer should confirm dates, add missing steps, and correct assumptions.

What should a MAP include?

Include the buyer's desired outcome, the operational date, milestones, why each step matters, a named owner, due date, evidence of completion, status, and any known risk. Keep it simple enough to update during a live conversation.

Is a mutual action plan the same as a close plan?

The terms are sometimes used interchangeably. In practice, a close plan often centres on the seller's signature date. A useful MAP continues through implementation or first value and is built around the buyer's path, responsibilities, and timing.

Research note: This guide builds on public mutual action plan guidance from Salesforce and Close. LogicNotes added the buyer-date model, evidence column, example plan, co-editing language, and forecast review questions.