Talk about your next project
Blacksmith case study

The lesson

Anchor a technical case study on one engineer's before-and-after timing that any developer reading can compare against their own.

The move

The hero puts the headline beside a three-field row: Industry SaaS, Developers 58, Previous GitHub-hosted. A boxed card with the VEED logo summarizes Problem, Solution and Results, shows "2x" faster CI/CD pipelines and "70%" annual CI infrastructure cost savings, and ends with "Want similar results?" and a TRY US FREE button. The body runs "Problem: When your local machine is faster than Github", "Solution: Selecting the fastest option" and "Results: From 28 to 14 minutes waiting time on a PR", each followed by a large pull quote from Máté Nagy, Staff Software Engineer. It closes with a short call to action, a MORE STORIES list tagged by industry and previous setup, and a footer offer of 3,000 free minutes per month.

Why it works

  • Our readThe firmographic row, especially Previous GitHub-hosted, tells an engineering buyer in one glance whether VEED started from the same setup they have.
  • Our readThe 10 minutes locally versus 22 minutes on GitHub-hosted runners detail makes the problem concrete for a developer who has seen the same gap.
  • Our readThe summary card gives a skimmer the problem, the fix and both figures, then puts the trial button right next to them.

What not to copy

Don't copy Blacksmith's CPU and bare-metal claims, the Arrow Lake aside, the EU latency point or its casual asides like "a whopping". Keep the firmographic row with the prior tool, the summary card with two result figures and a trial button, problem, solution and results headings that each state their point, and one named engineer quoted after 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.