Chapter 23: Turning Soft Data Into Hard Data (And Ultimately Into Impact)

Soft data funnelUp to this point we have been discussing how to measure problems, how to define problems, how to determine what a favorable end result would be, what the value of that end result would be, and what that value would be over time. In Chapter 22: Turning Financial Analysis Into A Value Discussion, we took some very simple round numbers from Hard Data and had a discussion with our client to hopefully create an understanding that there is a problem worthy of a cost-effective solution. Ready to sell now? Hold on – there is another type of data that we need to talk about:  Soft Data.

Soft Data is by nature hard to quantify and put into a measurable ROI. If your customer wants to increase security in their building, create an environment that attracts better employees, elevate their position in the marketplace, or foster better teamwork, you are going to have a hard time turning this type of general statement into actionable data. While it will always be more difficult to uncover and quantify Soft Data and how it affects the problems and potential solution, there are ways to increase the clarity of the situation.

We all have heard, simply put, that customers buy to either increase the good or decrease the bad. Sometimes a solution will address just one of these, but more often it will impact both good and bad issues (for example, an exercise program will increase your fitness and decrease your weight). For our purposes here, let’s look at these as two distinct situations.

If your prospect is focusing on increasing good things, you will most likely hear phrases from them that talk about the goals, objectives, accomplishments, targets, or improvements that they desire to obtain. For example, they may say that they want to improve the security in their employee parking garage. How do you measure that to create an ROI? It starts with a series of questions:

  • “If you improved security in the employee parking garage, what would that do?” (It would make our employees feel safer when they work late and have to walk to their cars in the dark)
  • “If they worked late but felt safer when walking to their cars, how would that affect your business?” (Some of our high priority projects are in danger of slipping, and we need people to work longer hours to catch up…if they felt safer walking to their cars at night, they would be more likely to work later)
  • “And if those employees worked later more often, what would the impact be on those high priority projects?” (We would complete those projects on time and we would bring in an extra $XXX dollars over YYY months into the company)

A bit simplistic? Of course, but it illustrates the process of turning Soft Data into Hard Data and ultimately into Impact. What if your prospect is focusing on decreasing bad things? If so, you will most likely hear phrases from them that talk about pain points, concerns, margin slippage, process roadblocks, or work silos that they want to diminish. While it can be difficult to get a prospect to fully unveil all of their pain points, once they are discussed, these are usually easier to measure. Let’s use the same example, except this time the prospect is saying their problem is that people are unable to work late to finish some important projects:

  • “Why don’t your employees want to work late?”  (We had some cars broken into at our employee parking garage, and now people don’t want to be in the garage when it’s late, dark, or when they are alone)
  • “Did they work late in the past, and did they feel safe then?”  (Yes, we never had a problem with employees working late until we had the car break-ins)
  • “What will it cost the company if you don’t finish these important projects?”  (It will cost us $XXX dollars over YYY months)
  • “What else could happen if the employees don’t feel safe?”  (Morale will decrease because employees will feel management doesn’t care about their safety, and ultimately, we could get sued if an employee were attacked in the garage)

This line of questioning could go on, uncovering both Hard Data (those $XXX dollars over YYY months that have a financial impact) and Soft Data (decreased morale, potential for a lawsuit, difficulty in recruiting new employees, etc.). The point is that much of the data that you thought would be hard to quantify is really an issue of your ability to drill down with a series of questions that will turn that Soft Data into Hard Data, and ultimately into Impact. The goal of course is to walk down this path of discovery with your prospect, unearthing different types of data, quantifying it as best as you can, and then helping your prospect understand the problem. A side benefit is that this process will help your prospect explain these findings to his or her colleagues who may become a part of the final decision of moving forward with your solution.

What if you uncover issues that just can’t be quantified? We’ll cover that next in Chapter 24.

 

Advertisement

Chapter 22: Turning Financial Analysis Into A Value Discussion

photo-30By now you may be chomping at the bit, wondering when you get to do your PowerPoint or demo.  After all, your competitors have already given their presentations, and here you are, still asking questions instead of talking features and benefits. Steady…stay on target…we’re setting the table here, not going straight to dessert.

In Chapter 21, we looked at how to turn soft, hard, or inferred data into a form of impact. The degree of financial analysis required will depend on your industry and the order of magnitude of the problem to be solved.  It is important to not get too bogged down in the early stages. Consider the problems of a traditional detailed financial cost analysis:

  1. Determine the project’s cost savings impact over 3-5 years (a guess)
  2. Determine the project’s cost over 3-5 years (another guess)
  3. Subtract #2 from #1 for the project’s total cost savings (guess – guess = guess²)
  4. Factor in the average weight of capital to the equation (the mother of all guesses)

