“The analyst is blocking the deal.” Verify the claim first.

When a salesperson says an analyst is blocking an opportunity, the immediate task is to understand the buyer's concern. Escalating an incomplete account can waste time and leave the actual obstacle untouched.

Several different situations can arrive under the same label. A buyer may have read an older report. An analyst may have raised a limitation that matters to this particular deployment. A competitor may have paraphrased research. The sales team may have heard only part of the conversation.

Each requires a different response. Start by establishing what is known.

Capture the concern accurately

Ask the account team for the buyer's question in the buyer's words, where available. Record whether the source is a published report, direct advice or a second-hand account. Include the date, product or use case concerned, and the decision the buyer is trying to make.

Do not turn a paraphrase into a quotation. If the original wording is unavailable, retain that uncertainty. Ask only for information the buyer is comfortable and permitted to share; a useful response does not require access to their confidential advisory conversation.

Establish the decision and the deadline

Ask what the buyer needs to decide next and when. Are they excluding the product from a shortlist, checking one deployment requirement or seeking reassurance before approval? The response should address that decision. A broad defence of the company can miss a narrow but decisive question.

Agree one response owner with the account team. Product may need to verify a capability and AR may need to review the research context, but sales should know who will bring those inputs together. Set a realistic next update even when a complete answer is not yet available.

Keep these details in one short account note, alongside the evidence checked and anything still unknown. A missing product version or an unclear buyer requirement should remain visible until someone resolves it.

Test the concern against the evidence

Check the product version, deployment context and relevant limitations. Then decide which kind of problem you have.

• A factual error: assemble current evidence and check the appropriate correction route.
• Missing context: explain the relevant use case, operating conditions and limits.
• A capability gap: involve product and the account team, and state accurately what is available.
• An unclear second-hand account: ask a focused clarification question before drawing a conclusion.

An unfavourable assessment is not necessarily an error. A capability may exist but still be unsuitable for the buyer's requirements. A roadmap item may address the gap later without solving the current decision.

Give sales something usable

The account team needs a concise response it can stand behind. State the concern, what the evidence establishes, what remains unresolved and who owns the next step. Include supporting material that is appropriate to share.

For example, if the concern is deployment location, a generic company presentation is unlikely to help. A precise description of supported locations, architecture and any restrictions is more useful. If those restrictions rule out the requested deployment, say so internally before promising an answer to the buyer.

Keep any discussion with the analyst factual and proportionate. Verify the relevant firm's current process before seeking a correction or review. Do not promise sales that an opinion will change.

Recognise when the buyer is right

In an illustrative situation, a buyer says an analyst warned that a platform cannot run in the buyer's required environment. The vendor's broad deployment slide appears to contradict that warning. A technical check then shows that the product runs in the environment, but a required management component does not.

The response needs to describe that limitation. Calling the analyst misinformed would distract from the buyer's actual requirement. If a supported alternative exists, explain its trade-offs; if none exists, let the account team make an informed commercial decision.

If the same check instead establishes full support in a current release, provide dated documentation and clarify the version involved. Similar opening complaints can lead to very different actions once the evidence is clear.

Close the loop

Record whether the buyer's question was answered and whether the opportunity progressed. Those are separate outcomes. Feed recurring concerns back into the product story, customer evidence and analyst engagement plan.

A simple intake note is enough to begin: buyer concern; source and date; confidence in the account; relevant use case; current evidence; unresolved gap; owner; next action. That creates a better basis for action than the phrase “the analyst is blocking us”.

Share this article