You Can Do Analyst Relations Yourself. Trial and Error Is Still a Poor Operating Model.

You can run Analyst Relations yourself. What you should not do is learn the basics on the analysts who matter most.

There is nothing inherently wrong with running AR in-house. Some of the strongest programmes are led internally because the team has deep market knowledge, access to leadership and the authority to connect analyst feedback with product, sales and strategy.

The problem is not ownership. It is improvisation.

Analyst Relations looks deceptively simple from the outside: find the analyst, book a call, show the deck, answer questions and follow up. The visible meeting is the easy part. The judgement sits around it: choosing the right analyst, understanding their remit, deciding why the conversation matters, building the narrative, preparing evidence, briefing executives and knowing what to do with the response.

Trial and error is how every team learns. It becomes expensive when avoidable mistakes are made in front of scarce, high-value relationships and then repeated because nobody has built an operating model around the learning.

In-house AR is not the problem

Companies sometimes frame the decision as internal versus agency. That is too crude to be useful.

The real question is whether the programme has the capability, time and authority required to do the work well. An experienced internal AR leader with executive access and a functioning analyst map may need very little external help. A marketing generalist given AR as ten per cent of their job may need considerably more, even if the company prefers to keep ownership inside.

External support is not automatically more strategic and internal ownership is not automatically more authentic. Both can fail if the programme is built around activity rather than judgement.

The useful distinction is between ownership and capability. Ownership answers who is accountable. Capability answers whether the people doing the work know how to prioritise analysts, prepare the business, manage research processes, interpret feedback and maintain relationships over time.

You can own the programme internally and still borrow specialist capability where the stakes or workload justify it.

The meeting is only the visible part of the work

The briefing is the moment everybody sees, which is why inexperienced programmes tend to over-focus on it.

Before the call, somebody needs to establish why this analyst matters. What do they cover? Which buyers do they advise? Which research are they responsible for? What do they already know about the company? Which part of the story is relevant to their work now?

Then the company needs an objective. “Give them an update” is not enough. What should the analyst understand more clearly when the meeting ends? Which evidence will make that understanding credible? Which executive or technical leader is best placed to explain it?

The deck comes after those decisions.

After the call, the same discipline continues. What did the analyst understand? Which questions remained unresolved? What was promised? Did the conversation expose a product, evidence or positioning gap? Who owns the next action?

If the programme only gets serious once the calendar invite exists, most of the value has already been left to chance.

The mistakes that create avoidable market friction

Most weak analyst interactions do not fail spectacularly. They fail in ordinary ways.

The wrong analyst receives the meeting because the firm name looked important. The executive spends fifteen minutes on company history. The product team starts with features before establishing the buyer problem. A roadmap item is presented too casually and sounds like current capability. A customer logo appears without enough context to prove anything. The analyst asks a basic positioning question and three people answer it differently.

None of these necessarily destroys a relationship. Good analysts have seen worse. The cost is subtler: the company becomes harder to understand and future conversations have to spend time repairing avoidable confusion.

The same applies to research processes. A team can misread the purpose of a briefing, assume a subscription buys access it does not, prepare for an evaluation after the questionnaire arrives or treat one analyst’s feedback as universal market truth.

The individual mistake matters less than whether the programme learns from it.

This is where a deliberate operating model beats improvisation. Record the issue, understand why it happened, change the preparation and test whether the next interaction improves.

Learn on the process, not on the relationship

Every AR team needs to learn. The objective is not to eliminate experimentation; it is to move the experimentation to places where the cost of being wrong is lower.

Test the narrative internally before using it with the analyst who owns the critical evaluation. Rehearse the executive before the first high-stakes briefing. Challenge the analyst map before allocating CEO time. Build the evidence register before the research deadline. Ask a less sensitive relationship whether the new explanation is clear before assuming it is ready for the market.

That is the difference between learning and gambling.

A strong programme creates feedback loops around the work. It compares what was intended with what happened, keeps commitments visible and brings recurring analyst questions back into the business. Over time, the team becomes less dependent on individual memory and more capable of repeating what works.

Our newer Insight Beyond Gut Feeling: What 20,000+ Analyst Interactions Teach Us About Measuring AR explains how to compare interactions without turning experience into fake statistical certainty.

What internal AR capability actually requires

A serious internal programme needs more than someone who is good at communication.

It needs analyst mapping and prioritisation, research awareness, relationship history, briefing judgement, evaluation discipline, executive preparation, evidence management and enough internal credibility to bring uncomfortable feedback back into the company.

It also needs time.

That last point is underestimated. AR often fails as a side responsibility because the urgent parts survive and the important parts disappear. The meeting gets scheduled. The research map does not get updated. The briefing happens. The follow-up is late. The questionnaire gets answered. The evidence library remains scattered until the next emergency.

A capable person without capacity still produces a reactive programme.

This is why companies should be realistic about the operating model. If one internal leader can own the strategy and relationships but lacks execution capacity, additional support may make sense. If the company has no internal AR expertise at all, a managed programme may be faster than learning every process from scratch. If the volume is low and leadership is engaged, targeted coaching and preparation may be enough.

When to build, borrow or buy AR capability

There is no universal answer. The right model depends on how strategically important analysts are to the business, how much work the programme creates and which capabilities already exist internally.

Build internally when the company has sustained volume, wants deep institutional ownership and can justify specialist headcount. Borrow capability when the internal team is strong but needs additional judgement or capacity around evaluations, launches, market shifts or coverage peaks. Use a managed model when the company needs the complete operating function but does not want to build it from zero.

The important thing is to make the choice deliberately.

Do not call a programme “in-house” when it is really an overextended marketer doing occasional outreach. Do not call external support strategic if it is only booking meetings. And do not assume that one successful briefing proves the operating model works.

You can do Analyst Relations yourself. The question is whether you want your most important analyst relationships to be where the organisation discovers what it does not yet know.

Use the AR Readiness Check to test the foundations. If the business has internal ownership but needs additional capacity or specialist depth, Additional AR Support is the relevant model. If it needs the complete function, see Analyst Relations as a Service.

Put this into practice

Give analyst engagement an owner and a next step.

Build preparation, follow-through and measurement into a sustained programme around your business priorities.

Explore AR-as-a-Service ↗

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

Share this article