Why this is hard to get right
A Real Scenario: When "We'll Follow Up" Kills the Deal
Sarah is a senior account executive at a mid-market SaaS company. She's been working a $90k ARR deal for eight weeks. The VP of Operations loves the product. The CFO asked good questions on the last call. Everything feels warm.
Then nothing happens for two weeks.
She sends a follow-up email. The champion replies: "We're still interested — just a lot going on." Sarah knows what that means. Without a shared plan, the deal is drifting. Each week that passes adds risk. New vendors enter the conversation. Budget cycles shift. Priorities change.
The problem isn't the buyer's interest — it's the absence of shared ownership.
Sarah sits down to create a mutual action plan. She opens a blank document and types something like: "Create a mutual action plan for this sales deal so the customer knows the next steps." The AI returns a generic five-step checklist. It doesn't mention the CFO approval. It doesn't account for the security review they always hit late. It doesn't reflect the 45-day close window she promised her manager.
She spends 40 minutes editing it by hand. The buyer gets a version that still looks like a template.
The root problem is context. Mutual action plans fail when they're built in a vacuum. They need the actual stakeholders, the real approval sequence, and the specific risks that slow deals in your industry. A generic checklist signals to the buyer that you don't know their process. A tailored plan signals partnership.
When Sarah finally builds a prompt that includes the deal size, the decision-maker map, the close date, and a risk section drawn from her last three stuck deals — the AI produces something she can send in 10 minutes. The buyer's champion forwards it to the CFO the same day. They schedule the security review for the following week.
The difference wasn't AI capability. It was prompt quality. Specificity in the prompt becomes specificity in the plan. And specificity is what moves deals forward.
That's the professional challenge this prompt type solves: translating everything you know about a deal into a structure a buyer will actually use.
Common mistakes to avoid
Omitting the Decision-Maker Hierarchy
When you don't name the economic buyer, legal approver, and IT lead separately, the AI creates a generic plan that misses critical approval gates. The result is a plan your champion can't get signed off because it doesn't reflect how decisions actually happen in the buyer's organization. Always list every stakeholder role and what they need to say yes.
Skipping Exit Criteria for Each Step
Listing steps without exit criteria produces a checklist, not a mutual action plan. Exit criteria define when a step is actually done — not just started. Without them, both parties interpret progress differently, and deals stall at ambiguous handoffs. Include a clear completion signal for every step, like 'security questionnaire returned and reviewed.'
Leaving Out the Close Date and Working Timeline
A plan without a target close date gives the AI no anchor for urgency. The AI defaults to vague timing like 'within the next few weeks' instead of concrete due dates. Provide the close date upfront and let the steps work backward from it. This forces realistic scheduling and reveals impossible timelines before the buyer does.
Ignoring Deal-Specific Risks
Generic plans don't include the legal review that always runs long, or the IT admin who needs two weeks of notice. Omitting a risks section means repeat stalls — the same issues that killed your last deal appear again. Prompt the AI to include a risks and mitigations section based on the specific stakeholders and deal type you've described.
Writing a Plan for Internal Use Instead of Buyer-Facing Use
Many reps write mutual action plans that read like internal CRM notes — full of sales terminology and internal process steps. Buyers disengage when the tone feels one-sided. Specify in the prompt that the output should use collaborative language and frame each step as a shared responsibility, not a task you're assigning to the buyer.
The transformation
Create a mutual action plan for this sales deal so the customer knows the next steps.
You’re a senior account executive selling B2B SaaS. Create a **1-page mutual action plan** for this opportunity. 1. Use a **table** with columns: Step, Goal, Owner, Due date, Exit criteria. 2. Include **10–12 steps** from discovery to signature. Context: Deal size $85k ARR, target close in 45 days. Buyer: VP Ops (champion). Economic buyer: CFO. Stakeholders: Security lead, IT admin, Legal. Tone: **direct and collaborative**. Add a short “Risks + Mitigations” section with 3 items.
Why this works
Role Assignment Sharpens Priorities
The prompt opens with 'You're a senior account executive selling B2B SaaS.' This single line reorients the AI from a general assistant to a domain expert. It changes word choice, step selection, and risk awareness. Without a role, the AI produces advice suited for a project manager, not someone closing an $85k ARR deal.
Output Format Prevents Filler
Specifying 'a 1-page table with columns: Step, Goal, Owner, Due date, Exit criteria' constrains the AI to a structure buyers can actually use. Unconstrained, the AI generates prose paragraphs that read like a memo. The table format forces completeness — every step must have an owner and an exit condition, eliminating vague entries.
Named Stakeholders Force Approval Logic
The prompt explicitly names 'CFO, Security lead, IT admin, Legal' as stakeholders. This causes the AI to insert security review steps, legal sign-off milestones, and CFO validation gates that a generic plan omits entirely. Named roles create named steps. Named steps create accountability.
Quantified Constraints Eliminate Guesswork
'$85k ARR, 45-day close, 10–12 steps' give the AI hard boundaries. The deal size signals enterprise complexity. The timeline forces realistic date assignment. The step count prevents both overly sparse and padded outputs. Specific numbers produce specific plans — the AI cannot default to safe generalizations.
Risks Section Adds Professional Depth
The prompt explicitly requests 'a Risks + Mitigations section with 3 items.' This elevates the plan from a checklist to a strategy document. It signals to the buyer that you've anticipated obstacles — which builds confidence. Without this instruction, no AI will volunteer risk analysis unprompted in a plan-style output.
The framework behind the prompt
The Strategy Behind Mutual Action Plans
Mutual action plans — sometimes called close plans, joint execution plans, or mutual success plans — are a staple of enterprise sales methodology. Their core purpose is to replace verbal commitments with documented, co-owned milestones that both the seller and buyer are accountable to.
The concept draws from project management principles and is central to frameworks like MEDDIC and MEDDPICC, which treat deal execution as an engineering problem rather than a relationship problem. MEDDPICC, in particular, treats the Paper Process (the "P" in the acronym) as a first-class deal component — one that should be mapped and managed with the same rigor as economic buyer identification or decision criteria.
Research from sales effectiveness firm CSO Insights consistently shows that deals with documented next steps close at significantly higher rates than those managed through verbal agreements alone. The reason is psychological as much as procedural: shared documents create mutual commitment. When a buyer helps shape a plan and sees their name next to a step, they feel accountable to it.
The STAR framework (Situation, Task, Action, Result) also applies here — not for the plan itself, but for how you present each step to the buyer. Framing steps in terms of the result they unlock ('Security review complete, confirming your data handling requirements are met') rather than the task required ('Complete security questionnaire') shifts the buyer's mental posture from compliance to partnership.
From a prompt engineering perspective, mutual action plans are a structured output challenge. The AI must produce a document with consistent formatting, specific column constraints, realistic dates, and professional tone — all at once. This requires more instruction precision than most content generation tasks. Vague prompts produce vague plans. Structured prompts with named stakeholders, step counts, and format specifications produce documents you can actually send.
Prompt variations
You are an experienced customer success manager at a B2B SaaS company.
Create a go-live mutual action plan for a new customer entering a 60-day paid pilot.
Output format: A table with columns: Phase, Step, Owner (Vendor / Customer), Due Date, Success Criteria.
Context:
- Product: a workflow automation platform
- Customer team: Operations Manager (day-to-day), IT Director (integration approval), VP of Operations (executive sponsor)
- Key milestones: kickoff call, data integration complete, first workflow live, pilot review meeting
- Goal: customer sees measurable ROI by day 45 so they convert to annual contract
Include: A 'Risks and Mitigations' section with 3 items specific to integrations and user adoption.
Tone: warm and collaborative. Frame all steps as shared responsibilities.
You are an account executive closing a mid-market software deal under time pressure.
Create a 30-day mutual close plan for a deal at the negotiation stage.
Format: Numbered step list with: Step name, Owner, Due date, Done-when criteria.
Deal details:
- Contract value: $28k ARR
- Buyer: Director of Marketing (champion and economic buyer)
- Additional approver: Procurement for vendor onboarding
- Current stage: Legal has the MSA, security review is complete
- Blocker: procurement requires a W-9 and insurance certificate
Steps to cover: Legal redlines returned, procurement checklist complete, final pricing approved, DocuSign sent, signed contract received.
Add: One risk item for the procurement delay with a specific mitigation action.
Tone: direct and efficient. The buyer is busy — keep every step under 20 words.
You are a solutions engineer preparing a proof-of-concept for an enterprise software evaluation.
Create a technical mutual action plan to align both teams before the POC begins.
Output format: Table with columns: Work stream, Step, Responsible Party, Target Date, Acceptance Criteria.
Context:
- POC duration: 3 weeks
- Customer team: IT Admin (environment access), Security Lead (data handling review), Integration Developer (API setup)
- Vendor team: Solutions Engineer, Implementation Specialist
- Key work streams: environment provisioning, SSO configuration, test data preparation, security questionnaire, API integration, success criteria sign-off
Include:
- A 'Pre-POC Checklist' section listing 5 items that must be complete before kickoff
- A 'POC Exit Criteria' section with 3 measurable outcomes the customer agrees to evaluate
Tone: precise and technically credible. Avoid marketing language.
You are a sales manager building a standardized mutual action plan template for your entire account executive team.
Create a reusable mutual action plan framework for B2B SaaS deals between $50k and $150k ARR.
Format: A master table with columns: Stage, Step, Typical Owner, Suggested Timeframe (days before close), Exit Criteria.
Stages to cover: Discovery, Technical Validation, Business Case, Legal and Security, Procurement, Signature.
Include:
- A notes row under each stage explaining what reps should customize per deal
- A 'Common Stall Points' section listing the 4 most frequent blockers at each stage with suggested recovery actions
Design this so a rep can fill in owner names and specific dates in under 10 minutes.
Tone: practical and coaching-oriented. Write for experienced reps who need structure, not hand-holding.
When to use this prompt
Account Executives
Send a shared action plan after a late-stage call to lock owners, dates, and approval steps.
Sales Managers
Standardize deal execution across reps and spot missing steps during pipeline reviews.
Customer Success Managers
Create a go-live plan for a paid pilot with milestones, owners, and success criteria.
Solutions Engineers
Align security review, technical validation, and admin setup before a proof of concept starts.
Pro tips
- 1
Define the close date and work backward so every step supports a real deadline.
- 2
Name the economic buyer and approval path so the plan reflects how decisions happen.
- 3
Add exit criteria for each step so you can confirm progress without guesswork.
- 4
Include top risks from your last 5 deals so the plan prevents repeat stalls.
Most mutual action plans fail not because they're poorly structured but because buyers don't feel ownership over them. Here are three advanced techniques to close that gap.
Co-create the plan on the call, don't send it after. Use the AI to build a draft before your next meeting. Then walk through it live with the champion and ask them to add, remove, or re-assign steps. Buyers commit more deeply to plans they helped shape. Your AI draft becomes the starting point, not the final word.
Tie each step to a business outcome, not a vendor task. Instead of 'security questionnaire returned,' write 'security review complete — confirms data handling meets your compliance requirements.' This reframes vendor tasks as buyer wins. The AI can do this if you add the instruction: 'Frame each step in terms of the benefit it delivers to the buyer, not the task required of the vendor.'
Version-control the plan after every call. Prompt the AI to generate a 'version 2' of the plan after each significant call, incorporating new information about delays, new stakeholders, or changed timelines. Include in your prompt: 'This is an update to a plan we shared two weeks ago. Add a change log section noting what shifted and why.' This signals to the buyer that you're actively managing the process, not just tracking it.
Mutual action plans look different depending on the industry you're selling into. A one-size-fits-all structure often signals that you don't understand the buyer's world.
Healthcare and life sciences: Regulatory and compliance steps come early and are non-negotiable. Your prompt should name HIPAA review, data processing agreements, and clinical workflow validation as explicit steps. Buying committees are large — often 6–10 stakeholders. Build that into the step count and approval sequence.
Financial services: Security and vendor risk assessments are almost always required before any internal champion can escalate to procurement. Prompt the AI to include a 'vendor risk questionnaire' step with a realistic 3–4 week timeline. Legal review of data handling clauses is standard and slow — plan for it.
Manufacturing and industrial: Implementation timelines matter more than approval timelines. Your plan should include integration testing with existing ERP or MES systems, operator training schedules, and production line validation steps. The economic buyer is often a plant manager or COO, not a CFO.
Professional services firms: Conflicts-of-interest checks and partner-level approval often appear in the process. Prompt the AI to include a step for internal sponsor alignment before external commitments are made.
In each case, add a one-sentence sector context line to your prompt: 'This buyer is a regional hospital network. All vendor approvals require compliance sign-off before escalating to the CFO.' That line alone shifts the AI's output significantly.
Run through this checklist before sharing any AI-generated mutual action plan with a buyer.
Content accuracy:
- Every stakeholder named in the plan is a real person or role at the buyer's company
- Due dates are realistic given the current date and confirmed availability
- The economic buyer's approval step appears explicitly — not buried or implied
- Exit criteria are specific enough that both parties could independently verify completion
Tone and framing:
- Steps use 'we' or shared ownership language, not one-sided task assignments
- No internal sales jargon appears (e.g., 'stage 4 opportunity,' 'CRM update,' 'close plan')
- The plan reads as a partnership document, not a vendor checklist
Completeness:
- A risks section is present with at least 2 specific items
- Every step has an owner — no step is assigned to 'TBD'
- The plan covers the full path from current state to signed contract or go-live
Format:
- The table renders cleanly in whatever format you're sharing (email, PDF, Google Doc)
- The plan fits on one page or can be summarized on one page with a detail appendix
- Dates are formatted consistently throughout
If any item fails this check, go back to the prompt and add the missing context rather than editing the output by hand. Editing the output fixes this plan. Fixing the prompt improves every plan you build in the future.
When not to use this prompt
Avoid this prompt type in these situations:
-
Early discovery calls where no deal structure exists yet. A mutual action plan requires knowing the buyer's decision-makers, timeline, and approval process. If you're still mapping the organization, a MAP will be fabricated rather than accurate. Use stakeholder mapping prompts first.
-
Transactional deals under $10k ARR with single decision-makers. The overhead of a formal MAP creates friction, not momentum. Buyers in simple purchase cycles respond better to a clear one-pager or a simple email with two or three next steps.
-
Inbound deals where the buyer sets the process. Some enterprise buyers — particularly large government or healthcare organizations — have rigid procurement processes that they control entirely. Imposing your MAP structure can signal that you don't understand how they buy. Ask about their process before proposing a joint plan.
-
Situations where you don't yet have a champion. A MAP needs an internal champion who will co-present it to other stakeholders. Without one, you're sending a plan into a vacuum. Build the champion relationship first, then introduce the plan as a shared tool.
When this prompt type isn't appropriate, consider a simpler follow-up email prompt, a stakeholder mapping prompt, or a business case prompt instead.
Troubleshooting
The AI produces a generic checklist instead of a structured table with owners and exit criteria
Restate the format requirement explicitly at the top of the prompt, not the bottom. Write: 'Output format: a table with exactly five columns — Step, Goal, Owner, Due Date, Exit Criteria. Do not use prose paragraphs or bullet lists.' AI models default to lists when format is ambiguous. Leading with the format constraint before any other instruction reliably produces tabular output.
The risks section is vague — items like 'stakeholder misalignment' with no actionable mitigation
Add specificity to the risks instruction. Instead of 'include a risks section,' write: 'Include a Risks + Mitigations section with 3 items. Each risk must name a specific stakeholder or process step where the delay typically occurs, and each mitigation must describe a concrete action the account executive can take this week.' Vague risk prompts produce vague risks. Constraint prompts produce actionable ones.
The plan reads like a vendor task list — all steps are assigned to the seller, not shared
Add an ownership instruction: 'Assign each step to one of three owners: Account Executive, Customer Champion, or Shared. At least 40% of steps should be assigned to Customer Champion or Shared.' This forces the AI to distribute accountability realistically. Also add: 'Frame customer steps as commitments they're making to their own success, not tasks you're assigning them.'
The step count is too low — the AI produces 5 steps when you need 10-12 for an enterprise deal
Specify the minimum and maximum step count as a hard constraint. Write: 'The plan must include between 10 and 12 steps. Do not combine steps that happen in different weeks or involve different owners.' If the AI still under-generates, add: 'Break approval steps into sub-steps — for example, separate legal review, legal redlines, and legal sign-off into three distinct rows.'
The output doesn't reflect the specific buyer's approval process — it assumes a simple two-person decision
Add a 'decision-making process' description to the context block. For example: 'This buyer requires three internal approvals before procurement can issue a PO: IT security sign-off, CFO budget approval, and a legal review of the MSA. These approvals happen sequentially, not in parallel, and typically take 10–14 business days total.' The more you describe the buyer's process, the more the AI replicates it in the plan.
How to measure success
How to Evaluate Your Mutual Action Plan Output
Before sending any AI-generated plan to a buyer, run it through these quality signals:
Structure checks:
- The table has all five columns: Step, Goal, Owner, Due Date, Exit Criteria
- Every row has a named owner — no 'TBD' or blank cells
- Step count matches the deal complexity you specified (10–12 for enterprise)
Content accuracy checks:
- Named stakeholders appear in the owner column at least once each
- Dates are realistic and anchor to the close date you provided
- The CFO or economic buyer has at least one explicit approval step
- Legal and security steps appear if those stakeholders were named in the prompt
Professional quality signals:
- Exit criteria are specific — they describe a verifiable state, not a vague activity
- The risks section names process-specific blockers, not generic ones like 'budget delays'
- Tone is collaborative throughout — no steps read as demands or vendor tasks
Buyer-readiness test:
- You could send this plan today without editing more than names and dates
- A colleague who doesn't know the deal could understand it in under two minutes
If three or more of these signals fail, return to the prompt and add the missing context rather than editing the output manually.
Now try it on something of your own
Reading about the framework is one thing. Watching it sharpen your own prompt is another — takes 90 seconds, no signup.
Build a buyer-ready mutual action plan for your next enterprise deal in minutes — not hours.
Try one of these
Frequently asked questions
Simply remove those stakeholder roles and replace them with whoever actually approves the deal in your buyer's organization. The key is naming real roles — even if that's just 'VP of Finance' and 'Office Manager.' The AI uses the names you provide to generate relevant steps. A plan with no named approvers defaults to generic steps that don't reflect the actual decision path.
Yes, but adjust the step range and close date accordingly. For early-stage deals, set a longer timeline (90–120 days) and ask the AI to include discovery steps, stakeholder mapping, and business case development. The table format works at any stage — you're just anchoring different milestones. Specify the current deal stage explicitly so the AI starts from the right point.
Add a short 'buyer process context' section to your prompt. For example: 'This buyer uses a formal procurement process that requires three competing bids before approving any vendor.' Or: 'Legal review always happens before the CFO sees pricing.' The more you describe the buyer's actual process, the more the AI reflects it rather than defaulting to a generic sales motion.
No — treat the AI output as a strong first draft. Review it for accuracy before sending. Check that every step reflects your actual process, that owner names match real contacts, and that dates are achievable. Remove any steps that don't apply. The AI produces structure and language you'd spend an hour writing manually. You spend 10 minutes editing instead of 60 minutes creating.
Add a tone descriptor and one or two example phrases to the prompt. For instance: 'Tone: collaborative and peer-level. Use phrases like "we'll work together to" rather than "the customer is responsible for."' If your buyers are technical, note that too. Tone instructions at the end of the prompt reliably shift language across the entire output.
For enterprise deals ($75k+ ARR), 10–14 steps typically covers discovery through signature without becoming overwhelming. For mid-market deals, 6–10 steps is usually right. Too few steps create ambiguity; too many create friction. Specify the step count in your prompt — if you don't, the AI will pick a number that may not match your deal complexity.
Absolutely. Mutual action plans work well for QBR follow-throughs, renewal negotiations, upsell timelines, and implementation go-lives. Adjust the prompt by changing the objective from 'close' to 'go-live' or 'renewal signed,' and swap stakeholder roles accordingly. The table structure and exit criteria logic apply in any context where two parties need shared accountability.