# Should You Publish a Customer Case Study Before You Have Repeatable Results?

> Publish an early customer case study when it documents a real problem, bounded work, and honest evidence without presenting one outcome as typical.

By buildpurdue Team · October 6, 2026 · 5 min read

Source: https://www.buildpurdue.org/blog/publish-case-study-before-repeatable-results

---

Yes, you can publish a customer case study before you have repeatable results, but only if you write it as evidence from one situation rather than a promise about every customer. The useful question is not whether the story sounds impressive. It is whether a skeptical buyer can tell what happened, what you did, and what the result does not prove.

## Key takeaways

- Publish early when the customer problem, scope, and observed change are specific enough to verify.
- Treat one customer as a useful example, not evidence that the result is typical.
- Put the baseline, time period, customer role, and limits beside every important claim.
- Get written approval for the customer name, quote, numbers, and any logo before publishing.

## What does the case study need to prove?

Suppose a founder has run a three-week pilot with a small operations team. The champion says the product saved time, but there is no clean revenue number and no second customer yet.

That is enough to write a useful case study if the founder can document the original workflow, what changed during the pilot, and the evidence the customer is willing to stand behind. It is not enough to write “companies save 40% of their time” unless the founder has a defined baseline, measurement period, sample, and support for that broader claim.

The [FTC’s guidance on endorsements and testimonials](https://www.ftc.gov/news-events/topics/truth-advertising/advertisement-endorsements) says testimonials must be truthful and not misleading. It also warns that an unrepresentative testimonial can mislead if readers are not told what they can generally expect. That is a good startup rule even when the page is a sales asset rather than a paid advertisement.

## Write the customer’s situation before your solution

The reader is trying to decide whether the example resembles their own business. Start with the customer type, role, workflow, and constraint. Explain what happened before the product was involved and why the problem mattered enough to change.

Then describe the work precisely. Say whether the pilot was paid, how long it ran, which users participated, what was manual, and what the customer actually used. A case study that hides the founder’s hands-on work can make a one-off service look like a repeatable product.

The [First 10 guide to B2B case studies](https://first10.workwithmohit.com/blog/b2b-case-study-structure/) recommends showing the situation, constraint, work, outcome, and limits. That structure helps a buyer evaluate relevance instead of scanning for a logo and a large percentage.

## Separate the observed result from the bigger claim

Use a small evidence table while drafting:

| Claim | Evidence to show | What it does not prove |
| --- | --- | --- |
| The customer used the product repeatedly | Usage record and dates | That every customer will use it the same way |
| A workflow became faster | Defined before-and-after measure | That the product caused every business improvement |
| The customer extended or paid | Invoice, renewal, or written confirmation | That the business has repeatable demand |

This distinction matters because a single case can be informative without being statistically generalizable. A [2025 BMJ Medicine guide to case studies](https://bmjmedicine.bmj.com/content/4/1/e001623) makes the same point: one case can provide practical insight, but it does not represent the wider world by itself.

Use language that matches the evidence. “In this pilot, the team reduced the review step from two hours to one” is different from “the product cuts review time in half.” The first is an observed result with a defined scope. The second sounds like a typical outcome that needs broader support.

## Get approval before you polish the story

Do not wait until the final draft to ask whether you can publish it. Confirm the customer’s preferred name, title, company description, logo, quote, numbers, and publication channel before you build the page around them.

If the customer needs anonymity, keep enough context for the reader to judge the example without making the company guessable. If the customer received a discount, free access, or another benefit in exchange for the story, disclose that relationship where a reader will see it. Do not edit a quote into a stronger claim than the customer approved.

If the customer cannot approve the evidence, publish a learning note without identifying them or keep the material private for sales conversations. A case study is not worth damaging trust with the person who gave you the evidence.

## When should you wait?

Wait when the only evidence is a compliment, a demo, a founder estimate, or a result you cannot reproduce from the customer’s records. Wait when the customer is still disputing what changed. Wait when the draft depends on a number with no baseline or period.

You should also wait if the story is mainly trying to fill a marketing calendar. Google’s [people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) asks whether a page offers original value, clear expertise, and enough information to help the reader. A thin success announcement gives the reader less than an honest account of a bounded experiment.

## FAQ

### Do I need a famous customer?

No. A small customer with a specific problem and credible evidence is more useful than a recognizable logo with vague claims.

### Do I need exact revenue numbers?

No. You can use a defined operational measure, a customer-approved qualitative result, continued usage, a paid extension, or another concrete behavior. Label what you know and leave out what you cannot support.

### Is one case study enough to change the product roadmap?

No. Use it to generate a sharper question or sales hypothesis. Compare it with later customers before treating the pattern as a product rule.

## Wrap up

Publish the case study early if it helps a buyer understand one real customer situation and the evidence behind it. Keep the scope narrow, show the limits, and let the reader distinguish an observed result from a promise.

Before publishing, ask a skeptical teammate to mark every sentence with one of three labels: observed, inferred, or claimed. Rewrite or remove anything that cannot earn its label. If you want peers to pressure-test the evidence and the next customer experiment, bring the draft to the [buildpurdue cohort](/cohort).