The Analyst Disagrees with You. That Does Not Make Them Wrong.

Critical analyst feedback can expose a weak claim, a real business problem or a misunderstanding. The value lies in finding out which—and giving the response an owner.

1. Is your leadership ready to learn?

An analyst challenges your positioning. Your first instinct is to explain it again. Before booking another briefing, ask a harder question: what if they understood you—and still disagree?

It is easy to value independent opinion while it confirms the company story. The real test comes when someone questions the product, the price, the competitive advantage or the market you have built your plans around. Suddenly, the expert you wanted to impress becomes the person who “does not understand us”.

Sometimes that criticism is justified. Analysts can work from incomplete information, misunderstand a capability or apply a comparison that does not fit. Sometimes your team is the one working from an outdated view. Your competitor has moved. A feature you call unique has become expected. Your product solves part of the problem, while your sales presentation promises the whole thing.

The title of this article does not mean the analyst is automatically right. It means disagreement is a reason to examine the evidence. Neither the analyst’s reputation nor your founder’s conviction settles the matter.

Before the next external conversation, leadership should agree what would cause it to reconsider a decision. What evidence would challenge the roadmap? What would make us withdraw a competitive claim? Who can authorise a pricing test? If every possible answer leads back to the same plan, you have organised a presentation, not a learning process.

Make it safe to report the uncomfortable version. If the person bringing back criticism is treated as disloyal, the notes will gradually become more flattering. The business will then mistake filtered reporting for market confidence. Ask for the strongest challenge heard, the strongest evidence against it and what remains unresolved.

2. Identify what is actually being challenged

“The briefing went badly” tells you almost nothing. Break the feedback into a claim that can be checked. A conversation may contain several different problems, each requiring a different response.

Your differentiation may have expired. You describe a capability as unique; relevant competitors now offer it. Check current releases, availability and real deployment conditions. The answer may be to change the claim, find a narrower advantage or improve the product. Louder messaging will not restore exclusivity.

Your product may be incomplete for the buyer you are targeting. A successful demonstration does not prove migration, integration, governance, reliability or support at the required scale. Establish whether the objection concerns missing functionality, operational maturity or simply missing evidence.

Your pricing may not fit the value or buying process. “Too expensive” could mean a weak value case, a costly entry point, unpredictable consumption, an unsuitable pricing unit or a genuinely uncompetitive total cost. Those are different diagnoses. Do not jump from one comment to a blanket discount.

Your competitive intelligence may be wrong. A battlecard that says another vendor cannot do something becomes a liability when the buyer has just seen it work. Date and source the claim. Check edition, geography, deployment model and availability before training another salesperson to repeat it.

Your market definition may be convenient rather than useful. You may prefer a category where you look distinctive, while buyers compare you with a platform, a service provider, an internal team or doing nothing. Investigate the actual shortlist and budget owner.

Your customer evidence may not support the ambition. A logo does not establish widespread adoption or measurable value. A pilot does not demonstrate production maturity. A strong result in one segment does not automatically establish fit in another.

Your delivery model may undermine the promise. Buyers may believe the technology works but doubt implementation capacity, partner coverage, support hours or the effort required from their own team. That is not necessarily a positioning problem.

The analyst’s information may be stale or the comparison unsuitable. A recently released capability, a different use case or a misunderstood commercial model can change the discussion. Supply the specific correction. Do not demand a favourable overall judgement because one fact was wrong.

In each case, ask the same question: what exactly would we need to establish before deciding whether to correct the explanation, change the business or hold our position?

3. When the challenge comes during the call

Imagine an analyst interrupts after twenty minutes: “I have not seen evidence for that claim.” This is an illustrative situation, not a quotation from a client engagement. The immediate job is to understand the objection without turning the rest of the meeting into a defence of the presenter.

Where the format permits clarification, ask: “Is the concern that the capability is missing, that our evidence is insufficient, or that it does not distinguish us from the alternatives?” That gives the team something concrete to examine. If the conversation does not allow that exchange, note the uncertainty and use the appropriate follow-up route.

