Circulos AI

Sales AI Skill

Strategic Account Planning

Develop comprehensive strategic plans for key accounts to drive multi-year revenue growth. Use when creating account plans, mapping stakeholder relationships, identifying expansion opportunities, building multi-year growth strategies, or executing account penetration strategies. Triggers on phrases like "account plan", "strategic account", "account strategy", "multi-threading", "stakeholder mapping", "account penetration", "key account management", "white glove accounts".

Strategic Account Planning

Develop comprehensive, multi-year strategic plans for your most valuable accounts to drive deep penetration, expand revenue, and build unshakeable relationships.

Workflow

  1. Identify and qualify strategic accounts based on revenue potential, strategic value, and growth trajectory.
  2. Research account thoroughly: organizational structure, business strategy, initiatives, pain points.
  3. Map stakeholder network: decision-makers, influencers, champions, blockers across all departments.
  4. Assess current relationship depth: contacts, engagement level, satisfaction, competitive landscape.
  5. Define multi-year growth targets: revenue goals, expansion paths, relationship milestones.
  6. Create action plan: quarterly milestones, engagement strategies, value initiatives.
  7. Execute plan with regular check-ins and course corrections.
  8. Measure results against targets and iterate.

Account Research and Analysis

ACCOUNT INTELLIGENCE FRAMEWORK
══════════════════════════════════════════════════════════════════════

Research Area 1 — Company Overview:
  → Company size: Revenue, employees, locations, growth rate
  → Business model: Revenue streams, pricing model, target customers
  → Market position: Market share, competitive landscape, brand strength
  → Financial health: Revenue growth, profitability, funding status, credit rating
  → Strategic priorities: Recent initiatives, M&A activity, geographic expansion
  → Sources: Company website, investor relations, news articles, earnings calls

Research Area 2 — Organizational Structure:
  → Executive team: C-level names, backgrounds, tenure, LinkedIn profiles
  → Department structure: Key departments, reporting lines, headcount
  → Decision-making process: Formal/informal, committee-based, executive-driven
  → Recent changes: Leadership changes, reorganizations, restructuring
  → Sources: LinkedIn, company org charts, news articles, employee reviews

Research Area 3 — Technology Landscape:
  → Current vendors: Direct competitors, complementary tools, legacy systems
  → Technology stack: Cloud vs. on-premise, integration ecosystem, API usage
  → Technology maturity: Digital transformation stage, innovation adoption
  → Technology budget: IT spending trends, vendor consolidation/expansion
  → Sources: BuiltWith, Datanyze, job postings, RFPs, industry reports

Research Area 4 — Business Challenges:
  → Operational challenges: Inefficiencies, bottlenecks, cost pressures
  → Market challenges: Competitive threats, market changes, customer demands
  → Growth challenges: Scaling issues, talent acquisition, market expansion
  → Compliance challenges: Regulatory requirements, security, data privacy
  → Sources: Customer interviews, industry reports, news articles, earnings calls

Research Area 5 — Current Relationship:
  → Contacts: Named contacts, department, role, influence level
  → Engagement level: Frequency, quality, depth of interactions
  → Satisfaction: NPS, CSAT, support ticket history, renewal status
  → Expansion history: Past upsells, cross-sells, contract changes
  → Competitive landscape: Competitor presence, win/loss history
  → Sources: CRM, customer success platform, sales team interviews

Stakeholder Mapping

STAKEHOLDER MAP TEMPLATE
══════════════════════════════════════════════════════════════════════

Stakeholder Categories:
  → Economic Buyer: Final decision-maker, controls budget
  → Technical Buyer: Evaluates technical fit, integration, security
  → User Buyer: End-users who will use the product daily
  → Coach: Internal ally who provides intelligence and guidance
  → Blocker: Influential person who may resist change
  → Bystander: Aware but not actively involved

Stakeholder Map Format:

  ╔═══════════════════╦═══════════════╦═══════════════╦═══════════════╦═══════════════╗
  ║ Name              ║ Role/Title    ║ Department    ║ Influence     ║ Relationship  ║
  ╠═══════════════════╬═══════════════╬═══════════════╬═══════════════╬═══════════════╣
  ║ Jane Smith        ║ CTO           ║ Technology    ║ Economic      ║ Champion      ║
  ║ John Doe          ║ VP Eng        ║ Engineering   ║ Technical     ║ Neutral       ║
  ║ Sarah Johnson     ║ Director Ops  ║ Operations    ║ User          ║ Supporter     ║
  ║ Mike Brown        ║ CFO           ║ Finance       ║ Economic      ║ Unknown       ║
  ║ Lisa Wilson       ║ IT Manager    ║ IT            ║ Technical     ║ Blocker       ║
  ║ Tom Davis         ║ End User      ║ Sales         ║ User          ║ Supporter     ║
  ╚═══════════════════╩═══════════════╩═══════════════╩═══════════════╩═══════════════╝

