Talk about your next project
Svix case study

The lesson

When you have no hard numbers, tell the story as the customer's build-versus-buy decision and let one named owner explain each step in their own words.

The move

A "CUSTOMER STORY" eyebrow sits over the headline and a wide image of a Brex card and phone with the Svix logo. A short intro sets Brex's scale, naming customers like Airbnb and DoorDash and a $12bn valuation, then the first quote card from Milo Spirig, API Product Lead. Three sections follow: "Brex's customers wanted webhooks", "Developers expect a great webhooks experience" and "Svix was the right choice", each closed by a Spirig quote card, with an indented long-form quote block in the third. "The end result" gives a qualitative outcome and a final quote, then a note that Svix is also a Brex customer and a story about founders' first checks.

Why it works

  • Our readThe sections follow the order a buyer actually thinks in: customer demand, the hidden cost of building in-house, then why this vendor won.
  • Our readEvery quote comes from the same named API Product Lead, so a technical reader hears one consistent peer voice instead of a marketing narrator.
  • Our readNaming the engineering pain directly, like retries, fanout, security and ongoing maintenance, lets an engineer reading the page recognize their own build-versus-buy debate.

What not to copy

Don't copy Brex's valuation and customer name list, the founders' first-check anecdote or the note that the vendor is also a customer. Keep the customer-scale intro, the demand, build-versus-buy, decision and outcome sections, and a quote card from one named owner closing each section.

More from Svix

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.