Account Planning

Build a comprehensive growth roadmap for each strategic account that maps decision-makers, identifies expansion opportunities, and turns reactive account management into a structured engine for expanding wallet share and extending renewal relationships.

Pre-Work Framework

Before building an account plan, gather this context:

1. What is the current contract value, seat count, and product mix? (Which products does the customer actually use, when does the contract renew, what's the annual recurring revenue) — This establishes your starting point and tells you whether you're planning for a renewal at risk, a stalled account, or a healthy expansion opportunity.

2. Who are all the people currently using the product, and who are the buyers and influencers? (Technical team, manager, department head, executive sponsor, finance owner) — The quality of your account plan directly correlates with how many people you can name in the account.

3. What is the health status of this relationship, based on concrete signals? (Product adoption trends, support ticket patterns, executive engagement frequency, meeting attendance, payment/renewal risk, net promoter score if available) — Don't guess. Find data: Are they actively using the product? Are they renewing without negotiation? Are they asking for new features?

4. What is the company's vertical, size, growth trajectory, and market pressures? (Industry, employee count, recent funding or acquisition, public financial data, known competitive pressures in their space) — This context helps you identify where they might be expanding and what's on their executive agenda.

5. What expansion opportunities are already visible, and what's your current penetration in those areas? (Unused features, untouched departments, known use cases the product supports but the customer doesn't use, adjacent products in your portfolio they haven't bought) — This prevents you from planning based on generic expansion ideas.

Core Principles

Principle 1: Single-Threading is Your Highest Risk

Rule: If more than 60% of your account value flows through a single contact, the account is single-threaded. Single-threaded accounts have catastrophic risk — if that person leaves, is promoted, loses influence, or deprioritizes you, the relationship collapses.

Rationale: Forrester data shows that single-threaded accounts are 3x more likely to experience unexpected churn. When you map stakeholders and realize you have deep relationships with only the champion, you've identified your top priority action for the next 90 days: multi-thread the account by building relationships at the executive level, the peer team level, or the department manager level. This is not optional for accounts over $100K ARR.

Principle 2: Whitespace is Inventory You Haven't Sold

Rule: Every customer should have 2-4 identified expansion vectors based on their organizational structure, use cases they've mentioned, and products they haven't purchased. Whitespace is not wishful thinking — it's real unsold opportunity that's already in scope.

Rationale: The probability of expansion is highest when you identify opportunities the customer has already implied they have. If their team has 80 reps but only purchased 50 seats, the whitespace is 30 seats. If they've adopted the product in sales but not marketing or CS, the whitespace is those departments. If they're using feature A but asking about feature B, the whitespace is feature B adoption. Expansion planning should never start with "what else could we sell them?" — it should start with "where is there a gap between what they bought and what they actually need?"

Principle 3: QBRs Are Either Strategic or Wasted Time

Rule: A QBR (Quarterly Business Review) is either a strategic conversation that delivers value, surfaces new opportunities, and strengthens executive relationships, or it's a status meeting that reads as busywork. There's no middle ground.

Rationale: Customers increasingly decline or deprioritize QBRs when they feel like you're just giving them a slide deck. Strategic QBRs lead with quantified outcomes ("Since we implemented this, your average ramp time dropped from 6 weeks to 4 weeks, saving you approximately $240K per year on productivity"), frame those outcomes as progress toward their strategic goals, and use that credibility to surface the next opportunity. When you lead with "here's a slide about your usage," you've already lost them.

Principle 4: Account Health is Observable, Not Aspirational

Rule: Account health assessment must be based on measurable signals, not assumptions. Healthy accounts show: consistent product usage, positive engagement trends, predictable renewal trajectory, and executive-level relationships. At-risk accounts show declining usage, support escalations, contract renegotiation patterns, or missed business reviews.

Rationale: Every sales leader has a customer they feel "good about" that churns six months later because health assessment was based on feeling, not data. Observable signals are: (a) product usage trending up or down, (b) active logins and feature engagement, (c) support ticket volume and sentiment, (d) renewal risk indicators (CFO request for alternatives, budget cuts, known competitive evaluation), (e) executive engagement (how often have you spoken with the VP or above, and are those conversations becoming less frequent?).

Principle 5: Expansion Requires Executive Alignment, Not Just User Enthusiasm

Rule: If you're planning expansion, you need alignment from two levels: the person who will use the product (the practitioner) and someone with budget authority or strategic influence (the economic buyer or executive sponsor). Expansion that only has practitioner support will stall when it hits budget approval.

Rationale: Many expansion opportunities fail because sales focuses on the user ("the marketing team would love this feature") without securing executive alignment ("and the CMO has $200K in budget left in Q2 to support this expansion"). In enterprise accounts, the practitioner might champion an expansion, but they can't approve spending. The expansion plan should map both the practitioner champion and the budget holder for each opportunity.

The Process

Phase 1: Account Data Gathering and Health Assessment

Entry criteria: You've identified an account that warrants a strategic account plan (typically $50K+ ARR, or a customer with expansion potential despite lower current value).

Actions:

• Document the account snapshot: company name, industry, employee count, contract value, seats purchased, products in use, renewal date, key contacts by name and title
• Assess current health based on observable signals: usage trends (up, flat, down), support ticket volume, payment history (on-time, disputed, at-risk), renewal risk signals, time since last executive engagement
• Assign explicit health status: Healthy (on track for expansion-focused renewal), Stable (will renew at current value), At-Risk (renewal conversations will be difficult), or Critical (immediate action required to prevent churn)
• For at-risk accounts, identify the specific signal that triggered the at-risk status: "Declining usage in Q3," "Product switched to evaluation mode by IT," "Budget cuts announced," "No executive engagement in 6 months"
• Document known competitive threats: Who else might they be evaluating, what competitive conversation happened recently, what gaps did they mention in your product

Output: Account snapshot with explicit health classification and top 2-3 health drivers.

Exit criteria: You have clear visibility into account health. You can answer: "If I had to make a case to my VP that this account is healthy/at-risk, what evidence would I point to?"

Phase 2: Stakeholder Mapping

Entry criteria: Account snapshot complete; you have names and relationships.

Actions:

• Map every contact you currently have in the account by (a) role/title, (b) relationship strength (Strong / Developing / No direct relationship), (c) influence level (Decision-maker / Influencer / End-user / Blocker / Coach), (d) likely priorities based on their role, (e) last meaningful interaction date
• For the champion (the person most aligned with you), document: their goals, their challenges, where they're measured, what their risk is if they champion you, and what success looks like from their perspective
• Identify stakeholders you don't have direct relationships with: Who should you know? Who controls budget? Who else is in the buyer committee? Who are the potential internal blockers? For each, draft a specific approach to introduction
• Document relationship gaps: If you only have contacts at the practitioner level, that's a gap. If you have the champion but no economic buyer, that's a gap. If you have sales contacts but no finance or ops contact (relevant for their expansion), that's a gap
• For single-threaded accounts (>60% of value through one person), flag this as a top-30-day priority and generate a multi-threading action plan

Output: Stakeholder map showing:

Contact Name | Title | Strength | Influence | Key Priorities | Last Contact | Action
Champion | Manager | Strong | Influencer | Adoption, team efficiency | 2 weeks ago | Maintain relationship
Economic Buyer | Director | Developing | Decision-Maker | ROI, budgeting | 2 months ago | QBR to reset alignment
End-User Lead | Senior Rep | Strong | End-User | Feature improvements | Weekly | Ongoing feedback loop
Executive Sponsor | VP | No relationship | Decision-Maker | Strategic fit, risk management | N/A | Propose 30-min call

Exit criteria: You have identified all significant stakeholders and clear gaps. You know who you need relationships with in the next 30 days.

Phase 3: Whitespace Analysis

Entry criteria: You understand current product usage and stakeholder needs.

Actions:

• Identify departments or teams not yet using the product: If they have 200 employees and only the sales team (40 people) uses your product, that's whitespace. If they have 5 offices and adoption is only in HQ, that's whitespace. Map these by department/location and estimate potential revenue.
• Identify use cases or features the product supports that aren't being used: If your product has integration capabilities and they haven't activated integrations, that's whitespace. If they only use feature A but feature B directly addresses a pain they mentioned, that's whitespace. Quantify each by estimated adoption rate and revenue.
• Identify adjacent products in your portfolio they haven't purchased: If you have a solutions suite and they only bought solution A, solutions B and C are whitespace.
• For each whitespace opportunity, identify: (a) potential user/champion who would care about this, (b) estimated revenue impact, (c) ease of adoption (high/medium/low), (d) prerequisite approvals needed
• Prioritize by a combination of revenue potential and adoption ease: Quick wins first (high revenue, low friction), then higher-value opportunities that require more work

Output: Whitespace summary:

Opportunity | Department/Use Case | Potential Revenue | Current State | Champion Likely | Ease | Prerequisites | Timeline
Expansion to Finance | Finance department (15 new users) | $45K ARR | Zero adoption | Finance Manager | Low | CFO alignment, process change | Q3
Integration capability | Sales operations | $30K ARR | Feature available, not activated | Head of RevOps | Medium | Technical configuration | Q2
Adjacent product | CS team (20 users) | $60K ARR | Not purchased | VP of CS | Medium | Product evaluation, budget approval | Q3-Q4

Exit criteria: You have 2-4 specific, quantified expansion opportunities. For each, you can articulate who the champion would be and what the approach looks like.

Phase 4: Competitive Threat Assessment

Entry criteria: You understand the account's landscape and known competitive dynamics.

Actions:

• Identify any known competitors in evaluation or conversation: If the prospect mentioned evaluating Alternative X, research that. If finance asked for pricing from Competitor Y, flag it. If you know there's a contract renegotiation window coming, prepare defensive materials.
• For each competitive threat, document: When did you learn about it? What's driving evaluation (RFP, user request, procurement initiative)? What is that competitor's strength relative to you? What's your advantage? What's your defense?
• Create defensive actions for the at-risk renewals or evaluations: Is it a product gap that competitors address? A relationship gap where competitors have better exec access? A perception gap where you're misunderstood?
• For expansion opportunities, preempt competitive entry: If you're planning to expand into a new department, do that before a competitor gets in. If a competitor is trying to unseat you, it's usually easier to expand your footprint (giving them new reasons to stay) than to defend existing business.

Output: Competitive threat assessment with specific, actionable defensive plays.

Exit criteria: You know what competitive threats exist, why they exist, and what you're doing about them.

Phase 5: Action Plan with Owners and Deadlines

Entry criteria: You have complete stakeholder map, whitespace analysis, and competitive assessment.

Actions:

• Build a 90-day action plan with specific, measurable actions: Not "strengthen executive relationships" but "Schedule a 30-minute business review with the VP of Sales in next 30 days to present Q3 user adoption data and Q4 expansion opportunities." Each action needs: (a) clear description, (b) owner (your name), (c) deadline (specific date), (d) success metric (how do you know this action succeeded?)
• Separate actions into categories: Relationship-building (exec meetings, site visits, peer introductions), expansion opportunities (initiate conversations, schedule technical evaluations), health improvement (usage adoption workshops, training), competitive defense (comparative assets, testimonials), QBR preparation
• For renewal accounts, map the renewal process and timeline: When is the renewal conversation supposed to start? Who needs to be involved? What's the renewal at-risk threshold? What's your upsell conversation strategy?
• For expansion opportunities, create a sequential timeline: Multi-thread first, establish executive alignment second, initiate evaluation third, close fourth. Don't jump to technical evaluation before securing executive buy-in.

Output: 90-day action plan:

Action | Category | Owner | Deadline | Success Metric
Schedule 30-min review with VP of Sales | Relationship | You | Jan 15 | Meeting confirmed on calendar
Present Q3 adoption dashboard + Q4 expansion roadmap | Relationship | You | Jan 30 | VP confirms expansion interest
Initiate Finance expansion conversation | Expansion | You | Feb 14 | Finance sponsor identified
Conduct technical evaluation of Finance features | Expansion | You + CS Engineer | Mar 14 | Finance team completes evaluation form
Submit renewal proposal with expansion options | Renewal | Manager | Apr 1 | Customer confirms alignment

Exit criteria: You have a clear 90-day roadmap with specific, dated actions. Each action has an owner and a success metric.

Phase 6: QBR Strategy (Renewal + Expansion Context)

Entry criteria: You have action plan and you're planning the next business review.

Actions:

• Design the QBR agenda around outcomes, not status: Lead with quantified results from the past quarter ("Your team went from average 4-week ramp to 2.8-week ramp, which aligns with your stated goal to accelerate hiring velocity")
• Build the narrative that connects past value to future growth: "Because we've achieved X outcome, you're now positioned to expand into Y opportunity"
• Prepare materials that demonstrate value: usage dashboard, adoption trend analysis, benchmark data showing how they compare to peer companies, ROI calculator showing impact, customer case studies from similar companies in their industry
• Map stakeholders: Who needs to be in the QBR (VP, manager, end-user champion)? Schedule it 30+ minutes to allow for discussion, not just presentation
• Plan expansion/renewal ask: Don't make the ask during the QBR. Use the QBR to align on outcomes and future opportunities, then follow up with a specific expansion proposal or renewal terms within 3-5 business days

Output: QBR agenda and supporting materials.

Exit criteria: QBR is scheduled, attendees are confirmed, and you have materials ready.

Anti-Patterns

Anti-Pattern 1: Single-Threaded Relationship

Before: You have a strong relationship with the Ops Manager. She drives adoption and loves your product. You rarely speak with her manager, and you don't know anyone in finance. When she gets promoted to a different function, your influence in the account collapses.

Problem: All your influence is concentrated in one person. If she leaves, is promoted, or deprioritizes you, you lose the account.

After: You intentionally build relationships at three levels: (1) ops manager (your champion and daily user), (2) her manager (the director who owns her function), and (3) a finance contact (who cares about ROI). When the ops manager gets promoted, you maintain the relationship with her new peer or boss, and you have relationship continuity with the director and finance contact.

Why it works: You've distributed risk across multiple relationships. Losing one contact is a setback, not a catastrophe.

Anti-Pattern 2: Vague Expansion Planning

Before: "This customer has whitespace. They should expand into the marketing department." No identified champion, no revenue estimate, no timeline, no approach for getting marketing involved.

Problem: Vague expansion ideas are not action plans. They're aspirations that never happen because there's no clear next step and no accountability.

After: "Expansion opportunity: Marketing department (estimated $75K ARR, 25 new users). Current champion: Head of Sales (developer of expansion idea). Required champion: VP of Marketing. Timeline: Initiate conversation in February, trial in March, close in April. First step: Sales champion introduces us to VP of Marketing via email with business context (email template drafted, ready to send)."

Why it works: Clear ownership, timeline, and next step make the expansion real.

Anti-Pattern 3: Reactive QBR Without Strategic Narrative

Before: QBR agenda: "1. Usage dashboard (5 min) 2. Support tickets and escalations (5 min) 3. Upcoming product roadmap (10 min) 4. Q&A". Customer leaves unmotivated. No expansion conversation happens. Renewal negotiation is contentious because customer doesn't feel like you've delivered strategic value.

Problem: You've treated the QBR as a status update, not a strategic conversation. You've missed the opportunity to align the customer on value delivered and position yourself for expansion.

After: QBR agenda: "1. 2024 success story: Your team went from 6-week to 4-week ramp, saving $320K in productivity costs (your stated goal). Here's how we contributed. 2. Benchmark: You're in the top 15% of adoption among peers. 3. Strategic opportunities ahead: We see three expansion vectors based on where you're succeeding. Which matters most to your 2025 plan? 4. Roadmap: Here's what's coming that supports your priorities."

Why it works: You've positioned yourself as a strategic partner who understands their goals and delivered quantified value. The expansion conversation is now natural.

Anti-Pattern 4: No Health Signals

Before: "I think the account is healthy. They're renewing next month." No usage data examined, no conversation with champion in 6 weeks, renewal terms not discussed, competing initiatives at the prospect not assessed.

Problem: Health is an assumption. When renewal conversation happens, you're blindsided by: "Actually, we want a 20% discount because we're evaluating alternatives." If you had monitored health signals, you would have detected this.

After: Account health tracked by: (1) weekly product usage dashboard (Is adoption trending up or flat?) (2) Support ticket sentiment and volume (Are they engaged or quietly struggling?) (3) Executive engagement frequency (Have I spoken with the VP in the past month?) (4) Renewal risk signals (Have they requested alternatives? Budget constraints announced?) (5) Expansion conversation readiness (Can I name 2-3 expansion opportunities they'd care about?)

Why it works: You're proactively managing risk rather than reacting to it during renewal.

Anti-Pattern 5: Whitespace Without Executive Alignment

Before: You identify an expansion opportunity to the Finance department. You reach out to the Finance Manager directly. Six weeks later, they're interested. You set up a technical evaluation. Finance Director attends the evaluation and asks "How much will this cost?" No one has secured budget approval, and the Finance Director deprioritizes the evaluation because she needs to align with the CFO first.

Problem: You secured user champion support without securing executive alignment. The expansion stalls because finance didn't budget for it.

After: You identify the Finance expansion opportunity. You approach the sales champion (the person who originally suggested it) and ask: "For this to move forward, we'd need alignment from the Finance Director and CFO. Are they aware this is on the list? Who's best positioned to make the case?" You only move to user evaluation after executive sponsor confirms budget and priority.

Why it works: You've eliminated a delay by securing executive alignment early. The evaluation moves faster because budget is already approved.

Output Format

A complete account plan generates:

ACCOUNT PLAN: [Company Name]
Account Tier: [Strategic / Core / Growth]
Current ARR: $[X] | Renewal Date: [Month, Year]
Health Status: [Healthy / Stable / At-Risk / Critical]

ACCOUNT SNAPSHOT
- Company: [Industry, size, geography]
- Products: [What they currently use]
- Key Contacts: [Name, title, relationship]
- Recent Activity: [Last 90 days of engagement]
- Risk Signals: [If any]

STAKEHOLDER MAP
[Table: Name | Title | Strength | Influence | Priorities | Last Contact]

HEALTH ASSESSMENT
- Overall Health: [Status with 2-3 supporting data points]
- Risk Signals: [If applicable]
- Next Review: [Date]

WHITESPACE OPPORTUNITIES
1. [Opportunity Name]: [Department/Use Case | $X ARR | Champion | Timeline]
2. [Opportunity Name]: [Department/Use Case | $X ARR | Champion | Timeline]

COMPETITIVE LANDSCAPE
- Known Competitors: [Competitor A, Competitor B]
- Threat Level: [High / Medium / Low]
- Defense Strategy: [Specific actions]

ACTION PLAN (90 Days)
1. [Relationship]: [Specific action] | Owner: [You] | Deadline: [Date]
2. [Expansion]: [Specific action] | Owner: [You] | Deadline: [Date]
3. [Health]: [Specific action] | Owner: [You] | Deadline: [Date]

QBR STRATEGY
- Scheduled: [Date, Time]
- Attendees: [Names and titles]
- Key Messages: [2-3 outcomes you'll highlight]
- Ask: [Specific expansion or renewal conversation to initiate]

Task-Specific Questions

For Healthy, Expansion-Ready Accounts

1. Which department or use case is the lowest-hanging fruit for expansion (highest revenue potential + lowest adoption friction)?
2. Who would be the user champion for expansion, and does that person have executive sponsor support?
3. What specific business outcome would validate that expansion is worth the investment?

For At-Risk Renewal Accounts

1. What specific signal triggered "at-risk" status (declining usage, executive disengagement, competitive evaluation, budget cuts)?
2. Who is most likely to advocate for renewal or churn, and why?
3. What expansion opportunity, if executed quickly, would reset the relationship and improve renewal confidence?

For Accounts Requiring Multi-Threading

1. Who is the economic buyer or budget owner you don't currently have a relationship with, and what's the most authentic reason to request an introduction?
2. What business outcome or strategic goal would resonate with that buyer?
3. Which of your current contacts is best positioned to make that introduction or can help you access that person?

Quality Checklist

Before finalizing an account plan, verify:

1. Every stakeholder is named and mapped, including those you don't have relationships with yet. (Not "sales stakeholders" but "Sarah Chen, VP of Sales; Marcus Rodriguez, Sales Director; Jamie Lee, Sales Development Lead")

2. Health status has explicit supporting evidence. (Not "healthy" but "Healthy: Q3 usage up 12% vs. Q2, executive engaged monthly, support tickets down 20%, renewal at-risk indicators minimal")

3. Single-threaded accounts are flagged as top priority and have a 30-day multi-threading action. (If 70%+ of value flows through one contact, you have a mitigation plan)

4. Each whitespace opportunity has a quantified revenue estimate, identified champion, and clear next step. (Not "expand to marketing" but "Marketing expansion: $60K ARR, 18 seats, VP of Marketing identified as sponsor, approach: Sales champion introduction + business case presentation, timeline: Feb 15 initial conversation")

5. Competitive threats are documented with specific defense actions, not general claims. (Not "defend against Competitor X" but "Competitor X has strong integration story. Defense: (1) schedule integration technical review with customer, (2) prepare integration case studies, (3) ensure customer knows our roadmap includes enhanced integration)")

6. All action items are specific, dated, assigned, and have success metrics. (Not "strengthen executive relationship" but "Schedule 30-min business review with VP of Sales by Jan 20 to present Q4 roadmap. Success = meeting confirmed and value realization metrics prepared")

7. QBR strategy is outlined with specific agenda, attendees, and follow-up play. (Not "hold QBR" but "Jan 30 QBR with VP, Director, and champion. Lead with ramp-time improvement metric ($320K productivity savings). Propose Finance expansion as next growth lever")

8. Renewal timeline and strategy are documented. (When does renewal conversation need to start? What's your renewal ask? What's your expansion ask?)

Related Skills

When building and executing account plans, you'll often need:

• Pipeline Review — How to assess overall health of your entire book of business
• Deal Qualification — How to determine if an opportunity is qualified before moving forward
• Competitive Intelligence — How to research and counter competitive threats
• Pricing Negotiation — How to navigate renewal and expansion conversations with budget and terms discussion

Example Prompts

1. Strategic Account Plan for Large Customer "Build a comprehensive account plan for Acme Corp, our largest customer. ARR is $450K, they've been with us for 3 years, and they currently use our sales and analytics modules. Renewal is coming in Q2. The main contact is Jane Smith (VP of Sales), who is fantastic. My director is pushing for expansion into their customer success team. What's the complete account plan that sets us up for a successful renewal + expansion?"

Expected output: Full account plan including: stakeholder map (who you need besides Jane), whitespace analysis (CS department quantified), health assessment (renewal confidence level), and 90-day action plan (multi-threading timeline, CS expansion approach, QBR strategy).

2. Renewal-at-Risk Account Recovery "I have a customer where usage dropped 30% in Q3, they've deferred their renewal conversation three times, and I haven't heard from them in 8 weeks. The contact I have is the practitioner (manager level). I need a plan to: (1) diagnose what's going wrong, (2) fix the relationship, and (3) either save the renewal or professionally close it. Help me build the account plan."

Expected output: Account plan focused on: (1) health assessment with specific diagnosis, (2) multi-threading strategy to access decision-maker and understand renewal decision, (3) 30-day action plan to reset the relationship or clarify their decision, (4) expansion opportunity if relevant.

3. Multi-Threaded Expansion Strategy "I have a customer at $150K ARR where I'm strong with the sales leader but weak everywhere else in the organization. They just announced a 50-person hiring surge and are opening new offices. I see clear expansion opportunities in multiple departments. Build an account plan that (1) multi-threads the relationship, (2) identifies all expansion vectors, and (3) maps a 6-month expansion roadmap."

Expected output: Account plan with: (1) stakeholder map showing all people you need relationships with in their growth plan, (2) whitespace opportunities (by department, by geography, by product) with revenue quantification, (3) expansion sequencing plan (who to approach first, what conversation to start), (4) 90-day action plan with multi-threading and expansion initiation.

4. QBR Preparation with Expansion Narrative "My customer renews in Q2 and I want to use the QBR to demonstrate value and position for expansion. They care about efficiency and process improvement. Build the QBR strategy: what metrics do I highlight, what expansion opportunities do I propose, and how do I structure the conversation to increase probability of expansion?"

Expected output: QBR agenda with specific outcomes to highlight (efficiency metrics, cost savings, adoption benchmarks), strategic narrative connecting past value to future opportunities, and recommended expansion opportunities with business cases. Also provides 3-5 day follow-up plan to convert expansion conversation into contract.