---
slug: mutual-action-plan
type: pattern
summary: "A shared buyer-seller close plan that turns enterprise opportunity into dated owners, decision gates, and a credible path to contract."
created: 2026-06-14
updated: 2026-06-15
sources_audited: 2026-06-14
related:
  gtm-motion:
    relation: implements
    note: "A Mutual Action Plan is one operating artifact inside a sales-led go-to-market motion, especially when enterprise deals require buyer coordination."
  meddic-qualification:
    relation: complements
    note: "MEDDIC tests whether an opportunity is real; a Mutual Action Plan turns that qualified opportunity into a dated execution path."
  pipeline-coverage-ratio:
    relation: supports
    note: "Pipeline coverage is more credible when large opportunities carry buyer-visible milestones, owners, and dates rather than only CRM stage labels."
  sales-velocity:
    relation: supports
    note: "Sales velocity improves when qualified deals move through agreed buyer and seller steps instead of waiting on vague next actions."
  pilot-purgatory:
    relation: prevents
    note: "A Mutual Action Plan prevents open-ended pilots by forcing success criteria, buyer ownership, and a conversion path before the startup funds the work."
  due-diligence:
    relation: used-by
    note: "Investors inspect Mutual Action Plans in diligence to test whether forecasted enterprise deals have process evidence behind the close date."
  runway:
    relation: informs
    note: "A dated close plan translates enterprise deal slippage into a cash-timing risk that can affect runway and fundraising timing."
---

# Mutual Action Plan

> **Pattern**
>
> A named solution to a recurring problem.

*A shared buyer-seller plan that converts a complex enterprise opportunity into dated milestones, named owners, approval gates, and a path from evaluation to purchase and go-live.*

*Also known as: mutual close plan, mutual success plan, close plan, joint execution plan, go-live plan*

A Mutual Action Plan is often shortened to MAP, but the useful test is not whether the seller has a plan. It is whether the buyer can see the path, agree to it, and put their own people and dates on it. If the plan lives only inside the seller's CRM, it is a forecast note. If both sides use it to coordinate the purchase, it becomes evidence that the deal is moving.

## Context

This pattern belongs in a sales-led [go-to-market motion](gtm-motion.md), especially after an opportunity has passed basic qualification and before the team treats it as forecastable revenue. The buyer is usually a company, not an individual user. The purchase may involve a champion, an economic buyer, procurement, legal, security, finance, implementation, and the team that will live with the product after signature.

That kind of deal needs more than a rep's next step. It needs a shared operating plan. [MEDDIC Qualification](meddic-qualification.md) asks whether the opportunity has value, pain, authority, process, and a champion. A Mutual Action Plan takes the qualified opportunity and asks a second question: what has to happen, in what order, owned by whom, by which date, for this buyer to buy and successfully start using the product?

The artifact is most useful when the company is beginning to care about [pipeline coverage](pipeline-coverage-ratio.md), [sales velocity](sales-velocity.md), and board-level forecast quality. At that stage, "Acme is in late-stage evaluation" is too soft. A dated plan with buyer-owned milestones is still not a guarantee, but it is much better evidence than enthusiasm.

## Problem

Enterprise startups lose deals to no decision as often as they lose to named competitors. The champion likes the product, the demo went well, and a pilot may even be underway, but nobody has mapped the path from interest to budget approval, security review, contract signature, and go-live. The buyer keeps asking for one more call, one more integration, one more stakeholder review. The CRM close date moves. The forecast absorbs the optimism.

Without a shared plan, the seller is managing the deal from the outside while the buyer's internal process remains hidden. That is dangerous for founders because enterprise deals consume scarce engineering, sales, and executive time before cash arrives. It is dangerous for investors because the pipeline can look large while the decision process is missing. It is dangerous for startup talent because missed enterprise forecasts turn into quota resets, bridges, cuts, and last-minute fundraising.

## Forces

- **Seller forecast versus buyer reality.** The seller wants a close date; the buyer has internal steps the seller may not know.
- **Champion enthusiasm versus organizational commitment.** A champion can want the product but still lack authority, budget, or access to the people who approve.
- **Speed versus proof.** The startup wants to move quickly, while the buyer often needs security review, procurement, legal review, and implementation planning.
- **Seller control versus mutual ownership.** A plan the seller writes alone creates compliance theater; a plan the buyer co-owns creates evidence.
- **Custom work versus conversion discipline.** Enterprise buyers often ask for pilots or integrations before purchase, and the startup needs a way to keep that work tied to a paid outcome.

## Solution

**Co-create a Mutual Action Plan with the buyer and use it as the deal's shared operating document.** The plan names the business outcome and the milestones that lead to purchase and go-live. Every milestone carries an owner, a due date, the evidence that marks it complete, and the risk that could delay it.

A useful MAP is concrete enough that both sides can run a meeting from it.

