| name | account-brief-builder |
| description | Build concise, decision-ready account briefs for account reviews, internal deal strategy, and customer meeting prep. Use when asked to prepare an account brief, summarize account risk and upside, map stakeholders, or define account-specific next steps. For executive-facing meeting strategy, use executive-briefing-builder. |
Account Brief Builder
Produce an account brief that helps teams make a better account decision in one read.
Confirm Inputs First
Collect the minimum required inputs:
- Whether a current
revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
- Account name and segment
- Brief objective and decision needed
- Current commercial state (pipeline, renewal, expansion, at-risk)
- Known stakeholders and recent interactions
- Data freshness window and required as-of date
- Top risks, blockers, and timeline constraints
If critical inputs are missing, ask for the smallest missing set. If the user prefers speed, proceed with clearly labeled assumptions.
Read The Right Reference
Default Workflow
-
Define the briefing objective.
State the decision or action the brief must support.
-
Build stakeholder coverage.
Map the champion, economic buyer, technical approvers, procurement/legal, and blockers.
Call out single-thread risk.
-
Summarize business context.
Capture account priorities, active initiatives, current solution fit, and recent change signals.
-
Set source-priority and freshness rules.
Use a simple source order, such as CRM first, then call notes, then anecdotal inputs.
Mark stale or conflicting data clearly.
-
Assess opportunity and risk.
Separate upside from risk.
Include probability, impact, and near-term trigger signals.
-
Recommend the next 30 days.
Produce a short action sequence with owner and due date.
Prioritize actions that improve alignment and reduce risk.
Tool Notes
CRM is useful for opportunity history, contacts, and activity trend.
Conversation intelligence is useful for stakeholder sentiment and objection patterns.
Docs/Slides are distribution layers only; keep the master brief editable.
- Use references/source-system-guide.md for source priority, freshness rules, and minimum pull guidance.
Keep workflow tool-agnostic when these systems are unavailable.
Output Contract
Deliver:
- Executive summary (5-8 lines)
- Account context and objective
- Stakeholder map with influence/stance
- Upside opportunities
- Risk register with trigger and mitigation
- 30-day action plan with owners/dates
- Data freshness and source-priority notes
- Open questions and assumptions
Quality Bar
- Tie major claims to evidence from the provided context.
- Keep the brief concise and decision-oriented.
- Make stakeholder mapping actionable, not a static contact list.
- Include clear owners, dates, and expected outcomes.
- Make staleness and source quality visible when evidence is incomplete or conflicting.
- Do not fabricate account facts, stakeholder roles, or commercial metrics.