Most of our headless CMS work falls into four kinds of project. In each, the CMS is chosen to fit the content and the team, and the frontend is built to keep search rankings and page speed intact. The case studies below show one example of each kind. Figures are copied from the case files.
Replatforming a marketing site off WordPress
A US-based Series-B fintech ran its marketing site on a heavily customised WordPress install, and every content change needed a developer review. We moved it to Payload and Next.js, with approval states inside the CMS so compliance review no longer happens in email threads. Publish time fell by about two thirds. Read the fintech replatform case study.
Moving a publisher without losing rankings
A US-based enterprise digital media publisher had thousands of articles on legacy WordPress and poor Core Web Vitals. We migrated the content to Payload, rebuilt the frontend in Next.js, and enforced the URL map before launch. LCP dropped from 4.2 seconds to 1.5 seconds and organic traffic held through the cutover. Read the publisher migration case study.
Leaving Drupal for a lighter stack
A European enterprise healthtech organisation was running on Drupal. We replatformed it to Next.js and Payload, which cut LCP from 4.3 seconds to 1.5 seconds and halved editor publish time. Read the healthtech Drupal migration case study.
One CMS for several brands and channels
A US-based enterprise multi-brand retail group ran a separate CMS for each brand. We built one Payload instance with a shared content model that serves storefronts, native apps and in-store screens through one API, and cut average publish time by about 65%. Read the omnichannel retail case study.
Which platform we pick
Payload is the CMS in all four projects above. We also build on Strapi, Sanity, Contentful and Directus, and the choice follows the team and the content. The headless CMS platform index sorts platforms by requirement, and our headless CMS agency page explains how we run a project.
