The Question We Get on Every Discovery Call

Here's the thing. We're not anti-WordPress the way some people are anti-gluten. WordPress runs something like 40% of the web, and for a huge slice of it, that's the right call. A local newsletter, a recipe blog, a five-page brochure site someone updates twice a year — WordPress is genuinely brilliant for those.

But you didn't come to a studio that calls itself a digital atelier because you wanted the same thing 40% of the web has.

Think of It Like a House

Imagine two ways to get a home.

The first: you buy a pre-fabricated house and start bolting on extensions. A conservatory from one supplier. A loft conversion from another. A smart-home kit you found online. Each addition works on its own. But none of them were designed to live together, and every new bolt-on is another seam where water can get in, another thing the previous builder has to keep updating, another joint that creaks when the wind blows.

The second: an architect draws the whole thing as one structure. Every beam knows about every other beam. Nothing is bolted on, because nothing needs to be — it was all there in the plan.

That, more or less, is the difference between a page-builder stack and a custom-coded site. WordPress, in practice, is rarely just WordPress. It's WordPress plus a page-builder plus a dozen plugins for forms, SEO, caching, security, image optimisation, GDPR consent, and the one obscure thing your booking system needs. Each plugin is a bolt-on built by a different team with different priorities, glued to the others and hoping for the best.

We'll come back to that house. For now, let's talk about the three places the seams show: security, speed, and craft.

Security: Every Plugin Is a Door

This is the one that keeps clinic and law-firm owners up at night, and rightly so.

Every plugin you install is a door into your site. Most of those doors are well-built and well-maintained. But you only need one with a faulty lock — and you have no way of knowing which one it is, because someone else holds the key.

The frustrating part is that this isn't really about being careless. You can keep everything updated, run a security plugin, do everything right — and still be exposed by a plugin whose author stopped maintaining it eighteen months ago. The risk isn't yours to control, because the code isn't yours.

A custom Next.js site flips this. There's no public admin panel sitting at a guessable URL waiting to be brute-forced. There's no sprawling plugin ecosystem. The surface a bad actor can even reach is dramatically smaller, because most of the site is rendered ahead of time and served as static files. For a clinic handling patient enquiries or a firm handling confidential matters, that smaller surface isn't a nice-to-have. It's the foundation of the trust your clients are extending to you.

What we trade away — honestly

We owe you the other side. With WordPress, you can log in tonight and add a plugin yourself. With a custom build, new functionality means us writing it. That's a real difference, and for some businesses the self-serve freedom genuinely matters more than the locked-down safety. We'd rather you know that going in than discover it later.

Speed: The Cost of the Seams

Back to the house. Remember all those bolt-ons? On the web, each one loads its own code — its own scripts, its own stylesheets, often its own copy of jQuery. The browser has to download, parse, and run all of it before your visitor sees a finished page.

This is why so many WordPress sites feel heavy in a way that's hard to put your finger on. It's not one big problem. It's twelve small ones stacked on top of each other: the form plugin, the slider, the analytics tag the previous agency added, the consent banner, the chat widget. Individually, each is fine. Together, they're a queue of luggage the browser has to carry up the stairs before anyone can move in.

Speed isn't a vanity metric, and it isn't only about Google rankings. It's about trust — the felt sense that this brand has its act together. We've written before about why those first couple of seconds decide whether a visitor stays, and the short version is that slowness reads, emotionally, as carelessness. Your dream client doesn't think "the third-party scripts are render-blocking." They just feel, faintly, that something is off — and they leave.

A custom Next.js site loads only the code that page actually needs, and much of it is rendered to static HTML in advance, sitting on a global CDN ready to appear the instant someone arrives. There's no database query firing off, no plugin chain to wake up. The page is simply there. That immediacy is something your nervous system reads as competence before your conscious mind has formed a single word about it.

Craft: The Part You Can't Quite Name

Here's the one that's hardest to put in a spreadsheet, and the one we care about most.

Page-builders are built to do anything for anyone. That's their genius and their ceiling. To be that flexible, they have to make assumptions — about how a section should stack, how an animation should ease, how much space sits between a heading and the paragraph beneath it. Those assumptions are fine. They are also, by definition, generic. They're the defaults that look acceptable for the largest possible number of businesses.

But the things that make a premium brand feel premium live precisely in the places the defaults don't reach.

The details that don't fit in a drag-and-drop

• The way a section of your story reveals itself as someone scrolls, paced to the rhythm of how the words actually read.
• An easing curve on a hover that feels weighted and intentional, not snappy and abrupt.
• Typography that breathes — line lengths, letter spacing, and vertical rhythm tuned to your specific words, not a theme's stock values.
• A custom cursor, a piece of generative motion, a transition between pages that feels like a single continuous experience rather than a series of reloads.

You can approximate some of this in a builder, with enough plugins and CSS hacks bolted on top. But you're now fighting the tool — overriding its defaults, adding weight to undo decisions someone else made for you. At some point it becomes far more honest, and far lighter, to simply write the thing from scratch with intention.

That's the work we actually love. When we built the concept site for Lumière, the gold hairlines, the centred serif hero, the unhurried pacing of the whole experience — none of that came out of a template's menu. It came out of decisions, made one at a time, about how that specific brand should feel. A builder can't make those decisions, because it has never met your clients.

When WordPress Actually Is the Right Answer

We promised honesty, so here it is plainly. There are real cases where we'd steer you away from a custom build:

• You publish new content several times a week and need to do it yourself, instantly, without a developer.
• Your budget is genuinely tight and a polished template will serve you well for now.
• You need a specific piece of off-the-shelf functionality — a complex shop, a membership portal — where a mature ecosystem saves you real money.

If that's you, a well-chosen WordPress setup is a perfectly good decision, and a good agency will tell you so. Choosing the right tool is part of the craft too. We'd simply rather lose a project than sell someone a Next.js build they don't need.

So when someone asks us, twenty minutes into a call, whether it'll be on WordPress — the real answer isn't a verdict on a piece of software. It's a question back: what are you actually building, and who is it for? Once we know that, the right tool tends to choose itself. For the brands we work with, it almost always turns out to be the one drawn as a single structure, every beam knowing about every other beam.

At Orpheus Studio, we write every site by hand in Next.js — no templates, no plugin towers, no seams for the wind to get through. If you're weighing the Next.js vs WordPress question for a brand that's meant to feel like more than the average, let's talk about what yours should actually be built on.