Sales

Using Mutual Action Plans to Stop Mid-Market Deals From Stalling

Mid-market deals stall because both parties let them. Mutual action plans create shared accountability for deal progression — making the prospect a co-owner of the close timeline rather than a passive evaluator.

SaaS Science TeamJune 14, 202611 min read
mutual action plandeal managementmid-market salesenterprise salessales process

The mid-market deal stall is one of the most common and most preventable revenue problems in B2B SaaS. A prospect who said "this looks great" three weeks ago has not responded to two follow-up emails. A deal that was projected to close this quarter is sitting in "negotiation" stage with no next meeting scheduled. The reason is almost always the same: both parties expressed intent without creating shared accountability for what happens next. The seller is waiting for the buyer to make a decision. The buyer is managing 15 competing priorities and the vendor's deal is not the one with the most immediate pressure. The mutual action plan is the tool that prevents this specific failure by making the close a collaborative project with co-owned milestones rather than a waiting game with one-sided urgency. SaaS Capital research on B2B deal velocity shows that mid-market deals with co-created mutual action plans close 30–40% faster and at 15–20% higher close rates than comparable deals without a defined buyer accountability structure.

See Your Growth Ceiling NowTry Free

Why Mid-Market Deals Stall (and Why MAPs Fix It)

The mid-market deal stall has a specific anatomy. It almost never happens in discovery or during the demo — both parties are engaged, the conversation is active, and next steps are scheduled. The stall happens between verbal positive and contract, in the 2–6 week window when internal alignment on the buyer's side is required but not yet complete.

The stall happens because:

  1. The champion said yes — but has not secured budget authority from the economic buyer
  2. The champion said yes — but has not mapped the internal steps required to complete the purchase
  3. The deal is real — but it is competing for the champion's attention with 10 other internal projects
  4. The deal is real — but a step on the buyer's side (security review, legal review, IT approval) has no owner and no deadline

In every one of these scenarios, the seller's follow-up email does not move the deal forward. It just confirms that the seller is still interested. What moves the deal forward is the buyer's champion having a plan they own — a sequence of steps with their names on them and dates they committed to.

