You do not need a rebuild to change who looks after your site. Most inherited sites can be supported as they stand, once somebody has established what is actually in them.
Agencies are often quick to recommend a rebuild when they inherit a site, and sometimes that is right. But it is also the answer that suits the agency, and plenty of sites are perfectly sound — they have simply been neglected, or the person who understood them left.
What an inherited site usually lacks is not quality but knowledge. Nobody knows why a particular plugin is there, what that scheduled task does, or which of the three staging copies is current. That is a documentation problem, and it is far cheaper to fix than a codebase problem.
So we start by establishing what is there and writing it down. Only then is it possible to say honestly whether the thing is worth keeping — and to show you the reasoning rather than asking you to take it on trust.
What we do
Working UK-wide — directly with businesses, and white label behind design and marketing agencies.
Discuss a projectPlatform, versions, and how far behind they are. Being behind is normal; being so far behind that updating is itself a project is the thing worth knowing.
Which parts are off-the-shelf and which were written for you. The custom parts are where the risk and the value both sit.
Payment providers, CRMs, feeds and third-party services — including any running on credentials belonging to somebody who has left.
Known vulnerabilities in the versions running, and anything exposed that should not be. This is usually the most urgent finding.
Whether backups exist, whether they run, and whether a restore has ever been tried. All three are different questions.
Whether changes can be tested before they go live, or whether every edit has been made directly on the production site.
A fixed price for supporting code nobody has read is a guess. The review is what makes a real quote possible.
Whether or not you go on to work with us. You should not have to buy a relationship to find out what you already own.
If the review turns up something actively dangerous — an exposed admin, an unpatched vulnerability — you hear about it that day, not in a report.
A lot of our work is delivered white label or under agreement, so these describe the problem and the approach rather than naming the client.
Ten brand websites across one instruments group. Several we built, the rest we inherited — and all ten are hosted, maintained and supported by the same team.
Migration · DevelopmentFive separate legacy CMS sites, five databases and five themes, consolidated into a single multilingual multisite CMS platform.
Multisite · MultilingualA multisite platform serving several regional websites from one build, each with its own content and language.
We will review what is there and tell you what you have, what state it is in and what supporting it would involve — including when the right answer is to leave it alone.