Talk about your next project
Trunk case study

The lesson

Start a case study at the moment the old tool failed under real deadline pressure, then show the buyer's own test of the replacement before you show results.

The move

The headline names the team size and the result, with a two-sentence dek and three stat chips: "~90% fewer escalations", "55 → ~38 min median queue time" and "19 merge queues in Terraform". A portrait pull quote from Rishabh Makhija follows, beside a sidebar card listing Industry, Team size, Product and Website, with demo and free-start buttons and an "On this page" list. The body runs through "When Bors Stopped", "Trunk Showed Up" (the stress test with flakiness injected up to 40%, the vendors compared, and three requested features shipped) and "From One Release Branch to 19 Queues". It closes on a second quote, three "More Customer Stories" cards and a "Try it yourself or request a demo" block.

Why it works

  • Our readOpening on a broken queue close to a database release, with strict timelines, gives an engineering buyer a failure they recognize before any product claim appears.
  • Our readDescribing the evaluation setup, with flakiness injected at 10%, 20%, 30% and up to 40% and volume pushed to about 150 PRs an hour, lets a technical reader judge the test instead of trusting a summary.
  • Our readResults are hedged in the customer's words, "about 90%" and "According to Cockroach", which reads as more credible to engineers than exact claims.

What not to copy

Don't copy the Bors outage story, the Terraform provider and merge-commit feature requests, or the competitor names from the evaluation. Keep the stat chips under the headline, the portrait lead quote, the sidebar profile card with section links, the incident, evaluation and rollout sections, and the closing quote.

More from Trunk

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.