Kea Insight / Analyst Relations

Your Analyst Subscription Is Not a Strategy. It Is a Stepping Stone.

By Bram Weerts

A research subscription is not a microphone. It is not a certificate of importance. And it is not a down payment on an analyst saying something flattering about your company.

If you are trying to get more value from a Gartner, Forrester, IDC or specialist-firm subscription, the problem is usually not access. It is whether the access is connected to real decisions, useful questions and people who will act on what they learn.

You buy research because there is something you do not understand well enough to make a decision. The right subscription gives you access to knowledge, evidence and expertise that can help close that gap. That makes it a stepping stone towards your goal. Your team still has to decide what the insight means, choose a course of action and do the work.

That might come from Gartner, Forrester, IDC or a specialist firm with a particularly strong understanding of your market. The starting point is not whose logo would look best in your board presentation. It is what your business needs to know.

If the real ambition is to tell the market how remarkable your company is, be honest about that. It is a communications objective. Buying a research subscription does not turn it into a learning objective.

This is a practical guide to buying, using and renewing research access with a purpose. It is not a ranking of research firms. Nor does it assume that every business needs a subscription. Sometimes the right answer is to use the access you already have. Sometimes it is to buy something narrower. Sometimes it is not to buy at all.

1. Start with the decision, not the subscription

“We need better market intelligence” is a reasonable aspiration. It is not yet a buying brief.

Which market? Which uncertainty? Whose decision? By when? What would you do differently if the research challenged your current view?

Consider a hypothetical software company debating whether to enter a new buyer segment. Its team already knows its product. What it does not know is whether those buyers recognise the problem, how they organise the budget, what alternatives they consider and what would stop them buying.

That is a knowledge gap. “We need analysts to understand how innovative we are” is a different problem.

Before speaking to a research firm, write down three to five decisions where external knowledge could genuinely help. For each, record:

The decision and the person accountable for it.
The deadline and the consequences of getting it wrong.
What you already know, and what remains an assumption.
The specific question outside expertise could help answer.
What evidence would cause you to change direction.

If nobody can name a decision, pause the purchase. An impressive library will not compensate for an organisation that has not decided what it needs to learn.

Also separate missing knowledge from missing agreement. If your leadership team has the evidence but cannot agree on priorities, another subscription may simply give each side more material to quote.

2. Separate research access from visibility

Several different activities sit around analyst relations. Confusing them creates expensive expectations.

Research access helps your team learn. Depending on the agreement, this may include published research, data, tools and conversations with analysts. You are buying defined access, not ownership of the research or an unlimited advisory relationship.

A vendor briefing gives a research firm information about your business. It is an opportunity to explain relevant developments, evidence and market experience. It is not the same as a client asking an analyst for advice.

Research evaluation participation involves a firm’s methodology, scope and eligibility requirements. It is not a subscription benefit you should assume you can purchase.

Marketing and commercial rights—such as authorised reprints or commissioned work—are separate questions. Where offered, their terms and permitted uses need their own examination.

Gartner’s Office of the Ombuds states that client status does not determine research positioning and that vendors do not need to be clients to request a briefing. That distinction matters: paying for access is not paying for favourable coverage.

Forrester likewise distinguishes client inquiry from vendor briefing and from other forms of analyst guidance. Do not assume one type of conversation entitles you to everything you might want from another.

The practical test is simple: can the person approving the budget explain what is being bought without using the words “influence”, “visibility” or “better ranking”? If not, the business case needs another look.

3. When the account executive’s email arrives

The account executive’s job is to sell something useful to your organisation. Your job is to establish whether the offer answers a real need. Neither side benefits from pretending a vague ambition is a qualified requirement.

Do not begin with “What discount can you offer?” Begin with the work.

We are reviewing research access against three decisions we need to make this year: [decisions]. Our knowledge gaps are [questions]. The people who need to use the service are [roles]. Please show us the relevant coverage and expertise, explain which proposed entitlements address these questions, and identify what would fall outside the agreement.

Ask for a demonstration around one of your actual questions. Where a full answer requires paid access, ask for enough permitted sample material or a coverage discussion to assess fit. You are evaluating the service, not requesting a free consulting engagement.

Then ask what the offer does not cover. Limits are useful information. An account team that helps distinguish relevant access from attractive but unnecessary additions is helping you buy well.

