If you've worked through Why Buy Anything? and Why Buy Now?, we hope you're aligned on beliefs about your enterprise product. We also hope you have an understanding of how the impact of the identified changes has created a critically important need from customers that they cannot find an answer to any other way.
Now you need to propose a new approach for solving the problem that meets the critical needs in Why Buy Anything? and Why Buy Now? AND demonstrates that your company is uniquely qualified to be the best solution for this new approach.
The best way to think about required capabilities is basically what a customer would put on an RFP. Or how Gartner would define requirements for a Magic Quadrant. It’s how the customer envisions solving the problem. There may be multiple vendors who meet this basic requirement.
Here’s a simple example: You and your spouse are having your first child and you decide you need a bigger, safer vehicle in short order because your small car that you currently own won’t work (eg., Why Buy Anything? and Why Buy Now?). Now you need to decide between an SUV or minivan, what child safety and family features are important, and how much you’re willing to spend. That’s required capabilities.
Next you head down to auto row and start the evaluation process. You’re looking to see which vendor exceeds your expectations the most. Some options have luxury stereo systems, others have better child safety features. Some get better gas mileage. And then there’s price — which car is the better value? Essentially in this phase, the customer is looking to see which vendor provides the most functionality for the lowest price.
There’s a tricky turn in the story here. After Why Buy Now?, a prospect should be receptive to something new. But try NOT to jump straight to how your company solves the problem. There’s an element of thought leadership embedded in how you designed your product that should come out in this part of the narrative. You’re trying to set the table vs. competitive approaches so you are the best option to consider. Maybe your cloud-first approach makes your product easier-to-use. Maybe your product provides visibility to some new problem that wasn’t important before.
When I worked for Okta, we latched on to "best of breed" vs. "integrated stack" as a core part of our approach. Customers liked thinking about how they regain control of products they choose vs. a vendor dictating what software to use. Again, you know the conversation is moving well when the prospect starts leading you to capabilities you’re about to reveal.
In short, there is a how to think about solving the problem before why a customer should choose you.
Let's move onto the specifics of your product. Every product marketer loves their messaging pillars — three to five "buckets" of product goodness that magically solve your customers' urgent problem. But to get there, you’ll want to take an iterative process — a bottom-up and top-down approach. For ease of reference for the bottom-up approach, I’ll use Okta’s single sign-on product as an example.
For bottom-up, you’re collecting an inventory of features that your product offers and grouping those features into concepts to simplify how to explain the product to a customer since there are usually too many features to discuss in one meeting. There should be no mystery or art to this part of the process — that comes in the top-down part of message development:
“Web Portal” is a good example of an Okta product feature — a single pane of glass for users to access all their apps. I suggest creating a Google spreadsheet and sitting down with engineering / product management for this exercise.
Essentially, this is the handshake agreement for marketing and product management to describe any product. This spreadsheet could also include SKU and feature flag–level detail. That is, one “feature” may have many feature flags associated with them from an engineering perspective. But since customers don’t buy feature flags — they buy features — the feature is the lowest level unit of messaging.
“Customizable User Experience” is a concept that includes the Web Portal feature above.
Top-down, the next step is to cluster concepts into pillars.
Pillars are the highest level of product messaging and need to be developed using a “MECE” approach — mutually exclusive, collectively exhaustive. No concept or feature should sit under more than one pillar, and the pillars should come together to tell a complete product story. So, SSO has four core pillars:
Pillars are organized to lead with the most important feature and end with the "back of house" reporting feature.
Pillars should be differentiated wherever possible. At Citrix, we used a three-point scale to determine differentiation of a particular pillar:
Table-stakes: required capabilities that everyone and where there’s no clear uniqueness.
Competitive differentiators: everyone has the capability, but your company does it better
Purple cows: your company provides this capability and no one else has it
The goal, of course, is that over time, "table stakes" features become more differentiators and the company develops more "purple cow" capabilities and product. In the early days, however, some juggling of concepts into different pillars may be needed to beef up the competitiveness of pillars that need more differentiation.
Continuing on the Citrix example, when we entered the market for mobility management, we had to redefine what was at the time a very crowded category. To differentiate from other mobile device management (“MDM”) vendors, we came up with a new term called “enterprise mobility management” (EMM). EMM was MDM plus app management and data management. We did this because we had unique app security capabilities and had acquired ShareFile, which was essentially Dropbox for enterprise. Here’s how we ranked the capabilities in our messaging source document:
The best part? The term “EMM” was adopted by Gartner, Forrester, and the rest, and really took off. In a highly competitive market, there’s always a fit-in/stand-out challenge. You need to fit into what all customers need or there’s no budget for what you offer. At the same time, you need to differentiate to win deals. Great messaging accomplishes both goals.
As an aid to help messaging development, see this Customer Storytelling: Why Buy Now Worksheet. This tool provides a good way to organize all of your company and product-level messaging. The entire document doesn’t need to be done all at once, but at a minimum, going through the bottom-up / top-down exercise to define capabilities will result in a nicely defined product that stands out from the competition.
Finally, and most importantly, we look at the business value that your company offers. This is where the rubber meets the road and where, ideally, you’re able to quantify the benefit of your solution to a customer.
I never really understood the power of business value until I worked for Okta, where it was essential to win deals vs. Microsoft. Microsoft used their Enterprise License Agreement (“ELA”) as a financial weapon to essentially give their competing product away by rolling it into a larger agreement that could include Office and/or Windows. How do you win vs. free? Compete on business value.
Business value is a topic that usually requires a consultant to explain (we hired Forrester to do a Total Economic Impact assessment at Okta), so here’s the reader’s digest version:
Business value quantifies the benefits of your product by three to four "value drivers" that either generate revenue or decrease costs for the customer. That’s it.
Ultimately, if your product doesn’t help drive top-line growth or expense reduction for your customer, it’s worthless. And, of course, your company needs to create more business value than the other guy to win the deal. At some point, you might spend six figures to get Forrester to interview your customers, figure out your business value drivers in great detail, quantify the benefits, and prepare a spreadsheet calculator. It’s a worthwhile investment, but if you don’t have the budget or time, just create a simple spreadsheet calculator to get started. Here’s how.
1. Figure out your top-level value drivers. Usually, you’ll have "hard" value drivers and "soft" value drivers. In Okta’s case, we had three value drivers: IT Cost Savings, Increase Productivity, and Secure Your Environment.
2. Figure out the sub-drivers of value for each top-level driver — sort of like the concepts/pillars process above. Here are some examples:
For each sub-driver of value, you’ll need to either make an assumption based on external data (like the security example above) or by interviewing customers. Or, if you don’t have customers, try to think about what it might be based on average FTE rates and conservative estimates — á la fake it ‘till you make it!
Check out ROI tool vendors like Alinean or VisualizeROI to create a web-based version of your business value tool for lead-gen purposes. Here’s one that we did with Alinean at Okta: https://www.okta.com/roi-calculator/. Notice how we just need to know two pieces of data: number of apps per user and number of employees (users) to create a nice business value report. This gets refined during a deeper engagement, of course, but you get the idea.
Let’s recap the steps to build a perfect story that wins customers:
This is the shift in the market that created the opportunity for your business.
Remember, this is about you and your customer agreeing on how the <move from="" on-premises="" to="" cloud,="" shift="" monolithic="" microservices="" apps,="" etc=""> has impacted a particular team / persona in an organization.</move>
This is the CUSTOMER language, NOT vendor language. For us, “protect against data breaches”, “collaborate with partners” and “increase pace of M&A” were urgent business initiatives that we could latch onto… and the start of solution selling.
Sometimes referred to as the ‘pit of despair’, think of the worst case scenario that your customer could be in without your solution and then back off a bit. That’s desperation. That’s where this stage needs to end. ANYTHING less will stall your sale.
Set the table with the key requirements to solving the new world problem. This is the time for thought leadership and framing the narrative to your favor. Think back to the Citrix example, MDM is not enough to enable mobility for your company. You need Device, App, AND Data Management to empower a truly mobile workforce. You need Citrix EMM not MDM. You get the idea.
There are hard and soft value drivers. Start by quantifying the hard drivers and lead with these (hardware retired, work avoided) and then round out with soft value drivers like productivity, security, etc. For some businesses, there’s top-line growth as well. Fake it ‘till you make it with your own knowledge and online research, but you’ll eventually need to interview customers and probably get a professional vendor to help you do this to win bigger deals.
So, there you have it! An end-to-end story that starts with a market shift and ends with a customer seeing the most value from your company. As a next step, we’ll look at three examples of how these stories come together and we’ll then flow this story into a brief customer presentation to bring it to life.
First customer presentation