Mutual Action Plan Template for Enterprise Deals

A mutual action plan (MAP) is a shared, dated list of the steps a buyer and a seller both commit to before an enterprise deal closes, with a named owner on each side for every step. This page is that template, filled in with the milestones that stall B2B enterprise deals in practice: security review, legal, procurement, executive sponsor sign-off, pilot criteria, and go-live. No download, no signup.

That's worth saying up front. Dock's own mutual action plan template page walks through what a plan contains in descriptive sections and screenshots, then puts the editable table behind a signup. Not here. This page shows the table, filled in. And if you want the fuller definition first, including the test for whether a step belongs on the plan, start with the glossary entry and come back. Already know what a MAP is and need a working one? Keep going.

The mutual action plan template

Every enterprise deal has some version of these six milestones, whether anyone writes them down or not. Security review can kill a deal in week nine if nobody scheduled it in week two. Legal and procurement run on their own clocks. Usually slower than sales expects. And a pilot with no written success criteria turns into an unpaid extension of the sales cycle.

The table below gives each milestone a buyer-side owner and a seller-side owner. But most published versions of this template list the milestone and stop there, which leaves the reader with a line item nobody is responsible for hitting.

How to fill in the first draft

Two habits sink most first drafts: guessing at dates before you have them, and naming a department instead of a person. Work backward instead.

Start from the date you need for go-live, then count back through pilot, executive sign-off, procurement, legal, and security. Each one gates the next. A security review can't start before legal clears the data-handling terms. And procurement can't issue a PO before an executive sponsor has signed off internally. Trying to run these in parallel on paper doesn't make them run in parallel in practice.

Leave Status blank for now. That column exists for later. And who updates it matters more than what it says.

Who owns each milestone

Ownership on this table splits by which side controls the outcome, not by who cares more about the deal.

Security review, legal review, and procurement are buyer-side gates almost every time. Your champion can push on pace. But they rarely run these processes themselves. A named security lead, a named counsel, and a named procurement contact do. If you can't name any of those three people yet, that's the real gap in your deal, not a gap in the plan.

Executive sponsor sign-off sits on both sides. The buyer needs an internal executive who will defend the deal in a budget meeting you're not in. And the seller needs someone senior enough to remove friction fast when it shows up, usually the AE's manager or above. Pilot criteria and go-live are shared by design. The seller proposes the criteria. The buyer sets the bar that counts as success for them. And go-live only happens once both sides agree it happened.

Working out who actually sits in the buying committee is the harder problem underneath this one, and it comes before the table, not after.

How to introduce it without it reading as a sales tactic

Every experienced buyer has seen a mutual action plan used to pressure them toward a signature under the label of collaboration. That reputation is earned, and it's why most reps hesitate to bring one up at all.

Timing fixes most of it. Introduce the plan after your champion has validated the business case internally, not before. Offered on the first or second call, a MAP reads as exactly what it looks like: a sales tool. Offered once the buyer has already said yes internally and needs the deal through their own process, the same document reads as what it actually is: a project plan for something already approved.

Framing does the rest. In conversation, call it a joint project plan, not a mutual action plan. "Let's build the plan to get from here to signed" lands differently than "here's our mutual action plan," even though the artifact underneath is identical. The first sentence describes a shared problem. The second names a sales artifact. Buyers who've sat through a few of these deals recognize the label immediately.

Do ask the buyer what has slowed similar deals down at their company before, and build the table around their answer. Don't hand over a pre-filled table with your own dates already in it and ask them to sign off.

One thing worth saying plainly: a MAP built this way still serves the seller. It surfaces where a deal will stall, weeks before it does. Building one for that reason is legitimate work. But presenting it as anything else is what earns the plan its reputation as a stalling tactic in the first place.

When to update it

A MAP that only the seller updates works as a private status report on the deal. And the buyer never sees it, let alone edits it, so calling it mutual stops being accurate.

The glossary definition puts a specific test on this: a step only counts as progress if the buyer, not the seller, marks it done. Apply that test to the table. If procurement shows "In progress" because your AE thinks it's in progress, the plan is decoration. But if procurement shows "In progress" because the buyer's procurement contact updated the row themselves, the plan is doing its job.

Update it the moment something changes. Not on a weekly cadence set by your own pipeline review. A cadence like that turns the MAP into an internal reporting tool with the buyer's name attached to it, which defeats the point of a shared document in the first place.

Common mistakes

A handful of mistakes account for most of the MAPs that quietly stop mattering halfway through a deal cycle.

• Every step owned by the seller. When your AE's name sits in every buyer-owner cell, the plan measures your effort, not the buyer's progress.
• No executive sponsor named until week ten, usually the moment the deal needs one most. A plan built without a named buyer-side executive is missing the person who removes internal friction, and adding them late means asking for a real commitment when patience is thinnest.
• A go-live date with no milestone dated against it. The date on the calendar means nothing if nothing upstream is scheduled to hit it; procurement and legal don't move faster just because the deadline is close.
• Nobody keeps one master version. Two slightly different tables floating between a shared drive and an email thread is worse than no plan at all, because now the disagreement is about which version is real.

Before you send it

Run the filled-in table through your deal review cadence before it goes to the buyer. And check whether the buyer side has enough names on it already. Then look at the table itself. If the buyer side has only one name on it, that name is your champion, and the rest of the buying committee is still invisible to you.