The platforms we build on, and how we choose between them

We're a London CMS development agency building on WordPress, Sanity, Payload and Next.js, and we pick whichever one fits how your content is made, where it needs to go and who'll be looking after it.

Our in-house London team works across projects on WordPress, Sanity and Payload with a Next.js front end.

Schedule a consultation

Front ends, and the CMS where the platform allows, run on our dedicated UK or US hosting.

Every site we build meets WCAG 2.2 AA, and our SEO team plans any migration to protect the rankings you’ve built up.

If you’re weighing up a headless CMS for the first time, our headless page explains how it works and when it’s worth it.

trusted by 100+ clients

The platforms

Each platform suits a different kind of project. These are the ones we build on, and where each tends to fit.

150+ Websites designed and built on the right CMS

WordPress

For marketing sites and multisite networks, especially where editors already know it.

Why build on WordPress

Sanity

For content that’s published in several places and needs a properly structured model.

Why build on Sanity

Payload

For self-hosted builds, portals and projects with strict data residency rules.

Why build on Payload

Next.js

The front end we use on headless builds, whichever CMS sits behind it.

Why build on Next.js

Four questions we ask before recommending a platform

Who's editing?

How many editors you have, how often they publish, and whether they have an existing platform preference.

Where does content go?

Are you approaching a multi-site project or are there multiple other apps, portals and partner feeds that may need to be considered.

Where does your data have to live?

Does data need to stay on a UK or US infrastructure you control or can it sit on a third-party cloud.

What does the site have to do?

Is this site a specific publishing site? Or are there any logins, permissions and custom logic that need to be considered?

How WordPress, Sanity and Payload compare

Where content is stored

WordPress

Your server

Sanity

Sanity's cloud

Payload

Your server

Licence cost

WordPress

None (open source)

Sanity

Free tier, then priced per user

Payload

None (open source)

Editing

WordPress

Block editor most editors already know

Sanity

Studio customised to your content, real-time collaboration

Payload

Admin panel configured in code, live preview

Headless

WordPress

Optional, through the REST API or GraphQL

Sanity

Always

Payload

Always, runs inside Next.js

Developer community

WordPress

Very large

Sanity

Large and growing

Payload

Smaller, growing

Suits

WordPress

Marketing sites, multisite networks, teams who know WordPress

Sanity

Publishing to several channels, highly structured content

Payload

Self-hosted platforms, portals, strict data residency

Choosing a CMS FAQs

Will Newland - SoBold founder

Get in touch with Will for more answers.

It comes down to who’s editing, where your content goes, where your data has to live and what the site needs to do. We go through those on a scoping call, then recommend one and explain why.

A headless CMS stores and manages your content, then sends it through an API to a separate front end, usually built in Next.js. It means the same content can be used on a website, an app or a portal, and the CMS can be kept off the public site.

Yes. We regularly migrate sites from Drupal, Umbraco, Sitecore and Contentful, and we can move you between WordPress, Sanity and Payload. Our SEO team maps URLs and redirects to protect the rankings you already have.

For new builds we focus on these four, so the people who build your site know the platform well enough to look after it for years.

Let’s scope your next project.

Whether you’re in financial services, healthcare, energy or another sector, we start every project with a conversation about your requirements. No commitment, just a discussion about your needs.

Schedule a consultation