Intro to Sales Engineering and Solutions Consulting: Creating a Mutual Action Plan / Success Plan

Creating a Mutual Action Plan / Success Plan

Mutual Action Plan (MAP) / Success Plan: Demo-Ready Study Guide

For Engineers → SEs, BDRs Upskilling, and SEs Sharpening Their Craft

What This Is

A Mutual Action Plan (MAP)—also called a Success Plan—is a shared document that aligns your team and the prospect on what needs to happen, who owns each step, and when it must be completed to move the deal forward. It’s not a sales pitch; it’s a collaborative project plan that reduces friction, surfaces risks early, and positions you as a trusted advisor.

Real-world scenario:
You’re an SE at a cybersecurity startup competing against a legacy vendor for a $2M SOC 2 compliance deal. The prospect’s CISO is skeptical of your "next-gen" approach and wants a POC to prove you can replace their incumbent. Instead of winging the POC, you draft a MAP that: - Defines success criteria (e.g., "Automate 80% of evidence collection for SOC 2 controls").
- Assigns owners (e.g., "Your team provides sample logs by Week 2; our SE configures the integration").
- Sets timelines (e.g., "POC completes in 30 days; decision by Day 45").
- Lists risks (e.g., "If logs aren’t provided on time, POC extends by 1 week").

The MAP turns the POC from a vague "try it and see" into a structured evaluation—making it harder for the prospect to default to the incumbent.

Key Terms & Frameworks

• MAP / Success Plan: A living document (often a slide deck, spreadsheet, or shared doc) that outlines the steps, owners, and timelines to close a deal. Used in complex sales cycles (e.g., enterprise, competitive POCs, multi-stakeholder deals).
• MEDDIC: Qualification framework to assess deal health. A MAP ties directly to Decision Process (who signs off?) and Decision Criteria (what must the solution prove?).
• POC (Proof of Concept): A time-bound technical evaluation. The MAP defines success metrics (e.g., "Reduce false positives by 50%") and exit criteria (e.g., "If metrics aren’t met, we’ll discuss alternatives").
• Champion: Your internal advocate. The MAP helps them socialize the plan with other stakeholders (e.g., "Here’s the timeline we agreed on with [Vendor]’s SE").
• Technical Validation: The phase where the prospect tests your product. The MAP breaks this into milestones (e.g., "Week 1: Data ingestion; Week 2: Rule tuning").
• Economic Buyer: The person who signs the check. The MAP includes business outcomes (e.g., "Reduce audit costs by 30%") to justify the purchase.
• Mutual Close Plan: A subset of the MAP focused on contract signing (e.g., "Legal review by Day 60; redlines due by Day 65").
• Risk Register: A section in the MAP listing potential deal blockers (e.g., "Budget approval pending; backup plan: Pilot in Q1") and mitigation strategies.
• Demo Flow: The sequence of your product demo. The MAP ensures the demo aligns with the prospect’s success criteria (e.g., "Show the SOC 2 dashboard first—they care about audit trails").
• Discovery Call: Early conversation to uncover pain points. The MAP is built from discovery insights (e.g., "They’re failing audits because manual evidence collection takes 200 hours/year").
• Competitive Battlecard: Internal doc comparing your product to competitors. The MAP neutralizes competitor FUD (e.g., "Competitor X can’t automate evidence collection—we’ll prove this in the POC").
• Stakeholder Map: A visual of who’s involved in the deal. The MAP assigns owners to each stakeholder (e.g., "Your Champion will get Security Team buy-in by Week 3").

Step-by-Step / Process Flow

1. Discovery: Uncover the "Why" Behind the Deal

Goal: Identify the prospect’s pain points, success criteria, and decision process so you can tailor the MAP.
How:
- Ask open-ended questions to uncover business impact (not just technical features).
- "What happens if this problem isn’t solved in the next 6 months?" - "How does this project align with your team’s OKRs?" - "What’s the cost of not fixing this?" (e.g., "We’re paying $500K/year in audit fines.") - Map responses to MEDDIC: - Metrics: "Reduce audit time from 200 to 50 hours/year." - Economic Buyer: "CFO needs to approve; they care about cost avoidance." - Decision Criteria: "Must integrate with our SIEM and automate evidence collection." - Sample dialogue:

