Analyst relations for PMMs: how to brief Gartner, Forrester, and IDC (and actually shift the placement)

Traffic stops on the interstate and the left lane starts moving.

You signal, you get over, and within thirty seconds it stops. The lane you just left is rolling.

That's what analyst relations feels like from inside most companies. Every cycle we're sure the vendors placed above us have something we don't, so we build a bigger deck for the next briefing.

Forty slides. Exec coaching. A dry run on Thursday.

And the placement doesn't move.

The briefing was never the lane. Analysts already know what we sell.

They read the site, they talk to our customers, and they take calls all week from buyers who are evaluating us right now. Thirty-five minutes of feature walkthrough hands them almost nothing they didn't already have.

What they don't have is our read on where the market is going, and what our customers did with the product after the contract was signed.

What we don't have is theirs.

---

Whose relationship this is

In most companies analyst relations sits with communications, and product marketing gets pulled in for the big evaluations.

That arrangement loses the part that matters. Analysts advise buyers who are actively shopping our category. When a CISO or a CFO opens a search, the first call is often to Gartner or Forrester, and what they hear on that call shapes the short list and the language of the RFP.

PMM is the team that knows what those buyers care about, how the product maps to their priorities, and where we stand against the competition. That's the material an analyst relationship runs on.

The flow in the other direction is worth more. Aggregate buyer research. An unfiltered read on how the market sees us against how we see ourselves.

A comms team can gather that. It can't route it to the people who write the messaging and build the roadmap. PMM can.

---

Who's on the other end

The firms aren't interchangeable, and the same deck lands differently at each one.

Gartner's analysts field a heavy volume of client inquiries, which makes them genuinely well-informed and permanently short on time. Be direct, be substantive, skip the warm-up.

Forrester's analysts tend to be thesis-driven. They show up with a point of view and they'd like to argue it.

The best Forrester calls feel like two people who both read the market closely. Bring a narrative instead of a deck.

IDC is strongest on sizing and share tracking, and their analysts run deeply technical.

The review platforms play by rules of their own. Influence there comes down to keeping product data accurate and having enough customers willing to write something.

---

The return half

A briefing runs sixty minutes and the firms don't charge for it, because sitting through briefings is how analysts stay current on their coverage.

Most of those minutes travel one way. Forty slides out, ten minutes of questions at the end, and the questions get answered like a recital.

Call the other direction the return half. It's the stretch of the call where information travels back toward us, and it's the only part most vendors never schedule.

Protect the last fifteen minutes and ask one question. "Based on what you're hearing from buyers in our space, what are we not talking about that we should be?" Asked genuinely, that produces intelligence we can't buy anywhere else.

Three habits earn that question a real answer.

Open with a market point of view instead of a product tour. Analysts think in categories. Where the old approaches break, where the category is heading, what buyers keep getting stuck on.

A well-argued POV invites them in, because they have opinions about every piece of it.

Be plain about where we're weak. They talk to our competitors and our customers, so they already know. "Here's where we lead, here's where we're still building" is rare enough to work as differentiation on its own.

Bring one customer. The state they were in, what changed, and the number attached to it. One real deployment story beats ten feature slides, because an analyst can hand a deployment story to a buyer and can't do anything with a capability claim.

Inquiries are the return half with the meter running. If the company holds an AR contract, there's a budget of hours sitting there, and most teams burn them reactively after a deal has already stalled.

Spend them as research instead. Read our core messaging to an analyst and ask them to respond as a skeptical buyer.

Ask how buyers in our market typically tell us apart from a named competitor, a question they can answer from real advisory calls. Their answer is often nothing like what sales reports.

Then keep the line warm between cycles. One short note per analyst per quarter, covering what changed, one customer proof point, and what we're building next.

It takes twenty minutes to write, and it's the difference between being remembered as a partner and being remembered as the vendor who surfaces when there's something to win.

---

Evaluation season

When a Magic Quadrant, a Wave, or a MarketScape opens in our category, the work changes shape.

The firms publish their research agendas. Watch the calendar, then contact the lead analyst and ask to be included. Obvious, and vendors miss the window every cycle.

The questionnaire matters more than the briefing, because the questionnaire gets scored. PMM should own it. The criteria map onto product capability, customer evidence, and strategy, and nobody in the building understands all three better.

Read what was asked and answer that. Put customer names and outcome data anywhere the criteria allow, because vague answers score badly.

Then brief the analyst without repeating the questionnaire. Assume they've read it.

Make three points instead:

1. Our most differentiating capability, made concrete with a customer
2. Where the roadmap is heading and why that reflects where the market is heading
3. One thing we believe the evaluation criteria may be underweighting

That third point is the one most vendors skip and the one that pays. Either the analyst agrees, which we can build on, or they explain why the weighting is what it is, which teaches us the model.

Send references who can tell a specific story rather than the ones who like us most. "We love this product" is unmemorable. Happiness without specificity gets nothing written down.

When the factual review comes, use it for facts. Revenue figures, customer counts, a capability described inaccurately. Arguing with the placement damages the relationship and almost never changes it.

---

The chip in the glass

A rock hits the windshield and leaves a chip the size of a dime. We drive on it for months without thinking about it. Then one cold morning it runs eight inches across the glass and the whole thing has to come out.

Analyst skepticism is that chip. It arrives as a throwaway line in the last five minutes of a call. "We're not hearing much buyer demand for that yet." "Customers tell us your implementations run long."

It reads like nothing, because in that moment it costs nothing.

But the buyers who called Gartner last quarter are the buyers in our pipeline this quarter, and the questions they asked an analyst come back to us as objections in the spring. Analyst perception is our own market perception, showing up a season early.

So write it down. After every analyst interaction, five bullets. What they said about the category, what they said about our competitors, what skepticism they voiced about us, and which buyer priorities came up without prompting.

Route those to whoever owns positioning, to product, and to enablement. Then read them as a set at the end of the year and look for the repeat. Where analyst perception keeps diverging from how we describe ourselves, that gap is the positioning problem arriving early and for free.

Close that loop and analyst intelligence sharpens the story before it shows up in a lost deal.

The deck was never the lane.

Stop building a bigger one and ask what's up ahead.

---

What to do next

If analyst calls keep ending in polite feedback and flat placement, and nobody on the team can say what the last four analysts actually told us, the problem sits upstream of the briefing.

A Bare Strategy positioning audit pressure-tests the market point of view we carry into those rooms. We start with the debriefs, the last evaluation questionnaire, and the objections coming back from enterprise deals, then find where the story stops holding.

If that's where you are, start here. The first conversation is free.