Kea Insight / Analyst Relations

What Does an Analyst Relations Agency Actually Do?

By Bram Weerts

An Analyst Relations agency should do more than book analyst meetings. The useful role of an external AR team is to help a technology company decide which analysts matter, what those analysts need to understand, which evidence supports the company’s claims and how the organisation should act on what it learns. The visible work may include briefings, inquiries, research tracking and evaluations. The value comes from the judgement connecting those activities to business priorities.

This distinction matters because “outsourcing AR” can mean very different things. One company may need a complete Analyst Relations function because no internal team exists. Another may have an experienced AR leader who only needs additional capacity for an evaluation, launch or period of heavy activity. A third may need strategic challenge more than execution.

A good agency should be clear about which problem it is solving, because the required operating model changes with the problem.

If you are choosing an Analyst Relations agency, assess the seniority of the people who will actually do the work, their analyst and evaluation experience, how they handle conflicts, how clearly they split client versus agency responsibility, and whether they can show evidence rather than promise access.

The core work an Analyst Relations agency should handle

Most serious AR programmes need the same underlying operating disciplines whether they are run internally or externally. Analyst Relations is also not interchangeable with public relations: the audiences, interaction model and evidence expectations are different.

They need a clear objective. They need an analyst map. They need a market story that can survive informed scrutiny. They need evidence. They need a cadence of useful engagement. They need a way to track relevant research and evaluation activity. They need follow-up after analyst interactions. And they need measurement that tells leadership more than how many calls took place.

An agency can take responsibility for all or part of that system, depending on what the client already owns internally.

Programme strategy: translate business priorities into AR objectives, audiences and a realistic operating plan.
Analyst mapping and prioritisation: identify relevant analysts across large and specialist firms and decide where senior attention should go.
Briefing and inquiry preparation: research the analyst, define the objective, shape the narrative, challenge weak claims and prepare spokespeople.
Outreach and relationship management: secure useful interactions, manage follow-up and maintain continuity without filling calendars for its own sake.
Research monitoring: track the reports, evaluations, market definitions and changes in analyst coverage that matter to the company.
Evaluation support: organise evidence, internal ownership, demos, customer references and responses without implying control over the analyst’s conclusion.
Feedback and measurement: capture what changed, identify recurring patterns and connect analyst insight back to positioning, product, sales and leadership.

The exact mix depends on the company. The point is that the agency should function as an operating capability, not as an appointment-setting service.

Why strategy comes before outreach

The easiest AR activity to see is the meeting. That makes it tempting to judge an agency by how many meetings it can secure.

That is the wrong starting point because analyst calendars are limited. Executive time is limited. Customer evidence is limited. A programme earns value by deciding where those scarce resources should be used.

Before outreach begins, the agency should understand the company’s business model, target buyers, product category, competitive alternatives, commercial priorities and upcoming research pressure. It should know why one analyst is more important than another and why a conversation needs to happen now.

This is also where an experienced agency should challenge the client. If the positioning is confused, the evidence is weak or the proposed analyst simply does not cover the problem, good AR advice is sometimes to delay the meeting and fix the foundation first.

That may feel less productive than adding another calendar invitation. It is usually more valuable.

What execution looks like in practice

Once the priorities are clear, the agency should reduce the operational burden without separating the client from the learning.

For a briefing, that can mean researching the analyst’s current remit, understanding the relationship history, agreeing one primary objective, shaping the deck, testing the evidence, preparing the executive team and managing the follow-up. For an inquiry, the preparation changes because the objective is to learn from the analyst rather than mainly update them.

For an ongoing programme, the agency should maintain the system of record: who has been engaged, what was discussed, which questions remain open, what follow-up was promised, which research is approaching and where the company’s evidence is getting stronger or weaker.

The company still needs to participate. External AR does not remove the need for executive judgement, product truth or customer proof. The agency should make those inputs easier to coordinate and harder to lose.

This is why good outsourced AR is not “throw it over the wall”. The agency can own programme management and execution. The business still owns the product, strategy, customers and decisions.

How agencies should support analyst evaluations

Evaluations are one of the areas where specialist support can save substantial internal time, but only if the agency respects the boundaries of the process.

A strong agency helps the company understand the market definition, inclusion rules, criteria, timetable and evidence requirements. It coordinates the people who own the answers, challenges vague or inflated responses, prepares demos and customer references and makes sure the submission presents one consistent version of the business.

