Talk about your next project
OpenRouter case study

The lesson

Write each headline stat as a before-and-after pair, and name the organizational bottleneck as plainly as the technical one.

The move

The page opens with a "CUSTOMER STORY" label, the headline "How Descript took new models off the engineering queue" and a summary paragraph. A left rail stacks four stats written as changes, such as "1 → 13" models in production and "1+ week → 1–2 hours" to evaluate a new model, plus a firmographic list of website, industry, headquarters and employees. The body runs "ABOUT DESCRIPT", "THE CHALLENGE" ("Every new model waited for an engineer"), "THE OPENROUTER SOLUTION" ("From one model to thirteen in production") and "THE RESULTS" ("Evaluation stopped being a project"), with quotes from Aleks Mistratov, Head of AI product. The solution section lists all 13 production models by model developer, and the results add named views from David Dodero and Keith Simmons.

Why it works

  • Our readArrows inside each stat show the starting point and the end point together, so the reader does not need the body text to judge the size of the change.
  • Our readThe challenge splits friction into technical (parameter drift) and organizational (waiting for an engineer's calendar), which lets a buyer see that the product fixes the second, larger one.
  • Our readAdmitting that a direct Anthropic connection remains, and that remaining delays come from Descript's own code, makes the claims easier for a technical reader to trust.

What not to copy

Don't copy the model list, the Baseten and provider-fallback detail, or the Slack eval loop, which belong to Descript's stack. Keep the before-and-after stat rail, the two kinds of friction in the challenge, the plain inventory of what runs in production, and the honest note on what the product does not solve.

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.