What is a mutual action plan?

A mutual action plan (MAP), sometimes called a close plan or joint execution plan, is a shared document that maps every step, owner, and date from the current stage of a deal to a signed contract and often through onboarding. It is mutual because both the buyer and the seller build it, agree to it, and own steps in it. Instead of a rep privately guessing at a close date, the path is explicit and jointly committed, which is why MAPs are common in complex B2B and enterprise deals.

What should a mutual action plan include?

At a minimum: the milestones between now and close (technical evaluation, security review, legal, procurement, signature, kickoff), a named owner for each on both the buyer and seller side, a due date per step, and the success or decision criteria at each gate. Many teams also list the stakeholders involved and the target go-live date the plan is built backward from. Keep it short enough that the buyer will actually maintain it with you.

How do you create a mutual action plan?

Start from the finish line. Agree the target go-live or signature date with your champion, then work backward listing every step that must happen, who owns it, and when it is due. Build it in a shared tool both sides can edit, review it live on calls, and update statuses as steps complete. The plan is only useful if it stays current, so make updating it part of every deal touchpoint rather than a document you write once and forget.

Where should you keep a mutual action plan?

Keep the working plan somewhere collaborative and easy to edit, which is why many teams build it in Notion rather than a rigid CRM field. The catch is that the rest of your revenue team lives in the CRM. NoteLinker solves that by rendering the Notion plan live on the matching HubSpot deal, so reps write the MAP in Notion and managers, deal desk, and leadership see it on the deal record without anyone copying it across.

What is the difference between a mutual action plan and an account plan?

An account plan is an internal, seller-side document about how you will grow and manage an account: whitespace, stakeholders, and strategy. A mutual action plan is buyer-facing and deal-specific: the agreed, dated steps to get one deal to close. You might have an ongoing account plan for a customer and a separate mutual action plan for each active opportunity within it.

Mutual Action Plan: How to Build and Run One

Most deals do not die from a hard no. They die from drift: a security review nobody scheduled, a procurement step that surfaced two weeks late, a champion who assumed you were handling the thing you assumed they were handling. A mutual action plan exists to kill that drift by making the path to close explicit and jointly owned.

This guide covers what a mutual action plan actually is, what goes in a good one, a template you can build in Notion in half an hour, and how to keep it visible to your whole team by surfacing it on the HubSpot deal. It is a close cousin of running a structured qualification like MEDDPICC in Notion; the MAP is the execution plan that qualification points at.

In this article

What a mutual action plan is

A mutual action plan (MAP), also called a close plan or joint execution plan, is a shared document that lists every step, owner, and date from where a deal is now to a signed contract, and often through kickoff. The word that matters is mutual: the buyer and seller build it together and each owns steps in it.

The payoff is not paperwork, it is predictability. When the path to close is written down and jointly owned, your forecast stops being a guess and deal slippage drops, because the steps that usually surprise reps late are already on the calendar.

What goes in a good mutual action plan

A MAP should be complete enough to catch the steps that derail deals and short enough that the buyer will actually maintain it with you. These are the pieces that earn their place.

Milestones from now to close
Every gate between the current stage and signature: technical evaluation, security review, legal, procurement, mutual signature, and kickoff. List the ones a deal at this size actually hits, not a generic template.
An owner on each side
Every step names who owns it, on both the buyer and seller side. A milestone with no owner is the one that slips.
A date per step
Due dates, built backward from the target go-live. Dates are what make the plan a forecast instead of a wish list.
Decision criteria at each gate
What has to be true to clear each step. This is where a MAP borrows from your discovery questions: you already know the criteria, the plan just makes them dated.
Stakeholders and the target date
Who is involved at each stage, and the go-live or signature date the whole plan is built backward from.

Build the plan backward from the date the buyer wants to be live, not forward from today. The finish line is the only fixed point everything else has to fit inside.

A mutual action plan template you can build in Notion

You do not need a dedicated tool. A MAP is a table with a few columns, and Notion is a good place to build it because both sides can read and edit the same live document. Here is the build.