That is a lot of guessing. And there are obviously many more steps than in this simplistic example; imagine how all of those guesses keep skewing the results! And what happens if you or your clients aren’t happy with the numbers you generated? Be honest…you most likely go back and tweak the numbers until you end up with something closer to what you were expecting.  Guessing and manipulation – that’s a recipe for disaster.

The art of getting useful results out of this process will depend heavily on how you take the exercise and turn it into a discussion, not a complete financial analysis. After all, your goal is to help your client understand the problem and its impact, help place you in the role of a trusted advisor, and of course, help you continue to qualify your prospect. Besides, if you are like most salespeople, you are not a spreadsheet genius who delights in the world of credits, debits, and pivot tables. Fortunately, if you can help your 4th grader with math homework, you have all the financial skills necessary for this phase.

In How To Take Data And Turn It Into Impact, we used the example of rekeying the locks at a university to illustrate how to create a very basic understanding of the financial impact of a problem. This type of financial analysis is obviously simple, often referred to as “back of the envelope” math. The exercise reduces the amount of guessing (or makes it obvious to you and your client that you are guessing and agree that you are using round numbers to get a general understanding of the problem). You are now in a position to take your ballpark numbers and talk about them in a way that not only starts to firm up your mutual understanding of the problem, but may also allow you to uncover additional problems that your company can solve.

You both need to work this together

Besides the obvious face time this gives you and the client buy-in it produces, it will give you additional insight into your client’s opinions, allow you to test your assumptions, and enable better, more educated guesses (yes, we’re still guessing at this point, but that’s okay). As you talk about the problem, you will need to put your findings into the language of money. After all, the solution you offer will be based on money. In the end, if your client can’t apply a viable ROI to your solution,  even the biggest problem won’t get the funding to solve it.

HP-12C

Yes, they still make the trusty HP-12C

Keep the math simple, and keep things centered on positive and negative numbers. This is not the place for percentages or ratios, and it certainly is not the place to show off your MBA skills with your trusty HP-12C calculator. If the numbers come up larger than expected, your client may start to distrust the process, even though you both contributed to that process. If this happens, take the conservative route  and say something like, “That seems a little high…is this what you were expecting?”

Pay careful attention here…you are about to either get solution buy-in or problem abandonment

If they answer that the number seems about right or might actually be underestimated, keep moving forward. If they answer that the number seems high, work with them until you both reach a conservative number that you not only believe, but can later prove to the client’s senior management who ultimately will write the check for your solution. Then ask one final question:  “Is this problem big enough to require a solution?” Because while your solution might solve a problem with an annual ROI of $100,000, that might mean nothing to a $50 billion company with other priorities.

If after all of your work together you get to the point where your client is not seeing numbers that justify moving forward, you need to take a deep breath and evaluate where you are. Should you keep pushing and try to get to a number that works? If you have been lazy with your qualifying over the past few meetings, you may be fooled into pushing forward. If you have been constantly qualifying your prospect throughout your entire engagement, you will probably see that you have reached the point where further time will not pay off. That’s a tough call, but an important one. Don’t keep trying to push that rope uphill. Move on.

But wait, not so fast. There are few absolutes in business. It may make sense to continue on with what appears to be an unqualified prospect. What if there is more to this problem’s ROI than can be easily measured financially? Just as there are soft costs, there is also soft data. We’ll look at soft data and how it impacts your client in Chapter 23.

Chapter 21: How To Take Data And Turn It Into Impact

You’ve followed Chapter 19 and 20, assembled a massive pile of facts and figures, and now have to find a way for it to make sense and show how it impacts your prospect.  You have probably found that the data can be grouped together in some obvious categories.  There are two bigger categories that all of the data will fit in:  Problem Data and Impact Data.  We covered Problem Data in Chapter 18, but what is Impact Data?

This is where you want to spend your time, as Impact Data is where the C-Level prospects spend their money.

All companies have problems, and some just sit there, year after year, annoying people who ask, “Why doesn’t the VP of Operations know about this and fix it?”  It is likely that the VP of Operations knows about the problem.  It is also likely that the problem has been evaluated, and one of two things have happened:  the impact of the problem is less than the money or time it would cost to fix the problem or the impact of the problem has not been supported by enough data to prove that fixing it is financially viable.

