WordPress support, and moving off it when that is right
Keep the site you have working, or move it properly. Both are normal answers.
In short
We look after WordPress sites and we migrate them when a business has outgrown one. The routine half is updates, backups, speed, security and the checks that catch a silent failure before a customer does. The occasional half is a migration, which is mostly a URL mapping exercise and only partly a build. We work on the platform you are on rather than selling you a different one, and if the honest answer is that your site is fine, that is the answer you get.
Work it out in a minute
Nine questions across revenue, capacity and control. Shows which of the three is costing you most, and where to start.
What we take on
Updates that somebody watches
Core, themes and plugins updated on a schedule with a backup taken first and the site checked afterwards. The risk in updating is real and it is much smaller than the risk in not.
Speed, in the order that pays
Hosting, images, caching, then plugins. Most sites get most of the improvement from the first two, which is why the diagnosis matters more than the tooling.
Security that is mostly hygiene
Fewer plugins, current versions, real backups you have tested restoring, and admin accounts that belong to people who still work there.
The checks that catch silence
Forms that stopped sending, a payment step that fails on mobile, a page that started 404ing after an update. These do not announce themselves and they are found by looking on a schedule.
Migrations, URL first
A move is a mapping exercise before it is a build. Every existing address gets a destination and a redirect, and that plan exists before anything is built.
Content, brought properly
Posts, pages, images and the structure that connects them. The part people miss is internal links, which quietly turn into 404s the day the addresses change.
Handover, either way
Whether we are maintaining or moving, the accounts are in your name and the documentation is written for whoever does this next, including when that is not us.
We will say when to leave it alone
Plenty of WordPress sites need nothing but hosting and an update schedule. Saying so costs us the project and it is the reason the next conversation happens.
Where WordPress sites actually go wrong
Almost never in the way people expect. The failures we find are updates nobody owned, a plugin doing a job that should have been a paragraph of code, and a form that stopped delivering four months ago with nothing to announce it. All three are ownership problems rather than platform problems, and all three are cheap to fix once somebody is watching.
Speed is the second, and it is usually simpler than the advice suggests. Hosting and images account for most of it on most sites. Plugin bloat is real and it is third, behind two things that can be fixed in an afternoon without touching how the site is built.
Migrations go wrong in exactly one place: the addresses. Content moves reliably, design is rebuilt on purpose, and both are visible when they fail. A missing redirect is invisible until the traffic report three months later, so the URL map is the first artefact of the project rather than a task near the end.
What we will not do is sell a rebuild to a business that needs a maintenance schedule. If you are trying to work out which of those you are, there is a page on this site for exactly that decision, and it is written to talk you out of the expensive one where that is the right answer.
Questions we get
Do you take over a site somebody else built?
Yes, and that is most of this work. The first pass is an inventory: what it runs on, which plugins matter, where the accounts are and who else still has access.
That inventory is worth having whoever maintains it afterwards, and you keep it.
What does the maintenance actually cover?
Updates with a backup first, uptime and error checks, the forms and payment steps tested rather than assumed, speed watched over time, and a short note on what changed.
The part that matters is that somebody is looking. Most of what goes wrong on a WordPress site is silent.
Can you speed up our site without rebuilding it?
Usually, and it is where we would start. Hosting, images and caching between them account for most of the difference on most sites.
If the answer turns out to be structural we will say so, but that is not the common case and it should not be the first assumption.
We want to move off WordPress. Where do you start?
With the URL map, before anything is designed. Every existing address needs a destination, and that document is what protects the search traffic you already have.
Then the content model, then the build. Whether it is worth doing at all is the question on our stay, refresh or rebuild page.
Is our site secure?
The honest answer needs a look, but the pattern is consistent: out of date plugins, too many of them, admin accounts belonging to people who have left, and backups nobody has tried restoring.
Fixing those four covers most of the realistic risk for a business site.
What if we already have a developer?
Then you may need nothing from us, and we will say so. Where we usually help teams that have one is the parts nobody owns: the update schedule, the checks, and the migration plan.
We work alongside internal people more often than instead of them.
More in the guides and every answer in one place.
Shaheer Shaikh, C-suite operations lead for a San Francisco AI company working with global pharma on clinical trial data and model benchmarking. Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built