Every case-study template you have ever seen is built around a number. The headline is "How Acme cut onboarding time by 62%," the pull-quote is "$400K in recovered revenue," and the whole structure assumes the customer will hand you a before-and-after metric you can put in a big bold font. Then you sit down with the customer who agreed to the case study, ask for the number, and get the answer that breaks the template: "We can't share that." Sometimes it's legal or procurement blocking financials, sometimes the customer never measured it, and sometimes the metric exists but it's a competitive secret. Whatever the reason, you are now holding a willing reference and an empty results box.
The instinct is to either abandon the case study or invent a soft number to fill the hole. Both are wrong. A case study without hard metrics can still be one of the most persuasive assets you own — but only if you stop trying to fake the missing number and instead build persuasion out of the material the customer will give you: specificity, sequence, and stakes. This guide is about how to do that deliberately.
Why the missing number feels fatal — and isn't
A metric is persuasive because it does two jobs at once: it proves the outcome was real, and it lets the prospect estimate their own likely return. "62% faster" is credible and portable — the reader can map it onto their own situation. Losing the number feels like losing both jobs at once, which is why founders panic and either pad the copy with adjectives or quietly drop the project.
But the number was never the only way to do those two jobs. Credibility can come from detail a fabricator wouldn't know to include. Portability can come from a situation the prospect recognizes as their own. A prospect reading "we went from three people manually reconciling exports every Friday to nobody touching it" does not need a percentage to understand the stakes — they are already doing the math in their head, and the math they do themselves is more convincing than the number you'd have printed. The missing metric is a constraint, not a disqualification.
First, find out which "no" you're dealing with
"We can't share numbers" is not one answer, and the right move depends on which one it is. Ask a clarifying follow-up before you redesign the whole case study.
"Legal/procurement won't let us publish financials." This is the most common no, and it is narrower than it sounds. The customer often can share operational and time-based facts even when revenue and cost are off-limits. Headcount reassigned, hours saved per week, tickets closed, cycles eliminated — these frequently clear review when a dollar figure never would. Ask specifically: "Understood on the financials — are operational details like time or headcount okay?"
"We never actually measured it." Here the number doesn't exist, and no amount of asking will produce it. Do not push the customer to estimate a figure they'll later feel was invented — that puts your credibility on their guess. Instead pivot entirely to the before/after narrative, which they can describe from memory honestly.
"That number is a competitive secret." The metric exists and is impressive, but publishing it would tell the customer's rivals something. Sometimes you can rescue it as a relative figure — "cut it by more than half" instead of the exact percentage — which often passes when the precise number won't. Offer that trade explicitly; customers who reflexively say no to a hard figure will frequently approve a directional one.
Knowing which no you have tells you whether to hunt for a softer metric, drop metrics entirely, or negotiate a directional version. Never assume; the follow-up question takes thirty seconds and changes the entire structure.
Build the case study out of what you have instead
Once you've accepted there's no headline number, you replace it with three things the customer can give you honestly. Together they carry more weight than most founders expect.
1. Specificity — the concrete detail a lie couldn't produce
Vague praise reads as invented; specific process detail reads as lived. Instead of "ProofShow saved us a huge amount of time," you want "Every Friday afternoon two people used to copy testimonials out of email threads into a spreadsheet and reformat them by hand — now that step doesn't exist." No number, but nobody doubts it happened, because fabricated praise is generic and this is not. The tell of a real story is the detail that serves no purpose except being true.
Interview for these details deliberately: ask what the exact task looked like before, who did it, how often, and what changed the day they switched. The answers become your proof.
2. Sequence — the before, the trigger, and the after
A case study without a metric still needs a shape, and the shape is narrative: what was breaking, what made them act, what changed. This is the same before-and-after structure that makes a transformation legible — the prospect follows the arc and recognizes their own "before" in it. The trigger moment matters most: "the third time we lost a testimonial in an email thread, we decided that was enough" tells a prospect exactly when they should act, which is often what a case study is really selling.
3. Named stakes — who felt the pain and what it cost them in effort
Numbers quantify stakes, but so do people and consequences. "Our head of marketing stopped chasing customers for quotes and got that afternoon back" names a role, a behavior, and a cost the prospect can feel. When you can't say how much money moved, say who stopped suffering and what they did instead. A prospect in the same role reads it as a message addressed to them.
Use the customer's own words as the proof
When you don't have a number to anchor the case study, the direct quote does the anchoring instead — which makes getting the quote right more important, not less. A specific, in-their-voice line like "I used to dread Fridays because of this and now I genuinely don't think about it" carries conviction a metric can't. Pull these verbatim from the interview; don't paraphrase them into marketing language, because the slight roughness of real speech is part of what signals authenticity. If the customer approved the case study but you want the strongest possible pull-quote, it's worth going back for explicit sign-off on the exact wording so the line you feature is one they'll stand behind.
What not to do
Don't invent a soft number. "Saved dozens of hours" when nobody counted is a fabrication dressed as modesty, and if the customer reads it and doesn't recognize it, you've damaged the relationship and the asset.
Don't pad with adjectives to hide the gap. "Transformative," "game-changing," and "incredible" are what founders reach for when the number is missing, and prospects read them as exactly that — filler covering an absence of proof. Specific beats superlative every time.
Don't bury the story waiting for a metric that isn't coming. A published, number-free case study built on real detail outperforms a perfect one that never ships because you're still waiting on a figure legal will never approve.
The takeaway
A customer who won't share numbers has not refused you a case study — they've refused you one template for it. Find out which "no" you're dealing with, harvest the softer operational facts they can share, and build the piece out of specificity, sequence, and named stakes instead of a headline figure. Done well, the prospect fills in the number themselves, and the estimate they make is more persuasive than the one you'd have printed. The metric was never the proof. The detail was.