The non-numeric outcome — what stops case studies from reading like marketing fiction

The non-numeric outcome — what stops case studies from reading like marketing fiction

You're reading a case study on a consulting firm's site. The headline reads "Increased revenue by 47%." The opening paragraph names the client — a mid-market SaaS company. The body walks through the engagement at appropriate detail. The outcomes section lists three numbers: 47% revenue, 22% retention, 4× pipeline.

You don't believe any of them.

Not because you think the consultant is lying. Because the case study has the unmistakable shape of marketing-grade content — clean numbers, no texture, no specific moment from the engagement that you couldn't have written from a template. Even if every number is true, the format guarantees the case study reads as fiction. And once it reads as fiction, the prospect filters it as fiction, and the case study fails to do the one job it was supposed to do: build credibility for the next deal.

This article is about the structural fix. There's a single section most consultants omit, the section that separates real case studies from the ones that read like marketing fiction, and writing it well doesn't require better writing skills — it requires capturing the right material in the right window.

This is a Category 2 task — structured but needing your voice. (The framework for which tasks should go to AI is the upstream filter.) Case-study writing is squarely AI-tractable when paired with the right inputs. The trick is the inputs.

Why numbers alone read as fiction

The pattern has a structural explanation. The reader of a case study has seen dozens of them. Their internal filter is calibrated. When they see clean round numbers — "47% increase" — without the friction of specific evidence, they round the case study down to "marketing claim of unverifiable lift." This doesn't require active skepticism on their part; it's automatic.

The friction that defeats this filter is texture. A specific quote. A specific moment. A specific surprise. A specific thing that almost went wrong. The case study reader can't fact-check 47%, but they can tell the difference between a piece of writing that has texture from a real engagement and one that doesn't. Texture is the credibility carrier.

This is also why the templates ranking for "consulting case study template" produce case studies that lose. They optimize for the structure (executive summary, challenge, solution, outcomes) and silence on the texture. A structure-only template produces marketing fiction every time, even when the underlying engagement was real and the outcomes were earned.

The non-numeric outcome

Every case study should include a non-numeric outcome alongside whatever numbers it cites. The non-numeric outcome is the behavior change, capability built, or visible difference in how the client operates after the engagement — the part that's hard to fake because it requires you to have actually been there.

Examples:

  • "Sarah, the ops lead, can now train a new hire to the receiving SOP in a single afternoon. Before, that took two weeks of shadowing."
  • "The Boise warehouse opened with documented procedures from day one — a small thing that becomes a large thing when the third and fourth markets follow."
  • "Marcus has a ranked list of which other operational areas are running on tribal knowledge and need the same treatment. He'll get to them when he gets to them."

None of those have a number. All of them are specific, concrete, and visibly from the actual engagement. The reader can't fact-check them, but the texture is the wrong shape for fabrication. Marketing-grade content doesn't reach for the line "he'll get to them when he gets to them" — it reads too unguarded. Which is exactly why it works.

A case study with one non-numeric outcome alongside one or two numeric ones beats a case study with five numeric outcomes. The non-numeric outcome anchors the numbers' credibility. Without it, the numbers float.

How to capture the texture

The non-numeric outcome is hard to write from memory two months after the engagement wraps. By then, the texture has decayed — you remember the deliverable, you remember the contract, you don't remember the specific moment when Sarah laughed about the new hire training.

The fix is structural: capture the texture in the two weeks after delivery, while the engagement is still fresh, in a project debrief document for your private files. The debrief is the source material from which the case study is later written.

The prompt for the debrief:

The engagement just wrapped. Help me harvest it. Output a 1-2 page
internal debrief — for my files, not for marketing.

Sections:

1. **The engagement** — 3 bullets: client, scope, dates.
2. **What the client wanted** — what they said in discovery.
3. **What they actually needed** — what I figured out by week 2.
   These are usually different. Note the gap honestly.
4. **What I delivered** — concrete artifacts and outcomes.
5. **The numbers** — anything quantified. Before and after if possible.
   If no before, just after with context.
6. **Specific moments worth remembering** — 3-5 details (a quote, a
   surprise, a near-miss, a turning point). These are the texture
   that makes future case studies vivid instead of generic.
