The website development process starts with a decision that quietly determines almost everything else: what will run the site. The three realistic options are an off-the-shelf CMS, a CMS plus page builder, or a fully custom build. Each is legitimate, and each is wrong for some businesses.
Option one: CMS with a standard theme
Systems such as WordPress install a theme and let you edit pages, posts, images and menus from a browser interface. The build is relatively quick, the cost is usually the lowest, and your team can handle updates without help.
The trade-offs are that popular themes are used by many sites, so your design will look familiar unless it is customised, and plugins need updating. Security depends on disciplined updating, backups and limited plugin use. If the site is mostly text, forms and images, this is often the sensible starting point.
Option two: CMS plus page builder
A page builder adds a drag-and-drop layout tool on top of the CMS. It lets you assemble pages visually without touching code, which speeds up changes considerably.
The costs appear later. Pages built this way often become a mixture of templates that are hard to keep consistent, the site gets heavier as more add-ons accumulate, and a full redesign can mean rebuilding every page rather than restyling a theme. Ask how many add-ons are involved and whether any are required for a feature you could get another way.
Option three: fully custom build
Custom code gives full control over performance, structure and unusual functionality. It suits businesses with genuinely distinctive requirements, or content-heavy sites where page weight matters.
Expect the highest build effort, a dependency on the developer for routine changes, and the most care needed around upkeep. A custom build is not automatically faster or better; it is a different allocation of cost between now and later.
How to choose
Ask four questions. How often will someone update content? What unusual functionality do you actually need? Who will fix things in three years, and will they still be reachable? What is your realistic budget for maintenance, not just the build?
If content changes monthly and the site is straightforward, a CMS fits. If a specific integration or performance requirement dominates the project, custom may be justified. If the answer is unclear, ask a provider to present both routes with the same scope so you can compare like for like.
A decision framework you can use in ten minutes
Answer four questions honestly and the choice usually makes itself. If content changes at least monthly and your needs are ordinary, choose a CMS, because editing cost dominates over a multi-year period. If there is one specific unusual requirement, price that requirement separately and see whether a CMS plugin covers it before committing to custom work. If your team has nobody who can write or publish content, weigh that heavily, since a site nobody can update becomes stale and therefore loses trust.
Also ask what happens when the person who built it leaves. Custom builds concentrate risk in a single relationship. CMS builds spread it, because any competent developer can work with them.
Migrating from an existing site
Moving platforms sounds straightforward and rarely is. Content has to be exported or re-entered, images relocated, redirects mapped, tracking reconfigured and forms reconnected. If your current site performs adequately, migrating for tidiness alone is rarely worth the disruption.
Ask for a migration plan that lists what moves, what will be rewritten, how URLs are preserved and who validates the result page by page. Test the new forms thoroughly, because integrations are the part most often missed.
Questions to ask before committing
Ask what will happen to your content if you ever leave, and whether the export is usable. Ask which tasks remain in the CMS and which need a developer. Ask how the site will be updated in three years, and confirm that domain, hosting and CMS accounts will be owned by your business rather than by the provider.
If you want help deciding, our website development guides set out the reasoning behind each approach. Send us a description of what you publish and how often, and we will tell you which route we think fits, including when the cheaper option is the right one.
Common questions
Is a CMS website cheaper to maintain than a custom build?
Usually, because a CMS lets your team edit text and images without a developer. Custom builds give more control and can be lighter, but routine changes then need someone with code access. The honest comparison includes your team's time as well as any monthly fee, so estimate how often content will actually change before deciding.
Do I need a CMS if my pages rarely change?
If you update content a few times a year and the site is small, you may not need an editing interface at all, and a lighter static build can work well. If you expect to add pages, update prices or publish articles regularly, a CMS will save money over time even if the initial build costs a little more.
Can I move my existing site to a different platform later?
It is possible but rarely free. Expect to rebuild the design, re-enter or migrate content, redo redirects and re-verify integrations. Ask a provider to structure content in portable formats and to hand over ownership of domains and accounts, since those are what make a future move feasible at all.