1
Set the close date and work backward
Agree the target signature or go-live date with your champion first. Every other date in the plan hangs off this one, so pin it before you list a single step.
2
List the steps as rows
Create a Notion database with one row per milestone and columns for step, owner (buyer or seller), due date, and status. Add the decision criteria as a note on each row.
3
Assign owners and dates
Fill an owner and a due date for every row. Leave nothing unassigned. If you cannot name an owner for a step, that is the risk to raise on the next call.
4
Review it live and keep it current
Walk the plan on calls, update statuses as steps complete, and let the buyer edit it. A MAP is only worth building if it stays current, so make updating it part of every touchpoint.

If you want the internal, strategic companion to this buyer-facing plan, our account plan template covers the seller-side view.

Common mutual action plan mistakes

A MAP fails in predictable ways. Most of them come from treating it as a document you produce rather than a plan you run.

A MAP that works

Built backward from the buyer's go-live date
Every step has an owner and a date
The buyer has edited and agreed to it
Updated on every deal touchpoint

A MAP that dies in a folder

A generic step list not tailored to the deal
Owners left blank or all on your side
Sent once and never opened again
So long the buyer refuses to maintain it

The subtlest failure is the last one on the left: a MAP that only you can see. If the plan lives in your head or a private doc, your manager cannot inspect the deal, deal desk cannot spot the missing procurement step, and a covering rep inherits nothing. The plan has to be where the team works.

Where the plan should live: Notion plus the HubSpot deal

Here is the tension. The best place to build and co-edit a MAP is a flexible doc like Notion. The place your revenue team inspects deals is HubSpot. Keep the plan in one and it is unusable in the other, unless you bridge them.

Best fitPickBuild in Notion, surface on the HubSpot dealWhenYour team writes in Notion and manages pipeline in HubSpot

Co-edit the MAP in Notion with the buyer, and render it live on the matching HubSpot deal with NoteLinker. Reps get a flexible plan, managers get it on the record they already inspect.

PickA shared spreadsheetWhenYou have no CRM discipline yet and just need a start

Better than nothing, but it lives outside the deal, goes stale, and gives your manager no view into the pipeline it belongs to.

PickA plain CRM text fieldWhenYou need it visible in HubSpot and nowhere else

Visible to the team, but a flat field is painful to structure and edit, so reps stop maintaining it and the plan rots.

NoteLinker adds a card to the HubSpot deal record that renders your Notion plan live, matched by deal name. The rep keeps building the MAP where it is easy, and the whole team sees it on the deal.

1
Install NoteLinker from the HubSpot Marketplace
Find NoteLinker in the HubSpot App Marketplace and install it. Standard OAuth, no code or API key.
2
Connect Notion and name the deal match
Grant access to the database that holds your action plans, then tell NoteLinker which Notion property holds the deal name (or Deal ID).
3
Open the deal in HubSpot
The NoteLinker card renders the matching Notion plan on the deal record, so the close plan sits next to the pipeline stage. Rows are visible by default.

Put your close plan on the HubSpot deal

NoteLinker renders your Notion mutual action plan live on the matching HubSpot deal, so managers, deal desk, and covering reps see the path to close without copy-paste.

Get Started

Why a shared, visible MAP moves deals

When the plan is both mutual and visible, the whole deal gets easier to run. The context is where the work happens, for everyone who touches the opportunity.

With the MAP on the HubSpot deal, your team can

Forecast with confidence, because the dated steps to close are on the record, not in the rep's head.
Run deal reviews off the actual plan, so managers coach the missing step instead of asking for a status update.
Hand off or cover a deal without losing the thread, since the plan travels with the record.
Trust the plan is current, because the card reads live from Notion every time the deal loads.

This is the same principle behind keeping strategy and execution in the right tools, which we make the full case for in why Notion is the best environment for strategy and HubSpot is the best for execution. Build the plan where collaboration is easy, and show it where the team runs the pipeline.

A mutual action plan is not extra process for its own sake. It is the difference between hoping a deal closes on time and knowing exactly what has to happen, who owns it, and when. Build it backward from the buyer's date, make it truly mutual, and keep it live on the deal your whole team already opens.