---
name: account-growth-plan
description: Builds a practical growth plan for an existing account from revenue, product usage, stakeholder, service, contract, and opportunity evidence. Use for key-account planning, expansion planning, whitespace analysis, relationship mapping, or strategic account reviews.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/account-management"
  adlass.industries: ""
  adlass.tags: "account-plan, expansion, whitespace, key-account, stakeholders, growth"
  adlass.adaptation: "mapping"
  adlass.source: "original"
  adlass.version: "1"
---

# Account growth plan

## Purpose

Turn existing-account evidence into a focused expansion plan with whitespace, stakeholder coverage, risks, goals, and measurable relationship actions. Keep recommendations grounded in the account's actual history.

## Scope

Revenue, products, business units, usage, contracts, renewals, support history, stakeholders, opportunities, competitive context, and expansion hypotheses.

**Excluded:** contacting stakeholders, guaranteeing expansion, changing account records, and recommending products outside the approved portfolio.

## Data basis

- Account, contract, revenue, product, support, and opportunity records.
- Stakeholder map and approved product portfolio.
- Prior account plans when available.

## Result

An account plan, whitespace matrix, and relationship action register.

## Quality criteria

- Every whitespace item has evidence and confidence.
- Revenue and product figures reconcile to source records.
- Risks distinguish observed issues from hypotheses.
- Goals include measure, period, and source rationale.
- Actions have owner, date, and dependency or open status.

## Instructions

Use the account's terminology and reporting period. Compare product presence with eligible business units or use cases, not assumptions. Treat relationship strength as evidence-based. State when a product or stakeholder is unknown. Prioritise a small number of actions that address the highest-value gaps.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Map account, revenue, product, contract, and stakeholder fields.
- Define eligible products, units, growth goals, and action owners.
- Add the current account-plan template if one exists.