How to Write Customer Case Studies That Actually Sell

Every buyer asks the same silent question before they sign: has anyone like me done this and been glad they did? Your website cannot answer it, because everything on your website is something you wrote about yourself. A good customer case study can, because it lets a prospect watch someone with their problem, their size and their doubts reach an outcome they want.

Most case studies fail at this. They read like press releases: a paragraph of praise for the vendor, a vague claim of improvement, and a logo. This guide covers the whole job, from choosing the customer and getting permission to running the interview, structuring the page, handling numbers honestly and putting the finished piece where deals are actually decided.

Key takeaways

What a case study is actually for

A case study does one thing: it reduces perceived risk for a buyer who is already interested. It is not for awareness, and it is rarely the reason someone first contacts you. It matters later, when the prospect is comparing options, justifying the choice to a boss or a partner, or quietly wondering whether you can deliver for a business like theirs.

That framing changes what you write. The buyer needs to recognise themselves, believe the starting point, see a credible path and weigh a concrete result. The vendor is a supporting character; the customer is the hero and the product is the tool they used. Once the story is mostly about you, buyers stop identifying with it.

Choosing the right customer

The instinct is to feature your best-known customer. Resist it. The right subject is the one whose story will persuade the buyers you want next, and three tests help you find them.

A clear before and after

The strongest stories have a visible change: a process that was slow and is now quick, a pipeline that was invisible and is now tracked, a problem that was recurring and has stopped. If the customer cannot describe how things were before, there is no story to tell. Quiet, steady satisfaction is real and valuable, but it does not make a compelling page.

A fit with the segment you want more of

Look at the customers you would happily clone and pick from there. A case study for a type of customer you do not want to win more of is a liability, because it will attract exactly the wrong enquiries. If your growth plan is mid-sized service businesses, a story about a one-person shop, however warm, does not help.

A willing champion

You need one person on the customer side who is enthusiastic, articulate and has the standing to approve publication. Without them the project stalls in someone’s inbox. The ideal champion is the person who felt the problem most, because they tell it best.

Asking permission and agreeing what is published

Permission is a two-step conversation, and most trouble comes from collapsing it into one. First you ask whether they would be open to being featured. Only after they say yes do you agree the details, in writing, before you draft anything.

How to ask

Be specific and make it easy to say no. Explain what it involves, what it is for and that they approve everything before it goes live. Do not ask during a problem.

What to agree in writing

An email reply is enough for most businesses, as long as it is specific. Ask for a yes or no on each item separately, because a customer may be happy to be quoted but not to share revenue figures.

• Company name. Named, or described by industry and size only.
• Logo. Whether you may display it, and where.
• People. Whether the champion’s name, job title and photo may be used.
• Numbers. Which figures may be published, and in what form: exact, rounded or as a range.
• Quotes. That quotes will be approved as written, and that any edit goes back to them.
• Duration and withdrawal. How long you may use it, and how they can ask for it to come down.

Keep that email somewhere you can find it in a year. When someone asks, months later, whether the customer agreed to the logo on the sales deck, you want a one-minute answer.

The interview: eight to ten questions

The interview produces everything: the narrative, the numbers and the quotes. Ask for permission to record it, take notes anyway, and keep it to thirty to forty-five minutes. Ask open questions and let the customer talk; the best material is usually an answer to a follow-up such as “can you say more about that?”

Run the questions in chronological order. People tell stories in sequence, and the order gives you the finished structure for free.

An interview script

• 1. Tell me about your business and your role. Establishes the snapshot: what they do, how big they are, what you are responsible for.
• 2. What was the situation before you started looking? Get the problem in their words, including how it showed up day to day.
• 3. What was it costing you? Time, money, missed work, stress. Ask for specifics, not adjectives.
• 4. What had you tried before? Spreadsheets, another tool, doing nothing. This is where buyers recognise their own workarounds.
• 5. Why did you choose us? The honest answer is often not the one you expect. Listen for the decision criteria other buyers share.
• 6. How did the first weeks go? Setup, hurdles, what they had to do. Prospects want to know the effort involved.
• 7. What has changed, in your numbers? Ask for the measure, the starting point and the period it covers.
• 8. What surprised you? Often the most quotable answer, and the most believable.
• 9. What would you tell someone in your position who is unsure? This produces the closing quote.
• 10. Who else should we talk to, and is there anything you would like us to leave out? Finds the next candidate and surfaces sensitivities early.

