Enterprise Account Expansion Playbook

🎯 **OBJECTIVE**

Execute strategic expansion within complex enterprise accounts for {{company_name}}, navigating multiple business units, geographies, decision-makers, and organizational politics to grow from initial departmental deployment to enterprise-wide adoption. This playbook addresses the unique challenges of selling into large organizations where {{average_deal_size}} can expand 10-20X through systematic multi-BU penetration.

📊 **YOUR BUSINESS CONTEXT**

**Company:** {{company_name}}  
**Product/Service:** {{product_description}}  
**Initial Entry Point:** [Department/BU where you landed]  
**Current ARR:** {{average_deal_size}} (initial deal)  
**Target Enterprise ARR:** {{lifetime_value}} (10-20X expansion)  
**Sales Cycle:** {{sales_cycle_length}} per BU  
**Target Enterprise Personas:** {{target_personas}} (multiplied across BUs)  
**Value Propositions:** {{value_propositions}}  
**Competitors:** {{competitors}}  

💡 **KNOWLEDGE BASE INPUTS**

{{knowledge_base}}

⚙️ **ENTERPRISE EXPANSION FRAMEWORK**

---

## STEP 1: ENTERPRISE ACCOUNT ASSESSMENT & MAPPING

Understanding the organizational structure is foundational to enterprise expansion.

### **ORGANIZATIONAL STRUCTURE ANALYSIS**

**Map the Enterprise:**

**Corporate Structure:**
- **Parent Company:** [Global HQ location]
- **Total Revenue:** $_______ (understand scale)
- **Total Employees:** _______ (addressable market size)
- **Geographic Footprint:** [Countries/regions with presence]
- **Public/Private:** [Ownership structure affects decision-making]
- **Industry:** {{industry}} + [sub-verticals]

**Business Unit Architecture:**

Document each major BU/division:

**BU 1: [Name]**
- **Function:** [Product line, geography, service area]
- **Revenue:** $_______ (relative importance)
- **Headcount:** _______ (expansion opportunity)
- **HQ Location:** [City, country]
- **Leadership:** [BU President/GM name]
- **Current {{company_name}} Status:** ☐ Using ☐ Not Using ☐ Using Competitor
- **Decision Autonomy:** ☐ Full autonomy ☐ Partial ☐ Corporate-controlled
- **Expansion Priority:** ☐ High ☐ Medium ☐ Low

**Repeat for BU 2, 3, etc.**

**Corporate Functions:**

These cut across BUs and can be powerful expansion vectors:

**IT/Technology:**
- **CIO/CTO:** [Name]
- **Centralized vs. Federated:** [Technology decisions made corporate or BU level]
- **Tech Stack Standardization:** [Extent of corporate mandates]
- **Influence on {{company_name}}:** ☐ High ☐ Medium ☐ Low

**Finance:**
- **CFO:** [Name]
- **Budget Control:** [Corporate vs. BU budget authority]
- **Procurement Process:** [Centralized vendor management?]
- **Influence on expansion:** ☐ High ☐ Medium ☐ Low

**Decision-Making Model:**

Understand how this enterprise makes buying decisions:

**Centralized Model:**
- Corporate makes technology/vendor decisions
- BUs must comply with corporate standards
- Expansion strategy: Win at corporate level, mandate to BUs
- Timeline: Longer enterprise sale, but broader impact once won

**Federated Model:**
- BUs have autonomy to choose vendors
- Corporate provides guidance but not mandates
- Expansion strategy: Win BU-by-BU, build coalition for corporate standard
- Timeline: Faster per-BU closes, longer overall enterprise penetration

**Hybrid Model (most common):**
- Corporate sets approved vendor lists
- BUs choose within approved options
- Expansion strategy: Get on approved list, then compete for BU selection
- Timeline: Two-stage process

**{{company_name}} Expansion Approach:**

