On a recent customer call being led by a vendor account manager and engineer I witnessed some key mistakes by the engineer as he presented the technology to the customer.Â None of the mistakes were glaring or show stopping but they definitely kept the conversation from having the value that was potentially there.Â That conversation got me thinking about the skills and principles that need to be applied to pre-sales engineering and prompted this blog.
Pre-sales engineering in all of its many forms is truly an art.Â There is definitely science and methodologies behind its success but practicing those methods and studying that science alone wonâ€™t get you far past good.Â To be great you need to invest effort into the technology, the business, and most importantly youâ€™re personal style.Â If youâ€™re already good at pre-sales and donâ€™t care to be great than the rest of this blog wonâ€™t help you.Â If youâ€™re an â€˜end-userâ€™ or customer that deals with pre-sales engineers this blog may help you understand a little of what goes through the heads of the guys on the other side of the conference table.Â If your job is post-sales, implementations, managed-services, etc this may give you an idea of what your counterparts are doing.Â If youâ€™re a pre-sales engineer who could use some new ideas or tools, this blogs for you.
Joeâ€™s 5 rules of Pre-Sales Engineering:
- You are a member of the sales team
- You are not a salesperson
- You must be Business Relevant
- You must be Technically Knowledgeable
- Know your audience
These are really rules of thumb that I use to get into the right mindset when engaging with customerâ€™s in a pre-sales fashion.Â They arenâ€™t set in stone, all encompassing or agreed upon by teams of experts, just tools I use.Â Letâ€™s start with a quick look into each rule:
You are a member of the sales team:
This one is key to remember because for a lot of very technical people that move into pre-sales roles this is tough to grasp.Â There is not always love, drum circles, group hugs and special brownies between sales and engineering and some engineers tend to resent sales people for various reasons (and vice versa.)Â Whether or not there is resentment itâ€™s natural to be proud of your technical skill set and thinking of yourself in a sales perspective may not be something your comfortable with.Â Get over it or get out of pre-sales.Â As a pre-sales engineer itâ€™s your job to act as a member of the sales team assisting account managers in the sale of the products and services your company provides.Â You are there to drive the sales that provide the blanket of revenue the rest of the company rises and sleeps under (if you missed that reference watch the video, itâ€™s worth it: http://bit.ly/dqTzU7.)
You are not a salesman:
Now that youâ€™ve swallowed the fact that youâ€™re a member of the sales team itâ€™s time to enforce the fact that you are not an account manager/sales representative etc.Â This is vitally important, in fact if you can apply only the first two rules youâ€™ll be significantly better than some of your peers.Â Iâ€™m going to use the term AM (Account Manager) for sales from here on out, allow this to encompass any non-technical sales title that fits your role.Â An AM and a pre-sales SE are completely different roles with a common goal.Â An AM is tightly tied to a target sales number and most likely spends hours on con calls talking about that number and why they are or arenâ€™t at that number.Â An AMs core job is to maintain customer relationships and sell what the company sells.
A pre-sales engineers job on the other hand is a totally different beast.Â While you do need to support your AM itâ€™s your job to make sure that the product, service or solution you sell is relevant, effective, right-fit, and complete for the particular customer.Â In the reseller world we talk about becoming a â€˜Trusted Advisorâ€™ but that â€˜Trusted Advisorâ€™ is typically a two person team consisting of an AM and Engineer who know the customer well, understand their environment, and maintain a mutually beneficial relationship.
As the engineer side of that perfect team itâ€™s your job to have the IDEA:
Note: Before continuing I have to apologize for the fact that I just created one of those word acronym BS objectsâ€¦
So whatâ€™s the bright IDEA?Â A pre-sales engineer you need to identify customer requirements, design a product set or solution to meet those requirements, evangelize the proposed solution, and adjust the solution as necessary with the customer.Â
You must be business relevant
This is typically another tough thing to do from an engineer standpoint.Â Understanding business requirements and applying the technology to those requirements does not come naturally for most engineers but it is vital to success.Â Great technology alone has no value, the data center landscape is littered with stories of great technology companies that failed because they couldnâ€™t capitalize by making the technology business relevant.Â The same lesson applies to pre-sales engineering.
To be a great pre-sales engineer you have to understand both business and technology enough to map the technical benefits to actual business requirements.Â So what if your widget is faster than all other widgets before it, what does that mean to my business, and my job?Â A great way to begin to understand the high level business requirements and what the executives of the companies you sell into are thinking is to incorporate business books and magazines into your reading.Â Next time youâ€™re at the airport magazine rack looking at the latest trade rag grab a copy of â€˜The Harvard business Reviewâ€™ instead.
You must be technically knowledgeable:
This part should go without saying but unfortunately is not always adhered to.Â Itâ€™s way to often I see engineers reading from the slides they present because they donâ€™t know the products or material they are presenting.Â Maintaining an appropriate level of technical knowledge becomes harder and harder as more products are thrown at you, but you must do it anyway.Â Â If you canâ€™t speak to the product or solutions features and benefits without slides or data sheets you shouldnâ€™t be speaking about it.
Staying up-to-date is a daunting task but there are a plethora of resources out there for it.Â Blogs and twitter can be used as a constant stream of the latest and greatest technical information.Â Add to that formal training and vendor documentation and the tools to be technically relevant are there.Â The best advice I can offer on staying technically knowledgeable is not being afraid to ask and or say you donâ€™t know.Â If you need training ask for it, if you need info find someone who knows it and talk to them.Â As importantly work to share your expertise with others as it creates a collaborative environment that benefits everyone.
Know your audience:
This may be the most important of the five rules and boils down to doing your homework and being applicable.Â Ensure youâ€™ve researched your customer, their requirements, and their environment as much as possible.Â Know what their interests and pain points are before walking into a meeting whenever possible.
Knowing your audience also applies during customer meetings.Â As the customer provides more information itâ€™s important to tailor the information you provide to that customers interest on the fly.Â Any technical conversation should be a fluid entity ebbing and flowing with the customers feedback.
Practicing the art:
Like any other art pre-sales must be practiced.Â You must study the products and services your company sells, develop your presentation skills, and constantly work on your communication.Â From my perspective the best way to build all of these skills at once is white boarding.Â White boards are the greatest tool in a pre-sales engineers arsenal.Â They provide a clean canvas on which you can paint the picture of a solution and remain fluid in any given conversation.Â Unlike slides white board sessions are flexible and can easily stay focused on what the customer wants to hear.Â I firmly believe that a pre-sales engineer should not discuss any technology they cannot confidently articulate via the whiteboard.Â You cannot take this concept far enough, Iâ€™ve instructed 5 day data center classes 100% on the white board covering LAN, SAN, storage, servers and networking because it was the right fit for the audience.Â The white board is your friend.
If you donâ€™t have a white board in your home get one.Â Use it to hone your skills, help visualize architecture, and practice before meetings.Â Look through the slides you typically present and practice conveying the same messaging via the white board without cues.Â As you become comfortable having technical discussions via the white board youâ€™ll find you can convey a greater level of technical information tailored to the customers needs in a much faster fashion.Â White boards also donâ€™t require slides, projectors, or power, they donâ€™t suffer from technical difficulties.
As you white board in front of customers think of painting a picture for them, start with broad strokes outlining the technology and add detail to areas that the customer shows interest in.Â Drill down into only the specifics that are relevant to that customer, this is where knowing your audience is key.
In the diagram above you can see the way the conversation should go with a customer.Â You begin at the top level big picture and drill down into only the points that the customer shows an interest in or are applicable to their data center and job role.Â Donâ€™t ever feel the need to discuss every feature of a product or solution because they are not all relevant to every customer.Â For instance a server admin probably doesnâ€™t care how fast switching occurs but network and application teams probably do.Â Maybe your product can help save a ton of cost, great but thatâ€™s probably not very relevant to the administrators who arenâ€™t responsible for budget.Â Always ensure youâ€™re maintaining relevance to the audience and the business.
Pre-Sales like any other skill set must be honed and practiced.Â It doesnâ€™t come overnight and as with anything else, youâ€™re never as good as you can be.Â Build a style and methodology that work for you and donâ€™t be afraid to change or modify them as you find areas for improvement.Â The better you get at the more value your giving your customer, team, and company.