Analyst relations

Analyst Relations

Overview

This skill covers how B2B marketers should approach analyst relations as a strategic function — from using third-party validation to differentiate a product, to orchestrating multi-channel consensus-building when establishing a new category. All practices are sourced exclusively from Exit Five podcast guests and reflect their direct experience. Note: both source practices for this skill are strategic in orientation. Where the guest did not specify a mechanism or first step, this skill says so explicitly rather than presenting directional guidance as actionable instruction.

Third-Party Validation as a Differentiation Pillar

Treat analyst coverage, press mentions, and customer testimonials as necessary components of differentiation — not optional add-ons — because customers will not take your word for it that your product is better. As Priscilla Barolo put it, "you can say your product is better till you're blue in the face," but external validation carries weight that self-promotion cannot. (Source: Priscilla Barolo, Episode #302)

Limitation: The source practice does not specify which analysts to target, how to initiate coverage, or what "building it into the mix" looks like operationally. This is directional guidance. The guest did not describe a first step or a mechanism for securing coverage.

Building Category Consensus Through Analyst Relations

When establishing a new category, execute a coordinated, multi-channel consensus-building strategy across three pillars. The strategic objective is to create "herd mentality": secure the first 1,000 customers and establish category consensus, and the next 10,000 follow more easily. Without this effort, you face a prolonged, deal-by-deal fight for every customer. (Source: Melton Littlepage, Episode #223)

The three pillars Melton Littlepage describes are:

1. Analyst relations — Engage Gartner, Forrester, and IDC early, as part of the category-building process itself, not after the category is defined. The goal is to give the emerging category institutional credibility by bringing analysts along the journey.

Limitation: The guest did not specify how to initiate this engagement — whether through a formal briefing request, a custom research engagement, a sponsored report, or another mechanism. The "how" was not addressed; this is strategic framing only.

2. Buyer community engagement — Participate in roundtables, forums, and Chatham House rule conversations with target buyers. Use these settings to provoke discussion of the problem, not to pitch your product.

Limitation: The guest did not identify specific forums, explain how to find or gain access to Chatham House rule conversations in a given space, or describe what "provoking discussion of the problem" looks like in practice (e.g., a prepared question, a white paper, a facilitated session). If your industry has an equivalent buyer community, the principle applies — but the guest did not provide a first step.

3. Thought leadership — Lead external communications with a category point of view, not product messaging.

Limitation: The guest did not provide an example of category POV content versus product messaging, nor a test for distinguishing the two. This is a directional principle without a concrete mechanism as captured in the source material.

What NOT To Do

• Do not wait until your category is established before engaging analysts. Melton Littlepage's framing implies that companies who engage analysts only after a category is named have already ceded the ability to shape how that category is defined — competitors who engaged earlier will have influenced the definition first. Analyst relations must be part of the category-building process, not a validation step that follows it. (Source: Melton Littlepage, Episode #223)

Where Experts Disagree

No disagreements were identified across the contributing episodes for this category.

Sources

Episode	Guest	Date	Note
Episode #223	Melton Littlepage	2025-02-27
Episode #302	Priscilla Barolo	2025-11-10	Date as recorded in source data; verify if this appears incorrect