Important: How to Impress / Annoy an Analyst During a Vendor Briefing? Best / Worst Tips Here!

About a year ago, I crowdsourced a collection of best/worst tips for Vendor Briefings (a one hour presentations from a technology vendor to a Gartner analyst) from other analysts, and now I finally found time to blog it, thanks for some motivation from the Twitterverse. The list is organized as DOs and DON’Ts for the vendors, listed in semi-logical order.

DO NOT:

  • Do not present a disorganized slide deck, full of typos and outdated information
  • Do not (NOT!) go to a VB without any materials such as slides; this negatively affects the retention of the shared information by the analyst
  • But also, do not bring a 110 slide deck and then fly through it, see the above point re: analyst retention of the material
  • Do not spend time talking about your team – in fact, don’t tell me anything I can read on your ”about us” page [we are analysts, NOT investors, a brief “who we are” slide is OK]
  • Do not go so fast that an analyst cannot ask questions, but also do not stop every 3 minutes to ask whether an analyst have any questions
  • Do not be vague about what your product/service actually does in real life [this, as you can easily guess, is a biggie!]
  • Do not focus excessively on marketing and “the story you tell” at a cost of product functionality, specific problems you solve and precise reasons why your approach is superior to alternatives
  • Do not spend too much time [or: any time] on industry statistics about how bad the threat is. We see this every time. Do focus on explaining the specific problem your product/service tackles
  • Generally, do not ask for feedback on Vendor Briefings, we are not allowed to provide it – please schedule a client call if you are client for that
  • Do not allude to having many customers and then say “but they are so secretive we cannot share anything about them”
  • Do not assign somebody who is unqualified, disorganized and arrogant to the task of doing a Vendor Briefing
  • Similarly, do not bring “a CTO” who cannot answer technical questions; because if your CTO is fake, perhaps your entire product is?
  • Do not name drop other analysts’ names and then imply that they really liked your product
  • Do not lie to an analyst such as by saying that you are fascinated by their brilliant research while it becomes clear you actually never read it
  • Do not ask for a briefing under NDA, unless you have some really, really, really good reasons for it [A.C. – this is very rare!]
  • Do not focus on bashing your competition [such as with rumors and innuendo], but do provide a crisp, fact-based comparison to the competition you fight in the field.

DO:

  • Do read the official Vendor Briefing instructions first!
  • Do bring a well-organized slide deck that you actually plan to follow (please no “let’s skip to slide 48”). Some analysts recommend 10-20 slides, I think a bit more is acceptable, as long as they tell a coherent story.
  • Provide a copy of your presentation in advance [we all prefer it, but some of us feel much strongly about this one!]
  • Do use a good quality phone line, and seek to minimize airport, dog, kid, pet hyena noises [A.C. – I do tell people “you sound like VOIP” sometimes, but I would never complain about the dog barking…]
  • You should make sure you tell the problem you solve and what makes you different in the first 10 minutes of the briefing. Be sure to describe this as a unique value for end users, not a unique marketing story.
  • Do ask an analyst what he wants to hear the most, but don’t be shocked if he says “I just want to know what you do and how” [this is true if this a new product space for them]
  • Do express your views on the market history, evolution, trends and your role in all this – but do not give us the market basics.
  • Ideally, share why we need yet another vendor, in this market, to do this [if you are a player in a very competitive market]. A free tip: if you cannot explain this to an analyst, you definitely will not explain it to a prospect….
  • If you are going to do a demo, please make sure it works. Include a realistic demo, i.e. with data, a scenario that represents how your customers use your product,
  • For a product new to the analyst, show how the product addresses specific problems and customer use cases.
  • If you are going to focus on your product strategy, please understand what the word means: a real strategy defines the actions you are taking to grow, help clients and beat the competition.
  • Do provide a fact-based slide comparing your approach to alternatives, direct competitors or even the old way of solving the same problem [all told, is your tool really better than doing it manually]
  • Do remember what you presented to this analyst in the past [we don’t like an introductory briefing 2 months after your introductory briefing…]
  • If an analyst asks a question, please ask concisely, and take no more than 30-60 seconds doing so.
  • Do be clear about what your product strategy is and try to actually articulate this in a Briefing
  • Do follow-up if you promised to send the materials later, share whitepapers, customer references, etc
  • Do cover the exact problems you solve, broad product architecture, top competitors you see (and, please don’t say THERE ARE NONE!), customer use cases, your largest deployments, roadmap [that you plan to actually follow!], etc.
  • Some of us care about your pricing and your pricing strategy, but some [typically us GTP analysts] don’t. Ask an analyst whether they want to know your pricing mechanics.
  • Most of us care at least somewhat about your number of production customer and/or revenue. Please share at least something on this even if you are very secretive
  • If you want to really impress, perhaps even shed some light on what lessons you learned selling, deploying and helping customer operate your product.

Thanks to those Gartner analysts who contributed [sorry, the list of names would be too long to list here, but extra thanks go to Lawrence Pingree for his help organizing the list]

An obligatory cryptic reference: my ROTC instructor once told me that in PSYOPS, we do not lie when we talk about easily verifiable things… perhaps vendors need to take notice of this tip as well…

Other useful materials on briefing analysts can be found at the links below [note that not all of the below agree on all the details, since analysts have different focus areas] – please add you fave resources on this to comments and I will update the post:

 

This is a Security Bloggers Network syndicated blog post authored by Anton Chuvakin. Read the original post at: Anton Chuvakin