Prospect: "We’re evaluating 3 vendors for SOC 2 compliance." You: "Got it. To make sure we’re aligned, can you share: 1. What’s the biggest pain point with your current process? (e.g., manual work, failed audits) 2. Who owns the budget for this? (CISO? CFO?) 3. What’s the timeline for a decision? (e.g., ‘We need to be compliant by Q3.’) 4. What’s the one thing we’d need to prove in a POC to win your business?"

Output: A discovery doc with: - Key pain points (e.g., "Failing audits due to manual evidence collection").
- Success criteria (e.g., "Automate 80% of evidence collection").
- Decision process (e.g., "CISO → Security Team → Legal → CFO").

2. Draft the MAP: Structure It Like a Project Plan

Goal: Create a collaborative document that feels like their plan, not your sales pitch.
How:
- Use a simple template (Google Slides, Notion, or Excel). Include: 1. Deal Overview (1 slide):
- Prospect’s name, company, and deal size.
- Business problem (e.g., "Reduce SOC 2 audit costs by 30%").
- Success criteria (e.g., "Automate evidence collection for 50+ controls").
2. Key Milestones (1 slide):
- Discovery: "Week 1: Align on success criteria."
- POC: "Week 2-4: Technical validation."
- Decision: "Week 5: Executive review."
- Close: "Week 6: Contract signed." 3. Owners & Timelines (1 slide):
| Task | Owner (Prospect) | Owner (Vendor) | Due Date |
|--------------------------|------------------|----------------|-----------|
| Provide sample logs | Security Team | N/A | Week 2 |
| Configure integration | N/A | SE | Week 2 |
| Review POC results | CISO | AE | Week 4 | 4. Success Criteria (1 slide):
- Technical: "Integrate with Splunk; automate 80% of evidence collection."
- Business: "Reduce audit prep time by 150 hours/year." 5. Risks & Mitigation (1 slide):
| Risk | Mitigation Plan |
|-------------------------------|------------------------------------------|
| Logs not provided on time | Extend POC by 1 week; offer to help prep |
| Competitor FUD ("You’re new") | Preempt with case studies + reference calls | 6. Next Steps (1 slide):
- "Prospect to sign off on MAP by EOD Friday."
- "SE to schedule POC kickoff for Monday."

Pro tip: Use prospect’s language (e.g., if they call it a "SOC 2 project," don’t say "compliance initiative").

3. Socialize the MAP: Get Buy-In from All Stakeholders

Goal: Ensure the Champion, Economic Buyer, and Technical Team agree to the plan.
How:
- Champion: Have them present the MAP to their team (e.g., "Here’s the plan [Vendor] and I put together").
- "Can you walk your team through this? I want to make sure we’re aligned on timelines." - Economic Buyer: Highlight business outcomes (e.g., "This will save $200K/year in audit costs").
- "Does this timeline work for your budget cycle?" - Technical Team: Validate success criteria (e.g., "Does automating 80% of evidence collection solve your problem?").
- "What would make this POC a success for you?" - Sample dialogue (handling pushback):

Prospect: "This timeline feels aggressive. We might not get logs to you by Week 2." You: "No problem—let’s adjust. If we push the POC start to Week 3, does that work? I’ll add a buffer to the timeline and update the MAP."

Output: A signed-off MAP (even if it’s just an email reply: "Looks good to me!").

4. Execute & Iterate: Treat the MAP Like a Project

Goal: Keep the deal on track by proactively managing risks and updating the MAP.
How:
- Weekly check-ins: Sync with the Champion to review progress.
- "How’s the log collection going? Any blockers?" - Update the MAP: If timelines slip, revise the plan and get sign-off.
- "We’re pushing the POC review to Week 5—here’s the updated MAP." - Surface risks early: If the Champion goes dark, escalate to the AE.
- "I haven’t heard back on the logs. Should we loop in [Economic Buyer]?" - Sample dialogue (handling delays):

Prospect: "We’re still waiting on Legal to approve the POC." You: "Got it. To keep things moving, can we: 1. Start the POC with a subset of data (e.g., just 10 controls)? 2. Have your Champion escalate to Legal to unblock this? I’ll update the MAP to reflect this."

Output: A living MAP that evolves with the deal.

5. Close: Use the MAP to Drive Urgency

