- 1 Ask sales which objections stall deals
- 2 Pick a customer with a clear before/after
- 3 Run a 30-minute interview
- 4 Write it and get customer approval
- 5 Make web, PDF and quote versions
- 6 Tag by industry and objection in CRM
Prospects believe other customers more than they believe your marketing. A good case study shows a buyer that someone like them had the same problem, chose you, and got a result. Most small companies have happy customers and no stories about them. A simple, repeatable process turns those relationships into proof that sales can send exactly when a deal needs it.
Why it works
Buyers are trying to reduce risk. A story from a company like theirs shows the product working in a similar setting, which convinces more than any claim from the seller. Specific details, such as who used it, what changed and the customer’s own numbers, make the story hard to wave away.
Timing matters as much as the story. When sales sends it the moment an objection comes up, the prospect gets evidence for the exact doubt they raised, from someone with no reason to oversell.
How to do it
- Ask sales what they need. Find out which objections stall deals and which industries or company sizes they sell to most. Choose customers whose stories answer those objections.
- Pick customers with a clear before and after. Look for accounts that renewed, expanded or sent praise to support. A visible change in how they work matters more than the size of their logo.
- Make the ask easy. Explain that it is a 30-minute call, that you will do all the writing, and that they approve everything before it goes live. Offer something in return, such as a link to their site or a feature in your newsletter.
- Interview for specifics. Ask what life looked like before, what they tried first, why they chose you, how rollout went, and what has changed. Ask for their own numbers and use only figures they confirm.
- Write a simple story. Use the structure of situation, problem, solution and result. Lead with the result in the headline. Use direct quotes from the interview, with their approval.
- Make versions for each use. Create a web page, a one-page PDF for sales, two or three quotes for the website and a short paragraph for emails.
- Put it where deals happen. Tag each case study by industry, size and objection in your CRM or sales folder so reps can find the right one in seconds.
Example
A B2B invoicing tool keeps losing deals with construction firms who doubt it can handle staged payments. The team asks a mid-sized builder that has used the product for a year to share its story. In a half-hour call, the finance manager describes how she used to chase payments by spreadsheet, why she switched, and how many hours her team now saves each month by her own estimate. The writer turns it into a one-page story, the customer approves it, and sales attaches it whenever a construction prospect raises the staged-payment concern.
Metrics to track
- How often sales sends each case study, from your CRM or document tracking.
- Win rate on deals where a case study was shared, compared with similar deals where none was.
- Coverage of top objections and segments: how many have at least one matching story.
- Visits and demo requests from case study pages on your website.
When it backfires
- Vague results. “They saw great improvements” convinces no one. Without a concrete outcome, the story reads like an advert.
- Publishing without approval. Sharing details or figures the customer did not sign off on can end the relationship.
- Stories nobody uses. A case study buried on a resources page and never mentioned by sales does very little.
- Only big logos. If every story features a large company, smaller prospects assume you are not built for them.
Questions people ask
What if the customer will not let us use their name?
Offer an anonymised version that describes the company by industry and size. It carries less weight than a named story, but it still answers the questions buyers ask and many customers agree to it more readily.
How long should a case study be?
Long enough to cover the problem, the change and the result, and short enough to read in a few minutes. A one-page version for sales and a slightly longer web version is a practical pair.
How often should we publish new case studies?
Pick a pace you can keep, such as one every month or two. Fill gaps first, like an industry or an objection with no story yet, before adding more stories of the same kind.