Kea Insight / Analyst Relations
What Are Analysts Saying About You When You Are Not in the Room?
You can see what an analyst publishes. You cannot see every conversation they have with buyers.
That creates one of the hardest measurement problems in Analyst Relations. A vendor may run good briefings, answer every request and receive positive feedback, yet still not know how relevant analysts would describe the company when a buyer asks about the market. The answer may be accurate, incomplete, outdated or based on a different competitive frame from the one the company uses internally.
If you are asking how long it takes to change analyst perception, there is no fixed timetable. First establish the baseline, then repeat the measurement against the same strategic question and the evidence you have put into the market.
The wrong response is to guess. The useful response is to test analyst understanding systematically, using a repeatable perception-audit process that separates what an analyst actually says from what the company hopes, fears or infers.
Why the invisible conversation matters
Industry analysts influence markets through more than published research. Advisory conversations, inquiries, events, evaluation work, speeches and informal market discussions can all contribute to how buyers understand categories and vendors. Some of those interactions are deliberately confidential.
Gartner, for example, describes Inquiry as a confidential client conversation and limits participation and sharing according to the client’s entitlement. Forrester likewise separates client Inquiry from vendor briefings and restricts how inquiry sessions may be used. Those rules matter because AR should never try to reconstruct or extract confidential client conversations. The question is not “what exactly did you tell Company X?” It is “what do you currently understand about us, and how would you place us in the market?”
That difference keeps the work ethical and useful. A perception audit tests the analyst’s own understanding. It does not ask them to disclose another client’s advice, breach confidentiality or replay a private conversation.
What an analyst perception audit is
An analyst perception audit is a structured way to test how a defined set of relevant analysts understand the company, its market position and the evidence behind its claims. It uses comparable questions across interviews so the AR team can identify patterns, disagreements and information gaps without pretending the sample represents the entire market.
The idea is not new. Earlier AR practice developed a structured “spoken word audit” approach to compare published views with what analysts say verbally and to repeat the exercise over time. The mechanics need updating for current analyst-firm access rules, but the core discipline remains valuable: use consistent questions, capture the answers accurately, and measure whether understanding changes.
Kea’s version is deliberately narrower. We do not treat analysts as a survey sample of all buyers, and we do not use paid inquiry access as a disguised vendor briefing. We test the understanding of analysts who are already relevant to the programme, through interaction routes that are appropriate to the firm and the relationship.
How to design the audit
Start with one business question. “What do analysts think of us?” is too broad. A stronger question might be whether analysts understand the company as an enterprise-grade provider, whether they place it in the intended category, whether they recognise a change in customer profile, or whether they believe a particular differentiator is supported by evidence.
Then select the analysts based on relevance rather than convenience. The set should reflect the people whose coverage, research, advisory role or buyer audience matters to the issue being tested. A large number of loosely relevant analysts produces more data and less insight.
Define the baseline before the conversations begin. Record the company’s own current hypothesis: what it believes analysts understand, what evidence should support that understanding and where uncertainty remains. This gives the team something concrete to test rather than a vague desire for reassurance.
Use the same core questions across the audit, but allow follow-up where the analyst raises something important. The structure creates comparability; the follow-up creates understanding.
What to ask
The strongest questions are neutral enough that the analyst can disagree with the company’s preferred story. They should also be specific enough to produce an answer the business can act on.
- Category: When you think about this market, where would you place us today?
- Buyer problem: Which customer problem do you associate most strongly with us?
- Competitive frame: Which providers or approaches would you expect a buyer to compare with us?
- Strength: What do you believe we do particularly well, and what evidence supports that view?
- Risk: What would make you cautious about us in a buyer conversation?
- Change: What has materially changed in your view of the company during the last year?
- Evidence gap: What would you need to see to become more confident in an important claim we make?
Do not turn the interview into a correction session. If the analyst gives an answer the company dislikes, capture it first. Clarification can follow where a factual error exists, but the audit loses value if every uncomfortable answer becomes an argument.
The same principle applies to positive feedback. “Strong enterprise traction” means little unless the team understands what the analyst has actually seen. Ask which customers, deployments, product capabilities or market signals created that impression.
How to interpret the answers
Separate four things in the analysis: factual understanding, market interpretation, individual opinion and evidence quality. They require different actions.
A factual misunderstanding may need a correction supported by current documentation. A market interpretation may reveal that the company is using category language buyers do not recognise. An individual opinion may remain just that until other evidence supports it. A weak evidence base may show that the company has made a claim repeatedly without giving analysts enough proof to assess it.
Do not convert a small purposive set of analysts into fake market statistics. If six of ten relevant analysts associate the company with one use case, the defensible statement is that six of those ten analysts did so in the audit. It is not evidence that 60% of the market believes the same thing.
Look instead for repeated patterns with practical consequences. Are several analysts using the wrong competitive set? Are they consistently uncertain about enterprise deployment? Do they understand the technology but not the business problem? Does the same customer proof strengthen one claim but leave another unsupported?
That is where the audit becomes useful. It creates an evidence backlog: what needs correction, what needs stronger proof, what needs a different market explanation and what the company may need to change rather than merely communicate better.
How long does it take to change analyst perception?
A perception audit becomes more valuable when it is repeated against the same strategic question. The objective is not to force every analyst towards the same positive answer. It is to see whether the company is becoming easier to understand accurately.
Keep the comparison disciplined. Use the same core questions, document changes in the analyst set and preserve the context behind each answer. If an analyst’s coverage changes, record it. If the product has materially changed, acknowledge that the second audit is testing a different business reality.
Track movement in categories that matter to the programme: accuracy of category placement, recognition of customer evidence, understanding of differentiation, recurring concerns and the number of important claims that analysts can substantiate independently.
Then connect the movement to activity cautiously. A series of briefings, customer references and product updates may have contributed to a change in understanding. That does not prove that one specific interaction caused it. The useful management question is whether the programme’s combined work is producing a better-informed analyst community.
What the method cannot tell you
A perception audit cannot tell you exactly what an analyst said in a confidential client inquiry. It cannot prove what every buyer believes, and it cannot turn analyst opinion into objective product truth. It also cannot guarantee that improved understanding will produce favourable research or commercial outcomes.
It can do something more practical: reduce the gap between the story the company thinks it has told and the story relevant analysts can actually explain back.
That is a stronger measure than meeting counts. A programme may have completed twenty briefings and still left analysts uncertain about the category, customer evidence or enterprise fit. Another programme may have fewer interactions but a much clearer external understanding of the business.
The question AR should be able to answer is therefore not only “who did we speak to?” It is “what do the people who matter understand now, what evidence supports that understanding, and what still needs to change?”
That is how perception work becomes a management tool rather than a popularity exercise.
Current-policy references: Gartner’s public Vendor Briefings guidance distinguishes briefings from analyst feedback, while its Inquiry Usage Policy describes client inquiry as a restricted service. Forrester similarly distinguishes vendor briefings from client inquiry. The structured-audit concept also draws on earlier AR practice; current firm rules take precedence.
Put this into practice
Find out what relevant analysts actually understand.
Kea can structure perception work around the analysts, questions and evidence that matter to your market, then turn the findings into clear actions.
Explore AR SupportNot sure where to start? Take the eight-question AR Readiness Check.