Prepare for a customer meeting
Turn approved evidence into a concise brief, discovery plan, and risk check.
Meeting brief
Finish with an artifact another professional can review, challenge, and act on.
When to use this
Turn approved evidence into a concise brief, discovery plan, and risk check. 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 meeting brief from the controlling sources and flag gaps.
Working
Compare sources, classify evidence, produce the meeting 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
- Meeting purpose and desired outcome
- Participant names and verified roles
- Approved account history, commitments, and current evidence
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 meeting 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 meeting brief and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
Prepare for a customer meeting
GOAL Prepare for a purposeful customer conversation with evidence-based questions. 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 Create a brief covering Purpose, People, Evidence, Questions, Risks, and Desired Outcome. CONSTRAINTS Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts. REQUIRED OUTPUT A one-page meeting brief followed by five ordered discovery questions and a verification list. 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
For Northstar, the brief centers a vendor-neutral workshop on operating visibility and handoff failures. It treats renewal timing and decision authority as unknown.
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 meeting 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
Prepare the Northstar workshop brief from the profile, stakeholder directory, and meeting notes.
Open Northstar exercises