| MAP field | What it should answer |
|---|---|
| Buyer outcome | What business result makes this purchase worth doing? |
| Success criteria | What must the product prove before the buyer moves forward? |
| Milestones | What steps remain between today and signed contract? |
| Owners | Who on the buyer side and seller side owns each step? |
| Dates | When does each step have to finish for the close date to hold? |
| Approval path | Which budget, security, legal, procurement, and executive gates remain? |
| Go-live path | What happens after signature so value starts, not just paperwork? |
| Risks | What could delay or kill the deal, and who is handling it? |

The plan should be written in the buyer's language. "Security review complete" is better than "advance to stage four." "CISO approves vendor-risk questionnaire by July 12" is better still. The buyer has to recognize their own process in the document, or they won't use it.

The practical discipline is to make the MAP conditional. If the buyer won't agree to dates, owners, success criteria, or access to the economic buyer, the opportunity should not be treated as committed pipeline. That doesn't mean the deal is dead. It means the next action is discovery, buyer access, or disqualification, not more product work disguised as momentum.

> **⚠️ Warning**
>
> A Mutual Action Plan can become a seller's fantasy spreadsheet. If the buyer hasn't confirmed the milestones, owners, and dates, the document is not mutual. Treat it as an internal hypothesis, not as forecast evidence.

## How It Plays Out

A Series B logistics-software startup is selling a six-figure system to a national retailer. The champion wants a pilot, the operations team likes the demo, and the seller puts the opportunity in late-stage pipeline. Without a MAP, the next two months disappear into custom integration work. Security review starts late. Procurement asks for vendor documents nobody prepared. The economic buyer sees the project for the first time after the pilot and asks why the team is doing this now. The pilot worked, but the deal slips because the purchase path never existed.

The disciplined version starts before the pilot. The seller and champion write a plan together: two-week technical validation, success criteria tied to a measured reduction in fulfillment errors, a security questionnaire owned by a named retailer contact, procurement intake by a fixed date, economic-buyer readout after validation, contract redlines the following week, and a go-live checklist owned by both teams. The plan names the decision that follows a successful pilot. When a date slips, everyone can see which dependency moved. When the buyer won't name an owner, the seller learns the deal is not as qualified as it looked.

The investor version comes during diligence. A founder claims \$2M of late-stage enterprise pipeline closing next quarter. The investor asks for the MAPs behind the largest deals. Two opportunities have no buyer-owned dates and no approval path, so they get discounted. One has a named economic buyer, completed security review, procurement already opened, and a go-live plan agreed by customer success and the buyer's operations lead. That deal still may not close, but it is much more underwritable than a CRM row with a close date.

## Consequences

Using Mutual Action Plans changes how a startup reads enterprise pipeline. The deal stops being a private seller forecast and becomes a shared buyer process that can be inspected.

**Benefits.** MAPs make forecast quality visible. They expose missing buyers, vague success criteria, hidden procurement steps, and pilots with no conversion path before those gaps consume more runway. They improve sales velocity by turning next actions into dated commitments and by forcing the buyer's process into view. They also help founders protect engineering and customer-success capacity: custom work tied to a buyer-owned plan is different from custom work offered to keep a vague opportunity alive.

**Liabilities.** MAPs add process, and process can repel early buyers if it arrives too soon or feels like seller paperwork. A small mid-market deal may not need a full plan. A founder-led exploratory conversation should not be smothered by a template. The pattern works when the deal is complex enough that coordination is already the bottleneck. It fails when the seller uses the MAP to make a buyer perform commitment rather than to help a committed buyer buy.

The deeper risk is false confidence. A beautifully formatted plan with dates that only the seller believes is worse than no plan because it lets the company keep forecasting against fiction. The value of a MAP comes from mutuality: buyer language, buyer owners, buyer dates, and buyer acknowledgment that these are the steps between interest and purchase. Without that, the startup hasn't solved the close-plan problem. It has decorated it.

## Sources

- Salesforce, *[Mutual Action Plans](https://www.salesforce.com/blog/sales/mutual-action-plan/)* — defines the MAP as a shared buyer-seller document spanning purchase, implementation, and value realization.
- Outreach, *[Mutual Action Plans](https://www.outreach.ai/resources/blog/mutual-action-plans)* — frames the MAP as a co-created roadmap for complex enterprise deals, with agreed responsibilities and timelines.
- SalesHood, *[What Is a Mutual Action Plan?](https://saleshood.com/blog/what-is-a-mutual-action-plan/)* — emphasizes co-ownership and writing the plan in the customer's language rather than in seller-stage language.
- Clari, *[Mutual Action Plan Best Practices](https://www.clari.com/blog/mutual-action-plan-best-practices/)*, and Highspot, *[Mutual Action Plans](https://www.highspot.com/blog/mutual-action-plan/)* — document the current revenue-operations treatment of MAP templates, buying-committee alignment, milestones, owners, and approval paths.
- Dock, *[Buyer Enablement](https://www.dock.us/library/buyer-enablement)* — places MAP-style deal planning inside the broader buyer-enablement shift from seller control toward shared buyer coordination.

---

- [Next: Pipeline Review Cadence](pipeline-review-cadence.md)
- [Previous: MEDDIC Qualification](meddic-qualification.md)