What it is

A structured briefing document that prepares your leadership team for an analyst meeting — from the 2-minute company narrative to the post-briefing follow-up note.

Analyst relations is one of the most underinvested comms programmes in B2B SaaS, and one of the highest-leverage. An analyst at Gartner or Forrester shapes how enterprise buyers perceive your category and your company. A well-prepared briefing doesn’t just update the analyst — it shifts their mental model, gives them better evidence to work with, and positions you as a credible, forthcoming source they want to quote.

This template covers the full cycle: pre-briefing preparation, the briefing document itself, Q&A preparation, and the post-briefing follow-up. It is designed for the comms or marketing lead to complete and then brief the CEO, CPO, or subject expert who will attend the meeting.

When to use it

Use this template when:

You are preparing for a formal briefing with a research analyst at a named firm
You are entering a Magic Quadrant, Wave, or MarketScape evaluation cycle
You have a new product story, funding, or significant milestone to brief analysts on
You are onboarding a new executive who needs to understand the AR programme and key messages
You have had limited engagement with a specific analyst and want to reset the relationship

Do not use this template if:

This is an analyst enquiry (customer of the firm asking for advice) — that is an analyst inquiry response, not a briefing
You are briefing a journalist — different relationship, different framing
You are responding to an RFI or formal evaluation questionnaire — use a separate template for that

Inputs needed

Before starting, gather:

The analyst’s profile: Who are they? What do they cover? What have they published recently? What is their stated view on your category?
Previous briefing history: What did you tell them last time? What was their reaction? What did they publish after?
Company narrative (approved): Your current positioning statement and the 2-minute version the briefer will deliver
What’s on/off the table: Which roadmap items are cleared for disclosure? What is NDA-protected? What absolutely cannot be mentioned?
Your best proof points: Customer numbers, growth rates, named references if permitted, third-party validation
The competitive landscape the analyst lives in: What vendors do they regularly write about? Where do they place you relative to competitors?

The template

Section 1 — Analyst profile and relationship context

Complete this before every briefing. Brief the internal attendees from this section.

Analyst name: [Name] Firm: [Gartner / Forrester / IDC / [Boutique name]] Coverage area: [e.g. Marketing Technology, B2B SaaS, Communications Platforms]

Research focus (most recent 12 months): [2–3 sentences summarising their most recent published research. What are they writing about? What’s their current framework or lens?]

Their stated view on our category: [What do they believe about the market we’re in? Are they bullish, sceptical, reshaping how it’s defined?]

Their known critiques of our type of company: [What objections or scepticisms do they regularly raise about companies like us? This drives Q&A prep.]

Our relationship history:

Last briefing: [Date and topic]
Their published coverage of us since: [Title and date of any research mentioning us — positive, neutral, or critical]
Current Magic Quadrant / Wave placement (if applicable): [Quadrant/position and date]
Outstanding issues or questions from previous briefing: [Anything you committed to follow up on]

Goal for this briefing: [One clear sentence. E.g.: “Update them on our Series B and enterprise product direction before the Forrester Wave evaluation opens in Q3.”]

Section 2 — 2-minute company narrative

This is what your CEO or briefer says in the first two minutes of the meeting. It should be rehearsed, not read from slides.

Company: [Name]

What we do (one sentence): [E.g.: “[Company] is the [category] platform for [primary buyer persona] who need to [core job to be done] without [primary frustration].”]

The problem we solve: [2–3 sentences on the market problem. Lead with the customer pain, not your product. Use a market trend or data point if available.]

How we solve it (differentiated approach): [2–3 sentences on your approach — what makes it different from alternatives. Be specific. Avoid “AI-powered,” “seamless,” and “end-to-end” without definition.]

Evidence it works: [2–3 proof points. Specific numbers, customer names (if permitted), third-party validation. At least one that is quantified.]

Where we’re going: [1–2 sentences on strategic direction — pitched at “where we’re taking the category” level, not a feature list.]

Why now: [What has changed in the market that makes this company more relevant today than 12 or 24 months ago?]

Section 3 — Competitive positioning

What you claim relative to competitors. Confirm legal has reviewed any direct comparative claims.

How we define the category: [Your preferred definition — the framing that positions you most favourably. Note where analysts currently define it differently and how you’ll address that.]

Primary competitors in analyst coverage: [List the vendors most likely to appear alongside you in analyst research]