Understanding the impact of a problem is crucial for proving the business case for any solution you hope to provide.  There are five questions that form the basis of understanding the impact a problem can have on an organization:

  • How do you measure the problem?
  • What is the current situation?
  • What results would you like?
  • What is the value of those results?
  • What is the value of those results over time?

This is relatively straight forward when dealing with hard data.  For example, let’s say that you are trying to sell a university an electronic dormitory room key lock system.  Your conversation might sound something like this:

  • Prospect:  Your electronic dorm room key lock system would increase the security of our 400 dorm rooms.
  • You:  What is the biggest problem that our system would solve? (measurement)
  • Prospect:  We have too many old keys floating around.  We only know where about 80% of them are.
  • You:  That’s about 200 keys that you are missing. (current situation)  What would be an acceptable percentage of unaccounted keys?  (desired results)
  • Prospect:  We need it to be zero, because it costs us $65 to rekey a lock.
  • You:  Let’s see, 400 dorm rooms times $65 dollars a lock…that’s $26,000.  (value impact)
  • Prospect:  And students are constantly losing keys, getting duplicates, moving in and out of dorms…we just aren’t as safe as we could be.
  • You:  If this is a continuing problem, then over four years at two semesters per year, you could have a total of over $200,000 in rekeying costs.  (value impact over time)

Other types of products and services can be more difficult to prove impact, as they often rely on soft or inferred data.  For example, let’s say that you are trying to sell a mass notification system to a university that would alert students to dangerous situations on campus.  Your conversation might sound something like this:

  • Prospect:  Your software would help keep our students safe from gun violence on campus.
  • You:  Other than the possibility of fatalities, what is the biggest problem that gun violence would create for the university?  (measurement)
  • Prospect:  Our students and staff would feel very unsafe, and the bad press we would receive would severely harm the university’s reputation.
  • You:  How do your students and staff feel now, and what is your university’s reputation for security?  (current situation)
  • Prospect:  We’ve never had a major incident, so our students and staff feel safe, and we have a reputation as a place where parents can send their kids and know that they are safe.  This is especially important for our foreign students and their parents.  (prospects implies desired results)
  • You:  What would happen if you had an incident that made the evening news?  (value impact)
  • Prospect:  Other universities have seen their enrollments decline by 10%…almost 25% for foreign students.  (inferred data)
  • You:  Let’s be conservative…if we take your 20,000 students, reduce enrollment by just 5%, and multiply it by your $15,000 tuition…that’s about $15,000,000 in lost tuition alone, not counting the fact that foreign students pay more and stop attending at a higher rate.  (value impact)  How long would it take to regain your reputation, and ultimately your students?  (value impact over time)
  • Prospect:  Others have recovered in three years, some never fully recovered from their foreign student losses.
  • You:  If that is the case, your university could face well over $30,000,000 in tuition losses.  (value impact over time)

This is of course simplistic and scripted, but hopefully you can see how there needs to be a process to help both you and your prospect understand the impact of the problem, especially the financial impact, so that you can create a better business case.

Chapter 18: Is Your Prospect’s Problem REALLY A Problem?

Part of the process of Confirm The Business Case (Chapter 15) is to guide the conversation so that your prospect is actively engaged and not just giving you the same pre-programmed answers that he is giving back to your competitors. You know that if you focus on developing your questions (Chapter 16) so that they continuously clarify the prospect’s problems, desired results, and existing issues that you can then help them prioritize (Chapter 17).  Now it is time for two very important questions:

Is there really a problem?  Does it really matter?

Let’s break these down a bit.  When I ask if there is really a problem, we both know that the answer is yes.  After all, you’ve done the work associated with the above listed chapters. If you are meeting with the person who actually writes the check, then you are well on your way.  However, if you are working on a large, technical, or complex sale, you are going to have to help your prospect justify to others within his organization that there is indeed a real problem, and that takes evidence.

What evidence am I talking about?  Let’s go back to the example we used in Chapter 17 of replacing an antiquated e-mail system with a new one.  We asked our questions, and were told that “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.”  We then helped our prospect prioritize these issues, and in the middle of that process found out that the president had a brand new iPad, which changed the priorities again.

Now that we have this kind of data, we need to ask the Who, What, Where, When, and How questions.  This is old school stuff, and you probably already know that you need to add hard data to some of the soft statements your client is making.  In the e-mail system example above, let’s take the first thing our prospect said, “The existing system uses old servers which are becoming unreliable.”  To properly build a business case, we need to ask questions such as:

  • Who manages the existing servers?
  • What are the existing problems?
  • Where will funding come from?
  • When will the budget be approved?
  • How will this project be managed between multiple stakeholders?

