| name | account-plan |
| description | Build an account plan; not one deal's close plan. |
| metadata | {"short-description":"Create a strategic, evidence-backed account plan"} |
Account Plan
Outcome
A focused plan connecting the customer's priorities, relationship landscape, current footprint, growth hypotheses, risks, and actions.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Organization profile, people, opportunities, products, contracts, activities, service history, goals, usage or success data when available, and authorized research.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Define the planning horizon and seller objective before selecting evidence.
- Separate verified customer priorities from seller hypotheses and public-market context.
- Assess current relationship and commercial footprint, stakeholder coverage, active initiatives, service risk, and potential whitespace.
- Turn growth hypotheses into validation questions and measurable actions rather than unsupported revenue claims.
Required output
- Account thesis
- Customer priorities and evidence
- Relationship and footprint summary
- Growth hypotheses
- Risks
- 90-day action plan
Actions and boundaries
Draft the plan read-only; confirm before creating tasks or updating account-plan records.