Positioning matrix:

Competitor	Their primary strength	Our differentiation	What not to say
[Competitor A]	[What they’re genuinely good at]	[How we’re different — specific and provable]	[Any claim that overstates or is legally risky]
[Competitor B]
[Competitor C]

Category narrative we’re trying to shift: [Is there a commonly held analyst view of your category that disadvantages you? What is your counter-narrative, and what evidence supports it?]

Section 4 — Product roadmap framing

What you can say, how to say it, and what absolutely stays off the table.

Cleared for disclosure in this briefing (under NDA if required):

Feature / Initiative	Expected timing	Disclosure level	Key message
[Item]	[Q3 2026 / H2 2026 / “in development”]	NDA / Public	[What to say about it in one sentence]
[Item]

Disclosed only if directly asked (with standard caveats):

Feature / Initiative	Standard caveat language
[Item]	“We’re exploring this direction but I can’t give you timing — I don’t want to set expectations we then miss.”
[Item]

Off the table (do not disclose under any circumstances): [List items that are not to be discussed — M&A, specific customer wins under NDA, litigation, unannounced partnerships]

How to handle premature roadmap questions:

“We’re not in a position to go into specifics on that yet, but directionally I can tell you that [approved general direction]. I’d rather give you something I can commit to than set a timeline we miss — can I come back to you when we have more certainty?”

Section 5 — Proof points by analyst priority area

Map your strongest evidence to the specific areas this analyst cares about. Generic proof points don’t land.

[Analyst priority area 1 — e.g. Enterprise readiness]:

[Proof point: named customer, metric, or third-party validation]
[Proof point]
[Proof point]

[Analyst priority area 2 — e.g. AI / automation capabilities]:

[Proof point]
[Proof point]
[Proof point]

[Analyst priority area 3 — e.g. Market traction / growth]:

[Proof point]
[Proof point]
[Proof point]

Named reference customers available for follow-up (if analyst requests): [List customers who have given permission to be referenced with this firm. Include their use case and the metrics they can speak to.]

Section 6 — Q&A preparation grid

Brief every internal attendee on these before the meeting. Assign one person to handle each question type.

Likely question	Ideal answer	What to avoid	Who answers
”How are you different from [Competitor X]?”	[Approved positioning — specific and provable]	Don’t disparage competitor directly	[Role]
“Where are you weakest compared to [Competitor Y]?”	[Honest acknowledgement + mitigation / roadmap context]	Don’t deflect — analysts respect honesty more than spin	[Role]
“What does your customer retention / NRR look like?”	[Metric if you can share it — or: “I can share that under NDA if useful”]	Don’t invent a number or give a range that isn’t defensible	CEO / CFO
”How are you thinking about AI — genuine capability or marketing?”	[Specific feature, specific customer outcome, third-party validation]	Don’t use “AI-powered” without specifics	CPO
”Why did [analyst’s known concern] happen?”	[Factual explanation — not defensive]	Don’t get defensive or suggest the analyst is wrong	CEO
”What would it take for you to be a Leader in our next [Wave/Quadrant]?”	[Ask what criteria they’re evaluating on, then engage substantively]	Don’t promise what you can’t deliver	[Role]

One question we hope they don’t ask: [Identify the hardest question and prepare an answer for it anyway. Brief the room.]

Section 7 — Post-briefing follow-up note

Send within 24 hours. Short. Specific. Useful.

Subject: [Company] — thank you, and follow-up on [specific topic]

[Analyst first name],

Thank you for your time today. It was a genuinely useful conversation — [one specific thing from the meeting you found valuable or that challenged your thinking. Not a generic “we appreciate your insights.”]

As promised, I’m following up on:

[Item committed to]: [Deliver it here — a data point, a document, an introduction]
[Second item if applicable]: [Deliver it]

[If you shared anything under NDA: “A reminder that the roadmap items we discussed around [topic] are under NDA until [date/event].”]

We’ll keep you posted as [specific milestone approaches — product launch, funding, Wave cycle opens]. In the meantime, if any of your clients ask about [your category], [Name] is the best contact — [their email].

[Your name] [Title] [Company]

AI prompt

Base prompt

I'm preparing for an analyst briefing and need help drafting the company narrative and proof point mapping.