If you cannot substantiate a claim, say so. “We cannot demonstrate that today. We will verify it and send the relevant evidence” is stronger than improvising a customer result or presenting roadmap functionality as available.

Do not let the executive with the strongest reaction become the only person interpreting the exchange. Assign someone to capture the wording, context and evidence requested. Separate the analyst’s actual statement from your team’s interpretation of their tone.

A disrespectful interaction can be addressed through the firm’s appropriate channel. Keep that conduct issue separate from the substantive question. Poor delivery does not make a technical objection false; a prestigious job title does not make an insult useful evidence.

After the call, hold a short debrief before memories converge around the loudest person’s account. What was said? What did we infer? What could we answer? What must we check? Avoid concluding that the analyst “loved it” or “hated it” unless the evidence supports something that specific.

4. Silence is not agreement—and a briefing is not an inquiry

An analyst may ask few questions, offer no opinion or decline a follow-up. None of those observations establishes agreement, rejection or lack of competence. They may reflect the meeting format, research priorities, coverage or available time. Record no expressed view as no expressed view.

Gartner describes vendor briefings as predominantly information flowing from vendor to analyst; feedback is not their purpose. A briefing should therefore not be treated as an entitlement to advice. Forrester also distinguishes briefings from inquiry and advisory services. Check the relevant firm’s current rules and your actual entitlements before designing the conversation.

Even paid access is not an unrestricted feedback channel. The kind of question, the material you want reviewed and the permitted participants can matter. Ask which service is appropriate rather than assuming a subscription gives you a right to a critique of every briefing or a route to improve research scores.

If you only have vendor briefings, you can still run a disciplined learning process. Present verifiable information, capture questions accurately, fulfil requests and send concise corrections through the accepted channel. Request another briefing when you have a material development relevant to that analyst’s coverage. Do not repeatedly request meetings simply to force a response.

Build the rest of the evidence outside that conversation: customer interviews, win–loss work, product testing, public research and current competitor information. You can investigate whether a concern is valid without persuading the original analyst to supervise the investigation.

If a particular knowledge gap justifies paid research or advisory access, evaluate that purchase on its own merits. Do not buy it to obtain approval. And do not assume an external AR partner can lend you restricted access or override a research firm’s rules.

5. What does eight out of twenty actually tell you?

Suppose you speak with twenty analysts and eight raise the same concern. Forty per cent sounds substantial. It is also easy to misuse.

The statement you can initially defend is: eight of these twenty analysts raised this concern during the recorded period. You cannot turn that into “40% of the market believes this”, or “the other 60% disagree”. Analysts were selected for a purpose, not randomly sampled from a defined population of buyers. Their coverage, exposure and opportunities to comment differ.

Before interpreting the count, ask how many covered the relevant question. How many saw the current product and comparable evidence? How many were explicitly asked, where appropriate? How many raised the issue spontaneously? How many had no opportunity to express a view?

Consider an illustrative breakdown. Twenty analysts were engaged. Twelve covered the relevant use case and received the current evidence. Eight of those twelve raised a concern; two explicitly offered a contrary view; two expressed no view. The other eight were outside that specific comparison.

Report the whole breakdown. Eight of twelve relevant conversations deserves attention, but it is still not a population estimate. Nor should you quietly remove analysts from the denominator after discovering that their opinions are inconvenient. Define relevance in advance and record any later change with a reason.

Do not attach a conventional survey margin of error to a purposively selected set of briefing conversations. More decimal places, a confidence interval or a significance test cannot repair an unsuitable sampling design. The useful discipline here is transparent observation and structured judgement, not a statistical costume.

There is no universal number of analyst calls that makes feedback actionable. Twenty poorly matched conversations can teach you less than a small number of relevant, well-evidenced ones. Equally, one prominent analyst is not a substitute for checking the broader picture.

6. Count independent evidence, not echoes

Eight similar comments are not necessarily eight independent discoveries. Several analysts may draw on the same research, speak with the same customers or repeat a widely circulated claim. Repeated calls with one analyst show persistence or change in that person’s view; they do not add new independent observers.