You get the idea.  These are all proof points that different people within the organization will want to understand, even if they are not directly responsible for the project.  These questions can seem obvious, but they help to clarify to others that there really is a problem.  The other aspect of building a business case is to quantify how the problem is negatively impacting the organization and then how a successful implementation would positively impact the organization.  For example:

  • Who is impacted by the server’s reliability problems?
  • What hard costs and soft costs are absorbed because of the reliability problems?
  • Where is the data that could verify those hard and soft costs?
  • When could the investment in the project reach a break-even point?
  • How can we measure if the project is successful?

These questions help to establish not only the impact that the problem is having on the prospect’s company, but to also set up a scorecard that can eventually be used to prove the success of your solution.  When you can answer these kinds of questions, you will be able to help your prospect show that not only do they really have a problem, but that it really matters.  It is surprising how many clients ultimately take this alternate way of exploring issues to assemble a compelling business case and use it in their daily life.  If they have been shot down in the past for projects that they worked on, they usually find that building a business case that the C-Suite can relate to is a skill that will pay dividends for years.

A side effect to this kind of questioning is that your contact may come to the realization that they do not understand the problem as well as they thought they did, especially when dealing with the financial impact.  In fact, it is likely that many of the answers are scattered throughout the company’s departments (silo alert!), and that some information is simply nonexistent.

This is not necessarily bad news.  In Chapter 11, “Yes Is Good, No Is Good (But Maybe Will Kill You!)” we discussed how bad news isn’t the end of the road, but just an inflection point.  We can show our value to our prospect not only by asking them tough questions that they can’t answer, but by showing them how to go about getting those answers so as to help build a strong business case for their project.

This will become very important down the road whether you submit your solution in a written proposal or as an in-person presentation.

Chapter 15: A Sales Process For Salespeople Who Hate Sales Processes

How many sales seminars have you been to that involved a lengthy or complicated sales procedure? Or perhaps they had a canned presentation with a general methodology that worked in their industry back in the days when they were carrying a bag? Too many, I’m betting. You’ve seen all kinds, from spreadsheet-intensive flow charts that require you to fill in all the blanks with names and titles whether they are pertinent or not, all the way to complex wall size documents that could have been used as a planning guide for the invasion of Normandy.

The problem? One size does not fit all. In fact, one size does not even fit one.

The reason is that every industry is different, with a unique sales cycle complicated by a multitude of factors. If you consider the individual nature of your prospect and the other people who will be a part of the decision, add the complexities of your own company plus your own sales style, it is easy to see why these overly complicated “fill in the blank” template sales seminars rarely have any lasting impact on salespeople. While they may make sense on paper, they become more of a hindrance than a help after just the first few minutes of your sales call (“Slow down Mr. Customer, I’m still filling in the blanks”).

After slinging all these arrows at sales processes, am I really going to offer you my own sales flowchart procedure? Yes, but I promise it won’t hurt. Much. It doesn’t fit into a nice format having exactly 10 steps or have the first letter in each step spell out a word. It would be great if the sales process was that predictable and linear, but so far, I’ve never seen that happen. At Client Centric Sales, there are ultimately only five phases:

  1. Confirm the Business Case
  2. Confirm the Budget
  3. Confirm the Scorecard
  4. Confirm the ROI
  5. Maintain the Client

It would be great if the last one was “Confirm the Client” so I could call this my “5 C’s Sales Program,” but then I would be as guilty as anyone else who was putting out a mnemonically titled program. You could argue that “Qualify the Prospect” should be added in there somewhere. But as regular readers of Client Centric Sales know, qualifying is done continuously within each of these steps. We will cover the above in more detail in coming chapters, but for now let me explain each a bit so that they make a bit more sense as we move forward:

Confirm the Business Case – We need to mutually examine the problems to be solved, agree on terms, eliminate assumptions, and verify that a solution exists. We must also understand the impact that our solution will have on the business, both positive and negative.

Confirm the Budget – We need to verify that there is a budget approved for the amount that is required for our proposed solution. It is also important that we align ourselves with our prospect’s expectation of not only the financial side of the budget, but also the time and people who will be required from both sides.

Confirm the Scorecard – There are many parts to the scorecard. We need to not only confirm that the person we are talking with is a decision maker, but we also need to verify who, if any, the other decision makers are. At this point we should have mutually created a scorecard that will be used to clarify what problems the product or service will solve, how it will solve them, whom it will impact, and how the purchase decision will be made.

