Midmarket Mutual Action Plans: Map Approvals Before the Proposal

A midmarket mutual action plan is a buyer-confirmed sequence of approval steps, each with a named owner, a realistic date, and the specific evidence that step requires. Build it before the proposal, not after. The proposal is an output of the approval map, because pricing only moves when it lands on a path the buyer has already agreed to walk.

Here is the pattern worth recognizing. Illustrative scenario: a midsize logistics company, a VP of Operations who loves the product, a short run of strong calls, a proposal sent soon after at the VP's request. Then weeks of near silence. When the deal reappears, a questionnaire arrives from someone you have never met, finance asks which budget line this comes from, and the VP mentions that whoever runs the rollout has not been identified yet. Nothing went wrong in your sales process. The approval path simply did not exist when you priced the deal.

Gartner's research on the B2B buying journey frames purchasing as a set of non-linear jobs that buyers revisit rather than complete in sequence, including problem identification, solution exploration, requirements building, supplier selection, validation, and consensus creation ^[1]. A plan keyed to your sales stages will misread that behavior every time. This article gives you a four-role approval map, an evidence table you can pre-stage, a confirmation script for the sponsor conversation, and the handful of metrics that show whether the plan is real or decorative.

The Proposal That Arrives Before the Approval Path Exists

The proposal feels like progress because it is the artifact both sides can see. Your sponsor asked for it, your manager wants it in the CRM, and the opportunity moves to a later stage. None of that tells you whether the company can actually buy in the quarter you forecast.

What the proposal does do is start a clock you do not control. The moment pricing enters the building, it triggers reviews that were never scheduled: a finance check against the current budget cycle, a technical review, and an integration question about the systems the product has to sit next to. Each of those reviews begins with its own discovery, and none of them accept your champion's summary as sufficient input.

The operating rule is simple to state and uncomfortable to follow. You map the approval path first, confirm it with the sponsor in writing, and then price the deal against the path. That order protects you twice. It stops you from forecasting against a date nobody internal has committed to, and it stops the buyer from running a sequential diligence process that restarts discovery after the commercial conversation is already done.

If you want the upstream half of this, the qualification work that should happen before a mutual action plan exists, our guide on how to qualify the decision behind a midmarket deal covers testing the buying jobs rather than the stage name.

Four Roles That Decide Your Midmarket Deal

Midmarket companies are big enough to have specialists and small enough that one person often holds two of these roles. Your job is not to fill four boxes with four different names. It is to know which human owns each decision and to have spoken with each of them at least once.

The business sponsor owns the problem and the business case. They are usually the only person who can convene the rest of the group, which makes them essential and dangerous in equal measure. Essential because nothing moves without their calendar. Dangerous because sponsor confidence is a weak proxy for whether an approval path exists.

The finance approver owns the budget source, the contract term, and the timing question that decides your quarter: does this spend fit the current cycle or wait for the next one? A sponsor who says "we have budget" and a finance approver who says "that line is committed through March" are describing the same company.

The IT or security reviewer is the person you ask what their review covers and what they will need from you. For AI-enabled products, these reviewers increasingly ask vendors to map controls to the NIST AI Risk Management Framework ^[2]. If your product touches contact data or outbound communication, expect questions grounded in the ICO's direct marketing and privacy and electronic communications guidance for UK and EU buyers ^[5].

The implementation owner owns the rollout and the internal training, and that step cannot start until the buyer assigns the person who will run it. Their absence is the most common cause of a slow start after signature, and a slow start becomes a renewal problem long before anyone calls it one.

Treat any unnamed role as an open qualification gap rather than an administrative detail. Record the gap in the opportunity before you forecast the deal, with the name of the person you asked and what they said. If you are working accounts where no one knows you yet, mapping the buying committee before the first touch gets you a working hypothesis for these four roles earlier.

The Evidence Each Approval Step Actually Requires

Most midmarket stalls are not missing decisions. They are missing artifacts. A reviewer asks for something, the request sits in your sponsor's inbox, you assemble the document under time pressure, and the review slips for reasons that have nothing to do with buying intent.

