Talk about your next project
Trunk case study

The lesson

Describe the customer's old workaround in their own embarrassed words, so the fix needs little selling.

The move

Under the customer name and the headline "How AgencyAnalytics Stopped Breaking Main" sit three stat chips: "30-40 PRs merged/day", "25-30min time to merge" and "4 repos → 1 monorepo". A right-hand card lists Industry, Team size, Product and Website with "Book a demo" and "Get started free" buttons, above an "On this page" list. The body runs "Who is AgencyAnalytics", "The Problem", "Why Trunk", "The Results", "Developer Experience", "Support" and "The Bottom Line", and quotes Matt Schurenko, Senior Cloud Developer, in nearly every section. The page closes with three "More Customer Stories" cards and a "Try it yourself or request a demo" block.

Why it works

  • Our readThe quote calling the recursive Cloud Build cancellation queue "ridiculous" shows the pain more credibly than any vendor description could.
  • Our read"Why Trunk" names the deciding gap, batching missing from GitHub's native merge queue, which answers an engineering buyer's first comparison question.
  • Our readThe sidebar with team size and product, plus the section list, lets a reader check fit and jump straight to results.

What not to copy

Don't copy the merge queue, monorepo and CI specifics, or the submit-and-walk-away framing that fits only this product. Keep the stat chips under the title, the profile card with jump links, the problem told through the customer's old workaround, a section on why they chose the brand over the obvious default, and a closing recommendation question answered by the customer.

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.