Talk about your next project
Scalar case study

The lesson

When the win is something that didn't happen, make the absence the headline result and state it plainly in the customer's words.

The move

The title sits over a row of tags, "Generated SDKs" with Go, TypeScript, Python and CLI, then a wide image of a race car in Warp livery. A one-paragraph summary and a pull quote from Adam Rankin, CTO, follow. Short sections cover the company ("An HR platform built to be called"), which opens with narrative text, then its API users ("Three kinds of developer showed up"), the vendor shutdown ("Needing a new home for the SDKs"), the in-house attempt ("He tried the build anyway") and the switch ("A migration nobody noticed"), each of which opens with a quote. The story closes with a one-line results strip, a section on OpenAPI extensions ("More than the libraries"), and a final repeat of the CTO quote.

Why it works

  • Our readThe language tags under the title tell a developer reader which SDKs are in scope before they read a sentence.
  • Our readThe "He tried the build anyway" section answers the build-it-yourself objection with the CTO's own estimate of the cost, "probably 50% of their time" for one person.
  • Our readOpening most sections after the company background with a short quote lets a skimmer follow the story through the customer's voice.

What not to copy

Don't copy Warp's HR and payroll context, the vendor end-of-life trigger, or the race car artwork. Keep the tag row under the title, the summary plus lead quote, a narrative context section followed by quote-led sections that move from forced change to rejected alternative to outcome, and a one-line results strip.

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.