Kea Insight / Analyst Relations
Analyst Relations Versus Public Relations
Analyst Relations and Public Relations are related disciplines, but they are not the same job.
Both help an organisation explain itself to influential outsiders. Both require clear messages, credible spokespeople and good judgement about timing. Both can influence how a company is understood beyond its own website and sales deck. That overlap is real—and it is one reason companies sometimes assume a PR team or agency can simply “cover AR as well”.
The problem is not that PR professionals are incapable of doing Analyst Relations. Some are excellent at it. The problem is assuming the disciplines are interchangeable without recognising the different audience, relationship, evidence and operating model involved.
A journalist and an industry analyst may both ask what has changed. What they need from the company, what they do with the answer and what makes the interaction valuable can be very different.
The core difference between Analyst Relations and Public Relations
Public Relations is generally focused on public reputation, media visibility, news, narrative and communication with journalists and broader audiences. Analyst Relations is focused on informed market understanding among industry analysts who research markets, compare vendors and often advise enterprise technology buyers.
That difference changes the purpose of the interaction. A journalist may need a timely angle, an expert comment, a clear announcement or access to an executive. The resulting output is often public and linked to a news cycle. An analyst may be building a long-term view of a category, advising a client privately, working on an evaluation or testing whether the company’s evidence supports the claims it makes. The interaction may never result in a public mention at all.
PR therefore often asks, “What should the market hear now?” AR more often asks, “What does this analyst need to understand, and what evidence will let them assess it accurately?” Neither question is inherently more strategic. They simply serve different purposes.
Different audiences create different conversations
One of the easiest ways to weaken both PR and AR is to give every external audience the same presentation.
A press announcement may be useful context for an analyst, but an analyst briefing should normally go further. The analyst may want to understand the buyer problem, market definition, competitive alternatives, architecture, deployment evidence, product maturity, commercial traction or roadmap. Those questions often sit beyond the headline and into the operating reality of the business.
The relationship also develops differently. Journalists and analysts both value relevance and accuracy, but analysts are typically expected to maintain a longitudinal view of a market. A meaningful AR programme therefore creates continuity: the analyst sees the company evolve, receives evidence as it develops and can test new claims against previous conversations and what they see elsewhere in the market.
This is why analyst mapping cannot simply be a media database with different job titles. The team needs to understand what each analyst covers, which buyers they advise, which evaluations or research they contribute to and how important that work is to the company’s commercial priorities.
The same principle applies to spokesperson preparation. A CEO can be excellent with media and still arrive poorly prepared for an analyst conversation if the team has not anticipated questions about category boundaries, product limitations, customer evidence or competitors. The executive needs the context for the specific audience, not just generic presentation coaching.
Why AR requires a different evidence model
Analysts hear vendor claims constantly, so the useful question is what supports them. That makes evidence a central part of AR. If a company says it is enterprise-ready, what deployments demonstrate that? If it claims a differentiated technical approach, where does the difference matter to buyers? If it says a new category is forming, what evidence exists outside the company’s own messaging? If the roadmap is central to the story, which parts are available now and which remain planned?
PR uses evidence too, of course. But the form and depth can differ because the audience is doing different work. A journalist may need a customer quote and a strong data point to support a story. An analyst may need to understand the methodology behind the claim, how representative the example is, what the product actually does and how the company compares with other approaches in the market.
This difference also affects measurement. Media coverage, share of voice and message pull-through can be useful PR measures. AR should be cautious about borrowing them uncritically. More analyst mentions do not automatically mean better analyst understanding. More meetings do not automatically mean stronger relationships. A programme needs to measure movement in understanding, evidence, relevance and business use—not simply volume.
The underlying principle is straightforward: the metric should reflect what the audience is actually there to do.
Where Analyst Relations and Public Relations should work together
The disciplines are strongest when they share facts without collapsing into one another.
A launch is a good example. PR may manage the announcement, media timing, public narrative and journalist engagement. AR may brief relevant analysts before or around the launch so they understand why the development matters to the market, how the product fits existing research and what evidence supports the company’s claims.
The facts should match even when the context differs. The same is true for customer proof. PR may use a case study to demonstrate market momentum. AR may use the same customer to support a specific claim about deployment complexity, use case or business outcome. Customer success needs to understand both requests so the company does not exhaust the same advocates through uncoordinated outreach.
Issues management can also benefit from coordination. Analysts should not be treated as friendly voices to mobilise during a crisis, but they may hold useful context about how a market is interpreting a material development. PR and AR can share what each audience is asking without attempting to manufacture agreement.
Good coordination therefore has a simple rule: one source of truth, different audience strategy.
Can a PR agency run Analyst Relations?
Yes—if it genuinely has AR capability. The label on the agency matters less than the capability of the people doing the work. A PR firm with experienced AR practitioners, analyst-firm knowledge, research awareness and the ability to challenge company positioning can run strong Analyst Relations. A specialist AR firm can do poor work if it merely books meetings.
The test is not “Are you a PR agency or an AR agency?” The test is whether the team can:
- identify the analysts who matter to the company’s buyers and market;
- understand analyst coverage and current research;
- prepare executives for analyst-specific conversations;
- turn positioning and product claims into evidence analysts can assess;
- support evaluations without implying control over the outcome;
- capture analyst feedback accurately and connect it back to the business;
- measure progress beyond briefing counts and report mentions.
If the answer is yes, the capability is credible. If the approach begins and ends with putting analysts on the press distribution list, it is not.
How to decide what operating model you need
The right model depends on what already exists inside the company. If an internal AR leader owns strategy and relationships but needs capacity around evaluations, briefings, analyst mapping or research monitoring, targeted AR Support may be enough.
If no internal AR function exists and analysts are strategically important to enterprise growth, a managed Analyst Relations as a Service model can provide the operating discipline without first hiring a complete team.
If the immediate problem is alignment—leadership, product, marketing and sales do not agree on the market story or priorities—an Analyst Relations Workshop may be the better first step.
The important thing is to decide based on capability and business need rather than organisational labels. PR and AR can absolutely sit close together. They simply should not be confused.
Put this into practice
Already have PR covered but need a serious AR capability?
Kea can run the full Analyst Relations function or work alongside an existing communications and AR team when specialist capability is the missing piece.
Explore AR-as-a-ServiceNot sure where to start? Take the eight-question AR Readiness Check.