Pre-staging fixes this, but only if you pre-stage the right things. Align your artifact set to the framework the buyer is actually using to assess risk, so diligence does not restart discovery ^[2]. A European buyer evaluating an AI-enabled product is working against obligations in Regulation (EU) 2024/1689, and those obligations shape the questions their reviewers bring to the call ^[3].

Read that table as a to-do list rather than a reference. For each open midmarket deal, you should be able to say which artifacts are already in the buyer's hands and which you would scramble to produce. The second list is your real risk register.

Turn the Map Into a Plan the Buyer Will Confirm

A plan the buyer has never seen is a forecast artifact. It becomes a mutual action plan the moment the sponsor reads it back, corrects it, and forwards it.

Run the confirmation conversation in this order. Read back the steps you believe are required. Ask who owns each one by name. Ask what date each step is realistically possible, not ideally possible. Then ask the question most sellers skip: what would delay this. The answers to that last question are usually more accurate than the dates.

Follow the call with a written recap short enough to forward without edits. List each step with an owner, a date, and the evidence that step needs. Keep it to one screen. If your sponsor has to rewrite it before sharing it internally, it will not get shared.

Then test consensus. Gartner's framing of consensus creation as one of the buying jobs buyers revisit is the practical reason to do this directly rather than assume agreement ^[1]. Ask the sponsor who disagrees and on what grounds, then arrange a conversation with that person instead of routing more material through the sponsor.

Set a standing re-confirmation point. Any change in people, timing, or budget source triggers a new recap rather than a silent assumption. A new CFO, a hiring freeze, or a reorg does not pause your plan politely. It invalidates it.

Reverse-Timeline the Close Date From the Last Approval

Start from the buyer's desired go-live date and work backward. That is the only direction that produces a defensible close date, because every approval step has a minimum duration that your urgency does not shorten.

Work the sequence in reverse and record two things for each milestone: how far before go-live it must happen, and whether the buyer confirmed that timing out loud.

• Implementation readiness, owned by the buyer's implementation owner, sits closest to go-live and needs the rollout owner named and training time blocked.
• Contract and procurement review sits before that and behaves as a fixed-length block. Midmarket legal review rarely compresses on request, so plan around it rather than negotiating with it.
• Technical and risk review usually precedes contract, and its length depends on the reviewer's queue more than on your product.
• Finance approval has to land inside a budget cycle, which means the latest-start date is set by the cycle calendar, not by your quarter.
• Business case sign-off is the first gate, and if it has not happened, every date after it is an estimate.

There is a hard distinction worth enforcing in pipeline reviews: a date you entered in the CRM and a date the finance approver said out loud are different objects. Forecast only against the second. Our piece on why CRM data misleads you about pipeline health covers the broader version of this problem.

Finally, write a disqualification rule and apply it without debate. If no approver beyond the sponsor can be reached within a defined window, the deal moves out of the committed forecast. An explicit rule applied consistently keeps forecast hygiene from becoming a judgment call ^[1].

Where Mutual Action Plans Quietly Fail

Failure one: the plan lives in your CRM and the buyer has never seen it. It looks like rigor in a pipeline review and functions as fiction, because no one on the buying side has agreed to any of it.

Failure two: steps are listed without evidence requirements. The plan names a review week and says nothing about what the reviewer will ask for. Every review then becomes a surprise document request that you fill under time pressure while the clock runs.

Failure three: the implementation owner is added after signature. Onboarding risk gets pushed into the renewal conversation, and the opening stretch after go-live is spent finding an internal owner instead of producing a result.

Failure four: the plan is never updated after a reorg, a new CFO, or a hiring freeze. You are forecasting against a committee that no longer exists, which is worse than having no plan at all because it carries false confidence.

Audit any open midmarket deal quickly with these five questions:

1. 1.Can I name all four roles (sponsor, finance, IT or security, implementation) with a real person in each slot?
2. 2.Have I spoken directly with each named person at least once, outside a group call?
3. 3.Does the buyer have a copy of the plan, and did the sponsor confirm or correct the dates?
4. 4.Is every step paired with its evidence requirement, and do I have those artifacts ready now?
5. 5.What has changed in people, budget source, or timing since the last written recap?