Keep both counts where useful: distinct people raising the concern and distinct underlying evidence sources you can identify. Do not pretend to know sources that cannot be disclosed. Mark independence as uncertain where it is uncertain.

Repetition can still matter commercially even when it is not independent proof. A claim circulating widely may affect buyer expectations. That makes it a perception issue to investigate, while leaving the truth of the claim unresolved.

Question wording also changes what you hear. “Would you agree our pricing is competitive?” encourages a different conversation from “Under what conditions would a buyer reject this pricing model?” Where feedback is permitted, use neutral questions and preserve enough consistency to compare answers.

Do not collapse different objections into a convenient theme. “Entry price is high”, “usage is unpredictable” and “implementation is expensive” all concern money, but they point to different interventions. Keep the original wording alongside any category you assign.

Have a second reader check important or ambiguous classifications. Record whether a statement was direct, paraphrased or reported second-hand. If automated tools help summarise notes, verify the output against the source and respect recording, confidentiality and licensed-content restrictions. A confident summary can still remove the qualification that mattered.

7. Decide whether to act, investigate or monitor

Frequency is only one input. Assess the relevance of the source, specificity of the claim, quality and independence of the evidence, commercial consequences, urgency and reversibility of the response. These are decision questions, not a formula that produces an objective truth score.

Act immediately on a verified error. If your team establishes that a sales slide makes a false capability claim, withdraw or correct it. You do not need eight analysts to confirm your own documentation. Similarly, a credible report of a serious product risk may justify urgent verification or temporary containment before prevalence is known.

Investigate a credible, material concern. A specialist raises a specific adoption barrier, or several relevant sources identify the same gap. Assign an owner, define competing explanations and gather evidence before making an expensive, hard-to-reverse change.

Run a limited test where the uncertainty is meaningful. Pricing comprehension, messaging or a sales qualification question can sometimes be tested in a bounded way. Decide beforehand what result would justify broader action and what would stop the test.

Monitor a plausible but weakly supported observation. Keep it in view with a review date or trigger. “Not enough evidence yet” should lead to an explicit next step, not indefinite storage.

Keep context without creating work. An interesting observation outside your target segment may be useful background. Unless it affects a decision, assumption or risk you own, it does not need to become a project.

Something becomes fascinating when it exposes an unexpected pattern or contradicts a comfortable assumption. It becomes valuable when resolving it could change a decision. It becomes urgent when delay has material consequences. Those are different thresholds.

Before collecting more evidence, ask what it might change. If every plausible finding leads to the same small, reversible correction, make the correction. If the choice involves a major product investment, gather enough evidence to compare the options properly. Research has a cost too.

8. Benchmark against the alternatives buyers actually have

Internal ambition needs an external reference point. “We are ahead” is incomplete until you say ahead of whom, for which customer, on what dimension and as of what date.

Start with the alternatives buyers genuinely consider. That may include a competing product, an incumbent platform, a services-led approach, an internal build or retaining the current process. A comparison that omits the buyer’s preferred alternative can make a weak proposition look strong.

Compare equivalent conditions: product edition, deployment model, maturity, geography, customer size and use case. Distinguish general availability from a demonstration, private preview or roadmap. Separate a technical feature from the outcome and operational effort associated with using it.

Use public documentation, appropriately licensed research, legitimate evaluations and permissioned customer evidence. Date the comparison and mark unverified claims as unknown. A competitor’s marketing statement is a claim to assess, not automatic proof; the same standard applies to your own.

On pricing, compare a realistic total scenario rather than whichever unit price favours you. Include implementation, required add-ons, usage assumptions and customer effort where relevant. Avoid publishing conclusions your evidence cannot support.

Product should own capability accuracy; product marketing should own the competitive narrative; sales enablement should retire outdated guidance. Give each important claim a review trigger. A release, changed commercial model or repeated customer challenge should reopen the comparison.

The result may be uncomfortable: your advantage exists only in a narrow segment. That can still be a useful position. An honest, defensible fit is more useful to sales than a universal leadership claim buyers can dismantle.

9. Bring analyst feedback together with business evidence

Analyst feedback becomes more useful when examined alongside evidence collected for different reasons. Ask whether customers, lost deals, product behaviour and market research support the same explanation—or point elsewhere.

