Talk about your next project
Astro case study

The lesson

Name the internal bottleneck the customer had, show it as a before/after picture, and measure the result in how many people can now do the work.

The move

A gradient banner with the Thinkmill logo sits above the eyebrow "Case Study • December 2023", the headline "No More Bottlenecks" and the subhead "How Thinkmill Reduced Dependencies on Senior Developers with Astro". A short customer intro and a summary paragraph ending in contributors going "from 1 to 15" lead into a Before/After illustration with a one-line caption for each state. The body runs through "Challenges", "Requirements" and "Solution and Implementation", with large pull quotes from Simon Swiss, Developer Advocate, and Ronald Aveling, Lead Designer, plus a screenshot of the Thinkmill homepage. "Results" splits into "Reduced Friction" and "Performance Gains", shows an Unlighthouse score screenshot, and closes on a "Take Astro for a spin" call to action.

Why it works

  • Our readThe Before/After captions state the whole story in two sentences, so a reader who only looks at the diagram still gets the change.
  • Our readThe "Challenges" section explains the agency's structure of designers and developers working on the same code, which makes the senior developer bottleneck believable to a reader with a similar team.
  • Our readThe "Requirements" section lists what the team needed before the product appears as the answer, so the choice reads as a fit to criteria rather than a pitch.

What not to copy

Don't copy Thinkmill's framework details, the React and JSX comparison, the Keystatic pairing or the Lighthouse score claims. Keep the bottleneck headline, the before/after visual with captions, the challenges, requirements, solution, results order with a pull quote between sections, and results split into named sub-heads.

More from Astro

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.