/gtm-enterprise-account-planning

name: gtm-enterprise-account-planning
description: Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
license: MIT
metadata:
  author: Smit Patel (https://linkedin.com/in/smitkpatel)
  source: https://github.com/beingsmit/technical-product-gtm

Enterprise Account Planning

Strategic account planning and execution for enterprise deals. Turn complex sales cycles into systematic wins — or at least know when they're dying before you waste months.

When to Use

**Triggers:**

• "How do I plan this enterprise deal?"
• "This deal has been in motion 3 months, why isn't it closing?"
• "Should I create a full account plan or simplified version?"
• "How do I know if this deal is actually moving?"
• "MEDDICC qualification"
• "Building a mutual action plan"

**Context:**

• Strategic deals above your average ACV
• Multiple stakeholders involved
• Sales cycle exceeds 60 days
• Complex buying process (legal, procurement, security)
• Enterprise or mid-market accounts

---

Core Frameworks

1. If Your MAP Hasn't Been Updated in 3 Weeks, That Deal Is Dead

**The Pattern I've Seen:**

The Mutual Action Plan (MAP) is the single best indicator of deal health. Not pipeline stage. Not verbal commitments. Not "they love the product."

**The MAP tells you everything:**

**Healthy deal:**

• MAP updated weekly
• Customer adding their own action items
• Both sides completing tasks on schedule
• New stakeholders appearing in MAP
• Dates moving up (not pushed out)

**Dying deal:**

• MAP last updated 3+ weeks ago
• Only your side has action items
• Customer tasks marked "pending" for weeks
• No new stakeholders engaged
• All dates in the past

**Why This Happens:**

When a deal is real, the customer wants it to happen. They're doing work. They're involving stakeholders. They're moving through their process.

When a deal is dying, you're doing all the work. They're "too busy." They'll "get back to you next week." The economic buyer is "traveling."

**The 3-Week Rule:**

If your MAP hasn't been updated in 3 weeks, the deal is dead — you just don't know it yet. **I've never seen a deal close with a stale MAP. Not once in 11 years.**

**What to Do:**

**Week 1 of silence:** Send MAP update: "Here's what we've completed. What's your status on [specific customer action]?"

**Week 2 of silence:** Escalate to champion: "Haven't heard back on MAP. Are we still on track for [date]? If priorities shifted, let me know."

**Week 3 of silence:** Qualify out or reset: "It seems like timing might not be right. Should we pause and reconnect in [timeframe], or is there a blocker I can help with?"

**Common Mistake:**

Keeping deals in pipeline because "they said they want it." Verbal interest ≠ action. If they're not doing work, they're not buying.

---

2. The EB Discovery Problem (And Why Deals Die at Week 8)

**The Pattern:**

You're 8 weeks into a deal. POC went great. Champion loves you. Technical validation complete. You send the proposal.

Then: radio silence.

**What happened?** You never met the Economic Buyer.

**The Economic Buyer (EB) is the person who:**

• Controls budget allocation
• Makes final purchase decision
• Signs the contract

**Not:**

• Your champion (they influence, don't decide)
• The technical lead (they validate, don't buy)
• The VP who attended one demo (they advise, don't sign)

**Why Deals Die Without EB Access:**

You built the business case with your champion's assumptions. But the EB has different priorities:

• Champion cares about: solving their team's pain
• EB cares about: ROI, risk mitigation, strategic alignment

When you send proposal to EB through the champion, EB sees:

• Price tag with no context
• Solution to a problem they didn't articulate
• Risk they haven't evaluated

**Result:** Deal stalls or dies.

**The Framework: EB Validation Checklist**

Before sending proposal, validate:

• [ ] Have you identified the EB? (Name, title, confirmed by champion)
• [ ] Have you met the EB? (Video call minimum, in-person ideal)
• [ ] Does EB agree on the problem? (In their words, not yours)
• [ ] Does EB agree on success metrics? (How they'll measure ROI)
• [ ] Does EB know the price range? (Ballpark discussed, not surprised)
• [ ] Does EB understand timeline? (Implementation, go-live, value realization)

**If you answered "no" to any, don't send the proposal yet.**

**How to Get EB Access:**

**Ask your champion:** "Before we finalize pricing, I'd love 15 minutes with [EB name] to make sure we're aligned on outcomes and timeline. Can you intro us?"

**If champion blocks:** "I can handle that, you don't need to talk to them" → This is a red flag. Either champion doesn't have access (not a real champion) or they're afraid EB will kill the deal (which means deal is weak).

**Push back:** "I totally understand. At the same time, I want to make sure [EB] sees the full value before seeing the price. In my experience, when economic buyers aren't involved early, deals get delayed in procurement. Can we do a quick alignment call?"

**Common Mistake:**

Treating EB meeting as "nice to have." It's mandatory for any deal >$50K. No EB access = no deal.

---

3. Personal Win Mapping (People Buy for Themselves)

**The Pattern:**

Enterprise software purchases are made by committees. But committees don't buy. **People buy.**

And people buy for personal reasons:

• Career advancement
• Looking good to their boss
• Reducing their workload
• Covering their ass (CYA)
• Proving they were right
• Not looking stupid

**Framework: Personal Win Identification**

For each stakeholder, map:

**Professional Win:**

• What do they get credit for if this succeeds?
• What pain goes away for them personally?
• How does this make them look good?

**Professional Risk:**

• What happens to them if