Structuring the case study

The outline below is an illustrative template with placeholders. Every bracket is something to fill from your own interview; none of the content is a real customer or result.

Write the headline last

The headline should carry the result, not your product name. A headline such as “How [Company] Cut [Problem] in [Period]” tells the buyer what they would get; “[Company] Success Story” tells them nothing. If you have no headline-worthy number, use the change instead: what was impossible before and is routine now.

Numbers: use real ones and show your working

Numbers make a case study persuasive, and fabricated or fuzzy numbers make it dangerous. The rule is simple: only publish figures the customer has confirmed, and always say what they measure.

• Name the measure. “Response time” could mean first reply or full resolution. Say which.
• Give the starting point and period. “From [start] to [end] over [period]” lets the reader judge the size of the change.
• Never round in your favour. Exact or rounded down is safe; rounded up is a claim you may have to defend.

If you do not have numbers

Many strong stories cannot be reduced to a figure, especially for small customers who do not track their own metrics. That is fine. Tell it qualitatively and honestly: what the customer no longer does, what they now see that they could not before, how their week changed. Let their direct quotes carry the weight.

What you must not do is invent a number to fill the gap, or ask the customer to estimate a percentage they have no basis for. A vague but true story beats a precise but doubtful one, and a reader who catches one inflated claim will discount the rest.

Length and formats

Write the full version once, then cut it into the formats your sales process actually uses. Most teams stop at a single long page and then wonder why nobody uses it.

• One-page PDF for emails and proposals: snapshot box, one quote, one call to action.
• Web page as the fullest version, with detail and numbers.
• Short video only if the champion is comfortable on camera.
• Social cut-downs of a quote or number, once approvals cover social use.
• One sales-deck slide: headline, snapshot, quote.

Where case studies belong in the funnel

A case study sitting in a menu called “Resources” works for the few people who go looking. The leverage comes from placing it at the points where a buyer is deciding.

• The pricing page. Visitors here are weighing the cost. A relevant story next to the price answers “is it worth it?” at exactly the right moment.
• Proposals. Include the story that most resembles this prospect. It is evidence for the person who has to justify the choice internally.
• Follow-up emails. After a call, send the one relevant story with a sentence on why you chose it, rather than a link to everything.
• Sales calls. Reps should be able to say “a company a lot like yours had this problem” and have the page ready to send.

Keeping a case-study pipeline

Run a small standing pipeline rather than occasional heroics.

• Ask after a good result. The best moment is when the customer has just noticed a win, not at renewal.
• Review candidates quarterly. Once a quarter, look at recent wins, reviews and check-ins and add two or three names.
• Track stages. Candidate, asked, agreed, interviewed, draft sent, approved, published. Most stalls happen at draft approval, so chase it politely.

Working with a customer’s approval process

In larger organisations, a case study passes through marketing, legal or procurement, and the champion may have no authority to approve. Plan for it.

• Ask early who needs to approve, and send a draft that is close to final so the reviewer edits rather than writes.
• Expect cuts to names and numbers. Have a version that works anonymised, described as “a regional [type of business]”.
• Accept a no. Ask whether a private reference call would be acceptable instead.

Regulated industries

In finance, healthcare, legal and similar sectors, involve the customer's compliance contact early, avoid outcome claims you cannot document, never include personal data about their clients, and have your own reviewer check the final copy. Rules vary by country and sector, so treat this as a prompt to ask, not as legal guidance.

Measuring whether it works

Case studies are easy to produce and hard to attribute. Page views tell you something, but the real question is whether they changed deals. A few honest measures:

