Do You Actually Need a CMS?Do You Actually Need a CMS?

Most early startups ship about four content changes a month. That does not pay for a content management system. Here is what does.

What a CMS actually costs

The licence is the cheap part. The real cost is a second system that has to be modelled, kept in sync with the design, updated, secured and paid for — and a build that now fails for reasons outside your repository.

For a six-page site edited by the two people who own the codebase, that is a lot of machinery to move four paragraphs a month.

The version that is usually enough

Keep the copy in typed files next to the code. It reviews in a pull request, it deploys with the site, it cannot half-publish, and a wrong field name fails the build instead of the page.

export const hero = {
  titleLines: ["Your product is real.", "Your website should be."],
  description:
    "We design it, build it front to back, and write it from what you already have.",
} as const;

Non-technical editors can work this way too — the file is prose in quotes, and the diff shows exactly what changed. It is a smaller ask than most content interfaces.

When you genuinely need one

• People outside the repository publish on their own schedule, without waiting on a deploy.
• The volume is real — a changelog, a docs set, or posts every week rather than every quarter.
• Someone needs to schedule or stage content ahead of time.
• Editors are non-technical and will not be trained, and there are enough of them for that to matter.

Add the CMS when a person is waiting on you to publish. Not before, and not because the stack looks incomplete without one.