A deadline, promotional offer or renewal discount is not evidence of need. Equally, the existence of a sales process is not evidence that the research lacks value. Keep the conversation commercial, specific and professional.

4. Choose the knowledge you need

The best-known firm is not automatically the best fit for every question. Nor does a specialist automatically have the depth you need because its positioning sounds precise.

Look at the relationship between your question and the actual coverage: buyer population, market definition, geography, company size, technology area and stage of adoption.

A broad view of a large enterprise market may be valuable for one decision and insufficient for another. A specialist may offer depth in a particular segment while leaving other questions unanswered. The point is to understand the trade-off before buying.

Ask how the research was developed. How current is it? What population does it describe? What are the limitations? Does it distinguish observed behaviour from forecasts or interpretation? Can you discuss where it does and does not apply to your business?

Research does not become relevant simply because your product category appears in its title.

If you are considering several subscriptions, give each a distinct job. One might address a broad strategic question, another a specialist operational question. If you cannot explain what each adds, investigate overlap before expanding the budget.

And remember the alternatives. Customer interviews, win–loss analysis, operational data, public research and specialist advice may answer parts of the problem. A subscription should complement those sources, not make them disappear.

5. Check what your team can actually use

A good match on subject matter can still become a poor purchase if the people doing the work cannot use the service as intended.

Before signing, confirm the proposed agreement in writing. Useful questions include:

Who holds the licences, and what can each person access?
Who can request analyst conversations, and who may attend?
Which topics, specialists, tools and data are included?
What preparation, document review or feedback is available—and what requires a different service?
How are conversations scheduled, and what availability should you plan around?
What can be shared internally or used externally?
What are the terms for renewal, cancellation and changes in users or scope?

Do not treat a colleague’s experience with another package as proof of your entitlements. Product names, access models and contractual terms can differ.

Check the applicable rules before recording, transcribing, circulating research or putting licensed material into an AI tool. A paid login is not permission for every downstream use.

This is also where the budget owner and the working team need to meet. Procurement may negotiate the agreement, but somebody must own whether the organisation can use it. Buying well and using well are connected responsibilities, not interchangeable ones.

6. Turn an inquiry into a useful conversation

An analyst inquiry should start with a question you are genuinely prepared to learn from.

“Can we show you our latest deck?” is not the same as “What are we misunderstanding about how this buyer makes a decision?” If the purpose is to provide a company update, pursue the appropriate briefing route instead.

For a useful inquiry, send a short context note through the firm’s agreed process. Explain the decision, the uncertainty, the evidence you already have and the question you want to explore. Check that the requested advice fits the service you have bought.

For example:

Market entry: “We are considering this buyer segment. What adoption barriers should we investigate before committing resources?”
Product priorities: “We believe these capabilities are differentiators. What evidence suggests buyers treat them as basic requirements instead?”
Positioning: “Our customers describe the problem this way. How does that compare with the language and priorities you encounter?”
Buying process: “Our opportunities repeatedly stall at this stage. What patterns in this market should we test against our own evidence?”

These are starting points, not promises that every firm or package will answer them. A request for detailed bespoke work may require a different arrangement.

Bring the people entitled to attend who can use the answer. An AR lead can frame and facilitate the discussion, but the product or commercial owner often needs to hear the reasoning directly.

Do not spend most of the available time rehearsing the company story. Give enough context to make the question answerable, then listen. Ask what the view rests on, where it may not apply and what evidence would challenge it.

An uncomfortable answer can be more useful than an encouraging one. The purpose is not to leave feeling validated. It is to leave with a clearer decision.

But how do you distinguish one analyst’s opinion from a pattern your leadership team needs to address? The analyst disagrees with you. That does not make them wrong. explores how to test critical feedback against wider evidence and turn it into action.

7. Get more value by making research part of the work

Access does not create a habit on its own. A subscription can quietly become one person’s login, a folder of unread reports and a renewal reminder.

Give the service a named internal owner. That person does not need to answer everyone’s questions or attend every conversation. They need to make sure relevant users know what is available, understand the rules and have a route to getting help.

Keep a short question backlog linked to real decisions. Revisit it when priorities change. A product planning meeting, market-entry review or sales-learning session may reveal the next useful question more naturally than a separate meeting about “using the subscription”.

