All posts tagged Sales Assumptions

Chapter 17: How To Ask Your Prospect Questions That Help Prioritize

In Chapter 16 we looked at the first part of the process called Confirm The Business Case. As you would expect, an important part of this phase is creating an understanding of all the issues facing your prospect. The next part of this phase is to help your prospect prioritize these issues.

If you plan your day the way most experts say you should, you probably write down everything you need to do, prioritize the list, and then work on the most important things first. We all agree that this is an intelligent and efficient way of doing things. So why is it that when working with a prospect and asking the questions that reveal the true depth of the problems, desired results, and issues we will be dealing with that we become so haphazard and random in our methodology?

We start well enough. “What keeps you up at night?” is an unoriginal, but often good place to start. We may even have the discipline to ask a few more questions, but then our inner-salesperson takes charge and we start to talk about our wonderful solution. All of a sudden, our dialog has become a monolog, and there is a good chance we will be going down the wrong road with our prospect.

Why wouldn’t we want to discuss the first things that come up first? Wouldn’t those be the most important things on the prospect’s mind?

Maybe. But that’s an assumption. And it could keep you away from other critically important opportunities that you may be able to help with. And your prospect’s stated #1 issue may be only a minor issue for his company. We need to fight our human nature of immediate problem solving and instead keep asking and asking until we have exhausted ourselves and all of the problems, desired results, and issues are down on paper.

How do we know when we have asked enough questions?

Perfecting your listening skills is critical for your success. Let’s take the sale of a new e-mail system as an example. Your first few questions will probably draw out the obvious answers. “The existing system uses old servers which are becoming unreliable, we have a hard time pushing large attachments through the system, it won’t do web-based e-mail, and it is hard to keep anti-virus software up to date” could be a response. While you may have the perfect solution to solve these few problems, it is likely that others do as well. Stopping here means that you are the same as all the other salespeople, which means pricing will matter more than you would like.

If you ask more questions and drill down with “what else?” (Chapter 7), you can learn about the impact these issues have. If you were to ask, “Why are large attachments a problem?” you might get a response that ultimately leads to problems with the existing network, not just the e-mail system. If that was the case, imagine the time and angst involved in explaining how your new software didn’t solve the large attachment problem.

After patiently asking questions, you will probably see patterns emerge and will be able to start grouping answers together. When you believe that you have narrowed down your large set of questions into the key issues, you can qualify those issues by asking your prospect to prioritize them. There is a good chance that they will say that all of the issues are important, and they probably are. But it is essential that you prioritize them, as it helps establish the value of each issue, a crucial part of understanding the ROI of your eventual solution.

“We’ll probably need to replace our servers regardless of what we do, so that’s the highest priority,” your prospect may say. “Attachments are the second priority, and I’ll have my network people take a look at some of the bandwidth problems and see if they can diagnose that. We are going to expand into healthcare records next year, and by then we’ll need better antivirus software in place, so that’s number three. Our traveling executives have been complaining about access to their e-mail when they don’t have their own computers with them, so that’s number four.”

It is a good idea to summarize and ask, “If we could solve these stated problems and give you the results you said you were expecting, would our e-mail system do everything you want it to do?” Give your prospect time to think about this. Endure the silence. “Well, the president just got a new iPad, but he’s the only guy using one.”

Wait just a minute. Did your highly tuned listening skills just hear that? Did your experienced ‘corporate politics’ brain just process that?

This is the part where the smart salesperson says, “Tell me more about the president and his new iPad…”

Keep this up until you have all the issues on the table and re-prioritize them as often as needed. The president’s new iPad may not be important to our prospect, but it could be very important to him, and helpful in justifying increased funding for the project.

Chapter 9: The Problem with Problems (and too many Assumptions)

There is more to the problem of assumptions than making sure that all parties have mutually agreed upon terms. I have found that there are many different kinds of assumptions that can keep you from giving your client a great solution to their problem.

For instance, your client may assume that there actually is a problem when there isn’t. Maybe there once was one, but for whatever reason, it is now gone, or that there never was a real problem in the first place. It is also possible that the client may be focusing on a single problem, when there are really several problems.

While every salesperson may believe that his or her company has the best solution to the problem, there is a chance that there is no solution to the problem. Alternately, the client may believe that there is only one solution to the problem when in fact there may be many. Or what if the reality is that the solution may be worse than the problem? (Insert your favorite “the government made the solution worse than the problem” story here).

What if nobody cares about the problem? While your contact may think that the problem is a mission-critical issue that could affect the very survival of the company, there is the possibility that nobody else believes him. And if the person who signs the contracts and writes the checks for projects doesn’t think there is a real problem, then you have a very steep road ahead of you.

As more companies focus on ROI as part of their purchasing decisions, it may be a poor assumption that the problem and solution can be measured in a way to prove ROI. In fact, it may be impossible to measure any aspect of the problem or solution. Also, if the client has many people involved in the project, there is a great chance that each of them will have their own perception of the problem and the solution. How do you handle this if your client has a team of twelve people who all want a piece of the decision?

One of the worst assumptions is that your client perceives your solution will solve the entire problem. While it may be true that ultimately there are only two kinds of problems (people problems and money problems), the world of large, complex, or technical sales usually means that many problems within the client’s organization are causing varying amounts of influence and these can greatly affect any solution you may be proposing.

Let’s go back to our cloud-based CRM example from Chapter 8. After lots of questions (Chapter 7), we all agreed that the client’s problem was that they couldn’t keep track of key data for their staff and customers, and they didn’t have a large budget to solve this problem. In reality there would be much more to this, but let’s agree your product or service met the client’s stated needs. How could this project possibly fail?

While your solution may solve your contact’s problem, it may cause real or imagined problems elsewhere, creating friction within the client’s organization that could result in a failure of your solution. For example, the IT department may not like the fact that your cloud-based CRM stores sensitive data offsite instead of on their servers. The HR department may not like the additional responsibility of training staff on how to use the new system. The finance department may not like the monthly software license costs, preferring to make a one-time purchase of a software program that the company would then own. The CEO may not like spending any money at all. And those always annoying, whiny salespeople? Instead of efficient data management, they see management asking them to do more reports.

How do you overcome all of those problems?

Don’t get too overwrought by all of this. Everyone involved in your project will have problems with assumptions – that’s just human nature. However, if you are aware of the multitude of assumptions that are being made, on both sides of the table, you can better navigate the sales process, keep qualifying, and reduce the possibility that some of those assumptions will have a negative impact. Keep your eyes and ears open to these issues and you will walk a straighter path towards a successful sale and implementation of your solution.