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:
- Treat them like they are special.
- Learn how to brief them before a demo
- Tell them what outcome you want, not what they should show
- Help them get set up for the demo or presentation
- Handle all non-technical tasks during the demo
- Make sure they can work the room at the breaks
- Give them direct, honest feedback, but only after you have won them over.
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.
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.
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.
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.
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.
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.
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.

Hi Dave,
While I agree with everything you said, I do feel you left out what I would call the most important step; 'Partner with your Sales Engineer." One of the most frustrating issues for a Sales Engineer is to feel like they are being treated as a Demo Dolly and are only being brought in at the last moment. Most Sales Engineer are paid on commision, and would like to partner with the Sales Rep on the territory. This approach helps build the relationship between the two far greater than anything else. Also by taking this approach, the Sales Engineer will help gather requiremnt, create the proposed solution, help relate product to issues back to the Sales Rep, etc.
Jeff – Agreed! That should be #8 (or perhaps I should say #1 on the list of 8). Thanks for the suggestion. I agree that the best Sales reps I ever worked with saw it as a partnership (and often a long term one) rather than treating me like a Demo Dave!
Great article, Tech Demo Guy! I hope sales reps and sales engineers alike read it and act accordingly!
John – Thanks for reading!
EMAIL an AGENDA the DAY BEFORE THE MEETING ~*~
On point #2 (btw, very nice writeup, Dave) I'd like to share it's important for the sales rep to email an agenda the day before. Benefits:
(1) an Agenda reminds those customers who you want most to be in attendance
(2) " " can "psych up" the customer's influencers/decision makers to want to be there
(3) " " gives a "heads-up" to the customer if you want them to describe their business problem(s) early in the meeting.
(4) " " with names / titles makes it easier for the Sales Engineer to address customers by name the day of the meeting
(5) " " can help the sales rep avoid embarrassing moments. TRUE STORY: I was in an IBM Customer meeting when the IBM sales rep addressed a customer by the name "Yolanda." While one can imagine that she might be a woman of color (she was)….her name was not Yolanda. It was Latricia. Sending an agenda the day before could have helped the rep avoid that cross-wired mistake!
@Skip – Great point. Sending an agenda also shows the Sales Engineer that you are on top of it and handling your end of the deal. This allows them to relax and do their work with confidence that the rep is handling their part with competence.
Dave – great article. I sent the link to my team and they want it added to our training program for new account executives. I've been managing sales engineers for a while and I can tell you there's a direct payback to account executives that collaborate this way. One AE on our team (he's moved on now) did these steps on every deal. He hit quota each of the 6 years he was at our company and he closed deals every quarter. Thanks for the post.
Scott
@Scott – glad to hear you and the team found it useful. I think consistency (like you described in that AE) is the key to success in sales. Doing the right things every time leads to consistent sales. Tips and tricks only go so far: you need a plan that you apply every time.On Thu, Jun 11, 2009 at 10:51 AM, Dave Sohigian <dsohigian@gmail.com> wrote: approve
On the other side of the fence, there should be a manual for the SE managers and company to which they serve. They powers that be should prioritize their SE team. I have found this list to be over simplified, yet powerful.
1. New sales
2 Existing sales
3. all other issues
How many companies hire an SE, fail to pay them on time, or ask the SE to work existing companies over new business? Let the managers fight the battles, work with existing clients and allow the SE's to perform their magic – pre-sales!
@Mikel – I wholeheartedly agree. Although there are times where the unique skills of the SE can be applied outside of New Sales. One area that I am very familiar with is demos at tradeshows. Often this falls on Marketing (and rightly so) but in most cases they don't have the skills to put together compelling demonstrations. So calling on SE's is, in my opinion, a good idea because it puts the best presentation possible in front of the potential clients. Of course, that should not get in the way of helping close new sales…
Hey Dave,
Love this (new?) blog. Really great stuff in here, not that I'm surprised. Have you found a Web 2.0 tool yet to send anonymous links to people by email? <ahem>
@Ben – thanks. I was just thinking of giving you a call. I have enjoyed writing this blog and getting some of my thoughts on the profession down. More to come.