Choosing a CMS When You Are Not a Publisher

en 2026-09-16 7 min read

Pick a CMS by counting the things on your site that will actually change, not by comparing feature lists. For a business that is not publishing every week, that count comes out short, and the CMS is already inside the build price: a step 02 mini-site at EUR 900-1.500 includes a basic CMS, and a step 03 business website at EUR 1.500-3.500 includes one across 4-7 pages.

The question that matters is not which CMS but how much of your site you need to edit yourself, because that is what the build is priced on.

Write the list before you choose anything

Write down the things you expect to change after launch. Be specific: not "the content", but "the prices on the services page" and "the team photos". For each line, answer two questions: who edits it, and does it have to happen without asking us. That list is your CMS specification. Everything not on it can live in the code.

Three shapes a site can take

1. No CMS. The content lives in the code, and changes go through us as small fixes under care at EUR 100-300/mo. No login, no editor to learn, nothing extra to update.
2. A CMS over the parts that move. Fields and repeatable entries for exactly what is on your list, and code for everything else. This is what step 02 and step 03 include.
3. A CMS behind every page. Every block editable, plus drafts, preview, scheduled publishing and several people with different permissions. This is a bigger build, and once it comes with login, roles, a dashboard or an API it is step 04 at EUR 3.500-7.500.

Our default is the second shape: control over what you change, and the parts that hold the design together kept out of reach of an accidental edit. If your list is short enough for the first shape, we will say so.

The options you will be shown

The front end we build for the last two options is described on the Next.js development page.

The price is in the fields, not in the brand name

Two sites on the same CMS can sit on different steps. A page with a handful of editable fields and a page where every element is editable are different builds: each field needs a design for empty, a design for too long and a check that an edit cannot break the layout. That work is the same whichever CMS the field lives in. When a quote names a CMS but not the fields and entry types behind it, ask for them. How we design for editing is covered on design and engineering.

What pushes the decision into step 04

A CMS stays inside step 02 or step 03 while it edits pages. When it has to do any of these, a new build is step 04 at EUR 3.500-7.500, and a site you already have takes the matching add-on, with the quote confirming the scope:

• Customer login and accounts
• Roles and permissions beyond editing content
• A dashboard that shows data rather than pages
• An API that another system reads or writes
• A CRM connection
• Payments and checkout
• A chatbot

If what you are describing is an admin panel for a product with accounts and billing, that is step 05, from EUR 7.500, priced after discovery.

Ownership

You own the code, the repository and the database. Content in a self-hosted CMS sits in your database; content in a hosted CMS can be exported as structured data that another system can import. Where the site is hosted is agreed per project. Ask who will hold the CMS account before the build starts.

Process and timeline

1. Scope. Your list of what changes becomes the list of fields and entry types. A fixed quote always follows scoping.
2. Design. Around your real content, not placeholder text.
3. Build. Templates, the CMS schema and the connection between them.
4. Content entry. Your text and images go in. This is the part that waits on you, because a template can be finished with empty fields but a site cannot launch with them.
5. Handover. A walkthrough of your fields, so you know what you can change and what counts as a care request.

Step 02 runs 2-3 weeks, step 03 runs 3-6 weeks, step 04 runs 6-12 weeks. The full description of each step is on the packages page.

When to spend less

• Your list has two lines on it. Skip the CMS. Care covers those edits as small fixes, and you never log in.
• You want a blog because a competitor has one. The bigger cost of a blog is the writing, not the CMS. A blog with an old last post tells a visitor the business has gone quiet; no blog tells them nothing at all.
• You cannot name the field today. Do not pay for it yet. Adding a field to a live site is a small piece of work; designing fields nobody fills is paid for in the build.
• You want traffic, not control. The money goes further in search work than in a bigger CMS. SEO foundation is a one-off at EUR 450-750, and SEO growth runs at EUR 500-800/mo.

Questions buyers ask

Is WordPress a bad choice?

No. It fits a business that publishes often and wants a familiar editor. It fits less well when the site has a handful of pages you rarely touch, because you take on core updates and plugin maintenance for an editor you barely open.

Can I move my content somewhere else later?

Content in a database you own, or in files in your repository, moves. Content locked in a site builder's page format moves as copied text, not as pages. Check before you commit.

Will a CMS make my site slow?

Not by itself. Pages can be generated when content is published, so a visitor loads a finished page and never waits on the CMS. Speed problems come from heavy plugins, oversized images and third-party scripts, and those can be avoided on any CMS.

Do I need a CMS to do SEO?

No. Titles, descriptions, headings and internal links can all be set in the build. A CMS helps only if you want to change them yourself. SEO foundation at EUR 450-750 is a one-off piece of work, and it is the same work whichever CMS you pick.

Bring your list of what changes, and tell us what you are building: you will get a step and a fixed quote after scoping.