Gtm-Enterprise-Account-Planning

# 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? (Implement