What a mutual action plan is
A mutual action plan is a short, shared list of the steps both sides will take to reach a decision, each with an owner and a date. It is sometimes called a mutual close plan or a joint evaluation plan.
Complex B2B purchases involve many people and many steps: technical reviews, security questionnaires, budget approval, legal review. Without a written plan, each side has its own idea of what happens next, and deals drift. A mutual action plan makes the path visible to everyone, and makes it obvious when something has stalled.
The word that matters is mutual. A plan written by the seller and sent to the buyer is a forecast. A plan agreed with the buyer is a commitment.
When to introduce one
Introduce a plan when there is a real evaluation underway and more than a couple of steps to a decision. Usually that means after a successful discovery call or product demo, when the buyer has said they want to go further.
Do not force one into a simple, fast purchase. And do not introduce it as a sales tactic. Present it as a way to make their evaluation easier: "There are a few steps on both sides before you'd be ready to decide. Would it help to write them down so nothing gets missed?"
A simple template
Keep it short enough to fit on one page. A table works well:
| Step | Owner | Due | Status | | --- | --- | --- | --- | | Confirm requirements and success criteria | Buyer: project lead | [date] | Done | | Technical deep dive with IT | Seller: solutions engineer | [date] | Booked | | Security questionnaire | Buyer: security; Seller: security lead | [date] | In progress | | Reference call with an existing customer | Seller: account executive | [date] | Not started | | Business case to finance | Buyer: champion | [date] | Not started | | Commercial proposal | Seller: account executive | [date] | Not started | | Legal and procurement review | Buyer: procurement | [date] | Not started | | Decision | Buyer: economic buyer | [date] | Not started | | Kickoff meeting | Both | [date] | Not started |
Add the decision date the buyer is working towards, and why it matters to them, such as a budget cycle, an event, or a contract ending. That reason is what keeps the plan moving.
Building it with the buyer
- Draft it, then review it together, in a meeting, not by email. Ask what is missing.
- Let them own their steps. Only they know their internal approval process. Ask: "Who needs to sign off, and what will they need to see?"
- Name people, not departments. "IT" does not do anything; a named person does.
- Check the dates are realistic. A plan that is already late on day one loses credibility.
The steps often reveal stakeholders you have not met yet. That is a natural moment to ask for introductions. See multithreading in B2B sales.
Keeping it alive
A plan that is written once and forgotten is worse than none.
- Review it at the start of every meeting with the buyer, in two minutes: what was done, what is next.
- Update it the same day and share the current version.
- When a date slips, ask why. A slipped step is often the first sign of a problem, such as a new priority, a sceptical stakeholder, or a budget question.
- Keep one version, in a shared document both sides can see, rather than copies in email threads.
After the contract is signed
The plan should not end at signature. Its last steps belong to the start of the customer relationship: the customer kickoff meeting, the first milestones, and the people who will be involved. Carrying the plan across the handoff from sales to the team that delivers shows the customer that what was promised during the sale is what will happen next.
CallShark is being built to keep the meetings in a deal, and their agreed next steps, attached to the account from first call to kickoff. The product is temporarily down.