Account Brief Builder

Produce an account brief that helps teams make better account decisions 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

• For default brief format and section definitions, read references/account-brief-template.md.
• Read references/source-system-guide.md when the brief depends on CRM, conversation intelligence, or internal notes.

Default Workflow

1. Define the briefing objective. State the decision or action this brief must support.

2. Build stakeholder coverage. Map champion, economic buyer, technical approvers, procurement/legal, and blockers. Flag single-thread risk explicitly.

3. Summarize business context. Capture priorities, active initiatives, current solution fit, and recent change signals.

4. Set source-priority and freshness rules. Define source priority (for example CRM over anecdotal notes) and mark stale or conflicting data explicitly.

5. Assess opportunity and risk. Separate upside from risk. Include probability, impact, and near-term trigger signals.

6. Recommend the next 30 days. Produce a short action sequence with owner and due date. Prioritize actions that improve stakeholder alignment and de-risk execution.

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:

1. Executive summary (5-8 lines)
2. Account context and objective
3. Stakeholder map with influence/stance
4. Upside opportunities
5. Risk register with trigger and mitigation
6. 30-day action plan with owners/dates
7. Data freshness and source-priority notes
8. Open questions and assumptions

Quality Bar

• Tie major claims to evidence from provided context.
• Keep content concise and decision-oriented.
• Make stakeholder mapping actionable, not a static contact list.
• Include clear owners, dates, and expected outcomes for actions.
• Make staleness and source quality visible when evidence is incomplete or conflicting.
• Do not fabricate account facts, stakeholder roles, or commercial metrics.