Confirm the ROI – Here we finalize the business case with data gathered by our prospect and by our company. This data will be used to confirm in great detail how our product or service meets or exceeds the solution required for the prospect. This step is often the creation of a formal proposal or presentation, and it will summarize the data gathered in the first three steps.

Maintain the Client – Whether you won the sale or not will affect your future relationship with the prospect. If you were awarded the sale, it is only the first half of the relationship. Over the next five years, a well-maintained client relationship can produce additional revenue equal or greater to the original sale. If you were not awarded the sale, that doesn’t mean your engagement with this prospect should end with a slammed door.

We have covered all of the above in Chapters 1-14. Next we will spend more time getting into the detail of each of these steps.

Will the Client Centric Sales method work for all sales situations? Obviously, the answer is no. The depth of engagement that I am asking from you is best served when dealing with large, complex, or highly technical sales. And if you take the lessons we will be discussing in coming chapters as a guide, and then add the particulars of your personality, your company, your prospect, and your industry, then you can use these five simple steps to develop your own unique sales process that fits you perfectly.

Chapter 4: How Does Your Client Measure Success?

If you were to ask your prospect, “How will you know if this project is successful?” I’m betting that they wouldn’t know how to answer you. A study on IT system implementations showed that 37% of them failed. That means only 67% of IT projects succeeded, which in any school would be rated a “D.” Why did they fail? The study cites that the requirements for the project were unclear, resources were lacking, schedules were unrealistic, planning data was insufficient, and risks were not identified.

Does this sound like any of your past projects?

Whether you are in the IT industry or the TP industry, there are lessons to be learned here. The most important lesson is that it was, at best, only after the project was completed that thought was given to how success would be measured. As customers are (thankfully) getting smarter, more and more are learning to define the scorecard in advance to measure the success of the project.

The greatest opportunity with your prospect is to help them develop the scorecard that will be used to determine what success looks like.

What kind of measurements will your clients be using? Return-On-Investment (ROI) is a common business measurement yardstick. It is certainly one that is dear to the CFO‘s, CEO’s, and Board of Director’s hearts. If you can show your prospect that your product or service can reduce costs, increase revenue or margins, increase productivity, increase quality, or increase customer satisfaction, then you have a good chance of moving your proposal up through the organization. If you can help your contact at that company matter to the C-Suite, and help him or her enable the company to survive tough times and even grow, then that contact will start to treat you like a trusted advisor who is out to help the organization.

After you have proven yourself to be an expert and have identified the key people you need to meet and work with (Becoming An Expert In Order To Qualify Successfully, Chapter 3), you are ready to start writing the score card that will be used by your client (and hopefully forced upon your competitor). The sum of that scorecard needs to be firmly anchored in the Client Centric Sales model of win-win; it is imperative that you work together to create and supply the optimum solution to the company’s most important problems.

Win-Win is easier said than done. The most difficult part of this is that the contacts you have at your prospect’s organization will most likely not have a full understanding on how the project affects the business drivers of their company. They may have secured budget money, and may even have a specification written. The project may have been funded to solve “Problem X” which is funded for “Y dollars” for a period of “Z months,” but has a business case been developed that would enable your contact to justify the project? Are you in a position to help your prospect show the C-Suite how the proposed project is a win for them?

You probably have a good understanding of your prospect’s industry, and an even better understanding of the challenges your prospect’s company faces. You will need to identify how your product or service can address at least one of those challenges, and you will need to help your client develop the scorecard that will be used to both establish the success of the project and can be used to make sure that your competitors are being measured to the same standard.

Problems?

Many, and half of them are caused by ourselves.  We don’t listen, we make assumptions, we think of solutions that we have already sold instead of working to understand every aspect of our prospect’s business, and we assume that we are talking to the right people within that organization. But it is not all our own fault. It doesn’t help that our prospects don’t really know what they need, can’t find a way of accurately describing the problem, keep key information to themselves, won’t let us near the right people, are unrealistic about expectations, and are more concerned with company politics than end-results.

This is why you need to help write the scorecard for your project. Granted, it is not easy, and it takes a lot of time. The good news is that each step you take will help you to continually educate and qualify your prospect. In coming chapters, we will examine a simple methodology that you can use to create a concise, measurable, and justifiable scorecard that you and your prospect create together that will help put you in the driver’s seat.

%d bloggers like this: