The lesson
When the win is consolidation, list each old tool with an arrow to the product that replaced it, so the reader sees the whole swap in one glance.
The hero pairs the incident.io and Fin logos over a photo of a speaker, with the migration headline, a one-paragraph summary and a stat stack: "3 tools consolidated into 1 platform", "Weeks to migrate from PagerDuty + Atlassian" and "Adoption spread beyond engineering to CS + GTM". A band of firmographic tags (Industry, Company size, Use case, Products used) sits above jump links and a boxed "Challenges before incident.io" section with a customer quote. "Why Intercom chose incident.io" and "Implementation and adoption" follow with named engineering quotes and an arrow list mapping PagerDuty, manual in-house workflows and Atlassian Status Page to incident.io On-call, Response and Regional Status Pages. "Results" opens with a Director of Engineering quote and six qualitative bullets, then related stories and a demo CTA.
Don't copy the train-to-Marseille anecdote, the Fin and Intercom naming split, or results that stay as unmeasured bullets like faster MTTR with no figure. Keep the logo lockup hero with a short stat stack, the firmographic tag band, the boxed challenge section, the old-tool-to-new-product arrow list and a quote at each stage.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.