Talk about your next project
Blacksmith case study

The lesson

Show every workaround the customer tried before buying, so the switch reads as the last reasonable option rather than a sales win.

The move

A yellow hero puts the headline beside three facts: Industry SaaS, Developers 40, Previous Third-party. A sticky left card summarizes Problem, Solution and Results with "2x" faster deployment times and "75%" annual CI infrastructure cost savings, ending in "Want similar results? TRY US FREE". The body runs "Problem: Moving away from a legacy CI provider", which covers a larger 16 vCPU runner, then test sharding, then queueing and outages, before a co-founder quote. It continues with "Solution: Selecting the fastest option in the business", a side-by-side runner benchmark and "Results: From 0 to 3500 vCPUs in seconds", with an engineer quote after each, then a More Stories list and a 3,000 free minutes CTA.

Why it works

  • Our readThe three hero facts, including the previous provider type, let an engineering lead check fit before reading a word of the story.
  • Our readWalking through vertical scaling, then sharding, then queue delays shows the reader the same fixes they have likely tried and why each one stopped working.
  • Our readThe benchmark step, where the engineer tested a 16vCPU runner on both providers, turns the vendor's speed claim into something the customer checked for itself.

What not to copy

Don't copy Blacksmith's GitHub Actions and Buildkite framing, the "Spoiler alert: We weren't bluffing" voice or the Slack support quote. Keep the fit facts in the hero, the sticky summary card with two result numbers and a CTA, the escalating list of failed workarounds, the customer's own benchmark, and a named quote closing each section.

More from Blacksmith

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.