What Is a Sales Playbook? A Practitioner's Definition

A MEDDPICC mutual action plan is not a seller's close plan copied into a buyer-facing document. It is a shared execution plan that makes the buyer's decision process visible: milestones, owners, evidence, dependencies, and dates that both sides can inspect. For Heads of Sales, RevOps, and Enablement, that distinction matters because a deal can be fully qualified and still miss its close date when security, legal, procurement, or implementation steps remain unowned.

Let's Meet! Build a buyer-owned MEDDPICC action plan with practitioners who have run complex technology sales organizations.

What is a MEDDPICC mutual action plan?

A MEDDPICC mutual action plan (MAP) is a buyer-and-seller working agreement for completing the steps between a qualified opportunity and the buyer's desired business outcome. It translates MEDDIC evidence into coordinated action, then extends that view across the Paper Process and Competition when the deal uses the MEDDPICC variant.

The plan should answer five operational questions:

• What must happen? List the buyer's decision, approval, contracting, and implementation milestones.
• Who owns each step? Name a buyer owner and seller owner where both sides have work to do.
• What evidence completes the step? Define the artifact, meeting, approval, test result, or commitment that proves progress.
• When must it happen? Use dates tied to the buyer's required outcome, not only the seller's forecast period.
• What could block it? Surface dependencies, missing stakeholders, security requirements, legal review, procurement rules, and alternatives to changing.

A MAP is not a new qualification framework. It is the execution layer that turns qualification into buyer-visible commitments. The MEDDIC framework remains the discipline for understanding value, authority, decision standards, decision steps, pain, and champions. The mutual action plan gives those findings a sequence that can be acted on.

Why MEDDIC evidence needs an action plan

Many revenue teams record MEDDPICC fields without changing how a deal moves. A CRM may show a champion, an economic buyer, and a target close date, yet no one has confirmed who owns the security questionnaire or when procurement will issue a purchase order. That is not a minor data-quality problem. It is an execution gap.

The original MEDDIC discipline came from operating real technology sales. Dick Dunkel authored MEDDIC at PTC in 1996, and RevCentric's practitioners have applied the framework in the field, with sellers and revenue leaders who had to make complex opportunities real. The lesson is practical: a qualification statement is only useful when it changes the next customer-facing action.

Use the MAP to expose the difference between an assertion and an inspectable commitment:

The MAP should make weak evidence visible without pretending that a green CRM field equals buyer commitment. If the buyer will not co-own the plan, that is important deal information. Do not disguise seller activity as mutual progress.

How do you build a MEDDPICC mutual action plan?

Build the plan with the buyer, not about the buyer. The seller can prepare a first draft, but the buyer must correct the sequence, assign the right owners, and confirm the dates. The working session is itself a qualification event because it tests access, urgency, decision authority, and the buyer's willingness to act.

1. Start with the buyer's required outcome

Begin at the point the buyer needs to realize value. That may be a new operating process live, a compliance deadline met, a renewal decision completed, a revenue target supported, or a production launch approved. Avoid starting with the seller's preferred close date. Ask what must be true for the buyer to achieve the outcome and what happens if the date slips.

Record the outcome in the buyer's language, with a named owner and a measurable indicator where possible. This anchors Metrics and Identify Pain without turning the MAP into a generic project plan.

2. Reverse-plan the Decision Process

Work backward from the buyer's required date to the decision events that precede it. Separate evaluation from authorization. A technical validation may show that the solution works, but the organization may still need a business case, executive review, finance approval, or a formal selection meeting.

For each Decision Process milestone, capture:

• the decision or meeting that must occur;
• the stakeholder who owns or participates in it;
• the evidence the buyer needs to make the decision;
• the pass condition or unresolved question;
• the date and the next step if the milestone moves.

This is where a MEDDIC Decision Process map becomes operational. The MAP should not merely repeat the buyer's stages. It should show the actual sequence of buyer-controlled events and the people accountable for them.

3. Add the Paper Process before the verbal yes

A verbal decision is not a signed contract. Add the work required after the buyer selects a solution and before the agreement can be executed. For a B2B technology purchase, that may include security review, privacy or compliance review, vendor onboarding, procurement registration, legal redlines, insurance documentation, purchase-order creation, and signature authority.

Do not combine all of this into one row called "legal and procurement." Separate steps have different owners, evidence, and lead times. A security questionnaire can be complete while legal has not accepted the data-processing terms. Procurement can approve a vendor while finance has not released the purchase order.

Use the detailed MEDDPICC Paper Process guidance to identify the gates that apply, then place each gate in the MAP with an accountable buyer owner. Ask the champion to confirm the sequence with legal, security, procurement, and finance rather than relying on a seller's assumption.

4. Assign owners on both sides

A mutual action plan needs more than a list of seller tasks. Every material milestone should have a buyer owner, even when the seller is doing most of the preparation. The buyer owner might be a security lead, procurement manager, legal counsel, implementation leader, finance partner, or executive sponsor.