Based on decision-making model:
- Our structure: ☐ Centralized ☐ Federated ☐ Hybrid
- Optimal expansion path: [Corporate-first vs. BU coalition]
- Key decision-makers to influence: [Names, titles]

---

## STEP 2: STAKEHOLDER IDENTIFICATION ACROSS BUs

Enterprise expansion requires managing 3-5X more stakeholders than initial sale.

### **STAKEHOLDER MATRIX**

**For Each Business Unit + Corporate:**

**Current BU (Where {{company_name}} Landed):**

**Executive Sponsor:**
- Name: _____________
- Title: [SVP/VP of _____]
- Influence: ☐ High ☐ Medium ☐ Low
- Relationship: ☐ Champion ☐ Supporter ☐ Neutral
- Expansion role: [Advocate to peers, corporate leadership]

**Champion (Day-to-Day User):**
- Name: _____________
- Title: [Director/Manager]
- Power user: ☐ Yes ☐ No
- Advocacy: ☐ Active ☐ Passive ☐ Silent
- Expansion role: [Peer influence, success story, reference]

**Target BU 2:**

**BU Leadership:**
- Name: _____________
- Title: [GM, BU President]
- Relationship to Current BU: [Peer, reports to same exec, separate]
- Introduction Path: [How to reach them]
- Likely Receptiveness: ☐ High ☐ Medium ☐ Low
- Decision Timeline: [Fiscal year, project cycle]

**Repeat for other BUs**

**Corporate Leadership:**

**C-Suite Executives:**

**CEO:**
- Name: _____________
- Strategic Priorities: [from {{key_goals}}]
- Relevance to {{product_description}}: ☐ High ☐ Medium ☐ Low
- Engagement Strategy: [{{company_name}} CEO-to-CEO, strategic initiative alignment]

**CFO:**
- Name: _____________
- Budget Influence: ☐ Final Authority ☐ Approval Required ☐ Consultative
- Cost Consciousness: ☐ High ☐ Medium ☐ Low
- Engagement Strategy: [ROI-focused, enterprise agreement economics]

**CIO/CTO:**
- Name: _____________
- Technology Strategy: [Modernization, consolidation, innovation priorities]
- Vendor Consolidation Push: ☐ Yes ☐ No
- Engagement Strategy: [Platform vision, integration strategy, roadmap alignment]

**Procurement & Legal:**

**Procurement:**
- Name: _____________
- Title: [VP Procurement, Strategic Sourcing]
- Vendor Management Approach: [Consolidation, cost-focus, strategic partnership]
- Engagement Strategy: [Enterprise agreement, volume discounts, MSA negotiation]

---

## STEP 3: POLITICAL LANDSCAPE NAVIGATION

Enterprise expansion is as much about organizational politics as product value.

### **POLITICAL DYNAMICS ASSESSMENT**

**Power Structures:**

**Formal Power (Org Chart):**
- Decision authority follows reporting lines
- Budget control by level (BU vs. corporate)
- Approval processes and thresholds

**Informal Power (Political Reality):**
- Who does the CEO trust most? (Inner circle)
- Which BUs are favored/strategic vs. disfavored?
- Rising stars vs. entrenched leaders
- Personal relationships crossing BU lines
- Historical rivalries or alliances

**Coalition Building:**

**Identify Natural Allies:**
- BUs with similar challenges from {{pain_points}}
- Leaders who collaborate regularly
- Functions with shared objectives from {{key_goals}}
- Geographies with common needs

**Build Expansion Coalition:**

**Stage 1: Initial Champions (Month 1-3)**
- Current BU success story fully documented
- Current executive sponsor actively advocating
- 2-3 power users willing to be references
- ROI data quantified and shareable

**Stage 2: Early Adopter BUs (Month 4-6)**
- Identify 1-2 BUs most similar to initial BU
- Facilitate peer-to-peer reference calls
- Offer pilot programs or proof of concepts
- Fast-track deployment with lessons learned