If analysts question implementation effort, inspect actual deployments. Look at time to value, customer resources required, escalations and differences between successful and troubled projects. A handful of showcase customers should not stand in for the whole installed base.

If pricing is challenged, examine where deals stall, the reasons buyers give, discount patterns and the alternatives considered. A salesperson’s “we lost on price” is an interpretation until the buyer evidence supports it. A weak product fit may surface as a price objection.

If the concern is product maturity, compare the claim with real usage, support patterns and the requirements of the target segment. If the concern is positioning, check whether buyers misunderstand the offer or understand it and prefer something else.

Do not count one source several times. A research note, a sales anecdote quoting that note and a slide quoting the sales anecdote are not three independent confirmations. Trace evidence back as far as practicable.

Seek contrary evidence deliberately. Which relevant customer succeeded without the supposed missing feature? Under what conditions? Does that narrow the concern rather than invalidate it? The objective is a better explanation, not a larger pile of supporting quotes.

When sources disagree, preserve the disagreement. It may reveal different segments, stages of adoption or product versions. An average sentiment score can hide the exact distinction your strategy needs.

10. Keep notes that can support a decision

A useful record connects the observation to its context and next action. It should be concise enough to maintain and specific enough for somebody who missed the call to challenge your interpretation.

• Observation: the exact wording where available, or a clearly labelled paraphrase.
• Context: date, analyst remit, interaction type, question asked and product evidence presented.
• Scope: buyer segment, use case, geography, version and time period.
• Evidence: what supports the statement, what contradicts it and what remains unknown.
• Interpretation: your hypothesis, kept separate from what the analyst actually said.
• Decision: the business consequence, accountable owner, next test and review date.

Use a stable set of themes, but allow exceptions. Otherwise every unfamiliar issue gets forced into the nearest existing category. Keep identifiers so that repeated discussions can be linked without double-counting them.

Where a feedback conversation is appropriate, useful questions include: “Which buyer situation does this apply to?” “What is the comparison?” “What would demonstrate that this concern has been addressed?” and “What alternative explanation should we test?” Do not request confidential customer details or assume the analyst can disclose everything behind a view.

Follow the applicable rules for notes, attribution and sharing. Store internal decisions in a form the responsible team can use without circulating restricted research or implying permission to quote an analyst publicly.

The quality test is whether the record helps somebody decide what to do. A transcript nobody reads is not a feedback system. Neither is a colour-coded dashboard whose labels cannot be traced to evidence.

11. Make the response somebody’s responsibility

AR should coordinate interpretation and follow-through. It cannot personally fix every problem the process uncovers. A product gap belongs with product leadership. An inaccurate battlecard belongs with product marketing and sales enablement. A pricing issue needs the commercial owner and the people responsible for the economics.

For each material issue, appoint one accountable decision owner. Name the people contributing evidence, the decision required, the deadline and the person maintaining the external communication. “The leadership team” is not a sufficiently precise owner.

Keep the decision short: here is the claim; here is what we know; here is the counter-evidence; here are the options; here is the recommended next step. Record the remaining uncertainty and what would cause the decision to be revisited.

Leadership must also decide what to stop. If the evidence undermines a competitive claim, remove it from sales materials. If a segment requires capabilities you cannot provide, change qualification or revisit the investment. Adding another meeting while leaving the old guidance in circulation is not a response.

When the evidence supports holding your position, document why. You may serve a different segment, accept a deliberate trade-off or have stronger proof than the criticism acknowledges. Openness to challenge does not require abandoning a sound strategy.

Tell the people doing the work what changed and why. Do not reduce the explanation to “Gartner told us to” or “the analyst wants it”. The business owns the decision and should be able to defend it on the underlying evidence.

12. A worked example: from criticism to a useful test

Consider a hypothetical technology vendor that claims rapid enterprise deployment. Several relevant analysts question that claim. Leadership initially assumes the story needs a better presentation.

The team separates three hypotheses: analysts have outdated information; the evidence is too narrow; or deployment genuinely becomes difficult in larger environments. It checks which observers saw the current product and what each meant by “enterprise”.