Use a simple ownership test: can the named person confirm the step, provide the required evidence, or move the dependency? If not, the row is not owned. A champion can coordinate access, but do not automatically treat the champion as the owner of every buyer function.

Seller owners matter too. Name the person responsible for the business case, technical response, security package, contract response, executive alignment, or implementation plan. Shared ownership prevents the MAP from becoming an external checklist the seller sends and the buyer ignores.

5. Define evidence, not activity

"Schedule meeting" is an activity. "Buyer decision committee confirms the three evaluation criteria and records the preferred option" is evidence. Activity can create motion without reducing risk. Evidence shows that a decision gate has actually been cleared.

For each row, use an evidence field such as:

• approved business case;
• completed security questionnaire and accepted findings;
• documented decision criteria and test results;
• legal redlines resolved in the current contract version;
• purchase order or procurement approval;
• implementation owner acceptance;
• executive decision recorded by the buyer.

The evidence should be observable by both parties. If the only proof is a seller's note that a stakeholder is supportive, mark the step as unconfirmed and define the next action needed to make it inspectable.

What belongs in a MEDDPICC MAP template?

A useful template is short enough to use in a live buyer conversation and specific enough to expose a stalled deal. The exact fields can vary by sales motion, but the core structure should include:

Do not turn every CRM field into a MAP field. A MAP is a collaboration artifact, not a second database. Store the durable evidence and current commitments in the systems your team uses, then link the MAP to the opportunity so managers can inspect it without asking the seller to recreate the story.

How should managers inspect the plan?

Managers should inspect the buyer's commitments, not grade the document's formatting. A plan can look complete while every date comes from the seller. Use deal reviews to test whether the MAP reflects buyer reality.

1. Ask what changed. Which buyer milestone was completed since the last review, and what evidence proves it?
2. Test the critical path. Which step controls the required outcome date? What depends on it?
3. Inspect access. Have the right economic, technical, legal, security, and procurement stakeholders confirmed their roles?
4. Separate decision from paper. Has the buyer selected a solution, and separately, can the contract be executed on the proposed date?
5. Challenge the champion test. What buyer action did the champion take, and what will they do next?
6. Make the next customer action concrete. If the next step is only another seller meeting, the deal may not be advancing.

For a deeper manager inspection cadence, compare the MAP with a MEDDPICC manager-led deal review. The two artifacts serve different purposes: the MAP coordinates the buyer-and-seller path, while the review tests deal evidence and coaching priorities.

Common MEDDPICC mutual action plan failures

The seller creates a close plan and calls it mutual

A seller-authored document is not mutual because it uses buyer language. Invite the buyer to edit the sequence, reject unrealistic dates, assign owners, and add missing gates. Their edits are more valuable than a polished seller template.

The plan begins at the contract stage

Late Paper Process planning compresses the highest-risk work into the end of the quarter. Ask about security, legal, procurement, and vendor onboarding while the buyer is still defining the decision, then update the plan as requirements become known.

Every row has a date but no evidence

A date without a completion standard creates false precision. Add the artifact, approval, or buyer event that proves the milestone is done. If the buyer cannot define it, the step is not ready to be forecast as complete.

The champion is asked to own the entire organization

Champions can create access and advocate for change, but they may not control legal, security, procurement, or budget. Use the champion to map those functions and make the introductions. Then verify each function's requirements directly.

The MAP is abandoned after the first version

Buying groups change. Dates move. A new security requirement can alter the critical path. Review the MAP after every material buyer event and update the last-confirmed date. A stale plan is worse than no plan because it gives the forecast an outdated sense of control.

Claim Your Assessment to see where your team loses buyer-owned commitments between qualification and signature.

Frequently Asked Questions

Is a MEDDPICC mutual action plan the same as a close plan?

No. A close plan is often seller-owned and focused on reaching a forecast date. A MEDDPICC mutual action plan is co-created with the buyer and records buyer-owned milestones, evidence, dependencies, and dates across the Decision Process and Paper Process.

When should a sales team create the plan?

Start when the buyer's required outcome and decision path are clear enough to discuss, then build it before late-stage contracting. The plan should evolve as the buying group, requirements, and approvals become more specific.

Who owns a mutual action plan?

Both sides own it. The seller usually facilitates the working session and maintains the shared version, while the buyer validates the sequence, assigns buyer owners, confirms dates, and supplies evidence for buyer-controlled milestones.

What is the difference between Decision Process and Paper Process in the plan?

Decision Process covers how the buyer evaluates options and authorizes a choice. Paper Process covers what must happen after that choice and before signature, including legal, security, procurement, vendor onboarding, and purchase-order requirements.

How can leaders tell whether a MAP is real?

Inspect buyer confirmation, named owners, dates tied to the buyer's outcome, and evidence for completed milestones. If every step was written by the seller and no buyer stakeholder has accepted the sequence, treat the plan as a hypothesis rather than a forecast.