> ## Content Index
> Fetch the complete content index at: https://www.datadab.com/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Most Customer Stories Never Show the Number Buyers Want
- URL: https://www.datadab.com/blog/case-studies-missing-number/
- Published: 2026-10-15T04:30:00.000Z
- Updated: 2026-10-17T11:54:21.000Z
- Description: Nearly a third of B2B customer stories contain no number, and only 11.3% say how long the win took. What a buyer needs before they will believe yours.
- Author: Amit Ashwini
- Tags: Content Marketing

*Nearly a third of the "case studies" on B2B software sites contain no quantified result at all. They are testimonials with logos.*

We collected 821 customer stories from 226 YC-backed B2B software companies in October for the [case-study index](https://www.datadab.com/research/b2b-saas-case-study-index), and coded how each one presents its result.

The question was narrow: where does the number sit, what shape is it, and does the story say how long the win took?

The answers are less flattering to the category than most vendors would like. They are also the most useful thing I have read on how to write a story that persuades.

Start with the uncomfortable one. 251 of the 821 stories, or 30.6%, carry no quantified result at all. Nearly a third of what the market calls a case study is a quote, a logo and a paragraph of adjectives.

That is not a crime. It is a choice. The buyer simply learns less than the page intends.

![Editorial cover: bold type reading that most customer stories never show the number.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-01-hero-1.png)

![Three pixel grids showing story-hub rates rising from 33.3% at 1 to 10 staff to 90.2% at 200 plus.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-02-story-hub-by-size.png)

## Whether you tell stories depends on your size

Before looking at the stories themselves, look at who publishes them. 271 of the 479 companies, or 56.6%, maintain a story hub. The rate runs from 33.3% at 1-10 employees to 90.2% at 200+.

That is the steepest size ladder in this research programme.

By a distance. Among the companies we studied, a customer-story library is close to a norm for larger vendors and an option for small ones.

When companies do publish stories, the form is far more consistent than the size effect suggests. The shape of a story depends less on who wrote it than on whether anyone decided it needed a library.

Contact-only enterprise vendors run hubs at 67.0%. Proof matters most where sales cycles are longest, and that is also where the buyer has the most to lose by reading a weak story.

![Bar chart of claimed improvement sizes: 52.2% fall in the 51 to 100% bucket and 6.4% claim more than 100%.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-03-percentage-default.png)

## The percentage headline is the default

Of the stories that do quantify a result, the most common format is a percentage. 42.0% of stories headline one, and that rate is clearly ahead of every other metric type, with non-overlapping confidence intervals against the runner-up.

The percentage has become the shorthand for proof. It is easy to scan, easy to compare and easy to remember.

It is also easy to inflate. The median percentage claim in the sample is 70%, and the most common bucket is 51 to 100%. Twenty-two stories claim more than 100%, including one footer figure of 1,300%.

Those outliers are where verification matters most. A claimed improvement above 100% is not impossible, but it is the sentence a careful buyer will want to see the working for, and most stories do not show it.

![A pull quote set large in serif type reading that the sectors that sell measurement quantify themselves least.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-04-irony.png)

## The irony: the sectors that sell measurement quantify themselves least

Here is the finding that should make a few analytics vendors uncomfortable. Analytics companies headline a percentage in 25% of stories and run qualitative-only stories in 50%. Finance is 18% and 40%.

Both sectors sell measurement. Both are the least likely to put a number in the headline of their own customer stories.

The gap is not universal. Sales-software vendors are more likely to run qualitative-only stories at 52.1%, but they also headline a percentage in only 14.6% of theirs, so the pattern is about the form of proof, not a single sector being unusually weak.

Sectors are the vendors' own YC classifications, and the breakdown uses only groups with at least 40 stories, so read the comparison as directional.

If you sell measurement, the buyer will ask you for the number that proves your product works. Put it in the first screen of your own stories before someone else asks.

![Density chart of claimed win sizes, showing a small tail of claims above 100%.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-05-win-distribution.png)

## How big the claimed wins are

Of the percentage claims in the sample, 52.2% fall in the 51-100% bucket. Another 21.2% sit at 31-50%, 15.7% at 11-30%, and 4.6% at 10% or less.

Only 6.4% of percentage claims exceed 100%. That is 22 stories. Small in number, but the largest claims are the ones a buyer is least likely to be able to reproduce, so they are where the reader's scepticism belongs.

A distribution like this is useful for a single reason. It tells you what is normal for your category before you write your own number. A claim of 500% in a story where the cohort median is 70% will be read as unusual, whether or not it is true. If the number is real, the story should show how it was measured.

![Large type stacked: 10x, 3x, 2x and 5x, with the line that a multiplier without a baseline is a number without a denominator.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-06-multipliers.png)

## Multipliers and money

Among 94 stories that headline a multiplier, the median is 6x. The most common claims are 10x (17 stories), 3x (14) and 2x (11).

Currency figures cluster at a few round numbers. The most frequent headline dollar figure is $38M, appearing on 5 stories, followed by $1 billion and $750M, each on 3.

A multiplier with no baseline is a number without a denominator. "10x faster" is the sentence a buyer remembers and the one they are least able to check.

If you use a multiplier, state the before and the after, and name the measure. The extra sentence costs you very little credibility and buys a great deal of it back.

![A near-empty dark panel with the figure 11.3% set on a single hairline rule.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-07-time-to-result.png)

## Time to result is the missing number

Here is the number most stories leave out. Time-to-result is stated on only 11.3% of stories.

Vendors show the win far more often than the wait. The rate barely moves across company sizes. That looks like a habit, not an editorial decision.

For a buyer, the wait is often the decisive question. How long before the first number moved? Did the customer have to rebuild a process, hire someone, or change a tool? A story that answers only the first question gives the champion nothing to take into an internal approval.

If you have the data, state the time to result beside the headline. If you do not, the honest version of the story says so.

![A schematic of a case-study page marking the median first metric at 7.8% and the quarter-page scroll line where 29.5% bury it.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-08-where-number-lands.png)

## Where the number lands

The median first metric sits 7.8% of the way down the main page text, close to the hero. Results are front-loaded on the typical page.

But 29.5% of metric-bearing stories place their first number past the first quarter of the text. Nearly three in ten make the reader work for the first figure.

The fix does not require rewriting the story. Move one quantified result above the first scroll. Keep the narrative for whoever wants it.

![A single unbroken line joining two nodes labelled publishes comparisons and publishes stories.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-09-proof-and-attack.png)

## Proof and attack travel together

Matched against the [comparison-page study](https://www.datadab.com/research/saas-comparison-page-map) of the same companies, 77 story-publishing companies also publish comparison pages. They average 4.8 stories each, against 4.3 for companies that publish no comparison pages.

Companies that argue against rivals also document their own wins. The two habits travel together, though the association is weak and we would not read it as cause.

For a buyer, that matters because a vendor willing to name a rival and show its results is making a checkable commitment. A vendor that does neither is leaving the buyer to do the comparison alone.

![A blocked figure with the name withheld beside the finding that anonymous stories quantify at 78.9% against 69.2%.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-10-anonymity.png)

## Anonymity costs nothing in numbers

Anonymous stories, where the customer name is hidden behind a phrase like "a leading fintech", quantify their results at 78.9%, against 69.2% for named stories.

So anonymity does not make a story less numerical. What it does cost is video. Anonymous stories embed video at 11%, against 22% for named stories. A faceless story stays text.

That is a sample-level comparison, small in places. It describes what these companies do, not what works. It does suggest that a credible anonymous story is viable when a named customer is not available. Anonymous framing appears on only 2.3% of stories, so it is the exception.

![Stacked paper sheets carrying three requirements: a repeatable sentence, a defensible baseline and a stated caveat.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-11-champion-needs.png)

## What a buyer's champion needs from a story

A story is rarely read for its own sake. It is read by a champion who has to carry a decision into a room where somebody else holds the budget and will ask hard questions.

So the story has a second job. It must hand that champion a sentence they can repeat, a baseline they can defend, and a caveat they can raise before anyone else does.

Most stories fail the second job even when they pass the first. The headline percentage is repeatable, but without a baseline or a time frame the champion cannot defend it, and a figure that cannot be defended tends to be quietly dropped from the internal deck.

That is why the missing wait matters as much as the missing baseline. A buyer who knows the win took nine months will plan differently from one who assumes it took a fortnight, and the story is the only place the vendor can make that difference visible.

![Three paper scraps listing what content teams, buyers and researchers should take from the study.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-12-who-this-is-for.png)

## Who this is for

\* *For content teams.*\* Copy the shape, not the numbers. The cohort's most common shape is a percentage headline in the first screen, a story of around 900 words, and video where it is available. The median story runs 921 words, with a quartile range of 594 to 1,324.

\* *For buyers.*\* Read past the headline percentage. Check whether the story states a baseline, a time frame and a measure. If it does not, the claim is a marketing figure, not a finding.

\* *For researchers.*\* The stories were coded by a single reviewer with a 20-story evidence check, which caught and fixed two measurement errors before publication. We have not yet had an independent second coder confirm the coding, so treat the category-level comparisons as descriptive.

![A typewritten method card listing the sample, exclusions, the single reviewer and the missing second coder.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-13-sample-limits.png)

## What the sample does and does not say

The study covers 821 stories from 226 companies, drawn from 2,423 discovered links, across 479 YC-backed B2B software companies. Stories that were PDF-only, behind a login, or rendered only in JavaScript were missed, and 253 domains yielded no fetchable story.

Headcounts such as "5,000 employees" were excluded, because they describe the customer rather than the result. Each company was sampled up to five stories.

These findings describe venture-backed companies at the time of collection. They are not a measure of how well any particular case study converts.

![Four short lines inside a hairline frame: a quantified result, a baseline, the time taken, and the customer name.](https://www.datadab.com/blog/content/images/2026/10/case-studies-missing-number-14-wrap-up.png)

## Wrap-up

I would put one number, one baseline and one date on every customer story a company publishes. A story that persuades a buyer does four things the median story does not. It puts a quantified result near the top. It states a baseline for that result. It says how long the change took. And it names the customer, or says plainly why it cannot.

None of it needs a larger budget. It needs the story to answer the questions the champion will face in the internal meeting, before somebody asks them.

Want to see whether your own stories answer those questions?

Take the story a prospect is most likely to read first and [scan the page for the gaps that decide whether they believe it](https://www.datadab.com/tools/decision-friction-scanner).

Coded by a single reviewer with a 20-story evidence check; category comparisons are descriptive. PDF-only, gated and JS-only story sets are missed; 253 domains yielded no fetchable story.

[Scan your customer-story page](https://www.datadab.com/tools/decision-friction-scanner)