Contents
The CMS question comes up on every site project, and it’s often answered by habit: the agency’s usual tool, or whatever the founder used last time. A better starting point is a simpler question. Who will change what on the site, and how often?
Start With Who Edits What
List the content the site will have and who touches it after launch. Main pages that change twice a year. A blog or news section updated every week. Job openings. Case studies. Events. A product changelog.
If only a developer edits the site and changes are rare, a CMS adds little. If the marketing team publishes every week, the parts they publish need one. Often the answer is a mix: the main pages in code, the blog and cases in a CMS.
No CMS
The content lives in the code or in Markdown files. Changes go through a developer or a small support plan. The site is as fast as it can be, there’s nothing to log into, update or secure, and nothing breaks between visits.
It suits landing pages and small sites that change a few times a year. The trade-off is that every text edit needs someone who can work with the code.
Payload
Payload is an open-source CMS written in TypeScript that runs inside the Next.js app itself. The content sits in your own database, Postgres or MongoDB, and the admin panel is generated from the content model the developer defines. There’s no per-seat fee, and you host it with the rest of the site.
It fits sites already built on Next.js with a blog, a catalogue, events or cases, when you want everything in one repository and in your own accounts. We covered why that matters in Who Owns Your Website After the Studio Hands It Over. The trade-off: you host and update it yourself, and a developer sets up the content model.
Sanity
Sanity is a hosted content platform. Its editor, Sanity Studio, can be customised heavily, and the content is stored in Sanity’s cloud and delivered through an API. It handles many editors working at once and content shared between a site, an app and other channels well.
It fits teams with several editors, or content that appears in more than one product. The trade-off: the content lives on Sanity’s platform, and the cost depends on the plan and on usage, so check the current pricing for your team size.
WordPress, Webflow and Framer
WordPress has the biggest ecosystem and the most developers, and its plugins need regular updates. Webflow and Framer let the team change pages and layouts visually without a developer, and the site lives on the platform. We compared them in Framer vs Webflow and wrote about their limits in When a Startup Outgrows Framer.
Choose the CMS for the people who will edit the site every week after launch.
A Simple Rule
- A landing page or a site that rarely changes: no CMS.
- A Next.js site with a blog, cases or a catalogue: Payload.
- Many editors, or content reused in an app: Sanity.
- A team that wants to change layouts itself: Webflow or Framer.
- A custom CMS written for one project: avoid it, because it’s the hardest thing to hand over later.
FAQ
Can we add a CMS later?
Yes. If the content is structured from the start, moving it from code into Payload or Sanity is a manageable piece of work.
Is Payload free?
Payload is open source and free to use. You pay for the hosting and the database it runs on.
Is Sanity free?
Sanity has a free plan with limits. Paid plans depend on the team and on usage, so check the current pricing.
Does the CMS affect SEO?
Not by itself. What matters is that editors can set titles and descriptions, the site renders fast, and addresses stay stable when the CMS changes. For a move between platforms, see How to Safeguard Your SEO During a Website Redesign.
Conclusion
Start from who edits what and how often, then pick the lightest option that covers it. Sometimes that’s Payload or Sanity, and sometimes it’s no CMS at all. If you’re planning a site and aren’t sure what it needs, tell us what’s coming up.

