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.
SKILL.md
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.
