Mutual action plan: what it holds and what it proves
A mutual action plan records the steps customer and seller agree to take, with an owner and a date for each. Check who confirmed the customer's steps and what has actually been completed.

Start with the customer's buying steps. Give each one a named owner, a date confirmed by that person and an agreed sign of completion. A champion's agreement, an owner's confirmation and a completed step give you different evidence about the deal. Keep those differences visible when you review the plan.
What a mutual action plan is
A mutual action plan, or mutual close plan, sets out the steps customer and seller agree to take, with an owner and date for each. It runs from the evaluation to a signed contract and the start of implementation.
Mutual action plan template and example
A mutual action plan template needs four columns: the step, its owner by name, the date that owner agrees and what shows the step is done.
Agree the applicable steps and their sequence with the customer. In the example below, replace each role with a person's name and enter the date that person confirms. Include the seller's own decision before the proposal as well.
| Step | Owner to identify by name | Date to agree with the owner | What shows it is done |
|---|---|---|---|
| The outcome and the date it matters | Owner to identify by name The customer's economic buyer | Date to agree with the owner To be agreed | What shows it is done The economic buyer states both in their own words |
| Written evaluation criteria | Owner to identify by name The customer's lead technical evaluator, with the business owner | Date to agree with the owner To be agreed | What shows it is done The customer's own criteria document, with priorities |
| Go or no-go before the Proof of Value | Owner to identify by name The customer's economic buyer | Date to agree with the owner To be agreed, before technical validation | What shows it is done The economic buyer confirms the go or no-go; for a go, the outcomes, timeline and next step are agreed |
| Proof of Value against the success criteria | Owner to identify by name The customer's technical champion | Date to agree with the owner To be agreed | What shows it is done Results read against the criteria by the people who wrote them |
| Seller's go or no-go before the proposal | Owner to identify by name The seller's account team; name the person responsible for the decision | Date to agree with the owner To be agreed, before the proposal | What shows it is done The team's go or no-go decision is recorded |
| Business case | Owner to identify by name The customer's deal champion, with finance | Date to agree with the owner To be agreed | What shows it is done The case in the customer's own format, with numbers its owners confirmed |
| Security review | Owner to identify by name The customer's security review owner | Date to agree with the owner To be agreed | What shows it is done Their questionnaire completed and their findings closed |
| Legal review | Owner to identify by name The customer's legal reviewer | Date to agree with the owner To be agreed | What shows it is done The legal reviewer confirms that the contract wording is agreed |
| Procurement and supplier setup | Owner to identify by name The customer's procurement owner | Date to agree with the owner To be agreed | What shows it is done The supplier registered and the order form agreed |
| Approval | Owner to identify by name The customer's economic buyer | Date to agree with the owner To be agreed | What shows it is done Approval within their authority, from the people whose agreement they need |
| Signature | Owner to identify by name The customer's authorised signatory | Date to agree with the owner To be agreed | What shows it is done The signed contract |
| Kickoff and success plan handover | Owner to identify by name The customer's project owner, with Customer Success | Date to agree with the owner To be agreed | What shows it is done The project owner confirms the kickoff took place and the success plan was received |
Give every customer step a named owner
Each customer step needs one person on the customer's side who will do it.
Write that person's name, not "procurement" or "legal". Where you do not know the person yet, finding out is the next thing to ask. Ask your contact which of the steps in the table their company has, and who runs each one.
Set the dates from the customer's date
Work backwards from the date the customer needs the result, and let each step's owner say how long their step takes.
Your quarter-end date is not evidence of the customer's deadline. Establish what the customer needs to achieve and by when before using it to set the plan's dates.
For the length of each step, ask how long it took the last time. HubSpot's guide to close plans suggests asking: "When you and your team last bought a solution like this, what were the steps? How long did legal take to return first cuts?" Then check the answer with the owner of the step. Legal's own estimate of its review is worth more than your contact's guess.
When the plan shows buying progress
The plan shows buying progress when the customer's people complete the steps they own.
Treat each customer line the way MEDDICC qualification treats each element: as an evidence claim, with five questions. What do we know, how do we know it, who confirmed it, what remains an assumption, and which conversation or action could create the missing evidence?
Use those questions to distinguish three levels of evidence for a customer step. Agreed by the champion: your champion has accepted the step on someone else's behalf. Confirmed by its owner: the person responsible has confirmed what the step involves, its date and what will show completion. Done: the step has happened and the agreed evidence is available.
Where a step has only been agreed with the champion, the next conversation is with its owner. Completing the seller's tasks does not supply that confirmation.
If a step slips, ask its owner for a revised date and what the delay changes for the later steps. Until that conversation, the completion date is unconfirmed; keep the other evidence of the owner's involvement.
Two decisions the Sales Engineer brings into the plan
The account executive and Sales Engineer put two go or no-go points in the plan: before the proof and before the proposal.
The account executive and the Sales Engineer confirm with the economic buyer that the outcomes, the timeline and the step after a successful proof are agreed before technical validation begins. In the plan, that is a line owned by the economic buyer and dated before the proof starts. Write the step after a successful proof beside the other agreements that come before a Proof of Value.

When the proof is done, the team decides internally whether to go to a proposal. That decision is the seller's line, and it rests on the customer's line before it: whether the people who wrote the success criteria have read the results against them.
The plan does not end at signature. When the customer decides, the value presentation and the Proof of Value success criteria become the customer's success plan, so the last lines hand the deal to Customer Success. In GitLab's sales process, the Solution Architect documents customer success criteria. The handbook says the document "should be signed by an accountable individual from both parties".
Reading the plan in a deal review
Start a deal review with the evidence for the customer's steps.
Ask three things of each customer line that is not yet done: who owns it by name, who gave the date, and what will show that it is done. Mark the owner and date as unconfirmed until the relevant person has confirmed them. Keep the evidence already established for the other parts of the step.

Then name the next conversation for each open line. For an approval step still unconfirmed, it is a meeting where you ask the economic buyer what they can approve and whose agreement they need. For a security review without a date, it is a call with the person who runs the review.
In my opportunity qualification training, a deal review examines the value hypothesis, the buying group, the MEDDICC evidence, the decision process, the missing evidence and the next step.
Sources
- Deal Closure. GitLab, 24 September 2026.
- A Guide to Using a Mutual Action Plan. Salesforce, 12 April 2024.
- Sales close plan: The best tool to close way more deals. HubSpot, 10 August 2026.
Facts last checked on 27 October 2026.
Updated 27 October 2026.