Skip to content
← All insights

Kea Insight / Analyst Relations

What Is Analyst Relations?

Analyst Relations is the discipline of building informed, evidence-based relationships with the industry analysts who study technology markets and advise the buyers operating inside them.

That definition is deliberately broader than “getting into reports”. A serious Analyst Relations programme helps the right analysts understand what a company does, where it fits, which problems it solves, what evidence supports its claims and how the business is changing over time. In return, the company gains an external view of how the market is being interpreted: which questions buyers are asking, which categories are changing, which evidence is missing and where internal conviction does not yet match outside understanding.

The work matters because B2B technology companies do not operate in a vacuum. Enterprise buyers rarely rely on vendor claims alone. They use research, advisory conversations, customer evidence, peer reviews, consultants, communities and increasingly AI-generated answers to reduce uncertainty. Analysts are one part of that trust system. When they understand a vendor accurately, they are better equipped to discuss it in context. When they do not, the market may continue working from an older, narrower or simply incorrect version of the company.

What Analyst Relations actually does

At its core, Analyst Relations reduces the gap between what a company knows about itself and what the outside market understands about it.

That sounds simple until a company tries to explain itself to someone who studies dozens of vendors, speaks regularly with buyers and has no obligation to accept the company’s chosen positioning. Internal language that feels obvious can be unclear externally. A differentiator that wins applause in a sales meeting may look ordinary in a market comparison. A roadmap can feel strategically important inside the business while an analyst sees no evidence that buyers care about the same direction.

AR creates a structured way to work through those differences. The company identifies which analysts matter, understands what they cover, briefs them with relevant information, listens to the questions they ask, follows up with evidence and records what the organisation needs to learn or change.

That makes the work both external and internal. Externally, AR helps analysts maintain an accurate understanding of the vendor. Internally, it gives leadership, product, marketing and sales a disciplined channel for hearing how informed outsiders interpret the market.

The purpose is not to persuade every analyst to agree with the company. That would misunderstand the relationship. The purpose is to make sure disagreement is based on current information, credible evidence and a clear view of the business rather than a preventable information gap.

Why industry analysts matter

Industry analysts research markets, technologies, vendors, buyer priorities and competitive change. Depending on the firm and individual, they may publish research, advise enterprise clients, run evaluations, speak at events, analyse market data or help buyers understand trade-offs between different approaches.

Their influence is rarely one-dimensional. A published report may shape awareness, but a private buyer conversation can matter just as much. An analyst may help a client understand a category, challenge the requirements in an RFP, explain the risks of an unfamiliar supplier or identify vendors a buying team has not considered.

That is why the analyst map matters more than the logo list. Gartner, Forrester and IDC can be important in many technology markets, but specialist firms and independent analysts may matter more in a particular technical category, geography or buying community. The useful question is not “Which firms are famous?” It is “Which analysts are relevant to the decisions that matter to this business?”

Kea’s view is that relevance should be earned through the combination of coverage, buyer influence, research activity, evaluation responsibility, regional importance and the company’s own commercial priorities. This is also why an analyst list should be reviewed regularly rather than inherited unchanged from the previous planning cycle.

What a serious AR programme includes

Analyst Relations becomes a programme when activity is connected to business objectives, evidence and follow-through. A calendar of briefings is not, by itself, an AR strategy.

A mature operating model usually combines six disciplines.

  • Market and analyst mapping: identify the firms and individual analysts who genuinely matter to the market, buyer and research priorities.
  • Positioning and evidence: make the market story clear enough to withstand external scrutiny and connect major claims to proof.
  • Engagement: plan briefings, inquiries and updates around a defined objective rather than around the need to fill a calendar.
  • Research and evaluation readiness: understand relevant research, market definitions, criteria, deadlines and evidence requirements before they become urgent.
  • Feedback and internal activation: distinguish a one-off analyst reaction from a repeated market signal and give material findings an owner inside the business.
  • Measurement: track movement in understanding, relationship depth, evidence quality, research relevance and commercial use instead of reporting activity alone.

The programme also needs ownership. Product teams hold technical truth. Customer teams hold deployment evidence. Sales hears objections and competitive comparisons. Leadership owns strategy and investment decisions. AR coordinates those inputs so the company gives the market one credible account of itself rather than a collection of departmental versions.

This is why Analyst Relations often becomes more useful as it moves upstream. The visible output may be a briefing or a report, but some of the most valuable work happens earlier: deciding what the company is trying to change in the market’s understanding and whether the evidence exists to support that change.

What Analyst Relations is not

Analyst Relations is not Public Relations with a different contact list. The disciplines overlap, but the audience, interaction model and desired outcome are different.

PR typically works with journalists and media to support public reputation, news visibility and broader awareness. AR works with analysts who research markets, advise buyers and test company claims against competing evidence. An announcement can be useful to both audiences, but the conversation around it should not be identical.

AR is also not a mechanism for buying favourable opinion. Analyst subscriptions can provide useful research and advisory access. They do not purchase belief. A vendor briefing can improve understanding. It does not create an entitlement to coverage, inclusion or a favourable evaluation.

And AR is not only about Magic Quadrants, Waves, MarketScapes or other vendor evaluations. Those processes can matter significantly, but a programme that only wakes up when a questionnaire arrives is managing deadlines rather than market understanding.

The same principle applies to analyst briefings. A briefing is primarily an opportunity to inform the analyst. It should not be treated as free consulting, and a lack of detailed feedback at the end does not mean the meeting failed. The analyst may have updated their understanding and moved on. That can still be a useful outcome.

How to know whether Analyst Relations is working

The easiest metrics are usually the weakest ones. Briefings completed, analysts contacted and reports tracked tell leadership that work happened. They do not show whether the market understands the company better.

A stronger scorecard asks different questions. Are relevant analysts placing the company in the right market? Are they comparing it with the right alternatives? Are recurring misunderstandings reducing? Is the company building stronger evidence around the claims analysts challenge? Is analyst insight being used in product, positioning, sales or leadership decisions? Where buyers or sales teams can confirm it, has analyst input contributed to a commercial conversation?

Those measures still require judgement. AR is not a paid advertising channel with neat last-click attribution. Its influence often happens before an opportunity appears in CRM. That makes discipline more important, not less: separate activity from movement, and separate contribution from claims of sole causation.

For a deeper measurement model, read Beyond Gut Feeling: What 20,000+ Analyst Interactions Teach Us About Measuring AR.

When should a company start Analyst Relations?

A company should start when outside analyst understanding can materially affect buyer confidence, category formation, evaluation readiness or how the business is compared in the market—and when the company has enough story, evidence and executive commitment to make the engagement credible.

That threshold is not the same as company size. A start-up can be ready. A much larger vendor can be unready if its market story is confused and its claims cannot be supported.

The best time is usually before AR becomes urgent. Relationships, evidence and market understanding are difficult to manufacture on demand when a major evaluation, enterprise opportunity or category shift is already underway.

Put this into practice

Do you have the foundations for a serious AR programme?

Use the Kea readiness model to test the market story, evidence, analyst relevance and executive commitment before adding more activity.

Explore AR-as-a-Service

Not sure where to start? Take the eight-question AR Readiness Check.

Share this article

LinkedInXEmail
Derk Erbé

About the author

Derk Erbé

Derk Erbé is Co-Founder and Managing Partner at Kea Analyst Relations. His career spans Analyst Relations, industry research, management consulting, business strategy and transformation. He advises technology companies on how to build market understanding and turn analyst engagement into practical business value.