Talk about your next project
StackBlitz case study

The lesson

Before you introduce your product, list the alternatives the customer tried or ruled out and say why each failed, so the solution arrives as the last option left.

The move

The hero states the headline, a short StackBlitz Enterprise pitch and "Learn how Google uses StackBlitz to support millions of passionate developers," then a quote card from Stephen Fluin, Developer Relations Lead at Google. "The Challenge" numbers the three manual getting-started steps, and "Top Obstacles" lists "30+ minutes" per bug report, "1,500,000+ developers" a month and "40,000+ bug reports" plus Google's security rules. Next come the options Google rejected: code pens and sandboxes, an internal build, and cloud VMs. "The Solution" and "The Impact" follow, with two more Fluin quote cards between them, then a general section on code collaboration and a "Reach out today" email contact.

Why it works

  • Our readRuling out sandboxes, an internal build and cloud VMs one by one answers the questions a technical buyer would raise about other approaches.
  • Our readThe "Top Obstacles" bullets give the problem in the customer's own numbers before the product appears, so the later impact claims have a baseline to compare against.
  • Our readThree quote cards from the same named Google lead break the long text into steps a skimmer can follow: the barrier, the single click, and the reduced support burden.

What not to copy

Don't copy the browser sandbox security argument, the WebContainer and Angular details, or the general collaboration pitch tacked on after the impact section. Keep the order of challenge steps, an obstacles list with the customer's figures, rejected alternatives, solution, and impact bullets, with a named quote card between sections.

More from StackBlitz

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.