Stakeholder Engagement Plan:
  → Jane Smith (CTO, Champion):
    → Current relationship: Strong, meets quarterly
    → Engagement strategy: Monthly executive briefings, industry insights
    → Value to provide: C-level strategic content, peer networking
    → Next step: Schedule Q2 business review

  → John Doe (VP Eng, Neutral):
    → Current relationship: Weak, met once
    → Engagement strategy: Technical deep-dives, integration workshops
    → Value to provide: Technical case studies, security briefing
    → Next step: Schedule technical demo with solutions engineer

  → Mike Brown (CFO, Unknown):
    → Current relationship: No direct relationship
    → Engagement strategy: ROI briefings, financial case studies
    → Value to provide: ROI analysis, TCO comparison
    → Next step: Request introduction through Jane Smith

  → Lisa Wilson (IT Manager, Blocker):
    → Current relationship: Negative, concerned about migration
    → Engagement strategy: Address concerns directly, provide migration plan
    → Value to provide: Migration support, training plan, risk mitigation
    → Next step: Schedule call to address migration concerns

MULTI-THREADING STRATEGY:
  → Current contacts: 3 (CTO, VP Eng, Director Ops)
  → Target contacts: 8 (add CFO, IT Manager, VP Sales, VP Marketing, Head of HR)
  → Connection method: LinkedIn outreach, warm introductions, conference meetings
  → Timeline: Add 2 new contacts per quarter
  → Success metric: 80%+ of key stakeholders engaged within 6 months

Account Plan Template

STRATEGIC ACCOUNT PLAN TEMPLATE
══════════════════════════════════════════════════════════════════════

Account Name: [Company]
Plan Period: [Year] (e.g., FY2024)
Account Executive: [Name]
Account Tier: [Tier 1 Strategic]

SECTION 1 — Executive Summary:
  → Account overview: [1–2 sentence description of account]
  → Current relationship: [Summary of current engagement]
  → Strategic importance: [Why this account matters — revenue, logo, influence]
  → Annual revenue target: [$X] (current: $[X], expansion target: $[X])
  → Key initiatives: [Top 3 priorities for this year]

SECTION 2 — Account Intelligence:
  → Company summary: [Size, revenue, growth, strategy]
  → Technology landscape: [Current vendors, stack, maturity]
  → Business challenges: [Top 3 challenges we can address]
  → Competitive landscape: [Competitor presence, our position]
  → Recent developments: [News, hiring, funding, M&A]

SECTION 3 — Stakeholder Map:
  → [Stakeholder map table — see above]
  → Multi-threading status: [Current vs. target contacts]
  → Champion strength: [Strong/Moderate/Weak — and development plan]

SECTION 4 — Revenue Plan:
  → Current revenue: $[X] (products: [list])
  → Expansion opportunities:
    → Opportunity 1: [Product/feature] — $[X] potential — [timeline]
    → Opportunity 2: [Product/feature] — $[X] potential — [timeline]
    → Opportunity 3: [Product/feature] — $[X] potential — [timeline]
  → Total expansion potential: $[X]
  → Quarterly revenue targets:
    Q1: $[X]
    Q2: $[X]
    Q3: $[X]
    Q4: $[X]

SECTION 5 — Engagement Plan:
  → Q1 Activities:
    → [Activity 1: QBR with executive team — January]
    → [Activity 2: Technical workshop — February]
    → [Activity 3: New stakeholder meetings — March]
  → Q2 Activities:
    → [Activity 1: Expansion opportunity presentation — April]
    → [Activity 2: Executive briefing — May]
    → [Activity 3: User adoption review — June]
  → Q3 Activities:
    → [Activity 1: Mid-year business review — July]
    → [Activity 2: New product demo — August]
    → [Activity 3: Stakeholder expansion — September]
  → Q4 Activities:
    → [Activity 1: Annual business review — October]
    → [Activity 2: Renewal negotiation — November]
    → [Activity 3: Next year planning — December]

SECTION 6 — Risk Assessment:
  → Risk 1: [Competitor displacement risk]
    Likelihood: [High/Medium/Low]
    Impact: [High/Medium/Low]
    Mitigation: [Specific action plan]

  → Risk 2: [Champion leaving risk]
    Likelihood: [High/Medium/Low]
    Impact: [High/Medium/Low]
    Mitigation: [Diversify relationships, build multi-threading]

  → Risk 3: [Budget constraint risk]
    Likelihood: [High/Medium/Low]
    Impact: [High/Medium/Low]
    Mitigation: [ROI justification, phased implementation, flexible pricing]

SECTION 7 — Success Metrics:
  → Revenue: $[X] target (current: $[X], expansion: $[X])
  → Stakeholder depth: [X] contacts (current: [X], target: [X])
  → Engagement frequency: [X] touchpoints per quarter
  → Satisfaction: NPS > [X], CSAT > [X]
  → Expansion deals closed: [X] deals
  → Strategic initiatives completed: [X] initiatives

SECTION 8 — Next 90 Days:
  → Priority actions: [Top 3 actions for next 90 days]
  → Key milestones: [Specific dates and deliverables]
  → Resources needed: [Support from manager, SE, CSM, etc.]
  → Success criteria: [How we measure 90-day success]

Edge Cases

Integration Points

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.