Let's get the bias out of the way first: we don't build WordPress sites.
Not as a pose, and not because we think everyone using it is wrong. It runs an enormous share of the web and plenty of those sites are doing their job perfectly well. If you've got one that works, we're not going to tell you to bin it.
But we've inherited a lot of WordPress builds over the years, and that's a genuinely useful education in where it stops being the right tool. Here's the honest version.
The bit nobody demos: the admin
Agencies sell you the front end. You live in the back end.
Log into a typical WordPress site and you get a sidebar of twenty items, most of which belong to plugins rather than your business. Editing a page means working out whether this one uses the block editor, a page builder, a custom field group, or some combination that made sense to whoever built it. Marketing wants to change a headline and ends up asking a developer, because nobody's confident which of the four boxes on screen is the real one.
That isn't a training problem. It's what happens when a general-purpose tool gets bent into a specific shape.
We build the admin around your business instead. We use Laravel with Filament or Twill, which means the editing screens contain your content, in your language, and nothing else. No plugin menus. No "ignore that section". If your business has venues, the menu says Venues.
The difference in practice is that people actually use it. Content gets updated because updating it is easy, rather than becoming a quarterly job somebody dreads.
The best test of a CMS is whether your team updates the site without asking anyone's permission. Most WordPress admins quietly fail it.
We train you afterwards, though you won't need much
Every build ends with us walking your team through the admin properly.
Honestly, it's usually short. When the editing screens only contain the things you actually manage, there isn't a great deal to explain, and that's rather the point. We'd rather spend an hour showing you something obvious than hand over a system that needs a manual.
And we're still here afterwards. 88% of our clients carry on working with us long after launch, so there's a real person to ask when something new comes up.
Speed
A WordPress page typically loads a theme, a page builder, and the stylesheets and scripts of every plugin that thinks it might be needed. You can cache it. You cannot make it lean, because the weight is structural.
We build only what the page needs. That shows up in load times, and load times show up in conversions and rankings. It's the least glamorous advantage on this list and probably the most valuable.
Security
More third-party code means more ways in. A site running fifteen plugins is trusting fifteen strangers to write secure code and patch it promptly, and to keep doing so for as long as your site is live.
WordPress's popularity makes it a target too. That's not a criticism of the software, it's arithmetic: attackers automate against the platform with the most installs.
A custom build has a much smaller surface. There's our code, the framework, and very little else.
What happens when you want to add something
This is the one that catches businesses out, and it's worth thinking about before you choose rather than after.
Say in eighteen months you want to take bookings. On a custom Laravel build, that's a feature: we design it, build it into the system you already have, and it works the way the rest of the site works.
On WordPress, it's a hunt for a plugin. You find one that does roughly 80% of what you need. It has its own admin section that looks nothing like the rest, its own data that doesn't talk to anything else, and a monthly fee. The remaining 20% becomes a workaround your staff perform by hand, forever. Then a plugin update changes something and you find out on a Tuesday morning.
That 80% fit is the single most expensive thing in the WordPress ecosystem, and it never appears on an invoice.
Custom builds expand. TableCloud grew from a booking platform into floor plans, multi-restaurant management and live service tools, all inside one coherent system. There was never a moment where we had to go looking for a plugin and hope.
So who should still use WordPress?
Being straight with you: if your site is almost entirely content, you publish constantly, your budget is genuinely tight, and you can't see yourself needing the site to do much beyond forms, WordPress will serve you fine and cost less to start.
We're not the studio for that job, and we'll say so on the first call rather than talk you into something bigger. There are people who do it well.
The quick test
- Is the site mostly content, or mostly doing things?
- Will non-technical people need to update it regularly?
- Are we already describing our own processes as workarounds?
- Might this need to do something new in two years that it doesn't do today?
- Is this a five-year system or a two-year brochure?
If you answered "doing things", "yes", "yes", "probably" and "five years", you're paying for custom either way. The only question is whether you pay it up front or in staff time forever.
Tell us what you're wrestling with and we'll give you a straight answer, including "you don't need us for this" if that's the truth.
