WordPress or Custom? The Questions That Settle It

Neither is a religion

The WordPress-versus-custom argument attracts more identity than analysis. Both are appropriate in different situations, and the same agency should be willing to recommend either.

Here is the framing that settles it in one conversation: is your site mostly content that people read, or mostly behaviour that people use? Content favours WordPress. Behaviour favours a custom build.

Where WordPress is genuinely the right call

• Marketing sites, blogs and anything where publishing volume matters
• Teams who need to add and edit pages without a developer
• Businesses that want a large pool of people able to maintain it
• Projects where an ecosystem plugin genuinely does what you need
• Budgets where a custom build would eat the whole allowance

The editorial independence point is underrated. A marketing team that can ship a landing page on a Tuesday afternoon without a deployment is worth a great deal.

Where it becomes expensive

WordPress gets costly when you use it as an application platform. Complex user roles, bespoke workflows, heavy integration, unusual data models — all possible, all more work than they would be elsewhere, and all fragile at upgrade time.

The tell is the plugin count. When you have bought four plugins to work around limitations and written custom code to make them cooperate, you have built a bespoke application with a content management system underneath it — at a higher price than building it directly.

The five questions

1. Who edits content, and how often? Daily by non-technical staff pushes hard towards a CMS.
2. Is the value in the content or the functionality? Content, WordPress. Functionality, custom.
3. How many systems must it talk to? One or two, fine. Five with bespoke logic, custom starts winning.
4. What is the data model? Pages and posts fit naturally. Complex relational data does not.
5. Who maintains it in three years? WordPress skills are abundant; specific framework skills less so, and that matters for a small business.

The hybrid that often wins

You do not have to choose one for everything. A common and sensible arrangement is WordPress for the marketing site and a separate custom application for the product, on a subdomain or path, sharing design.

Marketing gets independence, engineering gets a clean platform, and neither is compromised to accommodate the other. The cost is one extra deployment target, which is a small price.

Cost and timeline in practice

Frequently asked questions