We audit before we quote
No fixed price gets sent before we have looked at what you actually have. Quoting blind is how projects end up either overpriced to cover the unknown, or underpriced and then renegotiated halfway through.
About us
Most agencies are incentivised to say yes — to the rebuild, to the retainer, to the platform migration you did not need. We would rather be the team you keep for a decade than the one that wins one big project and loses the relationship.
Why we exist
Nearly every site that lands on our desk arrives with the same history. It was built quickly on a page builder, extended with a dozen plugins that nearly did the job, and handed over without documentation. It worked — right up until the person who built it left.
So we build the opposite way. Core WordPress APIs instead of proprietary builders. Content models designed around the business rather than forced into a theme. Documentation and a handover, so the next developer is not starting an archaeology project.
It is a slower sell. It is a much better decade.
How we work
No fixed price gets sent before we have looked at what you actually have. Quoting blind is how projects end up either overpriced to cover the unknown, or underpriced and then renegotiated halfway through.
Hooks, filters, Gutenberg, the REST API. No proprietary framework, no page-builder lock-in, no licence tied to us. If you leave, everything still works and anyone competent can maintain it.
Some enquiries end with us explaining that a plugin already does it, or that the fix is a setting. We lose that job and keep the relationship, which has always been the better trade.
Every project ships with documentation and a walkthrough for whoever maintains it next — including if that is not us. Knowledge living only in one developer's head is a risk you are carrying, not a feature.
A baseline gets recorded before work starts, so improvement is a fact rather than a feeling. The numbers live in your analytics and your Search Console, where you can check them yourself.
A named person who knows your site, not a ticket queue and a first-response SLA. Most of what clients need is a quick honest answer, and that should not require raising a formal request.
The team
Founder & Lead Engineer
Sets the technical direction and reviews the architecture on every build. Add credentials
WordPress Engineer
Themes, block systems and the integrations that connect WordPress to everything else. Add credentials
WooCommerce Specialist
Checkout, subscriptions, B2B pricing and the performance work large catalogues demand. Add credentials
Product Designer
Design systems and block libraries built around real content and real editors. Add credentials
QA & Performance
Testing, Core Web Vitals and the edge cases nobody thought to check before launch. Add credentials
Support Lead
The named person on maintenance plans — updates, monitoring and the quick answers. Add credentials
Beyond client work
We maintain plugins on the WordPress.org repository, used across more than a million sites. Public code gets reviewed by strangers, which is a useful discipline — a lot of our standards come from having to defend them to people who owe us nothing.
See our pluginsQuestions
If there's something else you want to know before getting in touch, just ask.
Small enough that you deal with the people doing the work, large enough to cover design, development, commerce, QA and support without subcontracting the parts we are weaker at. You are told who is on your project before it starts, and that does not quietly change halfway through.
No. Everything is built by the team you meet. If a project genuinely needs a skill we do not have — a specialist integration, a niche compliance requirement — we say so and help you find the right person rather than quietly subcontracting and marking it up.
Mostly established businesses whose site has become important enough that downtime or slowness has a number attached. That ranges from a growing store to a multi-brand platform. What matters more than size is whether the site is treated as infrastructure rather than a brochure.
Because it is genuinely the right answer for most content and commerce sites, and because depth beats breadth. We would rather be excellent at one platform than adequate at four. If your project would clearly be better on something else, we will tell you that instead of taking the work.
Written updates against a dated milestone plan, in whichever channel suits you — email, Slack, your project tool. We default to asynchronous and in writing so decisions are recorded and nobody has to attend a meeting to find out what happened last week.
You take everything and it keeps working. Code in your repository, documentation, no licence keys, nothing hosted in our name unless you asked for it. Clients stay because the work is good, and the moment leaving becomes painful is the moment an agency stops having to be good.