Customer Case Study Writer

Why this prompt works

The task clarity score is 60 because the prompt asks for a Challenge-Solution-Results structure but doesn't quite specify what 'good' looks like in each section. Despite that, the prompt holds up because the per-section word counts (200 each) and the explicit '3 quantified results' rule produce a case study that's structurally sound. The framework itself does most of the work; Challenge-Solution-Results is the format every B2B reader expects, and forcing the model into it stops it from writing testimonials disguised as case studies. The 'letting the results speak' tone rule and the warning against 'reading like an ad' are the small instructions that distinguish this output from a sales page in disguise.

When to reach for it

• You have a real customer outcome to document and want a structured first draft you can fact-check rather than write from scratch.
• You're publishing a case study library and want consistency in length and structure across multiple stories.
• You're sharing a win story internally with sales and want the format to mirror what the customer-facing version will look like.
• You're writing an early case study with limited customer cooperation, and need a draft to send for their review and quote approval.

How to customise it

Specifics in the input drive specifics in the output. 'Helped them save time' produces a generic study; 'helped them reduce monthly close from 9 days to 3 days' produces something the reader can verify. The customer details (industry, size, product used) shape the snapshot sidebar; if you don't have a real customer yet but want a template draft for review, use placeholders so they're obvious. For B2C case studies, drop the company-size sidebar field and replace with a 'use case' summary.

What good output looks like

A 600 to 800 word case study with a snapshot sidebar at the top, then Challenge / Solution / Results sections (roughly 200 words each), three direct customer quotes with name and title placeholders, and a closing 'What's Next' paragraph. The three quantified results are usually the section requiring most editing because they need real numbers, not placeholder ones.

Watch out for

The model can pad the Challenge section with tangential context that wasn't actually the problem the customer solved. Re-read the section and cut anything that doesn't directly motivate the solution they ended up choosing. The three quantified results sometimes include placeholder metrics ('43%' is a model favourite); replace with the actual numbers from the customer engagement before publishing. The synthetic quotes also need real-customer approval before going live; treat them as draft questions to ask the customer, not as final copy.