7. **What I'd do differently** — honest, no spin.
8. **Repeatability** — could I do this again, faster, for a similar
   client? If yes, what's the productized version of this engagement?

Inputs:
- Internal kickoff doc: [PASTE OR REFERENCE]
- Meeting debriefs across the engagement: [PASTE OR LIST]
- Final deliverable summary: [PASTE OR REFERENCE]
- Client's reaction: [QUOTE WHATEVER THEY SAID]

Voice: blunt and specific. This is for me. No marketing tone.

Section 6 — "specific moments worth remembering" — is where the case study's texture comes from. Three to five details, captured while the engagement is still in working memory. A quote. A surprise. A near-miss. A turning point. Without this section, the eventual case study has no texture; with it, the case study has more material than it needs.

The debrief is for your private files. It's blunt. It contains the version of "what I'd do differently" you wouldn't show a client. The case study is what gets written from the debrief — translated for an external audience, with permissions and anonymization applied — but the source material is the debrief.

Writing the case study from the debrief

Once the debrief exists, the case study takes 15 minutes. The structure that closes:

  1. Headline — names the outcome, not the project. Bad: "Lattice Provisions Operations Engagement." Good: "How a regional food distributor stopped silently losing 3% of every shipment."
  2. Opening hook — 2-3 sentences. The problem in the client's language with one concrete detail.
  3. Diagnosis — 1 paragraph on what was actually wrong. Where you signal expertise.
  4. What we did — 2-3 paragraphs. Specifics. No "engaged" or "worked with."
  5. Outcomes — bullets if you have numbers; one paragraph if not. Always include a non-numeric outcome.
  6. What this might mean for your team — 2 sentences bridging to the prospect.
  7. Tag line — your name + your offering, 1 sentence.

The non-numeric outcome lives in section 5, alongside the numbers. Without it, the section reads as marketing fiction; with it, the numbers gain credibility by association.

A worked example, end to end

Suppose the debrief surfaced these moments:

  • Sarah said "hiring a new ops manager would be cheaper than writing this" halfway through, with a laugh — and Marcus didn't laugh.
  • Three crates of clearly-damaged inventory had been accepted in a single quarter before the engagement.
  • The Boise warehouse opened with documented procedures from day one.
  • Sarah can now train a new hire to the receiving SOP in a single afternoon (was two weeks).

The case study's outcomes section, written from those moments:

  • Weekly inventory loss dropped from 3.2% to 1.1% of receipts in the 30 days following training. At Lattice's volume that's meaningful enough to track, not enough to celebrate.
  • The Boise warehouse opened with documented procedures from day one — a small thing that becomes a large thing when the third and fourth markets follow.
  • Sarah, the ops lead, can now train a new hire to the receiving SOP in a single afternoon. Before, that took two weeks of shadowing.
  • Marcus has a ranked list of which other operational areas are running on tribal knowledge and need the same treatment. He'll get to them when he gets to them.

Two numbers. Three non-numeric outcomes. The numbers gain credibility by association — a marketing-fiction-flavored case study would have produced "saved Lattice $480k annually" and stopped there. This version reads as real because the texture is wrong-shaped for fabrication.

What to do this week

If you have an engagement that wrapped in the last 30 days, write the debrief now — even if you weren't planning to write a case study. The debrief is high-value on its own as an internal lesson document, and it's the only way to capture the texture before it decays.

If you have multiple wrapped engagements without debriefs, pick the most recent one. Write the debrief from memory, knowing the texture is already partially gone. Use what you can capture; promise yourself you'll do the next one fresh.

The case study can come later. The window for capturing texture is now.

Going deeper

This article distills the case-study workflow from Chapter 7 of The Solo Consultant's AI Playbook, which adds the public-facing case-study prompt and the newsletter/social-post triple — the full chain that turns one wrapped engagement into four pieces of marketing in 30 minutes.

The framing for which tasks to give AI at all is in the first article. Case-study writing is Category 2 — needs your voice — which is why the bullets-first workflow from Article 2 applies here too.

— Digital Kreative

Back to blog