Analyst Relations Brief Skill
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
Anti-Patterns
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"
1---2name: analyst-relations-brief3description: Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.4---5
6# Analyst Relations Brief Skill
7
8Prepare 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.
9
10## What This Skill Produces
11
12- A briefing objective and the one message to land
13- A tight company + product narrative and market framing
14- Differentiation and proof points an analyst can verify
15- A demo storyline mapped to the analyst's evaluation criteria
16- Anticipated tough questions with honest answers, plus follow-ups
17
18## Required Inputs
19
20Ask for these if not provided:
21
22- **The analyst / firm** and their coverage area, plus any evaluation (Magic Quadrant, Wave, MarketScape) in play
23- **Objective** — inclusion in an evaluation, repositioning, launch awareness, feedback
24- **Company & product basics** — what it does, who it's for, traction
25- **Differentiation** and the proof (customers, metrics, architecture)
26- **Roadmap themes** you can share (and what's confidential)
27- **Known analyst views** or prior feedback, if any
28
29Never fabricate metrics, customers, or roadmap dates — mark `[to confirm]` and flag anything under NDA.
30
31## Process
32
331. **Set the objective** — what a good outcome looks like and the single message to land.
342. **Frame the market** — the category, the shift, and where you play; align to the analyst's taxonomy.
353. **Tell the narrative** — problem, approach, why now, why you.
364. **Prove it** — evidence that survives scrutiny; concede limits honestly.
375. **Map the demo** to the analyst's criteria — show, don't tell.
386. **Pre-empt hard questions** — pricing, scale, competition, gaps; prepare honest answers.
397. **Plan follow-up** — what you'll send, by when, and how you'll track the relationship.
40
41## Output Format
42
43---
44
45# Analyst Briefing Kit — [Firm / Analyst]
46
47**Date:** [date] · **Objective:** [outcome] · **Evaluation in play:** [MQ / Wave / none]
48
49## The One Message
50[The single thing the analyst should remember.]
51
52## Market Framing
53[The category shift and where you fit, in the analyst's language.]
54
55## Company & Product Narrative
56- **What we do:** [one line] · **For:** [ICP]
57- **Why now:** [market shift] · **Traction:** [customers / growth — or `[to confirm]`]
58
59## Differentiation & Proof
60| Differentiator | Why it matters | Proof (verifiable) |
61|---|---|---|
62| [Point] | [analyst-relevant value] | [customer / metric / architecture] |
63
64## Demo Storyline (mapped to evaluation criteria)
651. [Criterion] → [what we show]
662. [Criterion] → [what we show]
67
68## Anticipated Questions
69| Likely question | Honest answer | Where we're weak (and the plan) |
70|---|---|---|
71| [Question] | [answer] | [gap + roadmap theme] |
72
73## Roadmap Themes to Share
74- [Theme] — [shareable direction] · [confidential: yes/no]
75
76## Follow-Ups
77- [Deliverable] — [owner] — [by when]
78
79---
80
81## Quality Checks
82
83- [ ] The one message is explicit and repeated in the narrative
84- [ ] Differentiators map to the analyst's evaluation criteria
85- [ ] Every proof point is verifiable, or marked `[to confirm]`
86- [ ] Weak spots are acknowledged with a credible plan, not hidden
87- [ ] Confidential/NDA items are clearly flagged
88- [ ] Follow-ups have owners and dates
89
90## Anti-Patterns
91
92- [ ] Do not use marketing superlatives an analyst will discount
93- [ ] Do not dodge gaps — analysts probe them; own them with a plan
94- [ ] Do not invent metrics, logos, or roadmap dates
95- [ ] Do not ignore the analyst's taxonomy and force your own category
96- [ ] Do not overload the demo; map it to what's being evaluated
97
98## Example Trigger Phrases
99
100- "Prep me for a Gartner briefing next week"
101- "Write an analyst briefing document for our platform"
102- "Build talking points and anticipated questions for a Forrester Wave call"
103- "Prepare our narrative for a Magic Quadrant submission"
Mohit Aggarwal