WordPress or a custom website: what should a business choose?

WordPress or a custom website: the short answer

For most business sites, service pages and WooCommerce stores the right choice is WordPress. It runs a large share of all websites with a known CMS (content management system), which means another developer is easy to find and many editors already know it.

A custom build without WordPress pays off when the site is not a showcase but a product: customer accounts, self-service, complex pricing, many users at once. Between the two is a third path we choose most often: a WordPress base with your own code where a template no longer solves the problem. The decision depends on who edits content, how complex the logic is and who maintains the site a year from now.

A "custom website" can mean three different things

The market uses the same word for three products:

• a ready-made template with your logo
• a custom design and clean code on WordPress
• a system built without WordPress

Prices differ several times over, so you can only compare offers once you know which one you are looking at. Our WordPress website is the second: a custom design, editing without a developer and as few plugins as possible. When an offer says "custom", ask directly: will it be WordPress, which theme, how many plugins, and can you change texts yourself.

When WordPress is enough and when you need a custom system

WordPress is enough when the site publishes content and collects enquiries: services, articles, forms, several languages, a catalogue or a store with a standard cart. Here it wins on time to launch and on the fact that you edit content yourself.

You need a custom system when users create and store their own data, when a process has many states (order, approval, production), when you need real-time sync with an ERP (business management system) or the load is high. The sign that WordPress is getting in the way: the same logic is handled by three plugins that conflict with each other.

Custom code: when your own code beats a plugin

Custom code does not have to mean a site built from scratch. More often it is your own plugin inside WordPress: a calculator, a pricing rule, an accounting integration. One example is the MDS Terasos calculator, which sends a size-based price to the WooCommerce cart.

Your own code pays off when a plugin does ten things and you need one, when its licence costs more each year than the work, or when no plugin has the logic you need. When a ready, maintained plugin solves the task, writing your own makes no sense. Custom code stays part of your project and is handed over with documentation.

Security and maintenance: what you pay after launch

According to Patchstack, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025: 91% in plugins, 9% in themes and just 6 in core. Almost half had no patch on the day they were disclosed. Risk grows with every plugin, so fewer plugins is both a security and a speed decision.

A custom site is not maintenance-free either: it has its own libraries, server and dependencies, only the patches come from your developer instead of a community. WordPress maintenance with us starts at €40/mo, custom work is €40/h. Whichever path you choose, the contract should state that the code, domain, server and analytics access belong to you.

Headless WordPress and changing course later

Headless WordPress means content is edited in WordPress while the visitor-facing site is a separate application, e.g. React. It gives a modern interface and speed while keeping a familiar editor. WordPress has had a built-in REST API (programming interface) for this since 2016.

The cost: you maintain two systems, and some plugins (forms, SEO, page builders) stop working in the separate app and have to be rebuilt. The choice is not forever: you can start with WordPress and later move one part into a separate application, keeping URLs and rankings with 301 redirects. Not sure which path fits you? Get in touch.