What it should not do is promise a position, ranking or inclusion it cannot control.

The agency’s job is to help the company make the strongest accurate, evidence-based case and manage the process professionally. Analysts retain responsibility for the methodology and conclusion.

Preparation should also begin before the questionnaire arrives. If the company first discovers it cannot substantiate an enterprise deployment claim two days before submission, that is not an evaluation-writing problem. It is an evidence problem that should have been visible earlier.

What happens after the analyst conversation

An agency earns its value twice: in the external interaction and in what happens inside the company afterwards.

The analyst may challenge the category, question a roadmap assumption, identify a missing proof point or simply ask a question nobody in the company has answered cleanly before. The agency should record that accurately, compare it with previous interactions and decide whether it is a one-off observation or part of a pattern.

Material findings then need an owner. Product may need to investigate a capability gap. Marketing may need to sharpen the market explanation. Sales may need a better proof point for a recurring objection. Leadership may decide the analyst’s view is not representative and monitor it rather than act immediately.

AR should not turn analyst opinion into unquestioned truth. It should turn relevant external evidence into a better-informed internal decision.

What a good AR agency should not do

There are several useful red flags. An agency should not promise guaranteed research coverage, favourable rankings or analyst endorsement. It should not imply that buying a subscription changes an analyst’s independent view. It should not push irrelevant analysts into the calendar simply to demonstrate activity. It should not turn every briefing into a sales pitch, hide uncomfortable feedback or treat the client’s product language as automatically correct.

It also should not create a shadow programme around an experienced internal AR lead. When a client already owns the function, external support should strengthen that operating model, not bypass it.

The strongest agencies are comfortable saying no: no, this analyst is not relevant; no, this evidence does not support the claim; no, this meeting should not happen yet; no, one positive interaction is not proof that the programme is working.

That is not negativity. It is the judgement the company is paying for.

How to choose an Analyst Relations agency

Choosing an AR agency is less about the logo on the proposal and more about the people, judgement and operating model you will actually get. The useful questions are practical.

Who will do the work? Ask which named people will run the programme, prepare executives and speak with analysts—not only who appears in the pitch.
Do they understand your market and the analysts who shape it? Relevant coverage matters more than a generic claim of analyst access.
Can they handle evaluations as well as ongoing relationships? Magic Quadrants, Forrester Waves, IDC MarketScapes and specialist evaluations create different evidence and process demands.
How do they deal with conflicts? If an agency supports companies in adjacent or competing markets, it should be explicit about how teams, information and analyst relationships are separated.
What exactly will the client still own? The best proposals make responsibilities visible: strategy, outreach, briefing preparation, evaluation work, research monitoring, reporting and executive participation.
Can they show evidence of the way they work? Look for client references, verified reviews, named examples where permitted and a clear methodology rather than claims about privileged access.

Price matters, but it is difficult to compare before scope is comparable. A managed programme, a short evaluation project and senior overflow support are different services. Compare what is actually included, the seniority of the delivery team and how much internal workload the model removes—not only the monthly figure.

A useful agency should also be able to tell you when it is not the right model. If the company already has strong internal ownership and only needs specialist capacity, buying a complete outsourced programme can create duplication rather than value.

When to use an agency, an internal team or a hybrid model

There is no universal answer. Build internally when analyst engagement is strategically important, the volume justifies specialist headcount and the company wants deep institutional ownership of the relationships and internal influence.

Use a managed AR-as-a-Service model when the company needs the complete AR function but does not want to recruit, equip and manage it from zero. This is particularly relevant for start-ups, scale-ups and mid-sized technology vendors that need senior capability before they need a full internal department.

Use a hybrid model when an internal AR leader already owns strategy and relationships but needs additional AR support or specialist depth around evaluations, launches, regional expansion, analyst mapping or execution peaks.

The operating choice should follow the work, not ideology. An internal function is not automatically better because it is internal. An agency is not automatically more experienced because it is external. The right test is whether the model gives the company the judgement, ownership and execution discipline the programme requires.

Put this into practice

Need the complete AR function without building it internally?

Kea runs full Analyst Relations programmes and brings strategy, analyst mapping, briefing preparation, evaluation support and operating discipline together.

Explore AR-as-a-Service

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