Key takeaways: Customer case studies show business results, but they don’t make buyers question their current products, services or processes. They don’t specify how much old approaches cost customers before they invested in a solution. Without those persuasive numbers, the results read as someone else’s good news. Buyers think what they have is good enough and they don’t see any urgency in making a change.
Customer case studies are a staple for B2B marketing, but many have a numbers problem. They describe customers’ old challenges in vague terms, then get specific about the results. Revenue increased 20%. Downtime dropped 35%. Employees saved 10 hours a week. Those results prove the investment worked, but without numbers showing what the old approach cost, buyers can still decide what they have is good enough.
Why case studies don’t move buyers to change
The problem often starts with the numbers marketers feature. Most focus on what happened after a customer bought a product or service and skip what came before. The results document the outcome, but they don’t say what the customer dealt with before making the change. Buyers see the payoff, decide their own situation is fine and keep doing what they already do. It’s “if it ain’t broke, don’t fix it” complacency.
Most case studies compare the company’s solution with some vague alternative or with nothing at all. But that misreads how buyers make decisions. They need a reason to ditch a system they’ve paid for, trained people on and built processes to support. Without that, buyers’ inertia wins. Research behind the book, “The JOLT Effect,” analyzed 2.5 million recorded sales conversations and found that 40% to 60% of lost deals end in no decision, with the customer choosing to do nothing.
Impressive results create another risk. Challenger, a sales training firm, calls it “expectation overload,” which occurs when prospects don’t believe they can achieve the outcome presented to them. Challenger notes that case studies and results that look unusually impressive can contribute to that skepticism. Showing where the customer started gives buyers context for judging the outcome.
Quantify what the old approach cost the customer
That imbalance shows up first in the challenge section. “The customer wanted to reduce processing delays” identifies the problem, but it doesn’t tell buyers whether those delays ate five employee hours a week or 50, cost thousands of dollars or caused nothing worse than occasional frustration.
When interviewing customers, ask questions that put numbers behind their old approaches. With processing delays, for example, find out how many hours the process required each week. What did those hours cost in employee time? What work did employees postpone because of it? How often did errors occur, and what did each one cost to fix? What happened when volume spiked?
Sometimes the answer is “We never measured it.” The company may not have tracked the old process, or the person you interview may have arrived after the project closed. Ask your sales team for the numbers before you give up. Discovery notes, proposals and the business case that justified the purchase all predate the sale and often include the before-state numbers the story needs. Pull the figures worth chasing from those records, then ask the customer to confirm anything you plan to publish.
Next, pair those answers with the results. “The customer cut processing time by 40%” means more when buyers learn the old process took 25 employee hours a week, adding up to 1,300 hours a year. Make the same connection with other before-and-after numbers, such as error-correction costs falling from $185,000 a year to $48,000 or an approval cycle dropping from 14 days to three.
Here’s the contrast in practice. A conventional challenge paragraph might read, “The customer relied on a manual invoice-matching process that caused delays and frustrated the finance team.” Now quantify the before-state: “The finance team spent 30 hours a week matching invoices by hand. Mistakes sent 12% of invoices back for rework, and every month-end close ran three days long.”
The first version describes a problem. The second quantifies it.
Specific numbers give buyers something they can measure against their own businesses. When they recognize the same wasted hours, unnecessary expenses or recurring problems, they can calculate what their current methods may be costing them.
The numbers work even when they’re high enough that some prospects won’t see themselves in the example. A buyer whose company spends much less time on the problem learns it isn’t costing enough to act on yet, which is useful to know. A buyer who hasn’t counted those hours gets a reason to start. Either way, the figure helps buyers judge whether the problem warrants action.
What if customers won’t approve their cost numbers?
Of course, there’s a catch. Customers approve case studies before publication, and some won’t want their costs made public. Saying a company spent $185,000 a year correcting errors can invite uncomfortable questions about why the problem continued for so long.
In these cases, document the cost without publishing the exact number:
- Use operational numbers. A customer who won’t sign off on “$185,000 a year” may approve “employees spent 25 hours a week correcting errors.” Hours, error rates and cycle times give buyers enough information to make their own calculations.
- Cite credible industry data. Pair the customer’s experience with published research that establishes the financial cost. Keep the customer’s numbers and the industry benchmark separate so that buyers know where each came from.
- Describe a pattern across clients. “Manufacturers usually come to us losing 15 to 20 hours a month to unplanned downtime” gives buyers a meaningful benchmark without attributing the number to a specific customer.
- Anonymize as a last resort. Named customers make a more persuasive case than anonymous ones, which is why they’re worth pushing for. When a customer will share the cost only without the name attached, a specific description can preserve useful context. “A $2 billion telecommunications manufacturer with six plants” lets buyers judge the scale and relevance even when they can’t confirm the company’s identity. Use this approach only when naming and quantifying can’t coexist.
How you ask about the old approach can also affect whether customers approve those numbers. Ask why the previous method worked for the company when it adopted it and what changed. Maybe the business expanded, transaction volume increased or customer expectations changed. That context explains how a reasonable business decision became costly without suggesting the customer made a poor decision in the first place.
Some customers still won’t approve enough detail to quantify the old approach. Don’t force it. The goal is to look for persuasive numbers in every customer story instead of overlooking them by habit.
Don’t invent a cost of doing nothing
Not every customer left an expensive or broken system behind. Some had a process that worked until a merger, a discontinued platform, new regulations or business growth gave them a reason to change. Forcing a cost-of-doing-nothing argument onto those stories manufactures urgency that buyers can see through. If the customer didn’t have a measurable cost before making the change, don’t invent one.
Give buyers a reason to act
Getting found only gets a case study so far. Once buyers find it, the story still has to give them a reason to act.
We previously looked at how clear, extractable information can help case studies appear in AI search results. Quantifying the old approach helps there, too. Before-and-after numbers give AI systems comparable facts to identify and use, while a vague challenge section gives them nothing to work with. The same specificity that persuades buyers makes case studies legible to AI.
A 40% improvement sounds impressive, but buyers have to believe it justifies the disruption of changing. They may already believe another product, service or process would work. What they haven’t calculated is how much their current approach costs them every week. Provide those numbers, and your case study gives them a reason to stop settling for good enough.
Check your last five case studies
Review the last five case studies your company published and count how many numbers each one includes about the customer’s old method. Look for hours lost, error rates, downtime, cycle times, costs or other measures that show what the problem meant to the customer before the solution.
If you find few or none of those numbers, you’ve identified a gap your team can start addressing with its next customer interview. Ask writers to spend as much time quantifying the customer’s starting point as they do documenting the results.
Frequently asked questions
Include results and numbers that quantify the customer’s previous approach. Labor hours, error rates, downtime, cycle times and costs help buyers see what similar problems may cost their businesses.
The cost of inaction shows what continuing with an existing product, service or process costs a customer. Quantifying that cost can give buyers a reason to consider making a change.
Ask how much time it required, what problems occurred, how often they happened and what they cost. Then pair those numbers with the results the customer achieved.
Use operational measures such as hours, error rates, downtime or cycle times. You can also cite credible industry data, describe patterns across customers or anonymize the case study when appropriate.