Product and customer success then examine comparable projects rather than choosing the fastest examples. They find that the claim holds for a constrained deployment but has not been demonstrated consistently where customers need multiple integrations. Sales has been using the broad claim in both situations.

The immediate action is to narrow the sales claim and clarify qualification. The larger decision is whether to invest in the integration work needed to serve the more demanding use case. That requires commercial and product evidence, not another vote among analysts.

The team defines a test: document the required conditions, evaluate comparable deployments and assess whether the proposed changes reduce the problem. Product owns the capability work, customer success owns deployment evidence, sales enablement owns the guidance and AR coordinates an accurate update.

If the test fails, the next step is not to relabel it as a messaging success. Revisit the product or target segment. If it succeeds, communicate what is now demonstrable, including the conditions. A changed slide is not proof that delivery improved.

This is what a useful learning cycle looks like: an external challenge exposed an assumption, internal evidence narrowed the problem and named owners changed the work. It does not require a public argument about who was right.

13. Close the loop without demanding a changed opinion

There are two loops to close. Internally, verify that the action happened and whether it addressed the issue. Externally, provide relevant new evidence through an appropriate channel when there is something material to report.

A useful update is specific: “Our previous claim did not distinguish these two deployment scenarios. We have corrected it. Here is the current capability, the supporting evidence and the limitation that remains.” Keep it proportionate and respect what can be shared.

The analyst may retain their judgement, need more evidence or have no immediate reason to respond. Do not record a sent email as acceptance. Record evidence supplied, response received if any, and what remains unverified.

If published research contains a factual error, identify the exact passage and submit the relevant evidence through the firm’s current correction or review process. Check deadlines and applicable procedures. A disagreement over judgement is not automatically a factual correction.

Escalate a substantiated issue professionally when the normal route has not resolved it. Keep the evidence, correspondence and requested remedy precise. Commercial spend is not a reason the research should change, and an account relationship is not a licence to pressure an analyst into a favourable view.

Measure more than the number of calls. Track material issues with owners, unresolved evidence gaps, overdue tests, outdated claims withdrawn and verified changes in the business. Distinguish a changed analyst view from improved customer outcomes; neither automatically proves the other.

A decline in objections can also mislead. Did the issue improve, or did you stop speaking to the people who raised it? Keep the comparison population and scope visible. Silence is still silence.

14. What Kea adds—and what leadership still has to do

You can run this process internally. You need relevant analyst coverage, careful preparation, accurate notes, credible competitive work and someone with enough authority to bring difficult findings into the decision process. The challenge is sustaining all of that while the same people are delivering the product, supporting sales and defending the quarterly plan.

Kea’s role is to help make that work coherent. We help frame the questions, prepare the evidence, interpret what was actually said and connect feedback with the wider programme. We help distinguish a communication gap from a business gap and turn an uncomfortable discussion into a clear next step.

That includes challenging the internal explanation. If the product proof is weak, our value is not to find a more flattering way to describe it. If the analyst has missed an important fact, our value is to help present that fact clearly. If the evidence is mixed, we should make the uncertainty visible rather than sell certainty the record does not support.

For an existing AR team, that is where focused AR Support fits: additional senior judgement, preparation and practical follow-through alongside the people who own the programme. Where leadership first needs to agree what it is prepared to test, a workshop can help establish that starting point.

Kea cannot guarantee a favourable opinion, compel a research response or make product decisions on leadership’s behalf. What we can help build is a more disciplined connection between external insight and internal action.

Before your next round of conversations, ask your management team three questions: what could we be wrong about; what evidence would change our minds; and who will act if that evidence arrives?

The analyst may be wrong. Your team may be wrong. The useful organisation is the one prepared to find out—and then do something with the answer.

Put this into practice

Turn difficult feedback into a decision your team can act on.

Kea helps your AR team assess the evidence, challenge assumptions and coordinate practical follow-through with leadership, product and sales.

Explore AR Support ↗

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

Share this article

LinkedInXEmailCopy link

Not receiving The Kea Signal yourself? Explore the publication and subscribe →