A proposal can sit in an inbox while everyone believes someone else owns the decision.
The seller waits for approval. The buyer waits for a procurement answer. Procurement waits for a scope nobody has submitted. A target date survives in the calendar after its dependencies have stopped moving.
A mutual action plan makes that buying work visible. Give each decision an owner, an approver, a piece of evidence, and a date both sides can explain.
Salesforce describes a mutual action plan as a shared buyer and seller document covering purchase and implementation steps. The worksheet below applies that definition to a services purchase. Its fields and operating rules are a proposed method, not a vendor requirement.
Use a Plan When the Purchase Has Dependencies
Start with the decision the buyer needs to make. Then ask what must become true before that decision is possible.
Use a shared plan when the answer crosses teams. A consultant may need an agreed scope before procurement can review terms. The buyer may need an implementation owner before a sponsor releases funds. A delivery team may need an access decision before it can confirm a start date.
Those dependencies deserve a place where both sides can see them.
A short next-step note is enough when one person can make the purchase and the remaining question is narrow. Write the open question, its owner, and the agreed response date. A seven-column worksheet adds little to a straightforward document review.
Offer the plan as a working aid. Ask whether it reflects the buyer's process. If the buyer already has a purchasing checklist, use that checklist and add missing evidence fields. Maintaining competing versions creates another coordination task.
The plan earns its place by answering a question the participants cannot currently answer together: what blocks a responsible decision?
Separate Buyer Milestones from Pipeline Stages
A seller's pipeline stage describes the seller's view of an opportunity. A buyer milestone describes an observable piece of buying work.
“Proposal sent” records seller activity. “Operations accepts the proposed service boundary” records a buyer decision. Those events may happen days apart. They may never both happen.
Keep B2B sales pipeline stages in the seller's system. Use the shared plan to track the evidence needed for the buyer's choice.
Replace vague milestones with inspectable ones:
| Seller shorthand | Buyer milestone | Completion evidence |
|---|---|---|
| Discovery complete | Problem and exclusions confirmed | Buyer accepts a written problem statement |
| Proposal delivered | Scope is suitable for internal review | Scope owner records acceptance or requested changes |
| Legal stage | Required terms reviewed | Procurement records unresolved items and their owners |
| Verbal agreement | Authorized decision recorded | Named approver confirms the selected option and conditions |
These are examples, not universal stages. Ask the buyer which reviews apply. Do not invent legal, security, or procurement obligations for an organization you have not examined.
Keep the choice to decline visible. A completed buying process can produce a decision to defer, reduce scope, or do nothing. The plan should record that outcome accurately.
A Fill-In Mutual Action Plan Template
Put a short heading above the table: decision under consideration, buyer coordinator, seller coordinator, version date, and next review date.
Use one row per decision or prerequisite. Copy the table into a document both sides can access.
| Decision | Owner | Approver | Evidence | Dependency | Target date | Current status |
|---|---|---|---|---|---|---|
| [Question to resolve] | [Person producing the answer] | [Person accepting the answer] | [Document, test, or recorded decision] | [Earlier row or external condition] | [Agreed date or unknown] | [Proposed, agreed, blocked, complete, or stopped] |
| [Next question] | [Named person] | [Named person] | [Acceptance evidence] | [Dependency or none] | [Date or unknown] | [Status and reason] |
The owner moves the row forward. The approver decides whether its evidence is sufficient. A department name does not tell anyone who will answer the next question. Use a role temporarily if a person is unknown, then mark the assignment unresolved.
Atlassian's DACI framework separates the driver who coordinates a decision from its approver, contributors, and informed participants. Apply that distinction where it clarifies authority. A row's approver can differ from the final purchase approver.
Keep evidence specific. “Discussed on call” leaves the result open to interpretation. “Scope owner accepts the exclusions in version three” identifies what was decided. If acceptance is conditional, record the condition beside it.
A target date is a planning input. Mark it unknown when the owner cannot yet estimate it. Record why the date matters, such as an internal planning meeting. A seller's desired booking date does not establish the buyer's deadline.
Walk Through a Fictional Consulting Purchase
Consider a fictional business evaluating a consultant to document its supplier intake process. Every role, sequence, and date in this example is invented. The example describes coordination, not a completed engagement or a promised result.
The buyer wants a process map and a proposed operating procedure. The consultant needs access to a limited set of sample documents. Procurement must review the proposed agreement. Operations must assign someone to evaluate the deliverables.
The buyer coordinator drafts this plan with the consultant:
| Decision | Owner | Approver | Evidence | Dependency | Target date | Current status |
|---|---|---|---|---|---|---|
| Is the problem defined? | Buyer coordinator | Operations sponsor | Accepted problem statement and exclusions | None | Week one | Agreed |
| Is the scope suitable? | Consultant | Operations sponsor | Deliverables and acceptance criteria accepted | Problem definition | Week two | Proposed |
| Can samples be shared? | Buyer document owner | Buyer access approver | Written sample boundary and access conditions | Scope draft | Week two | Unassigned approver |
| Are terms acceptable? | Procurement contact | Authorized procurement approver | Review outcome and remaining conditions | Agreed scope | Week three | Waiting on scope |
| Can delivery begin? | Buyer implementation lead | Operations sponsor | Named reviewer and available start window | Access and terms decisions | Week four | Proposed |
The access decision has no named approver. Leave that assignment unresolved. Do not mark the row complete because the coordinator believes someone will approve later.
The consultant can draft a sample deliverable without receiving internal documents. That work may clarify scope. It does not remove the access dependency or authorize the exchange of buyer material.
Procurement can also identify its required inputs before scope approval. Separate “confirm review inputs” from “accept terms” if those are different tasks. Parallel work belongs in separate rows when its completion evidence differs.
Before accepting the plan, the buyer coordinator checks the dates with the people doing the work. The consultant confirms delivery availability separately. Neither side treats a proposed start window as a reservation until the relevant agreement establishes it.
Build Evidence Before Adding More Meetings
Use the next review to resolve uncertainty. Bring the rows that changed, the evidence now available, and the decisions still missing.
For the fictional scope row, the consultant attaches a deliverable outline. Operations annotates the acceptance criteria. The coordinator records which version the sponsor accepted. Everyone can now see what procurement will review.
For an access row, record the approved boundary rather than copying sensitive material into the plan. A link to the controlled record may be enough. Ask the buyer which participants may view that record.
The plan should remain a coordination document. Keep contract text in the agreement and working data in the buyer's chosen system. Record where the authoritative answer lives.
This is where consultative selling becomes practical. Ask which unanswered question prevents the buyer from choosing. Provide evidence for that question. Repeating the proposal does not answer a missing implementation concern.
When evidence conflicts, preserve the conflict. The sponsor may accept a scope that the delivery lead considers incomplete. Assign the disagreement to an owner. Do not turn two different views into a fictional consensus.
Revise a Slipped Milestone Without Pressure
Suppose the fictional procurement contact becomes unavailable. The review moves beyond week three. The plan now contains a date that no longer represents an agreed forecast.
Record the slip before proposing a replacement. Keep the original target in a change note. State the reason, the affected dependency, the current owner, and the next point of review.
A useful revision reads: “Terms review is blocked pending a replacement reviewer. Buyer coordinator will confirm ownership. Delivery start remains unconfirmed.”
That statement gives both sides something concrete to resolve. It makes no claim about the buyer's interest or the consultant's scarcity.
Revisit downstream dates after the dependency changes. Moving procurement one week does not prove delivery moves exactly one week. The consultant may have a different available window. The buyer's implementation reviewer may also need to reschedule.
If the new timing no longer fits, discuss a smaller scope, a later start, or a pause. Record the selected option and its consequences. Avoid an arbitrary deadline designed to preserve the seller's forecast.
Send a short revision note to the agreed participants. Name the changed rows and the open question. A new version should help participants understand the change without comparing two entire documents.
Hand the Buying Plan to the Delivery Owner
Approval changes the work. The buyer has selected an option. Delivery still needs its own sequence, responsibilities, and acceptance conditions.
Use the final buying review to identify what carries into client onboarding: approved scope, exclusions, access conditions, delivery contacts, unresolved conditions, and the first acceptance milestone.
Ask the delivery owner to acknowledge those inputs. A salesperson forwarding a document does not establish that delivery accepted its commitments. Record any disputed assumption before confirming the onboarding plan.
Keep the buying plan as the decision record. Start an onboarding plan for execution. Link the two in the buyer's chosen workspace so a later participant can trace why the engagement exists.
Do not silently carry proposed dates into delivery as commitments. Confirm the start window against the signed scope and current availability. Keep any outstanding approval condition visible until its owner resolves it.
Stop When Nobody Owns the Next Decision
An unowned plan is a document, not an agreement to keep pursuing a purchase.
Ask the buyer coordinator whether the decision remains active. Name the missing owner or prerequisite. Offer a concrete pause condition: resume when the buyer identifies the approver, confirms a review window, or restores the underlying priority.
If the buyer declines a shared worksheet but offers a workable next step, use that next step. Refusing your preferred format does not establish lack of interest.
If nobody accepts responsibility for the next decision, stop scheduling activity around it. Record the unresolved condition without inventing a rejection or a future close date. Keep future contact within the buyer's stated preference.
The worksheet is complete when it records the decision and its evidence. Keep ownership visible.
Sources
- Salesforce: The Sales Team's Guide to Using Mutual Action Plans. Definition and shared purchase-planning context. Checked 2026.10.28.
- Atlassian Team Playbook: DACI Decision-Making Framework. Driver, approver, contributor, and informed roles. Checked 2026.10.28.