Gartner Blog Network


Prepare Your Customer References – Providing Context Should Not Taint Their Perspective

by Mike Maziarka  |  November 21, 2016  |  1 Comment

As almost all tech providers can attest, customer references are critical for multiple needs:

  • Can help to influence a decision in the final solution selection process
  • Serve as due diligence prior to a buyer pulling the trigger on a purchase
  • Validate the providers story and value to market influencers (including analysts & press)

So, it’s not surprising that it customer reference programs have come up fairly frequently lately.

Beyond all the components that make a good customer reference program – from identification through management – it made me wonder “how good a job do most tech providers do at ‘briefing’ a customer reference prior to asking them to take a call?”

As someone who previously managed the AR function, I now recognize that I often was more cavalier with prepping a customer reference for an analyst interview than I was preparing a company executive for that same purpose. For the latter, I would provide as much context as possible to increase the probability of a successful exchange, including:

  • The analyst bio
  • Coverage area
  • Most recent and/or pertinent research
  • Topics of interest
  • Existing perceptions (plusses and minuses)
  • Points where we’re in agreement on the market
  • Points where we diverge – and how to address

Oddly enough, I didn’t take the same tact with customers being using for analyst references. Perhaps for fear of “tainting” the conversation, I never provided that same level of information.

I now recognize that’s a mistake. Knowing the context – the good, the bad, and the ugly – is always helpful. Whether the recipient takes advantage of it, and uses it effectively, is something that is beyond your control. But, you need to make the effort.

For sales reference situations, I have seen efforts by account executives to provide context. However, that typically happened only when the AE managed both the reference account and the prospect. In those cases, she would know the details about the prospective buyer and have the relationship with the existing customer. It was easy (and comfortable) to share the information at an appropriate depth. Otherwise, I’m not sure that the same level of thought or effort goes into references. In most cases, it resembles more of a toss it over the wall approach. That is a missed opportunity.

If you’re going to take the time, effort, and resources to build a customer reference program, think through exactly (and to what level) you will provide the customer reference with the necessary context for a request. It’s not putting words into their mouths, but instead providing an appropriate level of information for them to be effective in talking about their experiences.

Category: go-to-market  

Tags: advocacy  customer-references  

Mike Maziarka
Research Director
1 years at Gartner
29 years IT Industry

Mike Maziarka is a Research Director on the Tech Go-to-Market team in the Technology and Service Provider Research organization. He provides research and advisory services on go-to-market strategies for technology providers. Read Full Bio


Thoughts on Prepare Your Customer References – Providing Context Should Not Taint Their Perspective


  1. Mike I couldn’t agree with you more. It seems to me that many companies manage their customer references poorly, if at all.



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.