# Do you actually need a CMS? | Plyo

> When a content management system earns its place on a website, when it just adds cost and complexity, and how to pick one that your team will really use.

Source: https://plyo.studio/blog/do-you-need-a-cms

1.  [Home](/)
2.  [Blog](/blog)
3.  Do you actually need a CMS?

# Do you actually need a CMS?

When a content management system earns its place on a website, when it just adds cost and complexity, and how to pick one that your team will really use.

Plyo Studio 3 October 2025 6 min read

On this page

[What a CMS actually gives you](#what-a-cms-actually-gives-you)[When you need one](#when-you-need-one)[When you do not](#when-you-do-not)[Picking one your team will use](#picking-one-your-team-will-use)[The mistake we see most](#the-mistake-we-see-most) [Common questions](#common-questions)

Related service

[Webflow websites](/services/webflow)

A CMS is worth it when someone other than a developer needs to change the site regularly. If your pages change twice a year, a CMS is overhead you will pay for and never use. The question is not whether a CMS is good. It is whether anyone on your team is going to open it.

## What a CMS actually gives you

A content management system stores your content separately from your design, so the two can change independently. Add a blog post and it appears on the index, in the sitemap and in the related posts, without anyone editing a page.

That matters for content that repeats: blog posts, team members, locations, projects, products, events. It matters much less for a homepage that gets rewritten once a year.

## When you need one

-   **You publish regularly.** A blog, news, case studies or job listings.
-   **You have repeating content.** Team bios, locations, services, products. Anything where the same layout holds different data.
-   **More than one person updates the site.** A CMS gives you roles and a safe place to work.
-   **Content drives navigation.** Filtering by category or location needs structured data behind it.

## When you do not

-   A five page site where the content is settled.
-   A campaign or launch site with a short life.
-   A site where one developer makes every change anyway.

In those cases the content can live in the code. It is faster, cheaper and there is nothing to maintain.

## Picking one your team will use

The best CMS is the one that matches how your team thinks about the content.

### Built in, like Webflow

The editor sits on the page. You click the text and change it. For marketing teams who want to see what they are changing, this wins almost every time. [Webflow](/services/webflow) suits teams that publish weekly and want independence from a developer.

### Headless, like Sanity or Storyblok

Content lives in its own system and is pulled into the site. Better when the same content feeds more than one place, like a website and an app. More setup, more flexibility.

### Git based, like Markdown files

Content lives in the codebase as text files. Excellent for developer written content such as documentation. Not for a marketing team.

## The mistake we see most

Choosing a CMS with more capability than anyone will use. A fully modelled content system with fifteen collection types, and two years later the team has published four posts and edits everything else by asking a developer.

Start with what actually changes. You can always add a collection later. Taking one away after everyone has learned it is harder.

Not sure which side of the line you are on? Tell us what changes on your site and how often, and we will give you a straight answer.

## Keep reading.

[All posts](/blog)

-   [
    
    Platforms Choosing a domain and setting up business email 7 min read](/blog/domain-names-and-business-email)
-   [
    
    Platforms Astro or Shopify for selling online? 7 min read](/blog/astro-or-shopify-for-selling-online)
-   [
    
    Platforms How to make a Shopify store faster 6 min read](/blog/how-to-make-a-shopify-store-faster)

Updated 3 October 2025

FAQ

## Common questions

[Ask a question](/contact)

### Is WordPress a CMS?

Yes, and a capable one. The trade is maintenance: plugins, themes and core updates, each one a thing that can break or be exploited. For many sites a modern CMS with managed hosting is less work.

### Can I add a CMS to my site later?

Usually yes, if the site was built with that in mind. Retrofitting one onto a site where content is hard coded across fifty pages is a bigger job than it sounds. Tell us early if it is likely.

### How much does a CMS cost?

Anywhere from nothing to a few hundred a month. Webflow includes it in the site plan. Headless systems usually have a free tier that most small sites never outgrow. The real cost is setup, not licensing.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Webflow websites Visual, CMS-powered sites your marketing team can run day to day.](/services/webflow)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
