Skip to content
← All insights

Kea Insight / Analyst Relations

Your First Analyst Evaluation Is Out. Now What?

The evaluation lands. Your company is included, but the position disappoints. By the afternoon, sales wants a line for prospects, marketing wants to announce the result and leadership wants to know what it would take to move. AR has a more immediate job: establish what the report actually says before the company decides what to say about it.

Inclusion puts a company into a defined comparison. It is neither an award nor a promise of buyer interest. The opportunity is to learn what the assessment tells buyers about your fit—and whether that is the market you intended to serve.

First, decide whether this is the market you need to win

Start with the market definition and inclusion criteria. If the report addresses buying decisions that matter to your customers, its findings deserve serious attention. If it covers a broader proposition, a low position may describe your limited fit within that category accurately. Chasing a better position then risks pulling the product away from the buyers you serve.

Read the written assessment before preparing a public response. A deliberate product focus may explain a caution about breadth; weak customer evidence or delivery may expose a real constraint in the market you do want to win. The graphic cannot tell you which problem you have.

Separate errors, evidence gaps and business choices

We have seen the same mistake in evaluation debriefs: a company disputes its position before distinguishing a false statement from an unproven capability or an accurate limitation. Each calls for a different response.

Consider an illustrative platform that governs software artefacts but uses specialist security scanners. “No native scanner” may be an accurate caution. “Cannot act on scanner findings” would be an error if a working demonstration shows otherwise. If the integration exists but the company offered no customer proof, that is an evidence gap. And if buyers in this market require native scanning, leadership must decide whether to build it or accept that the evaluation covers a broader proposition than its own.

Those responses are not interchangeable. Check the research firm’s review stage and rules before asking for a factual correction; publication is not a fresh opportunity to renegotiate scores or criteria. Supply missing proof in the appropriate next conversation when a real capability was not established. Treat an accurate caution as a business choice, not a communications problem. A future roadmap is not evidence of a current capability, and no briefing can turn it into one.

Give buyers an answer they can trust

Sales teams will be asked about the result, often before they have read the report. Give them an answer they can use without rewriting the analyst’s conclusion. In the illustrative example, that might be: “The report is right that we do not provide a native scanner. We govern artefacts and use findings from specialist scanners; here is how customers operate that model. If native scanning in the same product is essential, we may not be your best fit.” The actual answer must follow the published assessment and customer evidence. Using research, graphics or quotations in marketing is a separate question governed by the firm’s permissions; inclusion itself is not an endorsement.

Turn the report into a work programme

Build a decision record against the assessment. For each material finding, record the exact claim, whether it is an error, evidence gap or accurate limitation, the buyers affected, the owner and the proof or product decision needed. Product owns capability choices. Customer teams identify shareable evidence. Sales tests the explanation in live opportunities. AR maintains the research history, uses the firm’s correction route where applicable and returns with substantive updates when there is something new to show.

Only then decide whether to announce the result, and to whom. Leadership should know which buyers use the report, which findings affect their decisions and who owns the response. A stronger position in a later evaluation may follow from the work, but it is not the work itself.

How Kea helps

Kea helps clients decide which evaluations belong on their research agenda before the process begins. When a report arrives, we compare its findings with the evidence submitted, what analysts said during the process and the buyers the company needs to reach. We organise the factual review and follow-up permitted by the firm, then work with product, sales and leadership on the choices only they can make. The objective is a defensible response and a better-informed next conversation, not a promise to change an independent analyst’s judgement.

For the mechanics behind specific formats, read our guides to Gartner Magic Quadrants and Forrester Waves. For the rules on using a published result in your own materials, see how to use analyst research without claiming an endorsement.

Put this into practice

Make the evaluation useful to your business.

Kea connects the findings to your market priorities, evidence and analyst history, then helps coordinate the decisions and follow-up.

Explore AR-as-a-Service

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

Share this article

LinkedInXEmail
Derk Erbé

About the author

Derk Erbé

Derk Erbé is Co-Founder and Managing Partner at Kea Analyst Relations. His career spans Analyst Relations, industry research, management consulting, business strategy and transformation. He advises technology companies on how to build market understanding and turn analyst engagement into practical business value.