Multi-segment programme: Payload headless CMS backend

Situation

Marketing and product were trying to steer several digital surfaces at once, but copy and structure kept fragmenting across separate places. They needed one editorial model in the middle, with previews that worked before any of the TypeScript fronts could responsibly ship.

What we focused on

• Payload: Collections, access control, and draft workflows tuned for that organisation’s structure, not a generic blog.
• API contract: Stable shapes for the shared front-end packages, versioning discipline, and clear ownership between CMS and app teams.
• White-label delivery: We reported through the agency partner; comms and documentation stayed on their rails.

Outcome

A single headless backend the three TypeScript properties could rely on, with editors able to publish without waiting on a deploy for every text change.