Talk about your next project
Optimizely case study

The lesson

Make a technical migration credible by showing the old constraints, the architecture choice and the measured improvement in that order.

The move

The page opens with the title “SCA upgrades to Optimizely CMS 12 cloud with headless solution,” a short summary, and tags for “Manufacturing and Distribution” and “Content Management System.” It then introduces SCA through “Driven by the force of the forest,” with company history, business lines and operating scale before naming the communication and platform reasons for change. The story moves through “Moving to a headless cloud solution,” where it explains the SaaS and headless decision, Comprend’s role, React, DXP cloud and the migration timeline. It closes with “Implementation of the new headless CMS” and “Immediate benefits,” including editor experience, security and Google Lighthouse speed scores moving from 43 to 70, 60 to 64 and 75 to 83.

Why it works

  • Our readThe customer background explains why a CMS change matters for SCA before the story moves into platform decisions.
  • Our readThe integration list, React details and Content Delivery API description make the case useful for technical buyers, not only marketing readers.
  • Our readThe benefits section gives concrete before-and-after speed scores, so the migration has an observable outcome.

What not to copy

Don't copy SCA's forestry history, Comprend partner role, React architecture or Lighthouse scores. Keep the structure of customer context, platform problem, architecture decision, implementation detail and measured technical outcome.

More from Optimizely

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.