**Stage 3: Majority Adoption (Month 7-12)**
- Momentum from 2-3 BU successes
- Corporate leadership sees pattern of value
- Laggard BUs feeling peer pressure
- Competitive risk if {{competitors}} winning other BUs

**Stage 4: Enterprise Standard (Month 12-18)**
- Corporate mandate or strong guidance
- Holdout BUs converting
- Full enterprise-wide deployment
- Strategic partnership status

**Navigating Blockers:**

**Common Blocker Types:**

**The "Not Invented Here" Leader:**
- Resists anything not their idea
- Strategy: Make them feel like partner in decision, incorporate feedback, give credit

**The Budget Guardian:**
- Protects departmental budget fiercely
- Strategy: Show ROI specific to their BU, offer flexibility in deployment timing

**The Competitor Advocate:**
- Already using {{competitors}} solution
- Strategy: Coexistence approach (integrate vs. replace), pilot for neutral evaluation

**The Risk-Averse IT Leader:**
- Fears security, integration, support issues
- Strategy: Comprehensive security docs, integration proof points, phased rollout

---

## STEP 4: PHASED EXPANSION STRATEGY

Enterprise expansion requires sequenced approach, not "big bang."

### **EXPANSION SEQUENCING**

**Phase 1: Prove Value in Initial BU (Months 0-6)**

Already completed, but ensure:
- ✅ Strong adoption metrics (80%+ DAU/MAU)
- ✅ Quantified ROI from {{value_propositions}}
- ✅ Executive sponsor enthusiastic
- ✅ Reference-ready champions
- ✅ Case study or success story documented
- ✅ Zero major issues or escalations

**Phase 2: Expand to Similar BU (Months 6-12)**

**Selection Criteria for Next BU:**
- Similar function/use case to initial BU
- Leader open to peer recommendations
- Clear pain point from {{pain_points}}
- Budget availability and decision authority
- Positive relationship between BU leaders

**Expansion Approach:**
- Peer reference call (current to target BU leader)
- Tailored demo showing BU-specific value
- Fast-track pilot (30-60 days)
- Leverage implementation learnings from BU 1
- Success metrics tied to BU-specific KPIs

**Phase 3: Cross-Functional Expansion (Months 12-18)**

**Target Different Function:**
- E.g., Started in Sales → expand to Marketing
- Requires different champion and value prop
- New stakeholders from {{target_personas}}
- Adjacent use case for {{product_description}}

**Phase 4: Geographic Expansion (Months 18-24)**

**Expand to Other Regions:**
- North America → EMEA → APAC (or reverse)
- Same function, different geography
- May require localization considerations

**Phase 5: Enterprise-Wide Standardization (Months 24-36)**

**Corporate Mandate:**
- CIO/COO declares {{company_name}} as standard
- Remaining BUs required to adopt
- Enterprise agreement negotiation
- Strategic partnership status

### **EXPANSION VELOCITY OPTIMIZATION**

**Accelerate Expansion Timeline:**

**Parallel Pursuits:**
- Don't wait for BU 2 to close before starting BU 3 outreach
- Run multiple BU evaluations concurrently
- Create healthy internal competition (FOMO between BUs)

**Corporate Air Cover:**
- Engage corporate early (even if federated model)
- Get on approved vendor list ASAP
- Secure CIO/CFO endorsement
- Leverage corporate mandate to accelerate BU decisions

**Standardize Deployment:**
- Create repeatable implementation playbook
- Pre-configure for enterprise (SSO, integrations, security)
- Train dedicated expansion team
- Reduce time from close to value

---

## STEP 5: EXECUTIVE ENGAGEMENT PROGRAM

C-suite relationships are crucial for enterprise-wide expansion.

### **EXECUTIVE ENGAGEMENT STRATEGY**

**{{company_name}} Executive Alignment:**

**Match Executives:**
- {{company_name}} CEO ↔ Customer CEO
- {{company_name}} CTO ↔ Customer CIO
- {{company_name}} VP Sales ↔ Customer COO/CFO

