WordPress or custom software? A decision table
How the two approaches differ on cost, speed, maintenance and handover; a decision table showing which is right when, and how a staged move works.
Yazan: OSBSA Bilişim
This question usually gets framed wrongly. People ask "which is better", when the right question is "which will cause me fewer problems on my project". Both are legitimate choices, and both cost dearly when used on the wrong project.
What is WordPress, and what was it designed for?
WordPress is open-source software that started life in 2003 as a blogging tool and grew over time into a general-purpose content management system. Its strength is its ecosystem: ready-made themes, thousands of plugins, and a great many people who know it.
For sites whose content changes often and whose structure is standard, it's still a sensible choice. For a blog, a news section, a corporate presentation or a simple catalogue, it covers most needs.
What does custom software mean?
Custom software is an application written from scratch for the needs of the project. These days we usually do that with a modern application framework such as TypeScript and Next.js, on a server-rendered architecture.
The difference is this: with a ready-made system you push what exists to its limits, with custom software you write exactly what's needed. The price of that is the up-front cost and the time.
What are the differences between the two?
| Criterion | WordPress | Custom software |
|---|---|---|
| Up-front cost | Low | High |
| Time to launch | Short | Long |
| Content management | Ready-made, mature admin | Written for the project |
| Page weight | Carries theme and plugin load | Only the code that's needed |
| Performance ceiling | Bounded by caching plugins | Speed comes from the architecture |
| Custom business rules | Forced through a plugin or custom code | Written directly |
| Security surface | Grows with the number of plugins | Few dependencies, high control |
| Maintenance load | Core + theme + plugin updates | Dependency updates |
| Finding developers | Easy | Easy on common technology, hard on niche |
| Handover | Depends on theme and plugin knowledge | Easy if code and schema are documented |
| Integrations | Fast if a plugin exists, laborious if not | Designed in from the start |
When is WordPress the right choice?
- The site's job is showing information: presentation, service descriptions, contact
- Content is updated often and a non-technical person will do it
- A blog or news feed sits at the centre of the site
- Budget is limited and you need to launch quickly
- The needs are standard: contact form, gallery, simple catalogue
- There's no particular business rule or integration
When do you need custom software?
- There's role-based access: dealers, customers and staff see different things
- Prices change by user, or are hidden
- A calculation engine is needed: quotes, freight charges, pricing by dimension
- There's two-way integration with an ERP, accounting or production system
- Page speed matters commercially and the ceiling is being pushed
- The pile of plugins has already become unmanageable
- The data model is non-standard: products with variants, project-based records, multi-stage approval
Is it really more expensive?
Up front, yes. But it's more accurate to look at total cost of ownership over three years:
| Item | WordPress | Custom software |
|---|---|---|
| Setup | Lower | Higher |
| Annual plugin/theme licences | Present | Usually none |
| Update and compatibility maintenance | Regular, grows with plugin count | Less frequent |
| Cost of a special request | Hunting for a plugin, or code that forces it | Developed directly |
| Performance work | Extra tools and effort | Comes from the architecture |
| Migration / rebuild | Theme dependency causes trouble | Easy if the code is documented |
In short: commissioning custom software for a simple brochure site is money spent for nothing; squeezing a project that has business rules into WordPress is a deferred expense.
Is "WordPress is insecure" true?
The sentence isn't true as it stands. The WordPress core is actively maintained software. The great majority of security problems come not from the core but from plugins that never get updated, abandoned themes and weak administrator passwords.
The practical upshot: if you're going to use WordPress, keep the number of plugins to a minimum, don't use abandoned plugins, turn automatic updates on and take regular backups. If you're not going to do those things, the problem won't be the software, it will be the maintenance plan.
Six questions to decide with
- Does the site have rules, or only content?
- Is there a view or a price that changes from one user to another?
- Will there be data exchange with another system?
- Who will update the content, and how often?
- Do you have a three-year budget, or this year's budget?
- If the site is critical to the business, who will you reach in an outage?
If you answer "yes" to the first three, custom software is probably the right place to look; if "no", a ready-made platform is.
Is there a middle road?
There is, and it's often the most economical option: a staged move. The presentation side stays on a ready-made platform, the part that does the work — dealer portal, quote engine, calculations — gets written as a separate application, and the two are brought together under the same domain.
This approach spreads the budget over time, divides the risk, and lets you measure which side is actually producing value.
The decision is yours; here's the measure
WordPress is still a reasonable tool for sites that present information. Once business rules, permissions, integration or a performance ceiling come into play, you need custom software. The decision is made from the project's list of needs, not from any fondness for a technology.
If you'd like to talk through which is right for you, fill in the quote form; we'll work out your list of needs together in the scoping conversation.
- wordpress
- custom software
- cms
- choosing technology