Talk about your next project
LightSource case study

The lesson

Open a case study with labeled outcome tiles that state the metric's scope, then let several named people from the customer team each speak to the part of the change they own.

The move

Under the headline and a one-sentence subhead sit three tiles: "EBITDA IMPACT, FIRST YEAR $1M+", "SOURCING CYCLE TIMES Months → weeks" and "COMPLETED PER YEAR, SAME TEAM More RFPs", followed by a Get a demo button. A left sidebar lists industry, headquarters and website, plus jump links to Summary, Challenge, Solution and Results, beside a video featuring Michael Elefante. The body runs Summary with his pull quote, Challenge framed as lost institutional knowledge, Solution covering speed and the archive, and Results built on quotes from Phebe Kearney, Michael and Nick. It closes with "Aramsco's future with LightSource", a demo prompt and a "Read more" row of other stories.

Why it works

  • Our readThe small labels on each tile say what the figure measures and over what period, so a skimming reader knows how to weigh $1M+ and More RFPs.
  • Our readNaming the challenge as data that disappears between projects gives the archive feature a specific problem to solve, rather than a generic efficiency claim.
  • Our readQuotes from a VP, a supplier management director and other team members let each result come from the person closest to it, which makes the story read as a team's account.

What not to copy

Don't copy Aramsco's RFP archive framing, procurement vocabulary or the months-to-weeks phrasing. Keep the structure of scoped outcome tiles, a facts sidebar with jump links, a named problem that the product directly answers, and results told through several named customer voices.

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.