**Engagement Cadence:**

**Quarterly Executive Briefings:**
- {{company_name}} exec presents to customer C-suite
- Topics: Product roadmap, industry trends, strategic vision
- Format: 60-minute session at customer HQ or virtual
- Outcome: Maintain strategic relationship, surface expansion opportunities

**Annual Strategic Planning Session:**
- Deep-dive on customer's 3-year objectives from {{key_goals}}
- Align {{company_name}} capabilities to strategic initiatives
- Identify expansion opportunities tied to customer priorities
- Multi-year partnership roadmap

**Executive Sponsorship Model:**

**{{company_name}} Executive Sponsor:**
- Assigned to each enterprise account >$500K ARR
- Quarterly check-ins minimum
- Escalation path for critical issues
- Internal advocate for customer needs

**Customer Executive Sponsor:**
- C-level champion within customer organization
- Willing to advocate for enterprise-wide adoption
- Provides access to peer executives
- Participates in reference activities

---

## STEP 6: ENTERPRISE-WIDE DEPLOYMENT

Successfully managing large-scale rollout across complex organization.

### **DEPLOYMENT PLANNING**

**Rollout Approaches:**

**Approach A: Phased by BU (Sequential)**
- Deploy fully in BU 1 → BU 2 → BU 3
- Pros: Learn and refine, manageable scope per phase
- Cons: Slower overall timeline
- Best for: Complex integration, high-touch deployment

**Approach B: Concurrent Deployment (Parallel)**
- Deploy across all BUs simultaneously
- Pros: Faster time to full enterprise value, create momentum
- Cons: Resource-intensive, higher risk
- Best for: Standardized product, SaaS with low touch

**Approach C: Hub and Spoke (Lighthouse)**
- Deploy in 2-3 strategic BUs (hubs) first
- Other BUs (spokes) follow proven model
- Pros: Balance speed and learning, create champions
- Best for: Most enterprise deployments

**Change Management:**

Enterprise expansion = organizational change initiative:

**Executive Communication:**
- CEO email announcing strategic partnership
- Town halls explaining why and benefits
- Executive talking points for team meetings

**Department Leader Enablement:**
- Training on {{product_description}} value props
- FAQs and objection handling
- Success metrics and reporting

**End User Adoption:**
- Comprehensive training program
- Champions network (power users as peer advocates)
- Gamification and incentives for early adoption
- Help desk and support resources

🎯 **DELIVERABLES CHECKLIST**

✅ **Organizational Map:** BU structure, decision-making model, key functions  
✅ **Stakeholder Matrix:** Identified stakeholders across all BUs and corporate  
✅ **Political Assessment:** Power dynamics, allies, blockers, coalition strategy  
✅ **Phased Expansion Plan:** 5-phase roadmap from single BU to enterprise-wide  
✅ **Executive Engagement Program:** C-suite relationships and strategic alignment  
✅ **Deployment Plan:** Rollout approach, change management, success metrics  
✅ **Enterprise Agreement:** Multi-year contract, volume pricing, partnership terms  

🧠 **IMPLEMENTATION CONTEXT**

Enterprise expansion is fundamentally different from initial sale. Success requires:

**Patience & Persistence:**
- Enterprise expansion takes 18-36 months typically
- Multiple sales cycles across different BUs
- Organizational politics take time to navigate

**Strategic Orchestration:**
- Coordinate across BUs without losing focus
- Balance corporate and BU relationships
- Manage internal {{company_name}} resources effectively
- Adapt strategy as you learn organizational dynamics

**Value Proof at Every Stage:**
- Each BU wants to see ROI, not just hear about peer success
- Quantify value specific to each BU's context
- Build champion network across organization
- Create unstoppable momentum through repeated success

For {{company_name}}, successfully executing enterprise expansion transforms single {{average_deal_size}} deals into {{lifetime_value}}+ strategic partnerships, dramatically improving economics while creating sticky, defensible revenue streams.