When is a custom website worth it instead of WordPress — and when is it not?
What WordPress is good for — and this is worth saying out loud
WordPress serves a significant portion of the world's websites, and that is no accident. Cheap entry point, plenty of developers know it, hundreds of thousands of templates to choose from, and for a blog or a company presentation page it is still a completely reasonable choice today. Whoever says WordPress is "bad" either hasn't used it enough or wants to sell you something.
So the question is not whether WordPress is good. The question is whether your process is standard.
The three points where a template gets tight
1. The plugin chain
A template site rarely stays just a template. You need a form plugin, a caching plugin, an SEO plugin, a security plugin, maybe a multilingual plugin and a page builder. These update independently of each other, and a single update is enough to take down the cart or the form.
The practical consequence is not technical but business: the bug is not noticed first by you, but by the customer, who cannot place an order. And the fix does not cost zero.
2. Speed
A template loads as much as its creator imagined — not as much as your site needs. The page builder brings its own stylesheets and scripts, every plugin brings its own. The caching plugin softens this, but the ceiling is fixed: the amount of code to load cannot be removed after the fact, only deferred. I break this down in detail here: why the WordPress web store is slow.
3. Security
Checking the real type of an uploaded file, sanitizing submitted data, limiting abuse: this is code, not a switch. With a template system you get whatever the plugin vendor wrote — and you do not even know what they wrote. And a vulnerability in a public plugin affects every installation at once: the attacker only needs to find it once.
Do the math: the template's hidden operating cost
The comparison is fair only if you do not compare development price against development price, but the three-year total cost. The formula:
`` template 3-year cost = development + (annual fee of paid plugins × 3) + (annual hours of maintenance and bugfixing × hourly rate × 3) + lost revenue due to downtime and slowness ``
The last item is the hardest to estimate and the largest. If you cannot estimate it, leave it out — the other items are enough to reveal the difference. The lesson is the same in most cases: the template is not cheaper, it just pays itself off later.
Decision table
| If this applies to you | Then |
|---|---|
| The site presents, informs, has a contact form on it | Stay on a template, and spend on copy and photos instead |
| You run a blog, publish often, multiple authors work on it | WordPress is specifically good for this |
| You need to turn visitors into leads, and you want to measure this | Borderline case — a custom form and measurement can be built on top of a template too |
| You take orders that are not "quantity × price" | Custom development |
| You handle different prices or minimum quantities per customer | Custom development |
| You need to connect invoicing, inventory, ERP | Custom development or automation |
| You already pay monthly for someone to "fix" the site | Calculate the three-year cost before you pay again |
What can you take with you if you switch?
This is the most common fear, and the least justified. When switching, you can take with you:
- The content. Text, images, product data — these are exportable.
- Your Google rankings. Redirects run from the old URLs to the new ones, so the positions earned so far are not lost. This is the most important technical step of a migration, and if someone skips it, it shows in the traffic.
- The domain, the email, the analytics. These do not belong to the system.
What you do not take over: the plugins' settings — but those were exactly what you wanted to get rid of.
The wrong reason to switch
Do not switch because someone said "WordPress is slow". Switch because you can name, by name, the three things your current system cannot do, and that you pay for monthly — in time or money. If you cannot list these three things, switching will not solve the problem, it will only postpone it.
Frequently asked questions
How much more expensive is custom development?
The entry point is higher: with me, a custom website starts at $350 (€300), while a set-up template site can be done for $250–500. The difference shows up in the three-year operating cost, not the first invoice.
Won't a custom site be harder to maintain?
It is usually the other way around. A custom site does not have thirty foreign dependencies updating themselves underneath you. What is there was written by one person, and it is documented.
What if the custom developer disappears?
This is why you need to receive the source code, documentation and full access at handover, and why it is worth choosing established technology. If you have these, any developer can continue — that is the difference between a custom system and an "only he understands it" system.
Can the existing site be saved?
Often yes. First I review the code and tell you whether it is worth repairing or rewriting: taking over an abandoned website.