Service 01 / 03 · WordPress
I help businesses and agencies build the WordPress sites and platforms they need to run their businesses, the way they actually want them to work. That covers bespoke themes, custom blocks, ACF, WooCommerce and headless setups when there's a real reason for one. The aim is always a site that loads quickly, is genuinely easy for your team to edit, and that you'll still be glad you chose two years from now.
onward
WordPress is the right call for most marketing sites and a lot of editorial platforms, and it's genuinely the tool I'd reach for first in those situations. It's also the wrong call when what you really need is a custom application, and I'll be straight with you when that's what I think is going on. Here are three of the signals I tend to look for when this service is going to be a good fit.
A starter theme has run out of road.
You've grown beyond what an off-the-shelf theme with a stack of plugins layered on top can really do for you, and what the site needs now is some proper custom thinking rather than yet another plugin.
Editors want flexibility without a developer in the loop.
Your in-house team need to be able to build pages, swap content around and launch campaigns themselves on a Tuesday afternoon, without having to call a developer first and without quietly breaking something on the way through.
WooCommerce is part of the picture.
There's a shop, a subscription product or a checkout flow that really needs to behave like a proper part of the rest of the site, rather than feeling like it was bolted on as an afterthought.
Discovery
Build
Aftercare
WooCommerce
WooCommerce powers more of the web than any other ecommerce platform, and the truth is that most of those stores are running on a templated theme with twenty plugins layered on top of each other. That tends to work fine, right up until it really doesn't.
For businesses and agencies that need a shop to genuinely behave itself (custom product flows, subscription logic, complex shipping rules, a checkout that actually converts) I build WooCommerce stores from the ground up. The store sits inside the same custom theme as the rest of the site, with the same level of care running through it and the same maintenance plan behind it.
I don't really do pricing tiers. Every project gets scoped properly before we start any work, and what you see below is just the kind of timeline range these projects usually fall into. Once we've talked through what you actually need, you'll get a written proposal back from me that you can act on.
Brochure / marketing site
Typically 6 to 12 weeks, start to finish.
Custom theme, content modelling and the lighter end of integrations work. This is the right shape for most company websites.
WooCommerce
Typically 3 to 6 months.
A higher level of complexity, where we're talking about custom blocks, a larger content model, and often a bespoke checkout or subscription flow that needs proper thinking through.
Ongoing support
Retainers from two days a month.
Maintenance, small features and advisory time, all on fixed monthly hours that roll forward when you don't use them.
Coeliac UKCharity2025
I was brought in by the digital agency leading the rebuild to take ownership of the WordPress page-building and the content migration from start to finish, and to act as the bridge between the charity's teams and the agency all the way through to launch day.
GT LiftingSSE network2025
A new website built from a design agency's files that gives GT Lifting a properly professional presence online, and gives their in-house team the ability to manage the machine-hire catalogue themselves without having to come back to a developer every time something needs changing.
Page-builder themes are great at getting a site live in a hurry, and then they tend to quietly make every future change harder than it should be. Going custom with WordPress means cleaner code, faster pages, and an editing experience that's actually designed around how your team works day to day. It does cost a bit more up front, but in my experience it saves you a considerable amount over the next three to five years.
Both, depending on what suits the project. ACF (Advanced Custom Fields) is still the right call for most editorial sites where the templates are reasonably predictable, and the native block editor is the right call when your editors need a lot more creative freedom over the layouts. I'll always recommend the approach that fits your team during discovery, not whichever one I happened to build last week.
Most of the time, yes. Take-over jobs usually start with a short audit so I can get a clear picture of what's in good shape, what really needs replacing, and where any security risks are sitting, and then we put together a remediation plan together from there. Whether that ends up being a full rebuild or a more steady refactor really depends on what we find when we look under the bonnet.
Hosting recommendations always come as part of the build. For most marketing sites that means managed WordPress (Kinsta, WP Engine or Pressable, depending on the project) and for higher-traffic platforms it usually means moving onto dedicated infrastructure. A proper performance and security pass at launch is standard with every build, and the ongoing patches and monitoring are looked after as part of the maintenance plan.
Yes, when the front-end actually justifies it. Headless is genuinely the right call for sites that need a JavaScript-heavy front-end, for teams who are publishing across multiple channels, or for projects that have to hit really strict performance budgets. For most company sites though, it's honestly overkill, and a well-built traditional WordPress theme is the better answer. I'll tell you straight which one fits where you are.
Next step