GTMGO TO MARKETPLAYBOOKS
← All playbooksComplex sales · Field guide

Mutual action plan

Coordinate a real buying decision with shared milestones and observable exit criteria.

When to use this

Use in a complex evaluation when both buyer and seller must coordinate evidence, approvals, and a decision date.

Before the working session

Run the process

01

Start with the buyer decision

Write the decision to be made, who can make it, why the date matters, and what a “no” decision would look like.

02

Work backward from evidence

For each criterion, name the proof artifact, owner on each side, review meeting, and exit condition. Technical validation should answer a buyer question, not simply produce a demo.

03

Expose dependencies

Mark milestones that must happen before others, lead times, and missing stakeholders. Use dates confirmed by the buyer rather than seller forecast dates.

04

Review together

At each joint check-in, update completed proof, changed priorities, blockers, owners, and the decision date. Share the revised plan with all working owners.

Fictional worked example

Fictional example: A buyer wants a decision before a budget meeting. The plan puts a sample-data validation before security review, legal review after commercial scope, and a final sponsor meeting. The buyer owns sample approval and the sponsor meeting date.

Failure checks

Editable workbook and filled example

Agree how the buyer will make a buying decision and what evidence must exist before that decision. Complete this together; an unsigned seller timeline remains a hypothesis.

Download editable Word workbook ↓

What you will complete

  • Buyer outcome and measurable definition of success
  • Decision to be made and alternatives including no purchase
  • Buyer decision authority and participating roles
  • Target decision date and business reason
  • Buyer plan owner and vendor plan owner
  • Last jointly reviewed date and next meeting

Give every milestone an observable exit condition. A demo held is an activity; buyer accepts a test result is evidence. Record dates as proposed or jointly confirmed. Identify security, legal, procurement and budget work before committing the final date.

Fictional filled evidence record

Buyer criterionProof and acceptance testReviewer and status
Weekly reporting can be reconciledApproved sample produces the same total as the buyer reference reportBuyer operations lead; awaiting test

Fictional action record

Milestone and exit conditionDepends onBuyer / vendor ownersDate and confirmation
Sample validation; buyer accepts reconciliation reportBuyer approves sampleOperations / solution leadOctober 8 proposed

Decision and next review

Keep the buying decision provisional. The buyer operations lead has not accepted the sample test, so security and contract timing are still estimates. The buyer sponsor reviews the revised sequence after sample approval; the seller must not treat this as purchase commitment.

Buyer operations lead approves the sample by October 5. Vendor solution lead runs reconciliation by October 8. Joint review on October 9 confirms whether to begin security review or stop the evaluation.

The download also includes approval sequencing, lead times, blockers, and acknowledgement by both plan owners.

The Word file includes editable response fields and blank tables. These examples are invented and do not represent a real buyer or employer.

NEW · PRESENTATION KIT

Same evidence.
Five different conversations.

A finished buying decision case for executives, finance, technical reviewers, operations and procurement. See what moves to the top of each page—and why.

Explore the presentation kit ↗Browse audience templatesBuild your own brief

See more fictional examples → · Open planning tools →