The method

How we read a case study

Every case study here is tagged by one thing first: the transformation it delivers for the customer. Name what actually changed, and you can see how the story is built, and borrow it.

Story Type

What changed for the customer?

Breakthrough 173 case studies →

The customer broke through a ceiling to a new level of growth or scale. A number went up and stayed up.

Test: Is the headline a number going up? Did they reach a level they could not reach before?

New Capability 119 case studies →

The customer became able to do something they could not do at all before: a new market, product, model, or motion built from scratch.

Test: Was this impossible or impractical before, not just slower or costlier?

Turnaround 12 case studies →

The customer reversed a decline, failure, or crisis. The before-state was actively getting worse or already broken.

Test: Was something going backward or broken, and did it recover?

Efficiency 372 case studies →

The customer reached the same or a better outcome with far less time, cost, or effort. A number went down.

Test: Is the headline a number going down? Same result, fewer resources?

Clarity 50 case studies →

The customer went from not knowing to seeing. The before-state was blindness or guesswork; the payoff is a reliable picture to act on.

Test: Could they even see or measure the problem before? Is the win sight, not growth or savings?

Resilience 29 case studies →

The customer became safer or more protected: survived a risky change or migration, closed an exposure, reduced a costly downside.

Test: Is the win that a bad thing did not happen, or that they came through a high-stakes change intact?

When two types fit

One primary tag per story. The tie-breaks:

Breakthrough vs Efficiency: follow the headline. A number going up (revenue, pipeline, volume) is Breakthrough. A number going down (time, cost, effort) is Efficiency. New Capability is only for what was impossible before, not something they already did faster or bigger. Clarity leads only when the before-state was not knowing. When it is a genuine coin-flip, we say so in the analysis.

The flag and the capture

Extra signal, kept off the main axis.

Competitive Switch flags a story about leaving a named competitor for this vendor. It rides alongside any Story Type, because it describes where the customer came from, not what changed. We also capture, where the story supports it, the North Star Metric (the single headline number), the Emotional Shift (the human before and after), and the Trigger (why they acted now).

The rest of the tags

Organizing detail, so you can filter to what you need.

Format is how the story is told — written narrative, video, data-heavy, mini / social, interview, or technical deep dive. Structure is how it's arranged — Challenge-Solution-Results, a story arc, metrics-first, or quote-driven. Industry is the customer's world. Together these let you filter the library down to, say, every metrics-first fintech story that led with a Breakthrough.

Why It Works & Steal This

The editorial layer — our read, not the vendor's.

Tags tell you what a case study is. The analysis tells you why it lands. Why It Works is two or three sentences on the mechanics of the piece. Steal This is the single element most worth copying into your own work. Everything here is commentary and curation: we always link to the original and lead with our analysis, never republish the vendor's work as our own.

← Browse the case studies