Any "no" is the next call you need to book. Three or more "no" answers means the deal does not belong in a committed forecast this quarter.

Metrics That Prove the Plan Is Real

Stop reviewing stage names in pipeline meetings and start reviewing confirmation. The headline number is buyer-confirmed steps as a share of total plan steps. A deal with most steps unconfirmed is not partly done, it is mostly assumption.

Approval-path coverage is the second metric: the share of open midmarket deals where all four roles are named and you have had at least one direct conversation with each. This is the number that predicts slippage a quarter in advance, because an unnamed finance approver in March becomes a pushed close date in June.

Evidence lead time is the fastest cycle-time lever you actually control: the gap between a reviewer's request and your delivery of the artifact. If that gap runs into days on every request, you are adding time to every deal through nothing but logistics. Pre-staging the artifacts in the table above drives it toward zero.

Slipped-milestone reasons by category gives your coaching a target. Tag each slip as people, budget cycle, technical review, integration, or contract. If technical review dominates your slips in a quarter, the fix is a better control-mapping package, not more discovery training. For AI-enabled products, that package often means documenting how your controls line up with the framework the reviewer uses, including the govern, map, measure, and manage functions described in NIST's Generative AI Profile companion to the AI Risk Management Framework ^[4].

Then apply retirement discipline. Any plan field that never changes rep behavior or outcome rates should be removed, the same way a signal-based team drops a buying signal that stops producing first meetings. A mutual action plan template padded with fields nobody acts on trains reps to fill forms rather than confirm approvals.

FAQ and Your Next Three Moves

What is a mutual action plan in midmarket sales, and how is it different from an internal close plan?

A mutual action plan is a shared, buyer-confirmed sequence of approval steps with named owners, dates, and required evidence. An internal close plan is your own forecast narrative. The test is simple: if the buyer cannot open it, correct it, and forward it to a colleague, it is a close plan. Both have uses, but only the first one reduces slippage, because only the first one creates commitments on the buying side.

When should you introduce the plan, and what if the sponsor resists sharing the approval path?

Introduce it after the second substantive conversation, once the business problem is clear and before pricing. Present it as a way to protect the sponsor's time rather than as a sales process document: "Here is what I think your organization will need from us, so you are not chasing documents later." If the sponsor resists naming the path, treat that as data about their internal standing rather than about their enthusiasm. Ask what has happened with similar purchases recently and who was involved, which is an easier question to answer than a direct request for an org chart.

How many steps should a plan have, and what if the buyer will not commit to dates?

Keep it to a single screen of steps. Longer than that and nobody reads it. If the buyer will not commit to dates, ask for sequence and dependencies instead: which step cannot start until another finishes. A confirmed sequence with no dates is still useful, because it tells you the minimum path length. A list of dates with no confirmed sequence tells you nothing.

Your next three moves

Pick your three largest open midmarket deals this week and fill in the four-role map. Mark every blank as a gap to close in the next call, with the specific question you will ask and who you will ask it of.

Then send one confirmation recap. One sponsor, one page, owners and dates and evidence for each step, with a direct ask: "Is this right, and would you forward it to the group?"

Start tracking buyer-confirmed steps per deal this week and bring that number to your next pipeline review instead of stage names. The logistics deal from the opening of this article did not fail because the proposal was wrong. It failed because the proposal arrived before anyone on the buying side had agreed on who approves what. Mapping that first is the cheapest stretch of calendar you will ever recover.

References

[1] Gartner, The B2B Buying Journey. https://www.gartner.com/en/sales/insights/b2b-buying-journey

[2] NIST, AI Risk Management Framework. https://www.nist.gov/itl/ai-risk-management-framework

[3] EUR-Lex, Regulation (EU) 2024/1689 (Artificial Intelligence Act). https://eur-lex.europa.eu/eli/reg/2024/1689/oj

[4] NIST, Artificial Intelligence Risk Management Framework: Generative AI Profile (NIST AI 600-1). https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf

[5] Information Commissioner's Office, Direct Marketing and Privacy and Electronic Communications. https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/