How to Write an Effective Case Study in 7 Steps

73% of B2B buyers say case studies are the most influential content in their purchasing decisions. Not product sheets, not sales decks. Case studies. People who read them are already in active evaluation mode — they are looking for exactly the kind of solution you offer.

The problem is that most professionals and agencies either publish none at all, or write them so generically that no one is convinced. This guide shows you how to do it properly, in 7 concrete steps.

What a case study actually is (and isn't)

A case study is not a portfolio. It is not a client testimonial. It is not a list of tasks completed.

It is a structured account with four specific elements: context (who the client was and what their situation looked like), the problem (what wasn't working or what they wanted to achieve), the solution (what you actually did and why), and the results (what changed, with numbers where available).

The difference from a standard portfolio entry is this: a portfolio shows what you did; a case study shows how you think and what you can actually deliver. That is what convinces a potential client to reach out — not a list of skills, but concrete proof that you produce results.

Step 1: Choose the right project

Not every project makes a good case study. The best ones share a few characteristics:

• You solved a specific problem, not just completed a brief
• There are measurable results — even partial ones
• The client would allow you to discuss it publicly
• The project represents the type of work you want more of

If you are choosing between multiple projects, pick the one where your contribution was most decisive. A project where you solved a difficult problem with limited resources is often worth more than a large, routine engagement.

Step 2: Gather your materials before writing

Before you type a single word, go back to the project:

• The original brief, emails, proposals submitted
• Results: analytics, reports, screenshots, sales or traffic data
• Client feedback — even informal messages count
• Timelines and approximate budgets, even in general terms if the details are confidential

If you don't have exact numbers, you can still write a credible case study. "Organic traffic grew 40% in the three months after launch" works. "The client reported a noticeable drop in support requests in the weeks following the handoff" works just as well. The rule is simple: don't invent, don't exaggerate.

Step 3: Write a title that says something specific

The title is the first filter. If it's generic, most readers won't continue.

Avoid titles like "Communication project for Company X" or "Website redesign." Use specific formats instead:

• Problem → Result: "How we reduced cost-per-acquisition by 40% for a law firm"
• Concrete number: "+280 leads in 60 days: inbound strategy for a B2B manufacturer"
• Specific challenge: "From zero to 18,000 organic followers in 12 months for a cosmetics brand"

If your title could describe any other project of the same type, it is too generic. The title needs to give the reader a concrete reason to keep reading.

Step 4: Set the scene — context and the problem

This section helps the reader understand who the client was and why the project mattered. Write it the way you would explain the situation to a colleague.

Include:

• The client's sector and approximate size (even generic: "a 30-person manufacturing company")
• What they were trying to achieve
• Why they couldn't do it on their own or with previous solutions
• What was at stake — the real-world consequences of the unsolved problem

Keep it concise. Three or four well-written paragraphs are enough. The goal is for the reader to recognise the client's situation — or see it as similar to a situation one of their own clients faces.

Step 5: Explain your solution in detail

This is where most case studies become too vague. "We managed their social media" or "we optimised the website" says nothing. Write what you actually decided, why you decided it, and in response to what specific situation.

A useful structure:

1. How you set up the work and what your starting approach was
2. What you discovered or understood during the project
3. The specific choices you made and the reasoning behind each one
4. The tools, methodologies, or frameworks you used

People reading your case study aren't just checking that you can do the work. They are trying to understand how you think — because that is what they are actually buying.

Step 6: Show the results with numbers

Results are what turn a good story into a concrete sales tool. Without numbers it remains a story. With numbers it becomes proof.

If you have precise data:

• Use both percentages and absolute values: "from 80 to 230 monthly enquiries (+188%)"
• Always specify the time period: "in the 90 days after launch"
• Separate the direct results of your work from the indirect effects you observed

If you don't have precise data:

• Use qualified estimates: "the client estimated the processing time was cut roughly in half"
• Quote direct client feedback, even if informal
• Describe observable operational changes: "the team stopped handling requests manually"

An honest result — even a modest one — is more convincing than an inflated figure that careful readers will immediately question.

Step 7: Add a clear call to action

Most case studies stop at the results. Readers who are impressed don't know what to do next. That is a missed opportunity every single time.

The CTA doesn't need to be aggressive. Keep it simple:

• A link to your full profile with all published case studies
• An invitation to get in touch for similar projects
• A reference to other case studies in the same industry or with similar challenges

If you've done a good job in the previous steps, the reader is already convinced. They just need to know where to go next.

The complete structure: a checklist

Use this as a reference every time you write a case study:

• Title — specific, with the result if available
• Context — who the client is and what their situation was
• Objective — what they concretely wanted to achieve
• Approach — how you set up the work
• Solution — what you actually did, with the reasoning
• Results — what changed, with data or qualified estimates
• CTA — what the reader can do right now

How long does it take?

A well-written case study takes between 3 and 8 hours of total work — gathering materials, writing, and reviewing. How much depends largely on how well you documented the project while it was underway.

Most professionals put it off not because they lack good projects, but because they lack time or don't know where to start. The result is that they do good work, but very few potential clients ever know about it. On CaseFolio, you can enter your raw project notes and get a structured first draft — in English and five other languages — ready to review and publish. Your profile is public, indexed by Google, and visible to potential clients worldwide.