Inside Sales Telesales Tips Blog

How to shine when giving an in-house product presentation

  

  

 delicious  

  

Particularly if you're selling a technically sophisticated solution, you may, as an inside salesperson, be called on to make a product/solution presentation to your own in-house sales or engineering team, as proof that you know your product. Such a presentation can be fraught with pitfalls, as more than occasionally you'll be expected to provide a product feature dump, particularly if your engineers are the intended audience. While we touch on presentation skills as part of our telesales training courses, it's worth reading this blog post if this presentation task is coming up for you.

The worst mistake you can make is trying to make sense out of a 400 page technical manual, then trying to craft the data into a presentation. This happened to me one time, and I made a really great presentation because I distilled three concepts before I started to craft my presentation to the brain trust. These three concepts are:

1) What customer problem does my solution solve?
2) What do I need to know about my solution in order to sell it?
3) What do I not need to know in order to sell it?

Presenting these three concepts will not only provide a "wow" factor for your in-house folks, but it provides a distillation that you can use effectively on the phone with prospects. It will also help you to avoid "feature dumping," or reading a list of features, a practice that bores colleagues and prospects alike.

Example: a software debugger

In an example from my own sales world, I sold a product called an Atron AT Probe, which was a hardware-based software debugger, a really techie product. Here's how I used the model.

1) The problem it solved was engineers spending long hours debugging software problems by manually debugging. Our solution saved dozens, occasionally hundreds of hours of engineering time. With the debugging time reduced, engineers could be put on new projects, reducing design and development schedules all over the company. The ROI could be put in engineering hours multiplied by the hourly engineering rate, or in getting the prospect's product to market faster.

2) What I needed to know: I needed to know that my debugger worked each time, every time. And I needed a pre-sales tech support person if there were technical specs I couldn't fathom. I needed to know what product my prospect was building, so I could talk about increased time-to-market, and how my solution could accelerate that, so my prospects could make money faster. I also wanted to know my prospect's anticipated release date of the finished product. This way I could use a "fear of loss" closing approach. I needed to know the decision process, because I might have to call others on the team (often, my engineer contacts would encourage me to "call high" to a director or VP to make a case). And I needed to know the meaning of commonly used technical acronyms and jargon.

3) I didn't need to know exactly how the solution worked, or go deep into the technology. Concepts like "sticky breakpoints" were commonly brought up. I knew we did that, but didn't know exactly how we did it. That's what pre-sales tech support was all about. We had a great pre-sales engineer that loved to talk tech. My technical expertise was limited to about ½ page of tech specs. The term I used to describe my approach was to be "intelligently ignorant."

Bottom line, my job was to make lots of good calls and move product. By having a clear understanding of how much I didn't need to know, I could flood my market with calls and make my company profitable.

So circling back to you, try using this technique next time you're asked to make an in-house presentation. You can even use something that, in the education biz, is called an "advance organizer," developed by an educator named David Ausubel. You begin your presentation by saying: "I'm going to tell you the major problem this product solves. Then I'm going to tell you what I need to know to sell it. Then I'm going to tell you what I don't need to know to sell it." Add this presentation skill to your Best Practices playbook, and I'll bet your presentations will be a lot more fun, effective and to the point.