Understand the account for a decision
Build a source-backed account view for a specific conversation or choice.
Account evidence brief
Finish with an artifact another professional can review, challenge, and act on.
When to use this
Build a source-backed account view for a specific conversation or choice. Use it when the decision matters enough that source authority, uncertainty, and human review must stay visible.
Match the depth to the consequence
Quick
Produce the minimum useful account evidence brief from the controlling sources and flag gaps.
Working
Compare sources, classify evidence, produce the account evidence brief, and run the task-specific checks.
Thorough
Add a countercase, conflict review, stakeholder challenge, and explicit validation plan before action.
Bring only what the task needs
- The decision this work must support
- Current, approved source material
- Known constraints and open questions
Boundary: Approved customer information in an employer-approved environment; otherwise use public or fictional material.
Do not add credentials, unnecessary personal information, private security details, unapproved pricing, contracts, or customer material.
Work sequence
- State the decision the account evidence brief must support.
- Select the controlling sources and record their date, owner, and authority.
- Separate customer evidence from seller interpretation before asking AI to synthesize.
- Build the account evidence brief and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
Understand the account for a decision
GOAL Build a decision-specific view of the account without turning public signals into private customer facts. CONTEXT The account, audience, decision, and current sales stage are [CONTEXT]. CONTROLLING SOURCES Use only [APPROVED SOURCES]. Identify the source behind every material fact. TASK Inventory the sources, extract relevant facts, classify implications, surface contradictions, and identify the next information needed. CONSTRAINTS Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts. REQUIRED OUTPUT Account evidence brief UNCERTAINTY BEHAVIOR Separate Known, Inferred, Assumed, and Unknown. Show conflicts instead of resolving them without evidence. Turn important unknowns into questions. VERIFICATION REQUEST List the claims, calculations, names, dates, owners, commitments, and source conflicts a human must verify before acting. Construct the strongest evidence-based case against the proposed conclusion.
Northstar example
Northstar has documented integration friction after acquiring Meridian. A vendor-consolidation mandate is not documented. The next move is a vendor-neutral operating assessment.
Task-specific checks
Why this works
The sequence starts with the decision and source authority, so fluent output cannot quietly replace evidence. The countercase turns uncertainty into focused customer questions.
A weak AI request
“Create a polished account evidence brief and make it persuasive.”
This request has no controlling sources, evidence boundary, uncertainty behavior, or verification step. It rewards confident prose instead of dependable work.
Practice safely
Use the Northstar profile, meeting notes, and risk register to identify the unsupported account story.
Open Northstar exercises