Talk about your next project
Sphere case study

The lesson

Name each pain as a bolded one-line claim, then close the story with results that answer those pains one by one, leading with the cost the customer avoided.

The move

The headline 'From a fragmented setup across three providers to a single partner built for global scale.' sits over a Client, Industry and Products strip and a wide photo. 'Problem' lists four bolded pains, from 'A widening set of obligations tracked by hand' to 'The need to hire additional tax staff', and a dark quote block from Eimear Hussey, Head of Finance, follows. 'Solution' opens with 'At a glance' and pairs each bolded capability with indented detail, then a second Hussey quote appears over her photo. 'Results' leads with 'The hire didn't happen', and a 'Who Sphere is built for' section describes the kind of company the story fits.

Why it works

  • Our readBolded lead-ins in Problem, Solution and Results let a finance buyer skim the claims and still follow the story from pain to outcome.
  • Our readLeading with the avoided hire turns a qualitative story into a cost the reader can price for their own team, without needing a percentage.
  • Our read'Who Sphere is built for' turns one customer into a profile, so a reader can check whether their own situation matches before booking a demo.

What not to copy

Don't copy Framer's details, the Stripe and SKU tax-coding specifics, the shared Slack channel claim or Sphere's vendor-versus-partner line. Keep the bolded pain list, the capability-plus-detail Solution, results that answer each pain, the two customer quotes and the closing fit profile.

More from Sphere

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.