Archive

Posts Tagged ‘sales’

Winning in a Crowded Field

In one of my earlier posts I talked about one reason why you should consider presenting last in a sales cycle: so that you can stand out in a crowded field. This is just one of the strategies that you can apply when you have lots of competition.

The biggest problem with having lots of competitors is not the competitors’ products, it’s the attention of the prospect. Most sales teams have never had the experience of sitting through multiple demonstrations, sifting through piles of RFP responses and having to put your familiar work environment aside for an extended period. But that is exactly what an evaluation team at a prospect goes through in a sales cycle, particularly one where there are lots of vendors on their preferred list.

What do I mean by a crowded field? If you have more than 3-4 competitors on a deal, the field is crowded. When I have been in deals with crowded fields, I have been amazed at just how confused prospects can get about the vendors. I remember one deal where a prospect regularly emailed me questions that were clearly intended for another vendor.

There are several strategies that can help you stand out in a crowded field:

  1. Have a personality
  2. Often prospects can’t keep all the salespeople from the various vendors straight. Showing a genuine personality during the sales cycle can help the prospect remember you and your product. This is especially true for Sales Engineers who are often expected to give “just the facts”.

  3. Build trust with specific individuals at the prospect
  4. It is inevitable that the prospect will get vendors confused in a crowded field, but if you have gone out of your way to build a relationship with a few individuals at the prospect, they can help you stand out in the evalutation. It does not matter whether the individuals are decision-makers or not, but it is helpful if they seem to be vocal. Your goal is to build an advocate or two that will speak up for your viewpoint in discussions.

  5. Focus on your product, not the competition
  6. In some deals it makes sense to set traps and focus on the competition, but this is not the case in a crowded field. The propsect is already confused enough about which vendor said what; you shouldn’t add to that confusion by talking about the competition even in a theoretical way. Focus on your product and how it will directly benefit the prospect.

  7. Stick with the main message
  8. Sales is all about flexibility and most successful sales cycles will diverge from the standard marketing message (or “brand”) of the product to win the deal. But if there are lots of competitors you should consider staying with your standard corporate message so that all your marketing materials and sales presentations are consistent. Keeping your message clear in the prospect’s mind is more important than tailoring it for that specific prospect when there are lots of competitors. You should absolutely focus on solving the prospect’s problems, but try to do so without moving too far away from your standard marketing message.

  9. Stand out early
  10. If there are many vendors early in a deal, it is tempting to just wait things out and see if you make the short list before investing in a deal. If you really believe you are column fodder then this strategy makes sense, but if you are confident you have a good shot you should come on strong and early. As a Sales Engineer you can do this by having a personality (see #1) and being willing to take risks early in the deal.

  11. Put yourself in the prospect’s shoes
  12. More than anything else you should think about what it is like to be the prospect when there are lots of vendors. Often individuals don’t have much choice about how many vendors they evaluate: the number might be set by upper management, company guidelines or one member of the evaluation team. Having empathy for the challenge being faced by the prospect can go a long way toward building a relationship that will help you as the field narrows.

Dave Sohigian - TechDemoGuy Selling , ,

Credibility: Hard to get, easy to lose

Credibility:

def. the quality or power of inspiring belief

Credibility is the key to a Sales Engineer’s success. Gaining credibility is hard, and losing it is easy. Sales Engineers know they have to build credibility with management, sales reps, developers and, especially, prospects and customers. The approach to building credibility differs with each group.

Credibility with Management

After many years as a Sales Engineer I came to the realization that most big deals fall apart not because of the prospect, but because of management at my company. Salespeople often hound executives to help them win deals (with price concessions or product changes) and executives are somewhat resistant to them because of it. A Sales Engineer can have a special status in the company because they are seen as experts and they help generate revenue (both are things that executives value). Building credibility with management can be done by showing competence and going out of your way to help executives when they need it. There were many times that I was called upon to help an executive with a demo, presentation or subject matter expertise. Rather than seeing this as a distraction from your work (closing deals) these should be seen as excellent opportunities to build credibility for when you need it later. Credibility with management can make all the difference in closing highly political deals.

Credibility with Sales Reps

I have always said Sales Reps are like quarter-horses: incredibly talented but easy to spook. As a Sales Engineer you are probably the one person that a Sales Rep can trust to put in front of a customer and not blow the deal. The best way to build credibility with Sales Reps is to help them win deals. But if you are new to a sales organization there is a shortcut: build credibility with other Sale Engineers. The best approach here is to help more experienced Sales Engineers with the busywork of their deals, RFP’s, answering followup questions, etc… The first place a Sales Rep is going to go for advice on the “New guy/gal” is other Sales Engineers. If they already have a positive view of your work, you are well on your way.

Credibility with Developers/Engineers

If you are in software sales then you have to deal with Developers. If you are in hardware, then it is Engineers. Either way, as a Sales Engineer you have to build credibility with this group to fully understand your product. Engineers speak a different language from Sales, and I have always seen the role of Sales Engineer as a bridge between these two very different departments. Engineers don’t understand what Sales does (and vice-versa) and there is often a lot of mistrust between the groups. Your credibility will determine whether you can bridge that divide.

The good news is that if you are technically competent or have an engineering background, then establishing credibility here is pretty easy. Demonstrating that you understand the pressures on an Engineer will go a long way toward building credibility. For example, if you have a feature you need for a prospect, instead of asking an Engineer to build xyz, tell them the problem that you are trying to solve. Engineers typically love puzzles and would prefer to be given the problem and work the solution out for themselves.

Credibility with Prospects

Credibility with prospects is about first impressions. Often a Sales Engineer will be introduced to a prospect late in the sales cycle and will have to impress the prospect with their competence in a demo or other high-pressure scenario. The best advice I can give for establishing credibility with prospects? Listen. A prospect will measure your competence by how well you understand their problems, not by how much you know. Active listening is a great way to build credibility in an initial meeting. Only once you understand the prospect’s issues can you impress them with your solutions.

More than any other factor, a Sales Engineer needs to quickly convey competence to the prospect. Doing great discovery helps in this regard (because you can address the prospect’s needs) but having excellent customer stories can also build credibility. First impressions are lasting when it comes to prospects and you may have only one chance to establish your credibility with a given client.

Credibility can be gained in many ways, and we each have our own style. I had a distinct advantage over many Sales Engineers because I am relatively tall and have a very deep voice. As ridiculous as it sounds, these are characteristics often associated with leadership (see Malcolm Gladwell’s book, Blink, for more on that) and credibility. Credibility is something that every Sales Engineer should consciously manage as much as they can.

Dave Sohigian - TechDemoGuy Selling , ,

7 Rules for Getting the Best out of Sales Engineers

Why is it that Sales Engineers do a great job for some Salespeople and not for others? What can a Salesperson do to get the best possible performance out of their Sales Engineers. Although the talent of the Sales Engineers you work with will vary (I will do another post on how to get the best Sales Engineers assigned to your deals) you can follow these tips to get the most out of what you have:

  1. Treat them like they are special.
  2. There are times when you may need a stellar performance in the demo to seal the deal. Or you may need a Sales Engineer to complete a long (but important) RFP. But even when the Sales Engineer is not critical to the deal (e.g. a deal where political connections are more important than product functionality) you still need to treat them as if they are special. Most Sales Engineers see themselves as the “talent” with a special set of skills and a role that requires ability to sell AND deep technical/product knowledge. They are typically well-connected in the company they work for (because they deal with so many different departments) and since they are on display at customers on a regular basis they are sensitive to their reputation. It may be annoying to ask them politely to take on work that you feel is just part of their job, but it will pay back dividends when you really need their help on a difficult deal.

  3. Learn how to brief them before a demo
  4. I have only encountered a handful of Salespeople who have mastered this skill; you will be among the very best if you can do it consistently. Briefing a Sales Engineer (or any team member) before a demonstration or presentation is a critical role for the Salesperson. You are the quarterback as well as the coach on the deal, and the team members will be looking to you to call the plays. A great briefing outlines the roles for every individual, what you need the Sales Engineer to accomplish, and what topics should be avoided during the demo or presentation. A briefing should also determine who takes on what questions and identify any key individuals that will be present from the prospect side.

  5. Tell them what outcome you want, not what they should show
  6. Although, as a Salesperson, you may think you know what the Sales Engineer should show in their demo, you should focus more on what you want to impress on the prospect and pass that advice on to the Sales Engineer (as part of your briefing). For example, rather than saying, “Let’s make sure to show them the scheduling administration screens” you could say, “There will be a couple of managers in the room that are going to want to know how easy it is to manage staff schedules. Let’s make sure they come away convinced it is easy and powerful”. This gives the Sales Engineer the information they need without boxing them in too much. This is part of the trust mentioned earlier: tell them the desired outcome and let them figure out how to get there.

  7. Help them get set up for the demo or presentation
  8. When a Sales Engineer arrives at a prospect site they often have a lot to deal with: setting up projectors, getting their demonstration equipment prepared, teleconference setup and arranging the room all require focus from the Sales Engineer. The more of these tasks you can handle, the better. Even if you can’t help with the task at hand, you can assist by keeping the prospect off of the Sales Engineer until they are completely set up. Getting them water, snacks or just asking what they need during this often stressful time will score you points for Rule #1.

  9. Handle all non-technical tasks during the demo
  10. Whether it is documenting the list of follow-up items, keeping track of time or writing down the names of attendees, if there is something you can do as a Salesperson that does not require the skills of the Sales Engineer, then you should do it. Although they may be menial tasks, they will free up the Sales Engineer to focus more on the thing that they do best: impressing the prospect with the value of your solutions.

  11. Make sure they can work the room at the breaks
  12. A good Sales Engineer will want to get feedback and inside information from the prospect during the breaks. As soon as there is a break you should ask the Sales Engineer if there is anything they need. Short of going to the bathroom for them, you should handle calls, water, taking notes, etc.. so that they can focus on interacting with the prospect. A good Sales Engineer can quickly build credibility with the prospect and they will want to talk honestly with them 1:1. Don’t let this great selling opportunity go by just because the Sales Engineer had to make a call that you could have handled for them.

  13. Give them direct, honest feedback, but only after you have won them over.
  14. My favorite Salespeople were those that gave me clear and direct feedback on how things went after a demonstration. They did not pull punches and gave me their perspective on what they saw in the presentation. But to accept that feedback I first had to have a sense of trust with the Salesperson, and understanding that the feedback was meant to be constructive and was about winning more deals. If the Salesperson was new (or new to me) and hammered me after a demo, I was unlikely to want to work with them in the future. So building that trust (by following rule #1) first allows you to give criticisms that will be heeded.

Dave Sohigian - TechDemoGuy Demo Prep, Demo Skills, Selling , , , ,

3 Things salespeople should NEVER say during a demo

If you have worked for a while in pre-sales, supporting salespeople by showing a prospect your software applications, then you know there are times when salespeople will say the darnedest things. Here is my partial list of “never say this during a demo” for the salespeople I have worked with (and I am sure they have a list of “never do this!” for me as well):

  1. “Can you show that thing you did yesterday?”
  2. I will could do an entire post on why this one is a bad idea, but the short explanation is that your demo guy/gal may not want to show that thing because it is going to blow up today! If you want to see a demo of something, ask before the presentation.

  3. “Let me introduce Dave who is an expert in…”
  4. Most Sales Engineers I know don’t like the word expert and all that it implies. It is just setting us up for our credibility being knocked out later in the presentation. Better to talk about experience, years with the company, or just let us introduce ourselves.

  5. “I just heard from Product Management yesterday that we are going to add that feature in the next release…”
  6. For a Salesperson to be effective they have to build trust. For a Sales Engineer to be effective they need to build credibility. Undermining a Sales Engineer’s credibility during a demonstration by pointing out a mistake they made is counter-productive. It’s not an ego thing – Sales Engineers are wrong all the time and need to learn from their mistakes. A better approach is to wait until the break and discuss it directly with the Sales Engineer. Besides, you may have misunderstood what the Product Manager meant by “new feature”…

Dave Sohigian - TechDemoGuy Demo Skills, Demo Tips, Selling , , , , ,

Dumb Things Sales Reps Say #1

As a Sales Engineer you depend on Sales Representatives for your success. Sometimes they are a great help during a demonstration, but sometimes they say some pretty dumb things. My first example is when a Sales Rep says to a Sales Engineer:

“Can you show that thing you did yesterday?”

Although your Sales Engineer may have done a spectacular demo yesterday and really wowed the customer, but that does not mean they can do the same thing again today. Your demo guy/gal may not want to show that thing because it is going to blow up today! Or, just as likely, they don’t think it will add to the demonstration (perhaps it is a feature that detracts from what the prospect is really looking for).
So what should you do if you saw a great demo yesterday that your SE seems to be forgetting? Your first choice should be talking to your SE before the demo and going over what they are going to show. Second choice would be to wait until a break to ask them or slip them a note during a lull in the presentation. And if you have to ask during the middle of the demo, then be prepared to be the cause of a disaster you will need to clean up later.

Dave Sohigian - TechDemoGuy Demo Tips, Selling , ,

6 Worst Demo Mistakes

There are lots of mistakes that a Sales Engineer can make in a demo, but these, in my opinion, are the worst:

  1. Show up and throw up:
  2. This is a common mistake of experienced Sales Engineers. If you have done a lot of demos of your product you may be tempted to just show up at the demo without knowing much about what the prospect is looking for in your product. You may not have been given the chance to do proper discovery (see below). You might just be in too much of a hurry to slam out the demo and get on to more important things. But if you don’t customize your presentation and demo to each prospect then you might as well not do the demo to start with. I have also heard this called the “Stop me when you see something you like” approach to demonstrations and I know Sales Engineers that have made a career of it. You can win deals with this approach, but you will win more if you know exactly what the prospect values and can demonstrate your product’s ability to meet their needs.

  3. Prepare too much
  4. Lots of Sales Engineers seem to think that it is impossible to prepare too much for a demo, but I disagree. You can definitely go overboard when it comes to preparation, especially if you either focus too much on one feature/function or try to meet ALL the prospects stated needs. A demonstration should be proof of your applications ability to meet the needs of the prospect. If you try to cover all the requirements outlined in an RFP or demo script rather than focusing on some key items first, you will probably spend way too much time preparing. And if you do an equally mediocre job on all the sections of a demo script you will be judged much more harshly than if you knock it out of the park on several and miss entirely on a couple. Focus your attention to limit the required preparation.

  5. Fail to dry run
  6. I already have a post on the importance of dry runs, but I am always amazed at how often sales teams skip them. They win demos and you should do them!

  7. Get too little sleep
  8. This goes along with “prepare too much”. Being well rested and ready to present on demo day is more important than tweaking that last slide or changing the color of that button. Know when to say when and get a full night of sleep before your demo.

  9. Skip discovery
  10. Although this is often not under the control of the Sales Engineer, experienced pre-sales people know how to push for discovery. Preparing your presentation based on what you hear from a sales rep, or worse, from your educated guesses based on previous customers, is a mistake. Good discovery reduces the amount of preparation required (see above) AND often results in fewer demos because you show them just the stuff they are interested in (avoiding the “show up and throw up” problem).

  11. Take too long to show product
  12. This ties in with my post on the 30 second demo. People who come do a demo want to see product. If the sales rep stands up and talks about your company for 1/2 an hour and then you get up and discuss the demo scenarios, requirements, etc.. for another 1/2 hour, then the prospect is left squirming in their seats for an hour. Do yourself a favor and show something, anything, in your product as early in the demo as possible.

Dave Sohigian - TechDemoGuy Demo Prep, Selling , , , , ,