Kimb Jones

Here we go again. I have heard some version of “we need a rebuild” more times than I can count. Sometimes it is true.

Sometimes the website really is too old, too limited, too messy, too slow, too hard to use or too far gone to keep patching.

But often, “we need a rebuild” is not the first problem it is just the latest symptom.

It is what people say when they have run out of confidence in the current WordPress site. The site might still be live. It might still look fine from the outside. It might still be getting enquiries, publishing content, serving customers or supporting campaigns.

Clients often get nervous about updates. They gripe that changes take too long. Nobody is quite sure what the last freelancer built. A new page takes days instead of hours. A simple navigation fix becomes a whole technical discussion.

Should you just rebuild?

A rebuild can be a good answer, but it is also a very expensive way to answer the wrong question.

If the real issue is unclear ownership, weak hosting, risky updates, plugin sprawl, poor staging, broken tracking or a messy support process, then a redesign may only change the surface.

You might end up with a nicer-looking version of the same problem, and this is the bit I think often gets missed. When clients say “we need a rebuild”, it is worth slowing down and asking what they actually mean. Do they mean the design no longer works, or that the site is hard to edit? Is performance the real issue, or is the plugin stack making everyone nervous? Is the hosting unclear, or does nobody know what is safe to change anymore? Those are all different problems, and they do not all point to the same solution.

Some of those problems might lead to a rebuild. Others point towards better support, hosting improvements, rescue work, a safer release process or a proper technical review. This is why I am talking more about reliability. Not reliability as in “is the site online?”, but reliability as in whether the site can be understood, updated, supported and improved without everyone holding their breath.

A reliable website gives people confidence. It gives them confidence to publish, update, run campaigns, plan improvements and make decisions without guessing. That does not always require a rebuild. Sometimes the better first step is to understand what is actually making the current site hard to trust.

That is the idea behind the WordPress 5-Day Reliability Sprint at Make Do. It is for teams who know their WordPress site has become slow, fragile, risky to update or difficult to improve, but are not sure what the next step should be. The answer might be support, hosting, rescue work, a phased improvement plan or a rebuild, but at least the decision comes from evidence rather than frustration. That feels like a better place to start.

Take a look at our WordPress 5 Day Reliability Sprint service.

I’m back! And I have been doing some work on the Make Do website recently.

Not a full rebuild. Not a rebrand. Not even the full future strategy, really. More like a bit of tidying up around what we actually help with now.

And the thing I keep coming back to is reliability of WordPress sites.

Not just whether a site is online. Not just whether the hosting is fast. Not just whether WordPress, plugins and PHP are technically up to date and issues like:

• Whether it is safe to update.
• Whether it is easy enough to improve.
• Whether the people using it actually trust it.
• That is where a lot of WordPress pain really sits.
• A site can be live, technically working and still be a problem.

It might be slow to change. Updates might feel impossible. Nobody might fully understand the plugin stack. The original agency might have moved on. The hosting might be fine on paper but unclear in practice. A small landing page change might take far longer than it should.

That kind of thing does not always look dramatic from the outside.

The site is still there. Pages still load. Forms might still work. Nothing is necessarily on fire.

But internally, the client starts to lose confidence. We’ve had this happen a lot at the agency, so this is my chance to “package up” all that we’ve learned over the years into a new helpful service offering.

For years, “WordPress agency” was a useful shorthand. It still is, to a point. We are still very much a WordPress-first technical agency.

But a lot of the work now is not just “build a WordPress site” because it is helping teams manage websites that have become more important, more connected and more operationally awkward over time.

The website might be connected to sales, marketing, CRM, ecommerce, reporting, internal workflows, forms, customer journeys or content operations.

At that point, it is not just a website, it is a system, a platform, a thing that MUST work that is part of how the organisation runs

So, enter our “WordPress 5-Day Reliability Sprint” which is a practical first step for teams who know their WordPress site has become slow, fragile, risky to update or difficult to improve, but are not sure what should happen next.

We review the current setup, identify the biggest risks, make practical fixes where possible and give the team a clearer route forward.

It is not a magic wand, and it is not a full rebuild in five days. It is a practical way to get a handle on what is actually going on, which feels like the right place to start.

So yes, I am going to be talking more about WordPress reliability, not because it sounds trendy, but because after working with WordPress for a long time, this is where I see a lot of the real problems sitting: in the messy middle between support, hosting, plugins, old decisions, internal teams, previous agencies, content workflows and the next thing the organisation needs the site to do. That is where reliability matters, and that is where Make Do can help.