Case Study Creation: The Situation-Assessment-Approach-Results Formula
Every engagement is marketing content. Not as a secondary benefit — as a primary reason to deliver excellent work. Here's the formula that turns client results into your most powerful sales tool.
Two months after wrapping an engagement with a manufacturing company, I asked the partner who delivered the work to write a case study. She stared at me like I'd asked her to write a novel. "I wouldn't even know where to start," she said. "It was a complex engagement. There were so many moving parts."
That complexity was exactly the problem. She'd lived inside the engagement for months. She knew every nuance, every pivot, every late-night problem-solving session. And all of that detail made it impossible for her to see the story clearly.
Because a case study isn't a project report. It's not a summary of what happened. It's a story — a specific kind of story with a specific structure designed to do one thing: help a future buyer see themselves in your past client's situation and believe that similar results are possible for them.
The formula is four steps. It works for every engagement, in every industry, at every scale. And it should be started on Day 1 of the engagement — not two months after it ends, when the details have faded and the client has moved on.
Step 1: Situation
Who Was the Client and What Were They Facing?
Start with context. Who is this organization? What industry? What size? What was the challenge they came to you with? And — critically — what had they already tried before coming to you?
The "what had they tried" element is more important than most people realize. It establishes that the problem wasn't simple. Smart people had already attempted to solve it. Internal initiatives had already been launched. Maybe another consulting firm had already taken a crack at it. Nothing worked. That context makes your eventual results dramatically more impressive.
Be specific. "A mid-sized company facing operational challenges" is useless. "A $180 million auto-parts manufacturer losing an estimated $3 million annually to project failures, after two internal reorganizations and a failed ERP implementation" — that's a situation a reader can feel. Anonymize if you need to, but don't strip out the details that make the story real.
The situation section does one job: it makes the future buyer say "that sounds like us."
Step 2: Assessment
What Did the Diagnostic Reveal?
This is where your methodology does the talking. What did the diagnostic assessment uncover? What were the scores? Where were the critical gaps? And — here's the crucial part — what was the quantified cost of those gaps?
The assessment section serves a dual purpose. First, it demonstrates the rigor of your diagnostic process. You didn't walk in with a pre-packaged solution. You assessed. You measured. You discovered things the client didn't know about themselves. Second, it establishes the financial baseline that makes your results meaningful. "We improved their process maturity" is vague. "Their initial assessment score was 35 out of 100, and the gaps in three critical areas were costing approximately $3.2 million annually" — that's a foundation for a compelling results narrative.
Include the client's reaction to the assessment. Did the CEO express surprise at certain findings? Did the data contradict internal assumptions? These moments of revelation make the story human. A CFO who assumed their project management was "pretty good" discovering that their maturity score puts them in the bottom quartile of their industry — that's a scene, not a data point.
"Don't use definitions. Use stories. A case study that says 'we improved their maturity score from 35 to 72' is interesting. A story about how a CEO discovered she was losing millions to a problem she didn't know she had — that's compelling."
Step 3: Approach
What Did the Engagement Involve?
This section describes what you actually did — but it needs to be written from the client's perspective, not yours. The buyer reading this case study doesn't care about your internal project plan. They care about what the experience was like for the organization going through it.
Cover three dimensions:
What areas were addressed. Which gaps from the assessment became the focus? Why those and not others? The sequencing decision matters — it shows strategic thinking, not just execution. "We prioritized the three gaps with the highest financial impact, starting with the one that had the shortest path to measurable results."
How the work was structured. Was it a 12-week sprint? A phased approach over six months? Ongoing advisory? The structure tells the future buyer what to expect from their own engagement. It makes the commitment tangible.
What the client team experienced. Did their people participate? Were there workshops, training sessions, collaborative working sessions? How much of their team's time was required? This is the section that addresses the department head's unspoken concern: "is this going to disrupt everything we're already doing?"
Keep this section concise. It's the bridge between the problem and the results. The reader shouldn't get lost in methodology details — they should understand enough to believe the approach was rigorous and to picture themselves going through a similar process.
Step 4: Results
What Measurably Changed?
Numbers. You need numbers. "The client was very satisfied with the engagement" isn't a result. It's a feeling. "The client's maturity score increased from 35 to 72. Annual project failure costs dropped from $3.2 million to $1.1 million. Time-to-market for new products decreased by 40%." Those are results.
Include the timeline. How quickly did the results materialize? This matters enormously in professional services because the fear of long, nebulous consulting engagements is universal. "Within 90 days, the three priority areas showed measurable improvement" is a powerful sentence that directly addresses the buyer's unspoken concern about how long this will take.
And then add the client's voice. A direct quote from the decision-maker — not a testimonial about your team being great, but a quote about the business impact. "We didn't just improve a score. We identified $2.1 million in recoverable value that we didn't know existed." That's a quote that sells.
The results section should make the financial case implicitly. If the client's gap was costing $3.2 million and your engagement cost $200,000 and recovered $2.1 million in the first year, you don't need to spell out the ROI. The reader can do that math instantly — and self-calculated ROI is always more convincing than stated ROI.
The Operational Discipline: Write It in Two Weeks, Not Two Months
Case studies decay rapidly. The details that make a story vivid — the CEO's surprised reaction, the specific metric that shocked the room, the moment when the team realized the real problem wasn't what they thought — these fade within weeks. Two months after the engagement, you're reconstructing from memory. Six months later, you're guessing.
Start collecting material on Day 1. Note the client's initial challenges in their own words during the first meeting. Record the assessment scores and the client's reaction when they see the data. Track the metrics throughout the engagement. By the time you reach results, you already have most of what you need.
Write the draft within two weeks of completion. Not a polished final version — a rough draft that captures the story while it's still fresh. The editing can happen later. The raw material has to be captured now.
Get client approval for the narrative and quote. This sounds like an obstacle. It's actually a relationship-building moment. When you send a client a well-written story about the impact your work had on their organization, you're reminding them of the value you delivered. Many clients become even more enthusiastic about referring you after reading their own case study.
Publish it everywhere. Your website. Partner profiles. Conference presentations. Sales decks. LinkedIn. A case study sitting in a shared drive folder isn't marketing content — it's a missed opportunity. Every sales conversation should include at least one relevant case study, and every partner in the network should be able to access the full library.
By the end of Year 1, your network should have 15-20 case studies organized by industry and problem type. By Year 3, you should have enough that every prospect hears a story about someone in their industry, at their scale, facing their exact problem. That's the moment where case studies stop being marketing materials and become closing tools.
Luis Goncalves
Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.