Skip to main content

WordPress Development

WordPress built properly, and the honest line at which it stops being the right tool. Plugin count is usually the tell.

Where WordPress Is Genuinely The Right Answer

Publishing. It is very good at it, it is cheap to run, and anybody can edit content without a developer. For a site whose job is to explain what a business does and generate enquiries, it is difficult to justify anything else.

It is also the right answer when the alternative is a bespoke content system nobody outside your supplier can maintain. Mainstream and well-understood beats elegant and unfamiliar for anything you intend to keep.

Where It Stops Being The Right Answer

When it becomes the platform rather than the website.

The pattern is familiar. A plugin for forms, another for memberships, another for bookings, a custom post type for products, one more for events. Each solved a real problem. Several years later the site runs a business-critical process across forty plugins that interact in ways their authors never anticipated, and nobody dares update anything.

Plugin count is the tell. Not because plugins are bad, but because each is a dependency whose maintenance you have inherited. Forty means forty authors who might abandon their work, and one abandoned plugin doing something important is the most common route into a WordPress site.

The Honest Split

Content in WordPress, business logic somewhere it can be tested and maintained properly.

That is usually the right architecture once a site has outgrown publishing. The booking engine, the membership rules, the pricing logic become an application with its own database, and WordPress does what it is good at.

The alternative, pushing further into plugins, works right up until an update breaks checkout and nobody can tell which of forty is responsible.

WordPress We Run

We run three WordPress sites for a lead-generation business. Each is a branded site with multi-step quote forms, and WordPress handles the pages and the forms. Everything after the form happens in a separate Laravel platform, which is where the split above would put it.

A form can stop working without anyone noticing, because a broken form produces no error, only fewer enquiries. The platform watches the submissions from each form and emails the team when one starts failing.

A legal-marketing platform we built uses WordPress in the same way. Its public site shows a benchmark directory of law firm websites and some preview widgets, but the data and the customer logins live in the application behind it, and the site displays what the application sends.

What Moves The Price

Plugin count and quality, on any existing site. Auditing what is there is frequently the first real piece of work.

Whether the theme is bespoke or a purchased multi-purpose one with a page builder. Builder-based sites are considerably more expensive to change, because content lives inside builder markup rather than as content.

How much business logic is in the site versus content.

Whether it needs to stay editable by non-technical staff. A genuine constraint that shapes the build.

Performance requirements. A fast WordPress site is achievable and takes deliberate work.

Where WordPress Projects Go Wrong

Updates deferred because something breaks. The site freezes at a version accruing published, catalogued, actively scanned-for vulnerabilities. This is the single biggest risk on any WordPress site and it is a process failure rather than a technical one.

No staging. Changes going straight to live, on a site running dozens of plugins, is how a Tuesday afternoon becomes an outage.

Page builder lock-in. Content stored as builder markup makes leaving expensive, and the cost rises every year.

Nobody owns the plugin list. Plugins accumulate, nobody removes them, and the attack surface grows quietly.

Questions To Ask Whoever Maintains It

  • How many active plugins, and when did each last receive an update? Anything over two years old is a liability.
  • Is core on the current major version, and if not, why?
  • Is there a staging site?
  • When did we last restore from a backup? Not whether they run.
  • Could a non-technical person change a headline? If not, the build is costing you more than hosting.

A Brief You Can Send Anyone

What the site does: [publishing, or something more]
What it runs on now: [theme, builder, rough plugin count]
What we cannot do that we need to:
Who edits it: [and how technical they are]
What must keep working: [forms, bookings, payments]
Performance or accessibility requirements: [if any]
Where it is hosted: [and who has access]

How We Work On It

An audit first on any existing site: what is installed, what is maintained, what is duplicated, what is exposed. That usually pays for itself immediately by removing things.

Then stabilise, get a staging environment in place, and only afterwards discuss features. Where genuine business logic has accumulated in plugins, moving it out into a proper application is the durable answer, and web application development covers that side.

For sites that have already become platforms, old WordPress systems describes the untangling in more detail. Get in touch with your plugin list.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.