How to pitch a WordPress rebuild without sounding negative

Pitching WordPress rebuilds is a different job from pitching a website to someone who has never had one. A business owner with an existing site, however tired, has already paid for it, is used to it, and probably feels some loyalty to whoever built it, even if that person hasn't answered an email in two years. Open with “your website is outdated” and most owners hear “you made a bad decision”, which is not a promising start to a sales conversation. The freelancers who land rebuild work consistently tend to lead with something closer to risk and opportunity, and leave the criticism out entirely.

Why the direct approach backfires

Telling someone their site looks dated is true often enough, but it puts the owner on the defensive before you have said anything useful. Most people do not experience their own website the way a stranger does. They see the logo they chose, the photos they picked, the copy they wrote or approved, and criticising the design can read as criticising those choices. It also assumes the owner agrees the site is a problem, which they may not, especially if enquiries are still coming in from other places. A pitch that opens with a judgement invites a defence of that judgement rather than a conversation about what to do next.

Lead with something specific and checkable

A stronger opening points at one concrete thing the owner can go and look at themselves, rather than a general opinion about the site's age or style. “Your contact form doesn't send an email when it's submitted” or “the site takes around nine seconds to load on a phone on a normal connection” are statements the owner can verify in thirty seconds, and they carry no implied opinion about taste. The signs worth checking before you write anything are covered in old WordPress site problems: what to look for, and the same discipline applies here: find one real, specific thing, not a list of everything that could be better. A pitch built on a single verifiable fact reads as helpful. A pitch built on several opinions reads as a sales script.

Frame the rebuild around what it protects, not what is wrong

Once you have the owner's attention with something specific, the case for a rebuild lands better when it is framed around continuity and risk rather than a fresh start for its own sake. An old WordPress theme running plugins nobody has updated in years is not just unfashionable, it is a security exposure and, eventually, a site that stops working when a hosting change or a plugin update breaks something nobody is watching for. Framing it that way, “the risk is that this breaks without warning, and a rebuild gets you off a version nobody is maintaining”, gives the owner a business reason to act rather than a design reason, and it does not require them to agree their old site looks bad.

Decide whether it is actually a rebuild

Not every ageing site needs replacing, and saying so where it is true builds more trust than pushing a rebuild regardless. A site that loads acceptably, works on a phone and simply has not been logged into in a while is usually a maintenance job, not a rebuild, and pitching it as one can cost you the smaller, easier sale entirely. A rebuild becomes the honest recommendation when the problems are structural: a layout that genuinely breaks on mobile, a page builder nobody can touch without something else moving, or a platform the business has outgrown. Being willing to say “this doesn't need a full rebuild, but it does need someone looking after it” is a small thing that makes the next pitch, when a rebuild really is the right call, far more credible.

Scope it before you quote it

A rebuild pitch that goes straight to a headline price without scoping the work first tends to either scare off a cautious owner or under-quote a job that turns out to be bigger once you are inside it. Migrating content, redirecting old URLs so search rankings and existing links do not break, and matching or deliberately changing the site's structure are all decisions worth making explicit before a number goes in an email. Getting this stage right matters more for a rebuild than a new build, because the fixed points, existing content, existing traffic, existing integrations, are already set and easy to underestimate. The general discipline of scoping a website project so it stays profitable is covered in scope creep in web design: keeping projects profitable, and a rebuild is exactly the kind of job where skipping that step shows up later as unpaid hours.

Offer maintenance alongside the rebuild, not after it

A rebuild without a maintenance plan attached usually just recreates the same problem a couple of years later: a site nobody is watching, running plugins nobody is updating, waiting for the next freelancer to pitch a rebuild of the rebuild. Raising ongoing care as part of the same conversation, rather than as an afterthought once the new site is live, tends to land better and gives the relationship a reason to continue past the handover. It also turns a single invoice into a recurring one, which matters more to most freelancers' income than any individual project fee.

Finding the sites worth this kind of pitch, rather than guessing from the outside, is the slow part when you are doing it business by business. Patchscout is built to speed that up: search a trade and UK location and Patchscout crawls and audits every result, checks the platform, speed, mobile behaviour and WordPress version where it can, and scores each prospect on how good a fit it looks like for a rebuild rather than a smaller job. It then drafts a first email grounded in the specific thing it found on that site, in your own voice, so the opening line is a fact rather than a guess. The three free searches at app.patchscout.co.uk/signup are enough to see how many rebuild-worthy WordPress sites are sitting in a trade you already know.