Mutual Action Plan: What It Is and How to Build One

What a mutual action plan is for

Most complex B2B deals are not lost to a competitor. They end in no decision: the buyer keeps doing what it does now, which costs nothing this quarter. The usual cause is not price. It is a deal with no agreed path to signature, where a security review, a budget meeting or a legal review starts late and the buyer’s deadline passes.

A mutual action plan puts both organisations on one schedule. It shows the buyer what has to happen, and by when, for them to get the result they asked for. It also shows the seller, early, which step is most likely to slip and who on the buyer’s side owns it.

What goes in each row

How to build one in six steps

1. Start from the buyer’s date

Ask when the buyer needs the product live and why that date matters to them: a peak season, a contract, an audit. A date with a business reason behind it holds; a date the seller chose does not.

2. List every approval the buyer needs

Security, legal, procurement, budget, the executive who signs. Ask the buyer which of these slowed their last purchase of this size.

3. Put each step on its date, working backwards

From go-live, subtract implementation, then signature, then legal review, then budget approval. Each step gets the latest date that still protects the go-live.

4. Find the critical path

The longest chain of dependent steps sets the earliest possible finish. Any delay on it moves the go-live date; delays elsewhere do not. Start the longest step on that chain first.

5. Send it to the buyer to correct

A plan the seller wrote alone is a forecast. A plan the buyer has corrected is a commitment. Ask the buyer to change any date or owner that is wrong.

6. State what happens if a date slips

Write down which date moves if a critical-path step is late, so a slip is reported rather than absorbed quietly.

Worked example: Brightwater Distribution

This is the plan Meridian sent Brightwater to correct. The shaded rows are the security review, the step on the critical path.

The critical path runs through the security review. Brightwater’s last software rollout slipped two quarters on security review, so the questionnaire goes back in week one. If it is not returned by 22 September, the 1 November go-live moves, and the plan says so.

The business case the budget meeting sees is built from Brightwater’s own numbers. Eleven shipments a month miss the contractual window with its largest retail customer, at an average penalty of $4,200: 11 × 12 × $4,200 = $554,400 a year. Modelled at a conservative 60% recovery, the penalties avoided are $332,640 against a year-one cost of $128,000: a net $204,640, or 2.6 times the cost.

What a one-line prompt gets wrong

Try it: a shortened Prompt 10

This is a shortened version of Prompt 10 from the Sales & Business Development pack, set up to run on its own. Paste it into ChatGPT, Claude or Gemini and fill in the brackets.

You are a former enterprise sales director who has closed six- and seven-figure software deals with long procurement cycles. A deal without a joint schedule usually ends in no decision, so you build the close backwards from the buyer's go-live date, give every step one owner, and start the longest approval first.

THE DEAL:
- What the buyer is buying and the year-one value: [product, amount]
- The date the buyer needs it live, and why: [date, business reason]
- The buyer's approvals: [security, legal, procurement, budget meeting, who signs]
- What slowed the buyer's last purchase of this size: [if known]

THE PEOPLE:
- Your contacts and their roles: [names or roles on the buyer's side]
- Your side: [account executive, solutions engineer, legal]

Produce:

1. THE MUTUAL ACTION PLAN. Every step from today to go-live as a table: step, owner (one named role), date, depends on. Dates worked backwards from go-live.

2. THE CRITICAL PATH. The chain of dependent steps that sets the earliest finish, and the step on it that must start this week.

3. THE SLIP RULE. For each critical-path step, which date moves if it is late.

4. THE EMAIL TO THE BUYER. A short note sending the plan and asking them to correct any date or owner.

Use only the dates and approvals I give you. Where an approval's length is unknown, mark it [TO CONFIRM WITH BUYER] rather than guessing.

The full Prompt 10 has eight parts rather than four. It adds the negotiation boundaries and what to do if the answer is no, and it reads the Deal Brief built by prompts 01 to 09, so the plan uses the buyer’s own business case and the account research already done.

Negotiating inside the plan

A mutual action plan also sets the order of the negotiation. Terms other than price, such as contract length, start date, scope and a customer reference, are traded first, because each has value to one side and costs the other little. Price is discussed last, once the buyer has agreed everything else it needs. Meridian’s plan put the budget meeting on 6 October with Brightwater’s VP presenting, not the seller’s representative, because the buyer’s own executive carries more weight in that room.

Checks before you send it

• Every date is worked backwards from a go-live date the buyer gave you.
• Every step has one named owner.
• The critical path is marked, and its first step starts this week.
• Each step shows the step it depends on.
• The plan says which date moves if a critical step slips.

Questions

Written by a former Gartner Managing Partner and investment banking SVP

The guides and the prompt templates on this site come from a career spent building these documents: board decks, forecasts, business cases and hiring decisions, as Managing Partner at Gartner, SVP in investment banking and Country Manager at international subsidiaries. The worked examples are published in full on each product page. Browse the Prompt Library.