A mutual action plan is a shared, dated list of the steps a buyer and seller agree on to get from interest to signature and beyond. Done well, it's one of the most useful tools in a complex sale. Done the usual way, it's a spreadsheet the seller made, sent once and never opened by the buyer again. Our read is that a mutual action plan only works if the buyer's team uses it, and the best place to put it is inside the proposal.
What goes in a mutual action plan
A good plan lists every step between today and the buyer's goal, with an owner on each side and a date for each. On a typical enterprise deal, that includes the security review, the legal review, procurement setup, budget approval, a pilot if there is one, the signature and the kickoff.
Each step should say what's needed to finish it and who's responsible. The buyer-side steps matter most, because they're the ones you can't see and can't control.
Why most mutual action plans die
The seller owns it. It's built by the rep, kept in the rep's files and updated when the rep remembers. The buyer has no reason to look at it.
It lives in a separate file. The proposal gets forwarded around the buyer's company. The plan stays in someone's inbox.
It's written in the seller's terms. Steps like "verbal commit" and "contract signed" matter to the seller's forecast. The buyer cares about different milestones.
The dates come from the seller's quarter. When the end date is clearly the seller's deadline, the buyer treats it as the seller's problem.
Making a mutual action plan mutual
Build it with the champion. Set up a working session, put the plan on the screen and fill in the steps together. Ask what their internal process looks like. You'll learn about approvals you didn't know existed.
Use their names and their steps. Put the names of their legal lead, their security reviewer and their budget owner on the plan. People take ownership of steps with their names on them.
Start from the date they care about. Ask when they need the new system working, then work backward to the signature. A go-live date belongs to the buyer, and a plan built back from it feels like their plan.
Keep it to one page. If the plan needs a scroll bar, it's too detailed. Put the step-level detail in a linked sheet if needed.
Put the plan in the proposal
The proposal is the one document every reader on the buyer's side sees. So make the plan its final chapter, right after the price. Each reader can find their own step. The CFO sees when budget approval is needed. Legal sees when the contract review starts. The signer sees the whole path in one picture.
In a live web proposal, the plan can be updated as steps finish, so the link always shows where things stand. The PDF keeps a snapshot for the file. This also gives your follow-up notes a natural purpose. Each one can point to the next step on the plan, which is covered in our post on how to follow up on a proposal.
A use case
Here's how it often plays out. A cybersecurity company is selling a monitoring service to a regional bank. The champion is the chief information security officer.
The rep's first plan had six steps, ending in "contract signed" on the last day of the rep's quarter. The bank never opened it.
The rebuilt plan came out of a 30-minute session with the champion. It started from the date the bank wanted the service live, ahead of its next regulatory exam. Working backward, it added steps the rep hadn't known about. The bank's vendor risk review, a sign-off from the board's risk committee and a data protection review by the bank's counsel. Every step had a name from each side. The plan sat at the end of the proposal, and the champion used it in the risk committee meeting to show the timeline was realistic.
Questions we hear about mutual action plans
When should we introduce a mutual action plan?
After discovery confirms there's a fit and before the proposal goes out. That way the plan can shape the proposal, and the proposal can carry the plan.
What if the buyer won't commit to dates?
Ask for the one date that matters to them, like a launch or a budget deadline, and work back from it. If nobody can name a date that matters, the deal may be stuck in indecision. See why so many deals die in no decision.
Who keeps it updated?
One owner on each side. A short weekly update from the seller, confirmed by the champion, is usually enough to keep it honest.
Does a mutual action plan work for smaller deals?
A lighter version does. Even a five-step plan with names and dates helps a smaller deal move, as long as the buyer helped build it.
What tool should we use for it?
Whatever the buyer can open without logging in. A page inside the proposal works for most deals. Shared project tools can work too, but only if the buyer's team already uses them.
The short version
A mutual action plan works when the buyer helps build it, sees their own names and steps on it and finds it inside the document their whole team reads. Start from their date, keep it to one page and make it the last chapter of the proposal.
For the people behind each step, see writing for a B2B buying committee. When a deal needs a plan both sides follow, start a proposal.
