Gartner Blog Network


The One Thing to Always Do When Mentioned in Analyst Research

by Hank Barnes  |  January 16, 2018  |  1 Comment

A primary goal of most, if not all, analyst relations programs is to get products, services, and/or companies mentioned, or featured, in analyst reports.  Whether it is a use case example to reinforce a point or in a report like Gartner Magic Quadrants (and similar  style reports from other firms) that evaluates companies and technologies, a mention is a measurable result of an AR program.

But what is the most important thing to do when mentioned, particularly prominently?

Source: pexels.com

Source: pexels.com

 

(Hint: It’s not “license a reprint.”)

 

The answer:  Sales Enablement.

When you are mentioned by a prominent analyst firm, it is likely that clients and prospects will ask you about it.  But they aren’t asking the AR team or the product team.  They are asking the sales team.   Make sure they are prepared. (As an aside, this applies to any article that you are mentioned in prominently, not just analyst reports.)

How do you do this?  Here are a few ideas:

  1. Develop the foundation (while following any of the relevant rules/guidelines from the analyst firm):
    1. Explain the context of the mention
    2. Provide the company perspective (what you agree with and what you don’t agree with.
    3. Share other insights from the research (could be on competitors or other scenarios)
  2. Share throughout the company, but focus on customer facing employees, particularly sales.  Use multiple communications strategies (e-mails, internal Webinars, intranets) to make sure the message is heard.
  3. Supplement with additional guidelines
    1. Situations to bring up the research proactively
    2. Objection handling

This all seems straightforward, but as I think about the various technology firms I worked for, I’ve rarely seen this done at all.  And I include those companies where it was my responsibility to have done this.  I screwed up.

When you don’t do this, everything is reactive.   I still remember a situation where there was a competitive POC bake-off.   Both my firm and the competitor were featured in “the best place” in an analyst report.  The competitor was slightly better positioned.   Despite winning the bake-off, the sales team had to defend the placement.  But they had no context.   Once they came to me, we were able to show the prospective client that all the things they liked about our product and strategy were reinforced in the research.  Some of the reasons the competitor was better positioned were not relevant to their situation.

We ended up succeeding, but the deal was delayed as we scrambled to put this together.  Don’t let this happen to you.  Be proactive.

And, if you are wondering about reprints, here are my general guidelines on content licensing.

But focus first and foremost on sales enablement.

 

Category: go-to-market  

Tags: analyst-relations  magic-quadrant  research  sales-enablement  

Hank Barnes
VP Distinguished Analyst
5+ years at Gartner
30 years IT Industry

Hank Barnes provides research and advisory services on go-to-market strategies for technology providers. He focuses on issues related to positioning, storytelling, the technology customer life cycle, and customer experience. Read Full Bio


Thoughts on The One Thing to Always Do When Mentioned in Analyst Research


  1. Simon Levin says:

    This is a really good point Hank. Surprising how many companies put in the days and weeks of hard work into responding but then fail to act on the result — handing the initiative over to competition. Free paper detailing the actions for all stakeholders at http://theskillsconnection.com/resources/mq-published-now/



Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.