Site builder, CMS or custom development: how to choose

The question of what to build a site on isn't settled once and for all — it's a choice made against a specific task, audience and planning horizon. Each of the three approaches has an area where it's justified and a point where it starts working against the business.

When a CMS is enough

An off-the-shelf content management system suits a site with standard content types — pages, articles, a product catalogue — and clear editor roles. The upside of a CMS is a mature ecosystem of ready components and a quick launch. But that only holds if the business processes fit the platform's logic and whoever owns the site is prepared to update the system and its extensions regularly — otherwise technical debt and vulnerabilities accumulate.

When custom development is justified

Custom development is needed when the site isn't a shop window but part of the core product or an internal management system: complex access rights, non-standard calculations, statuses, data exchange with other systems. It's worth understanding that custom doesn't mean "from scratch with no ready-made library" — frameworks and cloud services are used there too. The difference isn't independence from other people's code but control over the data model and the interface. Without testing, documentation and a clear architecture, custom development easily costs more than any CMS.

How to choose: five steps

• List content types, user roles and how often things change.

• List the integrations you need and think through what happens when they fail.

• Assess requirements for speed, SEO and accessibility.

• Compare licences, development cost, hosting, updates and support.

• Establish in advance what it costs to export your data and move to another contractor or platform.

Security and performance aren't an argument for either option

Popular CMSs require timely security updates — a platform being well known means its vulnerabilities are well known too. Custom development reduces the attack surface only with mature engineering practices, not automatically. Both approaches can produce fast, well-indexed HTML — the difference is usually discipline with metadata and third-party scripts rather than the type of platform.

The thing to settle up front

The ability to export your own data — pages, media, users, redirects — should be an architectural requirement from the beginning, not a question that only comes up once the business wants to change contractor or platform.

If you're not sure which option suits your particular task, we can go through it and propose something that won't cost more after a year of support than it appeared to at the start.