Talk about your next project
Rattle case study

The lesson

Once the results are on the table, teach the product as numbered steps the customer actually took, and close each step with the customer's own words.

The move

A "CUSTOMER STORY" eyebrow tops the headline "Putting the Strategy Back into RevOps: How Qualified Did It with Rattle". The sub-head packs in 1.5x productivity, 14% faster deal cycles and a 5% win-rate gain "all in one quarter", beside a portrait with a Qualified logo badge. Under the hero sit an About card (Company Size 200, Industry Software, Investors $95M Series C led by Sapphire, Book a demo) and a video. The body opens on the RevOps leader's problem, quotes Kieran Snaith, VP of Revenue Operations, under "A decision that can really pay off", and lists the three results as a checklist. "Vroom-vroom: Steering alignment with Atlas" then runs Step 1 to Step 3, each with a product UI image and a pull quote, before "It's time to take your seat at the table", a closing quote, and Related Case Studies.

Why it works

  • Our readPutting the three results in the sub-head and again as a checklist means a reader who never reaches the steps still leaves with the outcome.
  • Our readNumbered steps tied to one feature turn the story into a short how-to, so a RevOps reader can picture doing the same thing.
  • Our readA Snaith quote after each step shows the customer confirming each claim, which reads as more credible than the vendor's description alone.

What not to copy

Don't copy Rattle's jokey asides ("Vroom-vroom", "A+ work", "Bored of vanilla?"), the Atlas beta framing or the RevOps-specific alert language. Keep the results in the sub-head, the firmographic card under the hero, the results checklist after the first quote, and the numbered steps that each end on a customer quote.

More from Rattle

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.