Make the mechanics easy: who has access, how to find relevant coverage, how to request a conversation and where to ask about entitlements. Work with the account team on targeted onboarding rather than assuming the original demonstration was enough.

Capture your own decision and next action, while respecting restrictions on research content and analyst attribution. “We will test this assumption with five customer interviews” is operationally more useful than an unassigned page of meeting notes.

AR should help the organisation use external knowledge. It should not become a bottleneck through which every permitted question must pass, or a department measured only by how many calls it arranged.

8. Your first 90 days

The following is a suggested starting rhythm, not a promise about a research firm’s delivery times or a quota for your team.

Days 1–30: establish access and a first question

Confirm users, entitlements and ownership. Identify the first decision worth supporting. Find the relevant research and, where included and appropriate, arrange a focused analyst conversation.

Resolve access friction now. A useful contract that nobody knows how to use is already losing practical value.

Days 31–60: apply and test

Bring the findings into the decision itself. Compare them with customer evidence and internal data. Record what changed, what did not and what remains uncertain.

If the answer is too broad, refine the question. If the relevant expertise is not covered, address the mismatch with the account team. Do not hide a coverage problem behind another generic download.

Days 61–90: review the fit

Check whether the intended users are engaging and whether the service has helped the decisions you named. Separate a lack of internal follow-through from a lack of relevant external knowledge.

The result should be a clearer operating rhythm: which decisions merit research input, who brings the question and how the resulting action is followed through.

9. Measure what changed

Downloads, logins and inquiry counts can reveal whether access is being used. They cannot, by themselves, tell you whether it is useful.

A busy subscription may support poor decisions. A small number of well-targeted conversations may be valuable. Activity is a diagnostic, not the outcome.

Keep a simple decision record:

What question were we trying to answer?
What did the research add or challenge?
What other evidence did we use?
What decision or test followed, and who owns it?
When will we review whether that decision held up?

Look for concrete contributions: a weak market assumption exposed, a product priority reconsidered, an unnecessary initiative stopped, a buyer question investigated properly or a decision made with a better understanding of the risks.

Do not turn every subsequent commercial success into claimed subscription ROI. Deals and business outcomes have multiple causes. Record the research contribution without pretending it proves sole causation.

Not changing direction can also be a valid result—but only if an assumption was genuinely tested. “The analyst agreed with us” is not a sufficiently rigorous value statement.

10. Make renewal a fresh decision

Start the review early enough to respect the agreement’s notice requirements. Do not let a contract date become the first time anyone asks whether the service was useful.

Return to the original decisions. Which were supported? Which remain unresolved? Which new knowledge gaps matter now? Then examine coverage, access, internal adoption and cost together.

Low usage needs diagnosis. Was the expertise irrelevant? Were the wrong people licensed? Did the team lack time? Was the service difficult to access? Or did nobody take responsibility for putting it to work?

Those problems call for different responses. Renewing unchanged is not always sensible. Neither is cancelling something valuable because onboarding failed.

You may choose to renew, narrow the scope, change the users, seek different expertise or stop. Ask a useful counterfactual: if we did not have this subscription next year, which important decisions would be harder to make, and how else would we fill the gap?

Do not renew out of fear that ending a commercial relationship should harm research coverage. Do not cancel simply because an analyst offered an unwelcome view. Neither is a sound way to buy knowledge.

Buy better understanding, not applause

Before buying or renewing, five questions should have clear answers:

What do we need to understand?
Which decision will that understanding support?
Why is this source of expertise a good fit?
Who will use the access and act on what they learn?
How will we tell whether it helped?

A research firm cannot take responsibility for your strategy simply because you have paid its invoice. Your team still has to interpret the evidence, challenge it where necessary and make the decision.

Research and insight are stepping stones. They can help you see the next move, question a weak assumption or avoid a costly mistake. But reading the report is not the same as changing the product, testing the market or improving how your team works.

Start with the goal. Use the research to understand your options. Then assign the work, act on the decision and check what changed. The subscription supports that journey. Your team still has to make it happen.

Put this into practice

Put your research access to work

Already running analyst relations? Kea works alongside your team to connect research questions, analyst engagement and follow-through to the decisions your business needs to make.

Explore AR Support

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