Talk about your next project
Webflow case study

The lesson

Lead with the operating change, then use the customer’s old workflow to make the platform decision feel necessary.

The move

The story opens with the Ebury name, the title “How Ebury rebuilt its global website to match the company it had become,” a short summary, and three result callouts: “2x increase in visibility index,” “Same day turnaround for urgent compliance changes vs 3-6 months,” and “1 publishing action for a blog post across all locales instead of 40.” It then lists industry, country, and company type, followed by an “In this story” navigation with sections such as “A payments company that outgrew its own front door,” “When 30 WordPress instances become impossible to manage,” and “A rebrand, a replatform, and only three months to do both.” The body starts with a trust quote from Jon Heaton, explains Ebury’s scale and fragmented WordPress setup, then follows the rebrand, Webflow migration, Parallax partnership, and local publishing changes through named quotes.

Why it works

  • Our readThe opening numbers make the migration feel operational, not cosmetic, before the story moves into platform details.
  • Our readThe table of contents promises a clear arc from scale problem to migration pressure to local-team control.
  • Our readQuotes from engineering, design, and senior engineering show the change from multiple operating angles rather than one marketing testimonial.

What not to copy

Don't copy Ebury's finance context, Santander ownership, regulated-market footprint, Parallax relationship, or exact migration numbers. Keep the structure of visible results first, a named operational bottleneck, a deadline-driven migration, and quotes from the people who owned the change.

More from Webflow

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.