• Use by sales. How often a rep attaches or links one in follow-ups and proposals. An unused asset is a failed asset.
• Deals where one was shared. Compare win rates cautiously: deals that get a case study are not a random sample, so treat any gap as a hint, not proof.
• Ask the buyer. The simplest influence measure is a question in your onboarding or win conversation: “which of our materials did you read before deciding?”

Common mistakes

• A vendor-centric story. If the first paragraph describes your product rather than the customer’s problem, readers leave.
• No numbers and no detail. “Improved efficiency” is not a result. Either find a measure or tell the qualitative story properly.
• Unapproved claims. A quote edited for style or a number rounded up can end a relationship and a reference.
• No call to action, or anonymous “Company A” stories. A reader with no next step has nowhere to go, and generic labels look invented.

How Scalry handles this

Scalry does not have a case-study builder, and it does not write the story for you. What it gives you is the surrounding system, so the pipeline above is easier to run from the records you already keep.

• Finding candidates. The reputation tools let you send review requests by email, SMS or WhatsApp, keep reviews from your connected sources and respond to them. Enthusiastic reviewers and their quotes are a natural pool of candidates.
• Tracking the pipeline. In the CRM you can tag contacts, for example “promoter” or “case-study-candidate”, keep custom fields for approval status, and use the timeline of conversations to keep the permission email and notes in one place.
• Using the finished piece. Proposals are built from blocks, so a case study can be included as a block. Funnels and landing pages can host the case study page, and the blog is where longer-form proof can live. Reviews can also be shown on your website with a widget, next to the long-form story.

The honest scope: Scalry keeps the process organised and the proof close to where deals happen. The interview, the writing and the customer’s agreement are still yours to earn.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Which three customers would we most want to clone? Those are your first candidates.
• Do we have a written yes for every logo, name and number we already use? If not, fix that before producing anything new.
• Can each story be told with a measured result, or honestly without one?
• What do buyers say they read before deciding? If you have never asked, start.

If you cannot answer the first three, you are not ready to choose between Scalry and your current proof yet — you are still deciding what you need, which is a cheaper problem to solve first.

A 30-day plan to get started

In the first week, shortlist five candidates and send the short ask to the best match. In the second, confirm permissions in writing and run the interview. In the third, draft the page from the template and send it for approval with every number and quote marked. In the fourth, publish, cut a one-page PDF and a slide, and add the story to your pricing page, proposal template and follow-up emails. Then ask your next three customers which materials they read.

Frequently asked questions

What is a customer case study?

A customer case study is a structured account of how a real customer faced a problem, what they did about it and what changed. It works as a sales asset by letting a prospective buyer see someone like them succeed, with enough detail to judge whether the same result is plausible for them.

How long should a case study be?

The full web version can run to roughly six or eight hundred words. The PDF, sales slide and email excerpts should be much shorter, built around a headline with the result, a snapshot box and one strong quote. Shorter assets get used by sales teams; long ones get skipped.

How do I ask a customer to be featured?

Make a specific, low-pressure request after a good result. Explain that it takes a short conversation, that they will approve the draft, and that saying no is fine. Once they agree, confirm in writing exactly what you can publish: name, logo, numbers, quotes and where it can be used.

What if I do not have numbers for the results?

Tell the story honestly with qualitative outcomes and direct quotes: what changed in the customer's week, what they can now see or do. Do not invent a figure or ask the customer to guess a percentage. A true, specific story is more persuasive than a doubtful statistic.

Can I publish a case study without naming the customer?

Yes, if the customer prefers it, but be open about it by describing the business by size and industry. Anonymous stories are less persuasive than named ones, and generic labels such as Company A look invented. Ask whether a named version with fewer figures would be acceptable first.

Where should I use case studies?

Place them where buyers are deciding: next to pricing, inside proposals, in follow-up emails after sales calls and on landing pages aimed at the same type of customer. Send the story that most resembles the prospect rather than a link to the whole library.

How do I know if case studies are working?

Track how often sales uses them, which pages get read and which stories were shared in deals you won, but treat comparisons cautiously because those deals are not a random sample. The simplest direct signal is to ask new customers which materials they read before they decided.