Analyst context:
- Analyst name and firm: [Name, Firm]
- Their coverage area: [What they research]
- Their known perspective on our category: [What they've written or said]
- Our previous relationship with them: [Brief history]

Company context:
- What we do: [Description]
- Primary buyer: [Who buys us and why]
- Top 3 proof points: [Customer names/metrics/third-party validation]
- Competitive context: [Who we're most often compared to]
- Goal for this briefing: [What we want to achieve]

Please draft:
1. A 2-minute company narrative that leads with the market problem, explains our differentiated approach, and closes with evidence
2. A proof point mapping to the three areas this analyst most likely cares about (infer from their coverage if needed)
3. Three likely Q&A questions with recommended answers
Flag any statements that will need legal review before I use them.

Prompt variations

Variation 1 — Preparing for a critical or sceptical analyst:

We're briefing an analyst who has historically been sceptical or critical of companies like ours. Their specific concerns seem to be [describe their criticism — e.g. "they think our category is overcrowded and that we're not differentiated enough"].

Help me prepare for this briefing by:
1. Drafting a narrative that directly addresses their known concerns rather than ignoring them
2. Identifying the strongest evidence that counters their criticism
3. Preparing language for acknowledging their critique without being defensive — showing we've heard it and are responding to it
4. Suggesting what NOT to say that might reinforce their scepticism

Tone: confident but intellectually honest. We want them to update their view, not feel dismissed.

Variation 2 — Magic Quadrant / Wave evaluation preparation:

We are entering a [Gartner Magic Quadrant / Forrester Wave] evaluation for [category]. We need to prepare our submission and briefing to maximise our placement.

Here is our current positioning and proof points: [paste]

Help me:
1. Identify the criteria typically evaluated in this type of assessment (Completeness of Vision / Ability to Execute for MQ; Current Offering / Strategy for Wave) and map our strongest evidence to each
2. Identify where our evidence is weakest and what we could legitimately strengthen before submission
3. Draft our 2-minute narrative specifically positioned for an evaluation context — what evaluators are looking for vs a standard PR narrative
4. Prepare answers to the toughest evaluation questions we're likely to face

Variation 3 — Resetting a damaged analyst relationship:

Our relationship with this analyst has been difficult. They [published negative coverage / have been critical in calls / have placed us poorly in evaluations]. We want to reset the relationship at this briefing.

Background: [Describe what happened — what did they say, what was the situation]

Help me prepare a briefing that:
- Opens by acknowledging the previous situation without being defensive or litigious
- Shows specifically what has changed since then (with evidence)
- Addresses their concerns directly rather than hoping they won't come up
- Gives them something genuinely new and useful that makes the briefing worthwhile for them
- Ends with a clear ask for how we rebuild the relationship constructively

Tone: honest, direct, not self-pitying. We want a reset, not sympathy.

Variation 4 — Post-briefing follow-up with supporting materials:

We just completed an analyst briefing. Here are my notes from the meeting: [PASTE NOTES]

Please help me:
1. Draft a post-briefing thank-you email that references one specific thing from the conversation (to show I was paying attention)
2. Identify what I committed to follow up on and draft those specific follow-ups
3. Suggest what additional materials or proof points would be useful to send based on what the analyst seemed most interested in
4. Note any questions that came up where our answer was weak — and suggest how to strengthen those positions before the next briefing

Human review checklist

Before the briefing:

Has the 2-minute narrative been reviewed and approved by the CEO or relevant executive who will deliver it?
Are all proof points cleared for disclosure to this specific analyst (some reference customers have firm-specific restrictions)?
Has the roadmap disclosure list been reviewed by product and legal — what is and is not cleared?
Do all internal attendees know the Q&A prep grid — who answers what, and what is off the table?
Has the analyst’s most recent published research been read in the last 30 days?
Is there a clear NDA protocol if roadmap items are being shared under confidentiality?

After the briefing:

Is the follow-up note sent within 24 hours?
Have all committed follow-up items been delivered?
Has a briefing summary been logged internally (what we discussed, analyst’s reaction, any commitments made)?
Have you flagged any positive signals (increased interest, updated views) to the wider team?
Have you noted any outstanding concerns or commitments for the next briefing?

Example output

2-minute narrative (illustrative — B2B SaaS, communications technology)

What we do: [Company] is the communications workflow platform for enterprise comms teams who need to manage the full approval-to-publish cycle across multiple channels and markets — without losing version control, audit trail, or speed.

The problem we solve: Communications teams in regulated industries are managing increasingly complex content approval chains over email. The result is version confusion, missed compliance requirements, and campaigns that launch late or are pulled back. A global comms team managing 40+ markets can run 200+ approval threads simultaneously, with no single source of truth.

How we solve it: We’ve built the approval workflow around the asset, not around email. Every piece of content has a single version, a defined approval chain, and a live audit trail. Legal sees what marketing has approved. Regional teams can’t go live until HQ has signed off. The whole cycle is visible in one dashboard.

Evidence it works: Twelve months after deploying [Company], [Client A — anonymised: global financial services firm] reduced their regulated content approval time from 6.2 days to 2.4 days. [Client B — FTSE 100] eliminated 100% of version-control-related compliance incidents in Q4. Our net retention rate is 118%, which suggests customers are expanding use, not just renewing.

Where we’re going: We’re expanding the platform into market-level localisation workflows — which is the next friction point for global teams once central approval is solved. We’ll have more to share on that in Q3.

Why now: Regulatory requirements for content audit trails are tightening across financial services and healthcare in the UK and EU. What was good practice 18 months ago is becoming a compliance requirement. The market is arriving at where we’ve been building for three years.

Note what this narrative does: opens with the buyer and their job, not the product; names the specific pain (version confusion, email threads); gives three concrete proof points with numbers; closes with market timing that validates why this exists now.

Message House — Develop the underlying message architecture that drives the briefing narrative
Proof Points Bank — Maintain and organise the evidence base for analyst and media briefings
Stakeholder Mapping Matrix — Map analyst relationships, influence levels, and engagement history
Release Notes to PR Story Mapper — Translate product updates into the kind of proof points analysts find credible

Tips for success

Read their most recent research before every briefing. An analyst who has just published a wave about “the death of X” does not want to be briefed on your X strategy without acknowledgement. Reference their recent work and engage with it. “We read your recent piece on [X] and it challenged how we think about [Y]” is a better opener than a product demo.

Brief the briefer, not just the materials. The CEO or CPO who attends the meeting needs to know the Q&A grid, the no-go zones, and the proof points in their head — not on a slide they’re reading from. The best analyst meetings feel like a conversation. That requires preparation, not just materials.

Honesty earns more than polish. Analysts brief dozens of companies a year. They can identify spin on first contact. Acknowledging where you’re weak — “We don’t have the enterprise features [Competitor] has yet, and here’s when we’ll have them” — earns more credibility than a polished deflection. Analysts want to be able to trust what you tell them.

Treat the follow-up as part of the meeting. The post-briefing note is where relationships are built or lost. Deliver on every commitment. If you said you’d send a data point, send it within 24 hours. Analysts track which vendors are reliable. Being known as someone who follows through is a significant competitive advantage in AR.

Keep a running log of what each analyst knows. Over 18 months, you’ll have disclosed different roadmap items to different analysts at different points. A log of what was shared, when, and under what conditions (NDA/not) is essential for consistency and for legal protection if a roadmap item leaks.

Common pitfalls

Treating analyst briefings like press briefings. Journalists want a headline and a quote. Analysts want to understand your business deeply enough to advise their clients. The depth and candour appropriate for an analyst would be reckless with press. Prepare separately.

Going in without knowing their current research agenda. Briefing an analyst who is mid-way through writing about the exact thing you’re presenting — without knowing that — is a missed opportunity. Analysts appreciate when you’ve done the homework. It signals you take the relationship seriously.

Disclosing roadmap items that subsequently don’t ship. This is reputationally damaging and practically difficult to recover from. If you brief an analyst on a feature due in Q3 and it doesn’t ship until Q1 the following year, they either correct their published research (embarrassing) or publish based on the old briefing (inaccurate). Only disclose what you are highly confident will ship in the stated window.

Using the briefing as a sales meeting. Analysts are not prospects. Treating the briefing as a chance to pitch converts a research relationship into a transactional one. Ask questions. Engage with their views. Be curious about what they’re seeing in the market. The information exchange should flow both ways.

Not briefing after bad news. When something goes wrong — a CEO departure, a security incident, a product miss — the instinct is to go quiet with analysts until things stabilise. The opposite is usually correct. Analysts who hear about bad news from other sources, rather than from you, feel excluded and draw their own conclusions. Brief them early, be honest about what happened, and control the narrative.

Analyst Relations Briefing Document