Goal: Leverage the MAP to accelerate the decision and preempt competitor moves.
How:
- Final review: Walk the Champion and Economic Buyer through the MAP.
- "We’ve hit all the success criteria—are you ready to move forward?" - Competitive FUD: Use the MAP to neutralize objections.
- "Competitor X can’t automate evidence collection—that’s why we built this POC to prove it." - Contract signing: Align the Mutual Close Plan with the MAP.
- "Based on the MAP, we’re targeting a signature by [date]. Does that work for your procurement timeline?" - Sample dialogue (closing):

Prospect: "We’re still evaluating [Competitor]." You: "I get it—this is a big decision. Based on our MAP, we’ve: - Proven we can automate 80% of evidence collection (vs. Competitor’s 30%).
- Saved you 150 hours/year in audit prep.
- Met all your success criteria.
What’s the next step to get this signed?"

Output: A signed contract (or a clear next step).

Common Mistakes

SE Interview / Practical Insights

1. "The prospect says, ‘Your competitor does X for half the price.’ How do you respond?"

Answer:
- Acknowledge: "I hear you—price is always a factor." - Reframe: "But let’s look at the MAP. We’ve proven we can save you 150 hours/year in audit prep. Competitor X can’t automate evidence collection—how much is that costing you in manual work?" - Ask: "Does their lower price offset the extra labor and risk of failed audits?"

Why it works: You redirect to value (not price) and leverage the MAP as proof.

2. "The Champion goes dark after the POC. What do you do?"

Answer:
- Escalate to the AE: "Let’s loop in [Economic Buyer]—the MAP shows we hit all success criteria, but we’re stuck." - Offer a next step: "Can we schedule a 15-minute call to review the MAP and next steps?" - Surface the risk: "If we don’t hear back by [date], we’ll assume this isn’t a priority and close the loop."

Why it works: You use the MAP to create urgency and force a decision.

3. "The prospect asks a question you don’t know the answer to. How do you handle it?"

Answer:
- Don’t bluff: "Great question—I don’t have the exact answer, but I’ll find out and follow up by EOD." - Leverage the MAP: "This is a key part of the POC success criteria. Let me loop in our [Product Team/SE Lead] to get you the right answer." - Follow up: Add it to the MAP’s "Open Questions" section and assign an owner.

Why it works: Honesty builds trust, and the MAP keeps you accountable.

Quick Check Questions

1. A prospect says, "We’re not ready for a POC—let’s just do a demo." How do you respond?

Answer:
- "A demo is great, but a POC lets us prove we can solve your specific problem. The MAP shows we can do this in 30 days with minimal effort from your team. Can we align on success criteria now so the POC is focused?"

SE Mindset: POCs reduce risk—position it as a low-effort way to validate the solution.

2. The Economic Buyer says, "I need to see ROI before approving this." How do you use the MAP to help?

Answer:
- "The MAP includes business outcomes—for example, we’ve projected a $200K/year savings in audit costs. Let’s review the assumptions and adjust if needed. Would it help to include your Finance team in the next review?"

SE Mindset: Tie technical wins to business impact—the MAP is your proof.

3. The prospect’s Legal team delays the contract by 2 weeks. How do you adjust the MAP?

Answer:
- "No problem—let’s update the MAP to reflect the new timeline. I’ll add a risk mitigation step: ‘If Legal takes longer than 10 days, we’ll start onboarding the Security Team early to avoid delays.’ Does that work?"

SE Mindset: A MAP is a living document—adjust and get sign-off.

Last-Minute Cram Sheet

1. MAP = Project Plan: Aligns teams on what, who, and when.
2. MEDDIC + MAP: Tie success criteria to Decision Criteria and Metrics.
3. POC Success = MAP Success: Define exit criteria upfront (e.g., "If we hit 80% automation, you’ll buy").
4. Champion’s Job: Socialize the MAP internally. Your job: Keep them accountable.
5. Risk Register: List deal blockers (e.g., "Budget approval pending") and mitigation plans.
6. Demo Flow: Align with MAP success criteria (e.g., "Show the SOC 2 dashboard first").
7. Competitor FUD: Use the MAP to neutralize objections (e.g., "Competitor X can’t do Y—we proved it in the POC").
8. Close with the MAP: "We’ve hit all milestones—are you ready to sign?"
9. ⚠️ Never let the MAP go stale: Update weekly and get sign-off on changes.
10. ⚠️ If the Champion goes dark, escalate to the Economic Buyer—the MAP is your proof.

Final Tip: The best MAPs feel like collaboration, not sales. Treat it like a project plan, not a pitch deck.