← Back to blog

A mutual action plan is a short, shared document that lists every step between today and the day your prospect is live on what you sell, with a name and a date on each step, and with the prospect's steps on it as well as yours. It is written with the buyer, not for them. The template below fits on one page, takes about twenty minutes to draft after a first call, and does one job: it turns "this sounds good, let's keep talking" into a sequence of dated commitments that both sides can see slipping.

What is a mutual action plan?

The word that matters is mutual. Most reps already keep a close plan: the internal list of what has to happen for the deal to land this quarter. That plan lives in the CRM, the buyer never sees it, and it is mostly hope with dates attached.

A mutual action plan is the buyer-facing version. It has the same shape, a list of steps with owners and dates, but half of the owners are on the prospect's side, the prospect helped write it, and it starts from the buyer's goal rather than yours. The last line is not "signature." It is whatever the buyer is actually trying to get done: the team trained, the first campaign live, the number moved.

That framing is what makes it work. A plan that ends at your signature is a sales document, and buyers treat it like one. A plan that ends at their outcome is a project plan for something they want, and they will help you keep it on schedule.

Why bother? What a mutual action plan actually changes

Four things, in roughly the order you will notice them.

It surfaces the buying process early. Every company has steps you cannot see from outside: security review, procurement, a legal pass, a budget meeting that happens once a month. Writing the plan together is the moment the prospect says "oh, and it has to go through the vendor committee, which meets on the second Tuesday." You learn that on the first call instead of the last week of the quarter.

It names the people. A plan with dates needs owners, and asking "who on your side owns this step?" is the least awkward way ever invented to find out who signs, who evaluates, and who can say no. The names you get back are the buying team.

It replaces sentiment with dates. "They seem really engaged" is not a forecast. "The technical review is scheduled for the 24th and their IT lead accepted the invite" is. When a step slips, you see it slip, and you can ask about it while there is still time to do something.

It tells you when a deal is not real. A prospect who will not put a name or a date on any step on their side is telling you something. It is better to hear it in week two than in week nine.

What goes in a mutual action plan?

Eight fields. Anything beyond these is padding that the buyer will stop reading.

1. The outcome. One sentence, in the buyer's words, describing what they are trying to have true by a specific date. Not your product. Their result.
2. Success criteria. How they will know it worked. A number if you can get one, a description if you cannot.
3. The buying team. Names and roles on their side: who evaluates, who signs, who has to be consulted, who will use it day to day.
4. Your team. Names and roles on your side, so they know who to chase.
5. The steps. Each one has an owner, a date, and a one-line description. Discovery, demo, technical review, security questionnaire, reference call, pricing, legal, signature, kickoff, go-live. Keep it to the steps that actually gate the next one.
6. Decision criteria. What they are evaluating against, and what "yes" requires. If you do not know, that is a question, and it goes on the plan as one.
7. Risks and dependencies. The things that could stall it: a budget cycle, a competing project, a person on leave, an integration that has to exist first.
8. The go-live target. The date the outcome in field 1 is supposed to be true. Every step's date is derived backward from this one.

The mutual action plan template

Copy this into a shared document, fill in what you know, mark the rest as questions, and send it to the prospect within a day of the first call.

Outcome

• What we are trying to achieve, in your words:
• By when:

Success criteria

• We will know this worked when:

Who is involved

• On your side (name, role, what they own in this process):
• On our side (name, role, what they own):

Steps

For each step, one line: what happens, who owns it, target date, status.

• Discovery call held. Owner: both. Date: [done].
• Working session with the people who would use it. Owner: [buyer name]. Date:
• Technical or security review. Owner: [buyer name]. Date:
• Pricing and commercial terms agreed. Owner: [your name]. Date:
• Reference conversation, if wanted. Owner: [your name]. Date:
• Legal and procurement. Owner: [buyer name]. Date:
• Signature. Owner: [buyer name]. Date:
• Kickoff. Owner: both. Date:
• Live, and the success criteria measured. Owner: [buyer name]. Date:

Decision criteria

• What a "yes" requires:
• What we still need to find out:

Risks and dependencies

• What could slow this down:

Next check-in

• Date, and who is bringing what:

Delete the steps that do not apply. Add the ones that do. A plan with six real steps beats one with fourteen aspirational ones.

How to build a mutual action plan from the first call

The mistake most reps make is trying to write the plan after discovery, from memory, alone. The plan is easier to build if you walk into the first call with a rough draft already in your head and let the prospect correct it.

Before the call: pre-fill what research can tell you. Three of the eight fields can be drafted from public information before you ever speak to the prospect. What changed recently at the company (a funding round, a new executive, a product launch) is usually the outcome they care about, or close to it. What the prospect is probably measured on, given their role, is a first guess at the success criteria. Who else holds the adjacent titles, on the company's team page or their public professional profiles, is a first guess at the buying team, and that one you look up yourself. Write these down as guesses. Wrong guesses are fine. They give the prospect something to correct, which is faster than something to invent. If you want the fifteen-minute version of the first two, it is in our guide to researching a sales prospect before the first call.

In the call: ask for the plan, not the close. Somewhere in the second half of a good first call, once the prospect has said what they are trying to do, ask a version of this: "If we did this together, what would have to happen on your side between now and it being live? Who would be involved?" Then write down what they say. That is the plan. You are not asking for a commitment. You are asking them to describe their own process, and most people are happy to.

After the call: send it within a day. Type up what you heard, in their words where you can, with the steps they named and the names they gave you. Put "draft, please correct anything I got wrong" at the top. Send it to the prospect and ask them to edit it. Getting a buyer to change a date on a shared document is the first small act of co-ownership, and it is worth more than any amount of enthusiasm on the call.

Every touch afterward: open with the plan. The plan becomes the agenda. Which step is next, who owns it, is the date still right. When a step slips, ask why. The answer is usually the real obstacle in the deal, and you would not have heard it otherwise.

Mistakes that turn a mutual action plan into a sales document

It is your close plan with the buyer's logo on it. If every step is something you do, and the last step is "contract signed," the buyer reads it as pressure. Half the owners should be theirs, and the last step should be their result.

There are too many steps. A plan the buyer will not read is not a plan. Keep the steps that gate the next step and cut the rest.

No buyer owner on any step. This is the tell for a deal that has not really started. Do not fill the gaps in with your own name to make the plan look complete. Leave them blank and ask.

Nobody updates it. A plan that was accurate three weeks ago is worse than no plan, because it gives everyone false confidence. Update it before every meeting, and make the update visible.

It is used as a closing tactic instead of a working document. Buyers can tell. The plans that work are the ones where the seller genuinely wants the buyer's outcome to happen on time, and is using the document to make that more likely.

Where the inputs come from

Most of what you can pre-fill before the first call comes from public information about the company and the person: the trigger that makes this the right quarter, what the prospect is likely to be measured on, and the objections you should expect. That research is what a SalesBriefAI briefing does for you. You give it a company and a person. It reads what is publicly available about both, shapes the findings around the methodology you sell with, and hands back a briefing with an engagement plan, a sales strategy, and the likely objections. The inputs for your first draft of the plan are in there, so your guesses take minutes to write down before the call, and the prospect can correct them.

See what a briefing looks like, or try it free. Free credits to start, no card, enough to run briefings on a few accounts you know well and judge the research for yourself.

Building the plan starts with a good first call, and a good first call starts with fifteen minutes of research. If you want the checklist for that, it is here: the sales call prep checklist.