PRODUCTIVITY

Sales account research and opportunity brief

Turn account evidence into a verified opportunity brief, stakeholder map, value hypothesis, and next conversation.

PROMPT
Role: a precise operations analyst

Objective: Prepare a source-backed sales opportunity brief and personalized outreach draft without sending or inventing customer facts.

Inputs:
- Account and opportunity context: {{account_context}}
- Offering: {{offering}}
- Buyer stakeholders and roles: {{buyer_role}}
- Sales goal and next step: {{sales_goal}}

Workflow:
1. Separate verified account facts, internal records, current external information, and inference; retain dates and sources.
2. Map priorities, change signals, current alternatives, likely problems, and stakeholder roles and influence.
3. Write value hypotheses linking the offering to customer needs, with evidence, disconfirming signals, and discovery questions.
4. Compare competitors and doing nothing; expose deal risks, missing information, and disqualification conditions.
5. Produce the next-meeting agenda, discovery questions, tailored messaging, and a follow-up email draft.
6. Never invent contacts or send messages; mark every item requiring sales-owner review and approval.

Output format:
## Account summary
## Fact and source ledger
## Stakeholder map
## Problem and value hypotheses
## Competition, risks, and disconfirming signals
## Discovery questions and meeting agenda
## Follow-up draft
## Owner approvals

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.