Day 17: Customer Case Study
The Concept
A customer case study is the most persuasive piece of marketing content most companies never properly produce. It is the only format that combines social proof, concrete results, and authentic narrative in a single document — and it sits at the exact moment in the buying journey when a prospect has moved from interested to deciding. Done well, a case study does not sell your product; it lets a real customer do it for you, in their own words, to an audience that trusts peer experience far more than company claims.
Despite this, most case studies are either never written because no one has time, or written so cautiously — legal approval, customer approval, watered-down numbers — that they end up as polished endorsements with no story in them. The result is a website full of logos and a sales team resorting to vague references to "great customer outcomes" in conversations where a specific number would close more deals.
The bottleneck is almost never the customer relationship or the results. It is the writing. Transforming raw knowledge of what happened into a coherent narrative with a beginning, a turning point, and a measurable end requires a kind of structured storytelling that is genuinely time-consuming to do well.
What makes a case study worth reading
The structural difference between a case study that gets read and one that gets skimmed is simple: the one that gets read starts with a problem the reader recognises. It makes the reader think "that is us" before introducing any solution. The one that gets skimmed opens with a company description and a product name, which tells the reader immediately that this is marketing material and they can safely skim to the numbers.
AI applied to your raw notes can reliably identify the problem frame — the aspect of the customer's before-state that will resonate most with the audience you are targeting — because it has no stake in leading with your product. It will surface the customer's situation first, which is exactly the structure that works.
Numbers are not optional
Vague case studies fail not because they are badly written but because they are unprovable. "Significant improvement in efficiency" is a claim a reader cannot evaluate and therefore discounts. "Reduced their returns processing time from 4 days to 11 hours" is a claim a reader can visualise and compare against their own situation. Even approximate numbers — clearly flagged as approximate — are more useful than no numbers at all.
When you paste your raw notes, include every number you have, however rough. Percentage improvements, time savings, revenue figures, headcount changes, customer satisfaction scores. AI will use whatever is there and flag where precision is missing.
The pull quote as the atomic unit of social proof
Before you finalise any case study, read the pull quotes. A pull quote that surprises you — that captures something true and specific about the customer's experience in a way you would not have phrased yourself — is a signal that AI has found the real story in your notes. A pull quote that sounds like marketing copy is a signal that your notes did not contain enough raw customer voice, and you need to go back to the source: an email, a call recording, or a conversation.
Pull quotes travel. They appear in sales decks, email campaigns, social posts, and website testimonials long after the case study itself is forgotten. Getting three strong ones from a single set of notes is one of the highest-value outputs in this entire programme.
Prompt of the day
Copy this into your AI tool and replace any bracketed placeholders.
Prompt
You are an experienced B2B content strategist who specialises in writing customer case studies that are read because they tell a true story, not because they are polished marketing material. I am going to give you my raw notes about a customer success story — everything I know, in no particular order. Your job is to interview those notes and extract the elements of a full case study. My product or service: [e.g. a data analytics platform for e-commerce retailers] The customer I am writing about: [e.g. Northlight Outdoors — a UK-based outdoor gear retailer with £8m annual revenue and a team of 22] My raw notes about what happened — paste everything you know, including context, conversations, timeline, before and after states, and any numbers you have: [PASTE ALL YOUR NOTES HERE — include emails, call transcripts, Slack messages, numbers, quotes, or anything else relevant] The primary audience for this case study: [e.g. heads of e-commerce at mid-market retailers who are sceptical of analytics tools because previous implementations have been slow and hard to prove ROI on] The format this case study will be published in: [e.g. a 600-word page on our website, plus a one-page PDF version for sales conversations] Produce the following: 1. The before state — two to three sentences describing the customer's situation and problem before they worked with us. Written from their perspective, not ours. 2. The turning point — one sentence describing the specific moment or decision that prompted them to act. 3. The after state and measurable results — what changed, expressed in concrete numbers and outcomes wherever possible. If the notes contain approximate numbers, use them and note they are approximate. 4. Three pull quotes — actual or reconstructed quotes from the customer that capture their experience authentically. Flag clearly if these are reconstructed rather than verbatim. 5. The full case study draft — 550–600 words. Story-first structure: open with the customer's problem, not our product. Introduce our solution only after the reader cares about the problem. Close with the measurable result and what it means for their business. 6. A one-sentence version — for use in sales decks, email signatures, and social posts.
Your 15-minute task
Think of one customer who has had a genuinely good outcome using your product or service — not your most dramatic result, just a real one with at least one concrete number attached. Open your notes, emails, call recordings, or CRM. Dump everything you have about that customer into the notes field without editing or tidying it. Run the prompt. Read the pull quotes section first — those three quotes will tell you whether AI has found the real story in your notes. If a quote surprises you with how well it captures something true, the case study will be worth publishing.
Expected win
A complete, publish-ready customer case study — before state, measurable results, three pull quotes, a 550-word narrative draft, and a one-sentence version for sales use — extracted from your raw notes without a single interview or writing session.
Power user tip
Once you have the draft, send this follow-up: 'Rewrite the opening paragraph of this case study three ways: one that leads with the problem as a statistic, one that leads with a scene from the customer's day before they used us, and one that leads with the result and works backwards. I want to A/B test which opening performs best on our website.' Three openers in 60 seconds is faster than any copywriter.