The lesson
Show the maintenance burden first, then make the product decision feel like a way to return time to the team.
The story opens with the Skyscanner logo, “GitHub Enterprise,” and the headline “Skyscanner uses GitHub Enterprise to get travelers flying for less,” followed by a large office image. A sidebar gives quick facts: “Industry Travel,” “Customer Since 2018,” and “Number of Seats 800+.” The narrative introduces Skyscanner’s growth, Stuart Davidson and the Developer Enablement Tribe, then describes the previous source control system taking up support time. A mid-page section titled “Why Skyscanner chose GitHub Enterprise” lists three reasons, before the story moves into current use, consolidation, innersource, GitHub Apps, Snyk, the GitHub Checks API, pull requests, peer review, and support.
Don't copy Skyscanner’s travel metaphors, office growth story, Developer Enablement Tribe name, or toolchain details like Drone CI and Snyk. Keep the structure of customer context, named technical owner, old-tool burden, buying criteria, current workflow, and quoted operating change.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.