You’re Wasting Your Analyst Inquiries
A vendor called me for an inquiry. I was a few years into my time as an analyst, covering middleware. The call was scheduled for 45 minutes.
We spent 43 minutes reviewing their slides.
At minute 44, they asked me if I had any questions. I had struggled to get a word in. At the end, they thanked me, and we hung up. I could hear in their voices that they thought it had gone well.
It hadn’t. And I don’t think they understood what they’d missed: an opportunity to learn what buyers were hearing, where competitors were winning, and how their market was changing.
I’ve been on both sides of this table now — with 15 years as an analyst, and years since working with B2B tech companies on their AR programs. And the thing I see most consistently on the vendor side is this: most product and marketing teams treat a briefing, an inquiry, and a conversation as variations on the same activity. They’re not. They are three fundamentally different things, and confusing them means you spend time with analysts without getting the thing you actually need from the interaction.
A briefing is where you deliver evidence.
In a briefing, the analyst is listening. They are forming a view. At Gartner especially, analysts are trained not to give you substantive feedback in a briefing — that’s not what the briefing is for. They are evaluating your position in the market based on what you show them. So what they need from you is clarity: where you play, who you serve, what differentiates you, and what proof you have.
A bad briefing is a product pitch deck. It leaves the analyst no clearer on where you fit than when they started. A good briefing is organized, specific, and honest about your limitations. It gives the analyst the material they need to place you accurately.
The briefing is not where the relationship is built. It’s where evidence is delivered.
Image Credit: AllGo on Unsplash
An inquiry is different in kind, not just format.
Unlike briefings, an inquiry is NDA-protected. It is your time to ask questions — and the analyst, freed from the constraints of a public conversation, will actually tell you things. What they’re hearing from buyers. Where your narrative is landing and where it isn’t. Which competitor claims are gaining traction. Which market assumptions no longer hold. These are inputs into positioning, messaging, roadmap prioritization, and go-to-market strategy — not just AR activity.
But here’s what most product and marketing teams miss: the quality of what you get back is entirely determined by the quality of the questions you ask.
A vague question gets a polished, safe answer. “What do you think of our go-to-market?” is not a question — it’s an invitation for the analyst to give you a generic response that costs them nothing. A real question has specificity and stakes: “We’ve been positioning around operational efficiency, but we’re losing deals to Vendor X who leads on scalability — are you hearing that same tradeoff from buyers, and do you think it’s real or manufactured?” That question forces a real answer.
The vendor on that 45-minute call asked me one question and it was the vague kind. I answered it politely and completely. I didn’t lie to them, but they spent most of their inquiry presenting information they already had. They used very little of the time to learn information only I had.
They walked away thinking the inquiry was fine. They never found out what they missed.
A conversation is what you’re building toward.
A conversation is where analyst interactions become strategically valuable. This is when analysts stop simply evaluating your company and start helping you understand your market. It is what happens when genuine trust exists — when the analyst believes you will actually listen, and you know the analyst will actually push back. A conversation is the thing where both sides leave knowing something they didn’t know when they got on the call.
This doesn’t happen on a first inquiry. It happens over time, through consistent engagement, through showing analysts that when they tell you something, you do something with it. When you come back six months later and say “you told us our enterprise narrative was weak, so we changed it — here’s how” — that’s when the relationship shifts. When they tell you that you were the first vendor to make a key point, you know you influenced them.
The analyst who covers your category has a vantage point no product team, no marketing team, and no competitive intelligence function can fully replicate. They sit at the intersection of dozens of vendors, buyers, investors, and market shifts. The question isn’t whether that perspective exists. The question is whether you’ve built the kind of relationship that gives you access to it.
Look at your last three inquiries.
Did you learn something you didn’t know before? And did that insight change a decision?
If not, the questions were wrong. Not the analyst.
This is the work I do with companies now — not because the vendor side does this badly out of laziness, but because they don’t have someone internally who is thinking about the other side of the call. They’ve never experienced what it’s like to receive a briefing that’s really a pitch, or to answer an inquiry question that had no edge to it. They don’t know what they’re missing because they’ve never felt the absence of it.
I have been there. And it changes everything about how you prepare.
