In short
- A CMS is where you change the words and pictures on your site. A custom one is shaped around your business instead of around every business at once.
- Custom means fields: a menu item has a name, a price and a description; a location has hours and a phone number; nothing else gets in your way.
- Most custom CMS setups are headless. You edit in one place, and a pre-built site shows the result.
- It is not for everyone. A site that changes twice a year, or a publication with ten writers, may be better served elsewhere.
- AI coding agents have made custom editors quicker to build, so they now sit in the same fixed-price range as a well-built WordPress site.
What a CMS does, seen from a Saturday morning
A bakery in Boerne sells out of kolaches by nine on Saturdays and wants the website to say so. The owner has also raised the price of a dozen by a dollar, hired a new counter manager, and decided to close early on Christmas Eve. Four changes, none of them design. That is the ordinary life of a small business website, and it is the job a content management system exists to do.
A CMS is the part of a website where people who are not developers change content: text, prices, photos, posts, hours. Without one, every change is a message to whoever built the site and a wait for the reply. With a poor one, every change is a small gamble. With a good one, the bakery owner makes all four edits in ten minutes on a phone, between batches.
For the general background on what a CMS is and how the common systems compare, What is a CMS? covers it. This guide is about one particular kind: the custom CMS we put behind a Next.js build, what makes it custom, and who should and should not want one. It is one part of the larger WordPress vs. Next.js decision.
Headless and traditional, from the editor's chair
Developers argue about architecture. Owners experience it as a login screen, so here is the difference from that side of the desk.
A traditional CMS is the website. WordPress is the familiar example: you log into the same software that serves pages to visitors, edit a page more or less as it appears, and the change shows up because the public site reads straight from that database. Editing and serving live under one roof. That is convenient, and it is also why a plugin installed to help the editor can end up loading on every public page.
A headless CMS is only the editor. It stores your content as tidy records and hands them to a separately built site, which turns them into pages. When you press Publish, the affected pages are rebuilt and pushed to the CDN, typically within a minute or so. Visitors never touch the editor, and the editor never slows down the visitors.
Most custom CMS setups are headless, because separating the two is what lets the editor be shaped around your content while the site is shaped around your customers.
| Traditional (WordPress) | Headless custom CMS | |
|---|---|---|
| What you log into | The software that runs the public site | A separate editor that only holds content |
| What an edit looks like | A page canvas, blocks or a builder layout | A form with your fields: price, hours, photo |
| What you can change | Nearly everything, layout included | Content only; the design is set in code |
| When visitors see it | Immediately, from the live database | After a quick rebuild of the affected pages |
| Editor add-ons and speed | Plugins can load on public pages | No effect; the editor is not part of the site |
| Feeding an app or second site | Possible, with extra work | Built for it |
What "custom" means: fields shaped like your business
Off-the-shelf systems are built for every business at once, so they offer a blank page and a toolbox. That is generous, and it hands the job of structure to you. Every service page is laid out by hand, and every price lives wherever someone happened to type it.
A custom CMS starts from a question we ask in the first meeting: what do you change, and how often? The answers become the content model, the list of things the editor knows about. A landscaping company might end up with Services, Service areas, Seasonal offers, Projects and Reviews. Each has its own fields. A Service has a name, a starting price, a short description, a longer one, photos, and the towns where it is offered. A Service area has a town name, a few sentences about working there, and the services available.
Those records then appear wherever they belong. Change the starting price of sod installation once, and it updates on the service page, the town pages, the pricing table and the structured data search engines read. Nobody hunts through twelve pages for every place the old number was typed, and nobody misses the one on the Kerrville page.
You fill in the price. The site decides where the price goes.
What the editor holds for different kinds of business
The content model changes with the business. A few starting points from the kinds of companies we build for:
| Business | What they change most | Fields in their editor |
|---|---|---|
| Restaurant | Specials, menu prices, holiday hours | Menu items with price and dietary tags; specials with start and end dates; hours by day |
| Plumbing or HVAC company | Prices, service areas, seasonal offers | Services with starting prices; towns served; offers that expire on their own |
| Dental or medical office | Providers, insurance accepted, hours | Provider profiles; insurance plans; hours and new-patient status by location |
| Law firm | Practice areas, attorneys, case results | Attorney bios with bar admissions; practice pages; results with required disclaimers |
| Multi-location retailer | Store hours, events, staff | Locations with their own hours, phone and map pin; events tied to a store |
| Salon or spa | Services, stylists, prices | Services with duration and price; stylist profiles; a booking link per stylist |
Starting points, not templates. Every model is drawn from what the business actually edits.
Notice what is missing from every row: margins, fonts, column widths, slider timing. Those belong to the design, and the design belongs to the code, where a developer changes it on purpose and on the record.
How editing feels next to Gutenberg and Elementor
Take one ordinary job. The price of a teeth-whitening package goes from $299 to $349, and it appears on the services page, a specials banner, and a landing page left over from last spring's promotion.
The same price change, three ways
- 1
In Gutenberg, the WordPress block editor.
Open each page, find the block that holds the price, edit it, press Update. Repeat for every page. Hope nobody put the old price inside an image.
- 2
In Elementor or another page builder.
Open each page in the builder canvas, wait for it to load, click into the right widget among nested sections, edit, save. Check the mobile view too, because builders can store some settings per device.
- 3
In a custom CMS.
Open the Teeth whitening service, change the price field to 349, press Publish. Every page that shows the price rebuilds with the new number, and so does the structured data.
The builder approach is not foolish. It was designed so anyone could make any page look like anything, and it delivers on that. For a business that edits a dozen recurring facts, though, the power mostly shows up as places to make mistakes. A field is less exciting than a canvas. It is also far harder to get wrong.
There are two honest costs. First, you cannot drag a brand-new kind of section onto a page on a whim; new page types come from the developer. We build a library of approved sections so most new pages are assembled from parts, but the library has edges. Second, the editor is a separate login from the site, which takes a day or two to stop feeling strange.
Who does not need a custom CMS
A custom editor is worth building when there are recurring things to edit. Plenty of businesses do not have them, and we would rather say so than sell one.
You can probably skip it if
- Your site changes twice a year or less. A developer can make those edits faster than you could learn any editor, and a site with no CMS has even less to maintain.
- You publish like a magazine. Several writers, daily posts, editorial review and a deep archive are home ground for WordPress, and WordPress web design may be the better path.
- You are starting out on a very small budget. A hosted builder or a lean WordPress setup costs less up front, and that matters when cash is tight.
- Your site is mostly a store. A dedicated store platform's catalog, checkout and inventory tools usually beat a custom build for a product-heavy business.
- A plugin you rely on has no equal. Some membership, course and booking plugins carry years of features. Rebuilding them is possible, and often not worth it.
If you are on WordPress and none of that applies, the real question is whether to fix what you have or move. The free Should I Leave WordPress? check answers it for your actual site, and WordPress repair handles the fix side when that turns out to be the answer. If the editor is not the problem but the speed is, why WordPress is slow explains where the time goes.
What a custom CMS costs to own
There are two numbers to think about: the build and the upkeep.
The build is part of the site, not a separate purchase. Our custom builds on either platform are a fixed price, most often between $6,000 and $20,000, and the content model and editor are included. The biggest variables are how many content types the business needs and how much existing content has to be moved and cleaned. Builds can be spread over time at 0% interest with 25% down, as the financing page explains.
Upkeep is where the difference shows. Because the editor is our own, there is no CMS vendor charging by the seat, the record or the visitor, and no price list that changes under you. The database and file storage behind it are ordinary hosted services, billed at small business rates to an account in your name; ask for the current figure in writing before the build, as you would with any bill. Hosting for the pre-built site is often modest at small business traffic. What is missing from the list matters just as much: no premium plugin renewals, no builder license, no monthly round of updates to test.
The five-year cost of a WordPress site puts the two approaches side by side over time, and how much a website costs covers the build budget in general.
0
plugin or builder licenses to renew
1
place to change each fact on the site
25%
down to start, with 0% financing on the rest
How AI agents speed up building one
Building a custom editor used to mean a great deal of careful, repetitive work: defining every field, writing validation rules, building preview screens, and moving years of content out of WordPress by hand. That repetition is exactly where AI coding agents earn their keep.
On our builds, agents draft the content model from an inventory of your current site, generate the field definitions and editing screens, write the migration scripts that move each post and page into the right fields, and run tests that confirm every record renders properly. A developer reviews each change, corrects the model where an agent guessed wrong, and decides what ships. Nothing is generated by a chatbot and published unread, and none of your content is replaced with generic AI copy.
The practical effect is that a custom editor now fits inside the same fixed-price range as a well-built WordPress site. The hours that used to go into plumbing go instead into the parts you will notice: field labels in your own words, previews that look like the real page, and rules that catch mistakes before they go live. How AI agents build websites covers the workflow in more detail.
See your business done properly before you spend a dollar.
We will design a new home page for your business and show it to you at no cost. Custom, built the way a real development shop builds. Keep it either way.
Not sure whether to fix WordPress or leave it?
Pick what sounds like you. We will look at the site you have, tell you whether a repair or a rebuild makes more sense, and put a rough number on each. Free, and the findings are yours either way.
Which of these sounds like you? (pick any)
Questions people ask
Straight answers
WordPress is a general-purpose system that serves both the public site and the editor from one installation, with plugins and builders for everything else. A custom CMS is an editor shaped around one business, with fields for its services, prices, hours or menu, usually running separately from a pre-built site. WordPress offers more freedom to change layouts. A custom CMS offers fewer ways to break things and no plugins to maintain.
Usually, yes, after a short walkthrough. Because each screen holds only the fields that matter, such as a price, a photo or a set of hours, there is little to learn and little to get wrong. Roles can limit what each person sees, so a front-desk employee can update hours without reaching anything else. Most people are comfortable with it within a day or two.
You should, and the contract should say so. Your content belongs to your business and ought to be exportable in a standard format, such as JSON, that another developer could pick up. Before a build starts, ask the developer to put ownership in writing and to name whose account the CMS lives under. A clear answer to both questions means you can leave with your content if you ever need to.
Yes, and that is one of its strengths. Adding a service or a location means creating a new record with the same fields, and the site builds the page, adds it to menus and fills in the structured data on its own. Adding a whole new kind of content, such as events or a careers section, is a developer task, usually a small one, because the model was designed to be extended.
No, and it should not be. We built our own CMS once, run our own site on it, and reuse its foundation for every client: sign-in, drafts, scheduled publishing and the publish step that rebuilds pages. What each business gets new is its content model: the content types, fields, labels and validation rules that match how it works. You pay for fitting the editor to your business, not for reinventing a login screen.
Yes, if it is built properly, and you should insist on it. A preview shows the page exactly as visitors will see it, with your changes in place, before you publish. Scheduled publishing is common too, so a holiday closure or a seasonal offer can go live and come down on set dates without anyone having to remember to do it.
Where to go from here