Talk about your next project
Aaru case study

The lesson

When the customer used your product to make something, make that output the case study: lead with one finding from it, then show how it was built.

The move

A dark hero holds the headline and date, then a one-paragraph summary with FOCUS and SOURCE tags citing Business Wire. A left-side list links to "The task", "The result", "The launch", "What it simulates", "Inaugural findings" and "Beyond the quarterly". "The task" opens with a two-bar chart, retail investors who would pay more at 44 % against long-only investors at 13 %, and "The result" gives one line: "A quarterly tracker of 71 judgments across 40,000 simulated investors." After the launch story comes a six-cell stat grid, a quote from Mark Hayes of Breakwater, three bolded findings, a quote from Aaru's CEO Cam Fink, and a close on future editions and bespoke engagements.

Why it works

  • Our readOpening on a finding from the study shows the product's output before any claim about the product, so the reader judges the work first.
  • Our readEach finding opens with a short bold claim such as "Behavior tracks traits", so a skimmer gets the argument without reading the paragraph under it.
  • Our readQuotes from both the partner and the vendor CEO, plus a Business Wire source tag, show that the customer publicly stands behind the project.

What not to copy

Don't copy Breakwater's capital-markets subject, the simulated-investor counts or the press-release sourcing. Keep the jump-link list, the one-line result under the task, the stat grid after the launch story, the bold-claim findings, and the close on what comes next for the customer.

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.