What a MAP does:

  • Converts "we want to move forward" from an expression of intent into a set of concrete commitments
  • Gives the champion a tool for managing their internal stakeholders rather than managing the seller's follow-up
  • Creates shared context on the buyer's procurement timeline — removing the seller's main source of deal unpredictability (the buyer's internal process is a black box)
  • Establishes a cadence for deal reviews that keeps both parties accountable to the timeline

The MAP Introduction Conversation

The MAP introduction moment is the verbal positive — when the buyer says "this looks like what we need" or "we want to move forward." Most sellers respond by thanking the prospect and sending a proposal. The MAP-equipped seller responds differently.

The MAP introduction script:

"That's great to hear. Based on what you've shared about your timeline and the decision process at [company], I want to make sure we set this up so it moves forward smoothly. Can we spend 10–15 minutes now mapping out what the next steps look like on both sides — what you need to do internally to complete the purchase, and what we need to do to support you? That way we're both working from the same plan."

Why this framing works:

  • "What you need to do internally" positions the MAP as service to the buyer's internal process, not pressure from the seller
  • "Both sides" establishes mutuality — the seller is also making commitments
  • "So it moves forward smoothly" frames the MAP as deal protection, not deal acceleration (though it is both)

If the buyer pushes back on time:

"No problem — can I send over a template with what I know about our side, and ask you to fill in the steps on your side? It doesn't need to be complete today — even a rough draft of the key steps helps us both plan better."

Building the MAP in a Working Session

The highest-quality MAP is built in a 15–20 minute working session with the buyer's champion. Use a shared document (Google Doc works; a structured template in the CRM is better) and follow this sequence:

Step 1: Start with the outcome

"Let's start with the end state. If everything goes smoothly, what does 'done' look like — when you've signed a contract and we've kicked off implementation? What date is realistic for that?"

Get the buyer to name a target date. Do not propose one first — the buyer's date reflects their actual internal urgency, which is more reliable than your close date forecast.

Step 2: Identify buyer-side steps

"Working backward from that date, what are the internal steps you need to complete? Walk me through the process at [company name] for a purchase like this."

Listen and transcribe. Common buyer-side steps:

  • Confirm budget approval (who approves? VP? CFO? What is the threshold?)
  • Security review (who owns it? what does it involve? typical timeline?)
  • Legal review (your paper or customer paper? who leads the negotiation?)
  • IT review (is integration testing required before signature?)
  • Procurement submission (does the purchase need to enter a formal procurement system?)
  • Executive briefing (does the economic buyer need a formal presentation?)
  • Contract signature authority (who can sign at this contract value?)

Step 3: Assign owners and dates to each step

"For each of these steps — who is the owner, and what is a realistic timeline?" Let the buyer name the owners and estimate the dates. Correct only if a date is clearly unrealistic (e.g., "legal review in 2 days" when you know your legal redline process takes 5 business days).

Step 4: Map seller-side parallel steps

"On our side, here's what we need to do in parallel to make sure nothing on our end is a bottleneck." Fill in seller-side steps with your specific owners and dates:

  • Security questionnaire response
  • Legal redline turnaround
  • Contract generation
  • Implementation scoping (if applicable)
  • Kickoff scheduling

Step 5: Confirm the close date

"Looking at all these steps and the timelines you mentioned — does [your target date] still look achievable, or do we need to adjust?" This is the moment that reveals whether the deal is on track. If the buyer maps their internal steps and realizes the original target date is unrealistic, it is better to reset now than to forecast a close date you will miss.

The MAP Review Cadence

After the MAP is built, the deal review cadence follows the MAP — not an arbitrary follow-up schedule. Every week or two, the review covers where each step is against the MAP timeline.

Weekly MAP check-in format (15 minutes):

  1. Review MAP status: which steps are on track, which are behind?
  2. For any step that is behind: what is the specific blocker? Who needs to unblock it?
  3. Do the remaining steps still support the target close date, or does the date need to be revised?
  4. What does each party commit to completing before the next check-in?

The power of the MAP in the check-in:

When a step falls behind, the MAP makes the conversation factual rather than emotional. "Your legal review was on the MAP for last week — I noticed we haven't received redlines yet. Is that moving forward, or has something changed?" This is a much more effective conversation than "I'm just following up on where things stand." The MAP gives the seller standing to ask about specific steps without being perceived as pushy — because the buyer co-created the timeline.

Preventing Common MAP Failures

Failure 1: Seller fills out the MAP and emails it

The document the seller fills out is a project plan, not a MAP. It requires no buyer commitment and creates no shared accountability. The fix: always build in a working session. If the buyer truly cannot meet, use a partial template (seller-side pre-filled, buyer-side blank) and have a phone call to fill in the buyer side.

Failure 2: MAP is too detailed

A MAP with 30 line items for a $30K deal will not be maintained. Keep the MAP to the 6–10 steps that genuinely represent decision checkpoints, not every micro-action. The level of detail should match the deal complexity. See /blog/lightweight-deal-desk-first-enterprise-deals for how deal desk steps fit into a MAP for larger deals.

Failure 3: MAP is introduced after the deal stalls

A MAP introduced to a stalled deal is sometimes still effective (as a revival tool), but it carries less weight than a MAP built at the moment of verbal positive. The buyer reads a MAP introduced mid-stall as a sales technique, not a collaboration tool. Prevention: introduce the MAP at the verbal positive, not weeks later.

Failure 4: MAP close date becomes a pressure tool

Using the MAP date to pressure the buyer ("you committed to signing by Friday") damages the relationship and rarely accelerates the deal. The MAP date is a shared target, not a contractual commitment. When it slips, the conversation is "what changed, and how do we reset?" not "you said Friday."

Mid-Market MAP by Deal Size

The structure and depth of the MAP should scale with deal size and complexity:

Deal SizeMAP ComplexityCritical Steps to Include
$10K–$25K (SMB)4–6 stepsBudget approval, technical setup, signature authority
$25K–$75K (Mid-Market)6–10 stepsAbove + security review + legal review
$75K–$200K (Upper Mid-Market)8–12 stepsAbove + IT review + executive briefing + procurement submission
$200K+ (Enterprise)10–15 stepsAbove + board approval + DPA negotiation + dedicated pilot

See /blog/sales-led-vs-hybrid-gtm-decision-saas for how deal complexity connects to the GTM motion selection.

See Your Growth Ceiling Now

Calculate when your SaaS growth will plateau — free, no signup required.

Calculate Your Growth Ceiling

Conclusion

The mutual action plan is one of the highest-ROI process investments available to an early-stage sales team — it costs 15 minutes of structured conversation per deal and pays back in 30–40% faster close times and materially higher close rates. The key discipline is building it collaboratively, immediately after the verbal positive, with the buyer naming their internal steps and owners rather than receiving the seller's version of how their procurement should work. When the buyer's champion has built the MAP, they own the timeline — and a timeline with an owner is a timeline that gets followed. For the companion framework on how discovery creates the conditions for a MAP introduction, see /blog/founder-built-sales-playbook-template.

Frequently Asked Questions

What is a mutual action plan in sales?

A mutual action plan is a co-created document listing every step required to complete a purchase decision, with a defined owner and due date for each step from both the buyer's side and the seller's side.

When should you introduce a mutual action plan in a deal?

Introduce the MAP immediately after a verbal positive — when the buyer says "this looks like a good fit" or "we want to move forward." This is the optimal window because the buyer's intent is highest.

What should a mutual action plan include?

A complete MAP includes: a scope statement, success criteria, buyer-side steps with owners and due dates, seller-side steps with owners and due dates, a target close date, and an escalation path.

What is the most common reason MAPs fail to prevent deal stalls?

The MAP is treated as a seller-created document sent to the buyer for acknowledgment rather than a buyer-co-created document that the buyer's champion owns. When the champion has not participated in building the MAP, they have no commitment to the timeline.

How do you use a MAP to revive a stalled deal?

Reach out proposing a MAP as a reset: "Can we spend 20 minutes mapping out what a decision process looks like from here — I want to understand what you'd need to feel comfortable moving forward." This surfaces whether the deal is truly stalled or dead.

Frequently Asked Questions

What is a mutual action plan in sales?
A mutual action plan (MAP) is a co-created document that lists every step required to complete a purchase decision, with a defined owner and due date for each step from both the buyer's side and the seller's side. Unlike a proposal or a project plan that the seller sends to the buyer, a MAP is built collaboratively — the buyer identifies their internal steps (IT review, security questionnaire, legal review, contract signature authority) and the seller matches with their parallel steps. The shared nature of the document creates accountability on both sides and gives the buyer's champion a concrete tool for managing the purchase internally.
When should you introduce a mutual action plan in a deal?
Introduce the MAP immediately after a verbal positive — when the buyer says 'this looks like a good fit' or 'we want to move forward.' This is the optimal window because the buyer's intent is highest and their willingness to invest time in co-creating a plan is at its peak. Introducing the MAP before you have a verbal positive (too early) makes the document feel presumptuous. Introducing it at the contract stage (too late) means the deal has already had time to stall on unaddressed internal requirements.
What should a mutual action plan include?
A complete MAP includes: (1) A scope statement — what is being purchased, at what price, for what term; (2) Success criteria — how both parties will know the evaluation is complete; (3) Buyer-side steps with owner and due date — security review, IT approval, legal review, CFO approval, procurement submission, signature authority; (4) Seller-side steps with owner and due date — security questionnaire response, legal redline turnaround, implementation scoping, contract generation; (5) A target close date that both parties have agreed is achievable; (6) An escalation path — who to contact on each side if a step falls behind.
How do you get a mid-market buyer to actually co-create a MAP rather than just receiving one?
Ask, don't send. Instead of presenting a pre-filled MAP template, open a working session with a blank document (or a lightly pre-filled seller-side column) and ask the buyer to walk you through their internal process: 'Walk me through what needs to happen on your side to get this from a verbal yes to a signed contract. I want to make sure we build a realistic timeline.' Most buyers respond well to this framing because it signals that you are trying to understand their process, not rush them through yours.
What is the most common reason MAPs fail to prevent deal stalls?
The MAP is treated as a seller-created document sent to the buyer for acknowledgment rather than a buyer-co-created document that the buyer's champion owns. When the champion has not participated in building the MAP, they have no commitment to the timeline — it is your plan, not theirs. The fix is to build the MAP in a live working session where the buyer populates their side of the document. When the buyer has identified the steps and written in the owner names themselves, they become accountable to the timeline in a way they cannot become to a document you sent them.
How do you handle a buyer who refuses to participate in creating a MAP?
Resistance to a MAP is usually one of two things: a deal that is not as advanced as it appears (the verbal positive was polite, not genuine) or a procurement process the buyer's champion does not actually control (they are not the real decision maker). The diagnostic response is: 'I understand. Can you help me understand what the typical process looks like for a purchase like this at your company, so I can make sure we're supporting you correctly?' If they cannot describe a concrete procurement process, the deal needs to be re-qualified — it is almost certainly earlier than your pipeline stage indicates.
What is a realistic close-date range for a mid-market MAP?
Mid-market deals ($20K–$100K ACV) at companies with 100–500 employees typically have procurement cycles of 4–8 weeks from verbal positive to signature if a MAP is used and followed. Without a MAP, the median deal cycle is 8–12 weeks with high variance. The biggest drivers of MAP timeline length: security review (1–4 weeks depending on maturity of your security documentation), legal review (1–3 weeks depending on whether you use customer paper or your standard agreement), and budget approval authority (same-week for champions with direct budget authority; 2–4 weeks if VP or CFO approval is required).
How do you use a MAP to revive a stalled deal?
A stalled deal — one that has been in proposal or negotiation stage for 30+ days without progression — can often be revived by proposing a MAP as a reset mechanism. Reach out with: 'I realize we haven't had a specific next step in a few weeks. I don't want to assume the project has changed priority for you, but I also don't want to keep following up without context. Can we spend 20 minutes mapping out what a decision process looks like from here — I want to understand what you'd need to feel comfortable moving forward.' This approach surfaces whether the deal is truly stalled or dead.

Related Posts