ROI: Standard requirement for sales enablement
ROI: Required for sales enablement
Good news! The U.S. Department of Labor has reported that the job market has finally recovered to pre-economic crisis levels. Still there are some lessons that should not be forgotten. With this recession, enterprises around the globe adjusted their policies on how they make buying decisions. Across the board, enterprises implemented a strict set of requirements to justify purchases of new products and services. They require that each purchase needs to show a clear definition of the expected total cost of ownership (TCO) and anticipated return on investment (ROI). This has created new challenges for sales teams.
In order to enable sales teams to achieve their goals, they need to adjust their sales process. They need to be able to demonstrate they clearly understand the business of their customers and articulate how the product or service they offer will enhance their business. With tighter controls on spending by the enterprise, the burden of proof is in the sales teams court. To accomplish this, they need to team up with their product managers and product marketers to define effective ROI/TCO modeling tools to show the benefits of their product or service.
Beware of Snake Oil
I have seen a variety of ROI/TCO modeling tools being used in the technology sector. Some of them definitely fall into the category of “snake oil” or “cure-all” elixirs. These are the models that typically require only a few inputs, such as “Quantity of licenses to purchase”, and result in an amazing too-good-to-be-true ROI. Often, these models don’t take into consideration all of the critical factors to estimate a realistic total cost of ownership and return on investment.
Effective ROI Tools
An effective ROI modeling tool to support the sales effort is going to take into consideration the viewpoint of the customer CFO. It should allow as input all the expected cost factors experienced by their operations and particularly those factors impacted by a purchase of the product. Some of the factors would include:
- Manpower costs
- Facilities costs
- IT and data center costs
- Administration and maintenance costs
- Infrastructure costs such as new servers to support a software purchase
- Costs of the product and/or service being sold
The output of the ROI modeling tool should also be able to show the expected benefits that would result from the purchase of the product or service. These benefits may include reduction in operational and fixed costs such as:
- Reduction of infrastructure
- Redeployment/re-purpose of manpower
Benefits may also include new efficiencies such as:
- Increases in speed to revenue
- Efficiencies in transaction processing and volume management
- Improvements in customer service
A good ROI modeling tool will also be able to clearly define “tipping points” such as whether or not it makes sense to utilize cloud-based services or purchase premise-based equipment. This is a topic for a future post.
Corner Office Wisdom:
Sales teams, product managers and product marketers need to have the ability to show the ROI/TCO benefits of their products or service in order to be successful. This will require a comprehensive set of tools and training in order to empower the sales teams to have such a discussion. If they cannot support such a discussion and the competition can, they will lose the opportunity.
Supply and Demand: Price too high?
A challenge with managing any product or service is determining how to price the offer. There are many methods to determine price such as comparing with the competition, evaluating willingness to pay as well as assessing supply and demand. What if there was little supply and a lot of demand?
My grandfather told a story that provided a good lesson about supply and demand. In his later years of life, he refurbished wooden antiques and sold them throughout the midwest United States. At one antique show, he had a number of antique tools on display. They were priced at $14.00. One morning, he noticed a man stop by and give his tools a thorough examination. Then, the man walked away. The man came back again about an hour later and re-examined the tools. He walked away again. He came back a third time and had a very short conversation with my grandfather:
Man: “There is a store in town that had these tools for $7.00”
Grandfather: “Do they have anymore?”
Man: “No”
Grandfather: “Well – if I didn’t have any, I would sell them for $7.00 as well. But I have these and they are $14.00”
He always had a dry sense of humor. Was he priced too high? He had a supply. Was there demand?
I told you that story so I could tell you this one. At one time, I worked for a Sr. VP of Operations for a small software company. He decided to give me a new assignment. There was a group of application developers that were eating up a lot of salary but their efforts weren’t tied to any revenue stream. My assignment: Recommend what needs to be done with them to eliminate the costs.
I met with the team and found they were working on a stack of customer requests to modify custom applications on legacy systems. These modifications included significant design changes to the applications as well as complex interface updates to billing and CRM systems – all at no charge.
After my discussions, here were my observations:
1. They were providing a value-added service to existing customers. Without a billing/CRM system interface the application would not function and not be able to fulfill its purpose.
2. They had no process or organization to the work. They were receiving work orders from multiple directions including customer service, sales and the customers themselves. The work orders were not tracked, quantified or scheduled.
3. Customers being served were on legacy systems that needed to be upgraded.
4. They had no means or methodology in place of showing their value.
Their efforts were essential to maintaining a satisfied customer base. My recommendation to the Sr. VP of Operations was to define a standardized process for the work and to charge customers for the value provided. There was plenty of demand and this group was the only supplier for the service. He agreed to move forward with the recommendation.
As a team, we defined a standardized process for receiving, tracking and completing the work orders including customer sign-off. Since there was a consistency in the type of work being completed, we also defined a standard pricing catalog for various requests being made.
This is when things got interesting. The head of customer service went through roof thinking that she and her staff would be inundated with complaints about being charged for programming modifications. The head of sales felt that existing sales relationships would be put in jeopardy and that they would not be able to upgrade those customers to the next-generation systems being deployed. There was a lot of pressure being applied to not make any changes to the way things were being done.
Within the first 30-days of implementing the new process and pricing for value-added services, contrary to the fears of customer service and sales, the feedback we received from customers was: “I’m surprised you didn’t do this earlier!” The demand was there. The customers appreciated the value of the service being provided and were willing to pay for it.
Over the next set of quarters, the team successfully tracked, reported and recognized revenue to not only cover their salaries but also add some margin to the company’s bottom line. Customer service never received the high volume of complaints. Sales maintained their relationships and successfully upgraded those customers to the next-generation systems.
And as for my grandfather was his price too high? He didn’t need to drop his price by 50%. He knew the value of his products, the demand was there and he had no trouble selling them.
Corner Office Wisdom:
If there is demand for a product or service that you can supply, don’t sell yourself short. There is a willingness to pay. Price it in such a way that allows customers to appreciate the value of your offer.
Tim DeWitt
Corner Office Wisdom 