How Big Should Your Analyst Relations Team Be?

There is no useful industry rule that says a company of a certain size needs a certain number of analyst relations people. The right AR team is determined by the work the programme has to carry, not by employee count alone.

A focused company with one market, a small analyst universe and a handful of spokespeople can run an effective programme with very little dedicated capacity. A company selling across several categories, geographies and buyer groups may need substantially more coordination even when its revenue is smaller.

For many teams, that creates a second decision: what should stay in-house, what can be outsourced, and where a hybrid model makes more sense. The better question is not “How many AR people should we have?” It is “What work must this programme reliably do, and what capacity does that require?”

Start with workload, not headcount

An AR programme has both visible work and invisible work. The visible part is easy to count: briefings, inquiries, evaluation submissions, analyst events and executive meetings. The invisible part is what makes those interactions useful: analyst mapping, research monitoring, preparation, internal coordination, follow-up, CRM hygiene, evidence gathering, stakeholder education and reporting.

That second category is usually where capacity gets underestimated. Ten briefings do not equal ten hours of work. Each one may require speaker preparation, message alignment, evidence collection, logistics, follow-up and internal distribution of what was learned.

This is why activity counts alone are a poor staffing model. A programme can have relatively few external interactions and still need significant capacity if those interactions sit inside major evaluations, product launches or strategic market shifts.

The factors that actually drive AR capacity

Several variables increase the amount of AR work far more reliably than company size does.

• Number of markets or categories. Each additional market creates a new analyst set, research agenda and competitive frame.
• Geographic scope. Regional coverage may require different analysts, different evidence and different spokespeople.
• Number of priority analysts. A tightly tiered programme is much easier to run than a broad list nobody has prioritised.
• Evaluation load. Magic Quadrants, Waves, MarketScapes and other major evaluations create concentrated periods of high-intensity work.
• Executive involvement. Senior spokespeople improve AR when they are prepared properly, but preparation and coordination take time.
• Internal stakeholder count. Product, marketing, sales, leadership and communications all create legitimate demands on AR.
• Programme ambition. A programme designed only to keep analysts informed is lighter than one expected to contribute to positioning, product strategy, sales enablement and market intelligence.

The combination matters. A company with six analysts that truly matter may need less AR capacity than a company trying to cover forty names across several research firms without clear prioritisation.

What should stay in-house

Some AR responsibilities are difficult to outsource completely because they depend on internal authority and context.

Someone inside the company needs to own the business objectives, decide which internal priorities matter, secure executive participation and make trade-offs when different stakeholders want analyst attention at the same time. That owner also needs enough standing to tell colleagues when an interaction is not worth doing.

The internal function should also retain access to the information analysts need. An external partner can prepare and coordinate, but product direction, commercial context, customer evidence and leadership decisions still originate inside the business.

This is why even an outsourced AR model still needs a real client-side owner. Outsourcing work is not the same as outsourcing accountability.

When outsourced or external AR support makes sense

External support becomes useful when the company needs expertise or capacity that would be inefficient to build internally.

That can include analyst mapping, programme design, meeting preparation, evaluation support, research monitoring, interaction tracking, messaging feedback and ongoing relationship management. It can also absorb peaks in workload that would otherwise force a small internal team to choose between strategic work and administration.

The strongest model is usually explicit about the split. Internal leadership owns priorities and decisions. External support brings analyst knowledge, repeatable process and additional operating capacity. The programme fails when both sides assume the other owns the same task.

The choice is not simply in-house versus outsourced Analyst Relations. If you already have internal ownership but need senior capacity, AR Support can strengthen the team without taking ownership away from it. If you need an external team to operate the programme, AR-as-a-Service is the more relevant model.

Signs the team is too small

Under-resourcing rarely announces itself as “we need another AR person”. It shows up as operational symptoms.

• Briefings are booked but preparation happens at the last minute.
• Analyst feedback is heard but not circulated or acted on.
• Research appears after publication because nobody was monitoring it.
• Evaluation work displaces all normal relationship activity for weeks.
• The same few executives are repeatedly used because nobody has developed additional spokespeople.
• Follow-up depends on memory rather than a system.
• Sales asks for analyst intelligence and AR cannot respond quickly enough.
• The team spends most of its time coordinating activity and very little time interpreting what analysts are saying.

Those are capacity signals, but they can also reveal poor prioritisation. Adding people to an unfocused programme simply scales the unfocused programme.

Build the team around the operating model

Before adding headcount, define what the programme is responsible for, which analysts genuinely matter and which activities are essential. Then estimate the capacity required to run that model consistently through normal periods and peak periods.

For some companies the answer will be one internal owner plus specialist external support. Others will need a dedicated in-house team with regional or portfolio responsibilities. Some will need a hybrid model that changes as evaluations and market priorities move.

The size itself is not the success metric. A small team that can prioritise, prepare, follow through and feed analyst intelligence back into the business is stronger than a large team measured mainly by activity volume.

Build enough capacity to do the important work properly, then protect that capacity by saying no to the work that does not serve the programme.