User goal: Understand a real client story — the challenge, what Equal Experts did, and the outcome — well enough to trust EE with a similar problem.
This is a shared concept: the principles below hold across every medium that tells case studies. Each medium's implementation links back here for the why, and owns the how for its own format.
A case study is how EE turns experience into credibility — a named (or carefully anonymised) client story that shows the problem, the approach, and measurable outcomes. It appears wherever EE makes its track record concrete: in a sales deck, on a marketing page, in a capability overview. The same story is told differently in each medium, but the goal and the marks of a good telling are shared.
- Lead with the client's challenge framed in their terms, not EE's.
- Make outcomes concrete and measurable — headline metrics first, qualitative outcomes after.
- Establish credibility with specifics — technologies, scale, and team shape, where they add weight.
- Claim proportionately: "helped reduce", not "transformed", unless it genuinely was a transformation.
- Respect approval and confidentiality — a named case study needs client approval; anonymise only where required, and never to the point of meaninglessness ("a large UK retailer" with no metrics carries no weight).
This concept is implemented in the media that tell case studies:
- Slides — case studies: a standalone sales artefact that also embeds into a larger deck.
- Web-marketing — planned: a marketing-page case study, to be added when web-marketing adopts the pattern model.
It has no web-product implementation — a case study is a sales and marketing artefact, not a web-application page type.
A coded Block may later implement part of a web case study. The Block model is defined separately and is not yet wired into this reference.