Selling a Bigger Problem: How $40,000 Became $1.4 Million

An excerpt from Chapter 6 of Stories That Sell™, the forthcoming book by Paul Johns.
The revenue you can earn is connected to the size of the problem you solve—not the size of your product.
Of all the stories in this book, this is the one I come back to most often, because it holds so much of the argument inside it.
It is a story about value. And it is a story about how the same technology, told as the answer to a different problem, can be worth thirty-five times as much.
A Good Product, Sold to the Wrong Desk
Some years into my career, I was working for a company with a genuinely clever piece of software. It had been built to monitor communications—email and instant messaging—for appropriate conduct. It could spot inappropriate language, harassment and breaches of workplace policy, and flag them for review.
That was what it was designed to do, and it did it well.
It was solving a real problem. Inappropriate conduct in the workplace matters. It damages people, culture and trust. So we sold it to the people responsible for that problem: human resources.
And we sold it the way most software was sold at the time. As a product, with a feature list, a demo and a price tag of roughly forty thousand dollars.
At that price, and on that desk, it was a sensible purchase. It was also an easy one to postpone. HR had many priorities and a limited budget. The software was useful, but rarely urgent. It sat comfortably in the pile of things that would be good to have when the money allowed.
Important, yes. Pressing, no.
The World Changed
Then something happened in the market that had nothing to do with us.
In the United States, the Attorney General’s investigations into the financial services industry had started to treat email as the smoking gun. What people had written to each other—casually, quickly, assuming nobody would ever read it—was becoming evidence. Communications that had once been ephemeral were now the place where regulators went looking for misconduct, and where reputations and careers could be destroyed.
For the banks, this was a new and frightening problem. They had thousands of employees sending millions of messages. Somewhere in that traffic might be the email that cost them a fine, a lawsuit, a front page or a chief executive.
And it just so happened that our technology—designed to look for inappropriate conduct in emails and instant messages—could also look for non-compliant communications.
The product didn’t change.
The problem did.
The Thirty-Day Pivot
What followed was, looking back, one of the most remarkable turnarounds I have been part of.
In about thirty days, we took a story that was important and turned it into a solution for something far more pressing. We stopped talking about workplace conduct and started talking about regulatory failure and reputational risk. We stopped selling to HR and started talking to compliance, legal and risk—and, through them, to the most senior people in the bank.
The software was the same. The story was completely different.
Before, the story was: help HR manage behavior in the workplace.
After, the story was: find the message that could become your next regulatory failure—before the regulator does.
One was a departmental tool. The other was protection against a board-level risk at a moment when that risk was on the front page.
When we told it that way, a global investment bank bought it. Not for forty thousand dollars. For one point four million.
And that deal opened the door to nine of the ten largest investment banks.
Risk of Incarceration
I remember sitting on a panel at a conference around that time, right in the middle of the pivot. Somebody in the audience asked about ROI.
Before anyone on the panel could answer, another voice asked: “By ROI, do you mean risk of incarceration?”
The audience chuckled. Uncomfortably.
It was a joke, but it landed because everyone in the room knew it was true. The business case had changed completely. Nobody was buying this technology to save a few hours in HR. They were buying it because the cost of doing nothing had become material—to the institution, and to the people running it.
That is the moment a problem gets bigger. When the question stops being what will we gain if we buy this? and becomes what will happen to us if we don’t?
Read more in Stories That Sell™
Stories That Sell™ is Paul Johns’ forthcoming book on how strategic storytelling creates competitive advantage, customer preference and enterprise value. It introduces the RO40 frameworks: Identity, the Three Question Test, the Message Map, Marketecture and Decision Confidence.
Want to put these ideas to work in your business? RO40’s Stories That Sell™ workshop brings your leadership, sales, marketing, product and customer teams together to build a story that sells. Start a conversation with RO40.



Comments