Your sales prospects primarily run pre-sales evaluations (e.g. POCs, managed trials, etc.) in order to test whether your product can support their use cases. However the pre-sales evaluation is so much more than a just test phase of your features. It is a complete end-to-end customer experience in miniature, from POC kick-off to POC implementation to post-go-live POC support. The pre-sales evaluation is the first time that your prospect interacts directly with your company’s technical resources, sees how your product gets set up based on their requirements, and experiences how you support them while they are using your product during the evaluation. Your prospects understand that their pre-sales experience is a predictor of their post-sales experience. 

​Impress your prospects with your pre-sales experience and you will increase your win rates dramatically.

Prospects evaluate vendors based on the goodness-of-fit of their feature sets along with a variety of other criteria, including the expected post-sales experience. The evaluation leads at your prospect are asking their executives for real money to fund the project and often their careers are impacted by good or bad vendor decisions. So after determining that your product is an acceptable candidate based on the features evaluation, prospects often request to speak to current customers in order to ask about the implementation experience and the ongoing support that you provide. They want to get a sense of what it will be like to work with your team during the implementation:

• Was your team organized from day one with a clear project plan? 
• Did your team complete action items and deliverables on time? 
• Was your post-sales team easy to work with?
• Was your team actively engaged in the project or did you make the customer feel that they were just ‘one of many’?
• Did your team take the time to learn the customer’s true business needs and offer solutions that would solve their problems and add value to the business?

From a support perspective, prospects want to understand:

• Is your support team very knowledgeable about your product?
• Does your team respond quickly and resolve issues completely?
• Does your team make the customer feel a sense of security, knowing that you are always there for them?

The goal of your pre-sales evaluation should be to remove a prospect’s desire to ask these questions of a customer reference altogether. Yes it’s true that even with an amazing pre-sales experience, a prospect most likely will still ask these questions as part of their final due diligence. However you want your prospect simply to be confirming that the amazing experience that they just had with you is the norm of working with your company, not a lucky exception.

To achieve this goal, treat your pre-sales evaluation process as the mini end-to-end customer experience that it is. Communicate this goal to your sales engineers and what it means in terms of their day-to-day activities during the evaluation. You should have them follow the same best practices that your post-sales teams follows in your real implementations and in your real post-go-live support processes. Think of all of the questions that your prospects ask your customer references about the your post-sales process (like the ones above) and design your pre-sales process to deliver a positive experience a priori of the prospect becoming a customer.

You know that you have been successful in this endeavor when your prospects-turned-customers tell your sales reps that one of the main reasons that they selected your company was because they loved working with your team during the evaluation cycle.

Now that you have aligned the pre-sales and post-sales experiences for the prospect, you must still develop a smart hand-off from pre-sales to post-sales. When this hand-off is not well designed, a common complaint is that customers feel like they had to start over from the scratch with your post-sales team and waste valuable time getting this new team up to speed. That is horrible a customer experience. Your pre-sales team needs to set up your post-sales team for success by providing them with the complete history of the prospect’s evaluation, including:

• The evaluation plan (all of the use cases/scenarios that were tested and their results),
• The history of all action items (who did what and when),
• Key details about the evaluations, including highlights and technical attributes,
• Notes from all internal and external meetings,
• Feature requests that were made during the evaluation and the prospect’s expectations, about when/if they will make it into the product, and
• The pre-sales points of contact, specifically the lead sales engineer and sales rep.

If done correctly, your new pre-sales experience will create happy prospects during the evaluation phase and in turn happy customers as they transition into post-sales. Happy customers are more loyal to your company, more likely to explore additional products and services that you offer, more likely to talk about your company and their positive experience to their peers at other companies, and more likely to answer those post-sales questions when they themselves are serving as one of your new customer references.

Technical pre-sales teams play a critical role in closing sales: You can’t get the sales win without the technical win. While there are many variations of pre-sales teams (titles include sales engineer (SE), solution architect (SA), solution consultant (SC), Application Engineer (AE)) and many types of evaluations (POC (proof of concept), POV (proof of value) managed trials, self-guided trials, demo systems/environments), follow these seven best practices for managing your pre-sales evaluations and you will boost your win rates and set up your post-sales teams for success.

Note: If you want to learn more about how to implement the following best practices and many others, you can Request a Demo on our Demo page. We'd love to talk with you!

​
1. Understand the reasons why, not just the feature list
 
Customers will often start off an evaluation by giving you a long list of features your product needs to have or requirements that your product needs to satisfy. While this information is important to know, start the evaluation process by making sure that you clearly understand your customer’s motivation for searching for a product. Ask about the business problems that your customer is trying to solve, the reasons why they have these problems, and the expected benefits if you can solve these problems.

Understand your customer’s real motivation so that you can design the best solution for them, which may be very different than the solution that they originally had in mind. Do not sell ‘features’. Offer solutions to their problems.
​

2. Have a plan to get the technical win
 
Now that you know you know the ‘reasons why’, create a formal evaluation plan that will showcase your proposed solution and get your customer’s buy-in to follow the plan to completion. The evaluation plan aligns you and your customer on the use cases that will be tested and the definitions of success.

Creating an evaluation plan can be challenging though:

1. Customers may not know what their use cases should be.
2. Customers do not always know how to test their use cases.
3. Customer may be busy with their regular job activities and may not have time to figure out the best way to test your product.

 
Show your customer that you are experienced and value their time by recommending a list of use cases that will demonstrate how your product solves their business problems. Your evaluation plans should lead customers to test the most valuable features of your product.
 
If you find yourself following the same or similar evaluation plans over and over, create standardized templates that you re-use with new customers. Every customer is little different so modify the template as needed when using it with each customer.
 
A well-designed evaluation plan brings your evaluation to a logical conclusion as quickly as possible with demonstrated success. Congratulations! This is the very definition of the technical win.
 

3. Capture the details of the evaluation and track meetings and activities

Keeping track of all of the details of an evaluation is difficult, but important.

There are key details about a customer’s business processes, IT environment, etc. that are critical for you to know in order to support their evaluation. Capture these details up front as early as you can during the discovery process or early phases of the evaluation. Certain details should be tracked in a systematic way so that you quickly can identify trends across your evaluations, for example, the most common operating system across deals that you’ve won or the most common database in use across deals that you’ve lost.

Take notes in every meeting, whether internal with your team or external with your customer. Meeting notes are the ultimate refresher on where you are in the evaluation. Review your notes on the regular and show your customer that you remember everything about their evaluation. You will build confidence quickly when your customers see that you are engaged in their evaluation. Asking customers for the same details over and over kills your credibility and tells your customers that they are not important to you.

Customers know that their pre-sales experience is a predictor of their post-sales experience. Boost your chances of winning the deal by Impressing your customer with a high degree of engagement and demonstrated knowledge about their needs.
 
Bonus Results:

• Your evaluation notes improve teamwork and collaboration within your pre-sales team as peers can come up to speed quickly on where you are in the evaluation in the event that they have to cover a meeting or take over a deal.
• Your evaluation notes also are very useful during the post-sales handoff. Your customer success and support teams want to know how you got the sale and anything else that might be left hanging during that handoff. Your customer really will appreciate that the fact that they do not have to start with your post-sales team, which is common customer complaint.

4. When you say you will do something, do it, and do it quickly
 
Track your action items so that you remember to do what you promised to do. It’s easy to be on a call and say “Oh, I’ll check with engineering…” and then quickly forget as soon as you hang up. This is true whether you are managing 20+ evaluations at the same time or just a few very complicated evaluations. Either way, remember that this evaluation is very important to your customer. They will remember what you tell them, but you might not. Quick responses and follow-through show that you are engaged in the evaluation. Do not make the customer have to follow up with you to get a response or see if you completed an activity. If they have to ask, you took too long.

​
5. Capture feature requests and quickly pass them to your product team
 
The one question that every pre-sales team knows a customer will ask multiple times throughout the evaluation is: “Can your product do XYZ?” Some of these features requests are ‘must haves’ or you lose the deal, while others are simply ‘nice to have’.
 
Capture these requests as you learn about them, and dig deeper to understand the rationale for the request, such as the underlying business problem that this feature would solve and the expected impact on your customer’s business. Pass this information to your product teams so that they can compare what customers are asking for with their current product roadmap. These comparisons are critical to ensuring product-market fit over time.

Bonus result:
No company wants to lose deal after deal because of a missing feature that could easily be added. When your product teams are kept up to date on what prospects are actually asking for, they might be able to fast-track certain features into production before you lose the next one.
​

6. Check in at regular intervals and offer your assistance

Asking your customer if they need help is a great way to engage with them. They will feel more compelled to respond if you are offering genuine help rather than only trying to get the information that you need or trying to sell them on your product. Engaged customers are most likely to close.

For a variety of reasons, customers do not always let you know when there are problems with their evaluation. By checking in with them, you give your customer an easy opportunity to report any issues that they are having or feature requests that will roadblock the deal. Your evaluations can hang open if you don’t fix these issues or have a path for a feature. Resolve issues quickly to increase your chance of a successful evaluation.


7. Ensure a seamless transition to post-sales

Many companies struggle with the transition from pre-sales to post-sales. A common complaint is that customers feel that they are starting over from scratch with a new team and this degrades the overall customer experience. By following these best practices, you have everything that your post-sales team needs to avoid this complaint and improve the customer experience:

• A record of the customer’s evaluation plan and the results
• A record of the key details and attributes about the customer engagement
• A record of all internal and external meetings and what happened
• A record of the key action items that were completed
• A record of all feature requests
• A track record of helpful, positive, and responsive engagement

Bonus: Your marketing team will love you!
With these best practices, you directly increase the chance of winning deals and setting up your customer as well as your post-sales team for success. Following these best practices also will make your marketing team love you because:

• Happy customers are more willing to talk about their positive pre-sales and post-sales experiences on reference calls with future customers.
• Happy customers increase your ‘word of mouth’ lead flow because they talk to their peers about positive vendor experiences. Personal endorsements can get your company on the list for new vendor searches and quickly move you to the top.

​
Want to Learn More?
We designed Homerun around these seven best practices and many others as well as our years of experience as sales engineers and presales managers. Today, Homerun is the #1 solution built to manage your presales pipeline​, technical evaluations, POCs, and POVs. 

Request a Demo to learn how to implement these best practices and many others to improve your presales process, boost your team's performance, and win more deals.