Prepare a crisp, credible analyst briefing that lands the company's narrative and positions it well for evaluations. Analysts reward clear differentiation backed by evidence — not marketing gloss.
What This Skill Produces
- A briefing objective and the one message to land
- A tight company + product narrative and market framing
- Differentiation and proof points an analyst can verify
- A demo storyline mapped to the analyst's evaluation criteria
- Anticipated tough questions with honest answers, plus follow-ups
Required Inputs
Ask for these if not provided:
- The analyst / firm and their coverage area, plus any evaluation (Magic Quadrant, Wave, MarketScape) in play
- Objective — inclusion in an evaluation, repositioning, launch awareness, feedback
- Company & product basics — what it does, who it's for, traction
- Differentiation and the proof (customers, metrics, architecture)
- Roadmap themes you can share (and what's confidential)
- Known analyst views or prior feedback, if any
Never fabricate metrics, customers, or roadmap dates — mark [to confirm] and flag anything under NDA.
Process
- Set the objective — what a good outcome looks like and the single message to land.
- Frame the market — the category, the shift, and where you play; align to the analyst's taxonomy.
- Tell the narrative — problem, approach, why now, why you.
- Prove it — evidence that survives scrutiny; concede limits honestly.
- Map the demo to the analyst's criteria — show, don't tell.
- Pre-empt hard questions — pricing, scale, competition, gaps; prepare honest answers.
- Plan follow-up — what you'll send, by when, and how you'll track the relationship.
Output Format
Analyst Briefing Kit — [Firm / Analyst]
Date: [date] · Objective: [outcome] · Evaluation in play: [MQ / Wave / none]
The One Message
[The single thing the analyst should remember.]
Market Framing
[The category shift and where you fit, in the analyst's language.]
Company & Product Narrative
- What we do: [one line] · For: [ICP]
- Why now: [market shift] · Traction: [customers / growth — or
[to confirm]]
Differentiation & Proof
| Differentiator | Why it matters | Proof (verifiable) |
|---|---|---|
| [Point] | [analyst-relevant value] | [customer / metric / architecture] |
Demo Storyline (mapped to evaluation criteria)
- [Criterion] → [what we show]
- [Criterion] → [what we show]
Anticipated Questions
| Likely question | Honest answer | Where we're weak (and the plan) |
|---|---|---|
| [Question] | [answer] | [gap + roadmap theme] |
Roadmap Themes to Share
- [Theme] — [shareable direction] · [confidential: yes/no]
Follow-Ups
- [Deliverable] — [owner] — [by when]
Quality Checks
- The one message is explicit and repeated in the narrative
- Differentiators map to the analyst's evaluation criteria
- Every proof point is verifiable, or marked
[to confirm] - Weak spots are acknowledged with a credible plan, not hidden
- Confidential/NDA items are clearly flagged
- Follow-ups have owners and dates
Anti-Patterns
- Do not use marketing superlatives an analyst will discount
- Do not dodge gaps — analysts probe them; own them with a plan
- Do not invent metrics, logos, or roadmap dates
- Do not ignore the analyst's taxonomy and force your own category
- Do not overload the demo; map it to what's being evaluated
Example Trigger Phrases
- "Prep me for a Gartner briefing next week"
- "Write an analyst briefing document for our platform"
- "Build talking points and anticipated questions for a Forrester Wave call"
- "Prepare our narrative for a Magic Quadrant submission"