When Your Brief Argues Against Your Platform

Most website briefs we see are well written. They set clear expectations. They want the site to be fast, secure, easy to maintain, and simple to update. They want minimal plugins. They want strong performance scores. They want compliance handled properly.

Then they specify WordPress.

Not because anyone weighed up the options and decided WordPress was the best fit. Usually because it's the only CMS most people have heard of, and nobody in the process thought to question it.

The pattern

Here's what the mismatch looks like in practice, drawn from real briefs we've reviewed (details changed, obviously).

Performance targets nobody's hitting. The brief requires a PageSpeed score of 90+ on mobile. When you check the competitor sites named in the same brief, none of them score above the mid-50s. The WordPress-based ones typically land in the 30s. The gap between the target and reality isn't a development problem. It's a combination of platform overhead and third-party scripts that no developer controls.

Security specs that are platform damage control. The brief includes a detailed security specification: change the admin URL, disable XML-RPC, disable the file editor, install a security plugin, change the database prefix. Every single item is a WordPress-specific mitigation. On a platform that doesn't have those attack vectors, most of the spec is irrelevant.

"Minimal plugins" instructions the platform can't honour. The brief asks for the site to use as few plugins as possible. But WordPress needs plugins for SEO, caching, security, cookie consent, forms, redirects, and image optimisation before any project-specific functionality is added. That's seven plugins as a baseline, and "minimal" hasn't started yet.

Cookie consent mentioned nowhere. The brief specifies GA4 and GTM for analytics and conversion tracking but doesn't mention cookie consent at all. Under UK law, one requires the other. On WordPress, that's yet another plugin to add to the pile.

What the brief is actually describing

When you strip out the platform name and just read the requirements, most briefs are describing a website that's lightweight, fast, secure by default, easy to maintain without specialist knowledge, and compliant out of the box.

WordPress can be made to do all of these things. But it takes significant effort, ongoing maintenance, and a layer of plugins to get there. The brief is describing the destination. The platform choice determines how much work it takes to arrive.

Before you brief anyone

If you're about to commission a new website, or if you're reviewing a brief right now, here are three things worth doing first.

Check the PageSpeed scores of your three closest competitors. Go to pagespeed.web.dev, paste their URLs, and look at the mobile numbers. That tells you what's realistically achievable in your market with the same third-party tools. If the best competitor scores in the 50s, a target of 90+ needs a conversation, not a line in a spec.

Read your security spec with fresh eyes. For each line item, ask: is this a universal security requirement, or is this fixing a known problem in a specific platform? If most of the items are in the second category, the platform choice might be worth revisiting.

Count the plugins you'll need before the project-specific ones. If your chosen platform needs seven plugins just for the basics, that's seven things to maintain, seven potential conflicts, and seven ongoing costs. On platforms where those features are built in, that entire layer of complexity doesn't exist.

The platform-agnostic approach

The right platform depends on what you actually need. Sometimes that's WordPress. For complex content sites with large editorial teams or for WooCommerce at scale, it's often the right call. Sometimes it's Shopify, when e-commerce is the core of the site. Sometimes it's a lighter CMS like ProcessWire or Statamic. Sometimes it's a purpose-built solution.

The CMS we've built and maintain was designed specifically for brochure and services sites where SEO, security, cookie consent, forms, and performance all need to be handled natively without relying on plugins. You can see how it works at ilovemotley.co.uk/cms.

The point isn't that any one platform is always the right answer. The point is that the platform choice should be a considered decision based on what the project actually requires, not a default that nobody questioned.

An honest agency will walk you through the trade-offs rather than nodding along with whatever platform the brief specifies. If yours doesn't, that's worth noticing.

If you're writing a brief or evaluating one, we're happy to take a look. No charge for an honest opinion on whether the platform matches the requirements. Get in touch, or take a look at how we approach web projects.