How to Write a Mutual Action Plan for a Mid-Market Deal

Why do mid-market deals stall after a great demo?

Mid-market deals usually stall because the buyer's internal steps were never written down. The demo went well, but nobody agreed on who signs, who reviews security, who checks the contract, and by when. A mutual action plan fixes that by putting every remaining step, owner, and date in one shared document.

I see the same pattern in founder-led sales and in small sales teams. The rep hears "this looks great, let me take it to the team" and logs the deal as likely to close. Then two weeks pass. Then a month. The deal is not lost. It is simply sitting in a queue at the buyer's company that the seller cannot see.

Mid-market is where this hurts most. The deal is big enough to need several approvals, but the buyer usually has no procurement team running a formal process. So the process gets invented on the fly, and your deal waits while it does.

What is a mutual action plan?

A mutual action plan is a short, shared document that lists every step both sides must complete for the deal to go live, with an owner and a target date for each. It is written with the buyer, not for the buyer. Its job is to make the buying process visible to both sides.

The word "mutual" is the important part. A close plan that lives in your CRM is a forecast. A mutual action plan that the buyer has read, edited, and agreed to is a commitment. It covers their steps, like legal review and budget sign-off, as well as yours, like sending the order form or setting up a pilot.

It goes by other names. Some teams call it a success plan, a joint execution plan, or a close plan. The name does not matter. What matters is that it is shared, it has dates, and both sides can point to it when something slips.

When should you introduce a mutual action plan in a mid-market deal?

Introduce it right after the buyer confirms the problem is worth solving and your product is a real option. That is usually after the first proper demo or discovery follow-up. Earlier feels pushy. Later means the buyer has already started an internal process you are not part of.

I use one simple trigger. When the buyer says some version of "I need to run this by" someone, that is the moment. They have just told you there are steps you do not know about. The natural reply is to ask what those steps are and offer to map them together.

The phrasing I like is plain. "Would it help if I drafted the steps between now and going live, so both of us can see what is left?" Most buyers say yes, because they also do not want this project to drag. You are offering to do the admin work for them.

What should a mutual action plan for a mid-market deal include?

It should include the goal the buyer wants to reach, the go-live date they care about, every step between now and that date, an owner for each step, a target date for each step, and a short note on what could block it. Keep it to one page that a busy executive can read in two minutes.

Start with the buyer's goal in their own words. If they told you they need the new process running before their next quarter starts, write that at the top. Every date below should work backward from it. This keeps the plan about their outcome, not your quota.

Then list the steps in order. For a typical mid-market software deal, that includes technical review, a security questionnaire, a pricing and terms discussion, legal review of the contract, budget approval, signature, and onboarding kickoff. Your list will vary. The point is to name each one rather than lump them into "procurement".

For each step, name a person, not a department. "Legal" is not an owner. "Priya from legal" is. If the buyer does not know who owns a step yet, write that down too. An unknown owner is the earliest warning sign you will get.

How do you get the buyer to actually use the plan?

Make it easy to edit, review it on every call, and tie it to the buyer's own deadline. A plan the buyer helped write gets used. A plan you emailed as a polished attachment gets filed. The format matters less than the habit of opening it together.

I prefer a shared Google Doc or a simple shared page over a PDF. The buyer should be able to add a step or change a date without asking you. Some teams use digital sales rooms for this, and those work too, as long as the buyer actually opens them.

Then build the review into your rhythm. Start every follow-up call by opening the plan and checking what moved. It takes three minutes. It also changes the tone of the call from "are you ready to buy" to "how is our project going", which is a far better conversation for both sides.

How does a mutual action plan improve your forecast?

It replaces gut feel with evidence. A deal with a shared plan, named owners, and steps completed on time is a much safer bet than a deal where the rep simply feels good. You can forecast on what has actually happened, not on how the last call felt.

Here is the rule I would use with a small sales team. A deal only moves into your commit forecast when the buyer has agreed to a mutual action plan and the first two steps are done on time. Everything else stays in best case. It is a strict rule, and it is supposed to be.

You can track this in HubSpot or Salesforce with a couple of simple deal properties: whether a plan exists, the next step owner, and the next step date. Then a weekly view of deals where the next step date has passed shows you exactly where to spend attention. If you already run a stale deal alert, add the plan date to it.

What are the most common mistakes with mutual action plans?

The biggest mistakes are writing the plan alone, filling it with your own sales stages, making it too long, and never updating it. Each one turns a shared tool into a sales document the buyer ignores. The plan only works when it reflects the buyer's real process.

The first mistake is the most common. A rep writes a plan full of seller steps like "send proposal" and "negotiate" and calls it mutual. The buyer reads it and sees nothing about their own work. Ask the buyer to walk you through what happens on their side, and write that down.

The second is length. A plan with forty rows looks thorough and gets abandoned. Mid-market buyers are busy people doing a buying task on top of their real job. Eight to twelve steps is usually plenty. If a step needs detail, link to it.

The third is silence when dates slip. A missed date is information. If the security review was due Friday and nothing happened, say so on the next call and ask what changed. Often the answer reveals a new stakeholder, a budget freeze, or a competing project. You want to know that now, not at quarter end.

How does the plan handle discounts and pricing pressure?

It gives you a fair way to trade. When a buyer asks for a discount, you can tie any concession to a step in the plan, like signing by a date that matters to them. That keeps pricing tied to commitments rather than pressure, and it protects your margin.

Without a plan, discount requests arrive at the end and feel like a test of nerve. With a plan, you already know the buyer's timeline and constraints. You can say something like, "If signing by the end of the month helps your go-live date, I can look at the terms." Both sides get something real.

This only works if you have clear rules on what you can offer. I wrote about setting those in how to set discount guardrails for a small sales team. A plan plus guardrails turns negotiation into a short, calm conversation.

What happens to the plan if your champion leaves?

A good plan survives a champion leaving, because the steps, owners, and dates are written down where other people can see them. You can bring the next stakeholder up to speed in one meeting. Without a plan, the deal often dies quietly with the departure of the one person who understood it.

This is an underrated benefit. Every name on the plan is a relationship you can use. If your champion moves on, the person from finance or IT who owned a step already knows the project exists. Start there. I covered the wider recovery steps in what to do when your champion leaves mid-deal.

What should you do next?

Pick one open mid-market deal that has gone quiet after a good demo. Draft a one-page plan with the buyer's goal at the top and their steps listed in order. Send it as a draft for them to correct. Then open it at the start of your next call.

Do not try to roll this out across every deal at once. Use it on two or three deals, notice what the buyers change, and turn that into your template. The template you end up with will match how your buyers actually buy, which is the whole point.

I help founders and small revenue teams design the go-to-market systems behind deals like these, from the CRM properties that track a plan to the reports that flag a stalled step. If your pipeline is full of deals that stalled after a great demo, reach out and let's chat.