How to build a mutual action plan for a sales deal
Build a mutual action plan around the buyer's goal. Map approvals, name milestone owners, check dependencies, and confirm dates and exit criteria.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a mutual action plan is
A mutual action plan is a shared agreement between a buyer and a seller about the work needed to reach a decision or start using a purchase. It begins with the result the buyer wants and works back through the reviews, evaluations, and approvals required to get there. Each milestone says who leads it, what must happen first, and what evidence will show it is complete. If the buyer has yet to agree to the plan, the seller can record it as a proposal and use it to guide the next conversation.
A deal close plan often centers on getting to a signature. A mutual success plan can carry the same work forward through rollout or first use. In either case, define the end point with the buyer. For example, if a team wants a new service ready for an internal launch, signing the order is one milestone on the way to that goal. Time to test the service, prepare data, and train users may determine the latest feasible signature date.
What it does for the business
- Put the buyer's deadline to workA date tied to a real event helps both teams prioritize work. If the buyer needs a system ready for a planned launch, use the plan to reserve the people who will test it and schedule the decisions that affect that launch.
- Bring in approvers at the right timeA written approval path helps your buyer champion, the person advocating for the purchase inside the customer organization, see whom to involve. They can ask procurement about intake before either team budgets time around a tentative signature date.
- Base the forecast on completed workNamed exit evidence makes deal reviews more concrete. A sales manager can look at accepted test results, booked reviews, and open approvals to decide which dates to use in the forecast and which to revisit.
- Carry decisions into implementationOnce the deal moves forward, the people setting up the purchase can see which outcomes and acceptance checks the buyer agreed to. They can use that record to plan the first handoff and keep any remaining work with its agreed owner.
How to build a mutual action plan, step by step
Find the buyer's goal and the current deal record
A useful plan starts with a result the buyer can describe in their own words.
What to do
- Pick one deal and decide where the plan ends. For a purchase decision, stop at the agreed decision event. For a first rollout, also include the work needed to make the purchase usable.
- Open the latest buyer emails, meeting notes, evaluation briefs, and any timeline the buyer has shared. Write down who supplied each material fact and when it was recorded.
- State what the buyer wants to achieve and why the date matters. Record whether the date came from a buyer event, a joint discussion, or an internal sales target.
- Compare records when two dates or outcomes disagree. Ask which one governs the plan and keep both visible with their sources until someone resolves the difference.
Why
Different participants may be working toward different events. One person may mean a contract signature by the target date while another means a live rollout. Settling the outcome and the end point first gives you a basis for deciding which tasks belong in the plan and which people need to confirm the timing.
Identify the decisions and prerequisites
A task can start only when the prerequisites for that task are in place.
What to do
- List the buyer's decision criteria, meaning the conditions the buyer uses to choose. Turn each criterion that still needs proof into an evaluation milestone, such as a trial results review or a reference call.
- Map the approval process for this deal. Find who approves budget, who checks terms, and who gives the final go-ahead. Record the input each approver needs to begin.
- Write milestone dependencies as links between specific rows. If a committee needs a written recommendation after a trial, link the recommendation to the trial assessment and the committee decision to the recommendation.
- Check for missing predecessors and circular dependencies. If two owners say each needs the other's approval first, record that conflict and ask them to clarify which work can start.
Why
A calendar can make reviews look as if they happen independently even when they share a prerequisite. Mapping the links shows which work can proceed in parallel, such as budget preparation and a trial, and what must finish in sequence. The resulting plan gives each team a way to see the downstream effect of a delay.
Assign owners and define exit evidence
A milestone is complete when you can point to the agreed evidence.
What to do
- Ask the person responsible for each milestone to accept ownership. Distinguish that person from contributors and final approvers. If an approval role is known and the person is unknown, record the role and leave the person unresolved.
- Give each row exit criteria, the conditions that show the work is complete. For an evaluation, state which checks the buyer will review and which record will capture their acceptance.
- Write the action so that the owner knows what to produce. Replace a label such as 'procurement' with a milestone like 'submit completed purchase request' and give procurement approval a separate row if it comes later.
- Track the status of the work and the evidence of agreement. A seller may have already produced a proposal while the buyer still needs to confirm who will review it and by when.
Why
A broad activity name rarely tells someone what they owe the other team. A clear deliverable and acceptance check make it easier to hand work off and resume after a pause. They also let the plan show partial progress accurately when a document exists and a decision is still pending.
Test the timing against the dependencies
A date becomes credible when the people, prerequisites, and calendar support it.
What to do
- Ask the milestone owners how long the work takes once they can start. Include review queues and fixed approval meetings. Clarify whether durations use working days or calendar days.
- Work forward from the first available start. For each dependent milestone, use the latest finish among its prerequisites, then account for the owner's availability and any scheduled decision window.
- Compare the earliest feasible finish with the buyer's target. Trace the critical path, the chain of dependent work that controls the finish under your scheduling assumptions. Look for the unresolved gate that could change that timing.
- Record proposed dates as proposals. Where a duration or owner's availability is unknown, state the condition needed to estimate the date and explain what the plan can establish with the evidence you have.
Why
Backdating a plan from the desired finish is useful for seeing when work would have to start. A forward check shows whether that start and the work that follows are feasible. For example, a missed committee meeting may make a new date necessary even when the other work fits comfortably.
Check the plan and confirm it with the buyer
A shared plan stays useful when changes and commitments have a clear record.
What to do
- Review the plan row by row against the deal record. Check that every predecessor points to a real milestone, each exit criterion matches the decision it represents, and every confirmed date has a source.
- Walk the plan with the buyer champion and the people who own the consequential gates. Ask them to confirm the outcome, their roles, the order of work, and the next milestone they can commit to.
- Record agreement when it arrives. Keep unresolved rows visible and capture the next action that would resolve each one. Save a dated version of the plan that both teams can refer to.
- Update the plan after a material change. If a trial takes longer than expected, check the milestones that depend on the trial and get fresh agreement on any revised commitments.
Why
An agreed plan starts losing value when one team revises its dates and the other keeps the old version. Reviewing only the items that change and the milestones they affect makes updates easier. The latest record should always show what the buyer has agreed to and which decisions remain open.
Common mistakes
- Using the quarter-end date as the buyer deadlineAn internal forecast date gives the buyer little reason to reserve staff or expedite an approval.
- Assigning someone by job title aloneA role can guide your investigation while the actual owner and their availability remain open.
- Giving a review one row from start to finishSeparate the submission and the decision when they have different owners, prerequisites, or finish evidence.
- Treating meeting attendance as acceptanceRecord the decision made or the evidence accepted to show what the meeting accomplished.
- Moving only the late milestoneA slipped prerequisite can change every dependent date and the assumptions behind the forecast.
What a good result looks like
- The buyer's outcome and the reason for the target date are traceable.
- Each milestone names its prerequisite work and the evidence needed to finish.
- Owners, calendar assumptions, and agreements have an explicit status.
- The plan identifies the open decision most likely to affect timing and who can resolve it.
- Both teams can tell which next action to take and what version of the plan they are using.
And then what? Using the result
- Share the proposed milestone sequence with the buyer champion and ask them to correct the approval path.
- Ask the owner of the next open gate for a specific decision, input, or feasible review window.
- Reserve people for the work whose dates and owners are confirmed.
- Update your forecast from the agreed milestones and flag any date still dependent on an open decision.
- Pass the accepted outcome and outstanding actions to the implementation lead when the deal reaches handoff.
When to run it
- A serious evaluation startsBuild a first version once the buyer has a goal and both teams can identify work worth committing to.
- Several teams have to approve the purchaseMap their inputs and decision dates before overlapping reviews turn into a single queue.
- A buyer has an implementation deadlinePlan back from first use and test the path forward from the work that can start now.
- An active deal slipsReopen the dependency chain and discuss the specific change with the people who own the affected milestones.
Questions people ask
What is a mutual action plan in sales?
It is a plan a buyer and seller use to coordinate the work needed to reach an agreed outcome. It ties milestones to owners, dependencies, and proof of completion. A seller can prepare the first draft and record buyer agreement as it comes in.
Who owns a mutual action plan?
The buyer and seller share responsibility for keeping it accurate, and each milestone has a named owner. Agree on who maintains the shared copy. Ask the people who can make or accept each decision to confirm their roles.
How do you set dates in a mutual action plan?
Set dates from availability, durations, and prerequisite work, then compare them with the buyer's target. Include working-day rules and fixed review windows where they affect the sequence. Record dates that still need confirmation as proposed.
What should a mutual action plan include?
Include the buyer's outcome, target date and reason, milestones, dependencies, owners, exit criteria, and agreement status. Add the next action for each consequential gap. A reader should be able to tell what would change if the current blocker persists.
When should you introduce a mutual action plan?
Introduce it once the buyer has a concrete outcome and both teams have work to coordinate. A discovery call can establish the goal. An evaluation planning conversation often supplies the first milestones and the people who need to agree to them.
What do you do when the buyer has not agreed to the plan?
Label it proposed and ask the buyer to confirm the next decision and its owner. Use the reply to correct the sequence and record the scope of agreement. If the buyer agrees to the trial only, keep later milestones provisional.
More jobs in Sales & outbound
Build a mutual action plan, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac