Oxygen Builder developer, UK and worldwide

Oxygen is a visual site builder for WordPress that lets you build every part of a site, headers, templates and page layouts, without a theme deciding what the markup looks like. In careful hands it gives you tidy HTML, small CSS and JavaScript files, and a structure another developer can follow. In careless hands it gives you the same mess as any other builder, just harder to spot.

I have spent over fifteen years working with WordPress, and I use Oxygen where it suits the job. I work alone, so the person you brief is the person building. Everything is done remotely, so it makes no difference whether you are in London, Leeds, Dublin or Denver. This page is written for two audiences: business owners who have been told their site needs an Oxygen developer, and agencies or in-house teams who need a specialist to build, rescue or take on overflow work. Day rates are by arrangement; send the brief and you will get a scoped answer, with a fixed price where the work can be defined up front.

Oxygen suits sites where layout control, speed and long-term maintainability matter: brochure sites with a lot of custom design, service businesses with repeatable templates, and builds that will be edited by several people over the years.

I would not use it every time, and I will say so at scoping. Cases where I would suggest something else include:

• A small site that the owner wants to edit with the standard WordPress block editor and nothing else
• A project whose existing team already works happily in another tool, where switching would only add cost
• Work that is mostly custom functionality with minimal front-end design, where
  plain WordPress development
  is simpler

If the honest answer is that Oxygen adds nothing for your project, you will hear that before any money is spent, and I will point you towards the simpler option that does the job.

A lot of Oxygen work arrives half-finished or inherited from someone who has moved on. Before I quote for changes, I audit what is there so you know the real state of the site rather than a guess.

That audit looks at how the templates and reusable parts are organised, whether styles are consistent or scattered, how many plugins are doing work Oxygen or a few lines of code could do, and what is slowing pages down. You get a plain summary: what is sound, what is fragile and what I would fix first, with the order of priorities and the cost of each.

Some sites only need tidying and a handover. Others need a proper rebuild of certain sections, and I would tell you which parts are worth keeping. Nothing gets changed until you have agreed the plan. Once the site is stable, a rolling website maintenance plan can keep it that way.

If you run an agency or a design studio, I can act as the build specialist behind your name. That means white-label work: you keep the client, the relationship and the invoice, and I deal with you rather than your customer unless you ask otherwise.

Typical arrangements include:

• Building a site from your finished design files
• Taking over a build that has stalled, or that your team does not have time to finish
• Adding custom functionality or integrations to an Oxygen site you already run
• Overflow capacity when you are busy

You keep ownership of client domains, hosting accounts and licences, with no lock-in. I work remotely with clients across the UK and worldwide, by email, WhatsApp, phone or video call — my 09:00–21:00 UK hours overlap with most of Europe and the US East Coast — and I can document the build so that your own team can carry on with it afterwards. If you would like to see the kind of sites I build first, the work page has examples.

I build for speed from the first template rather than trying to bolt it on at the end. That means keeping stylesheets and scripts lean, loading only what each page needs, sizing images properly and being wary of plugins that add weight for small gains. My finished sites average under 0.8 seconds to load.

Handover matters just as much. A site your team cannot safely edit is a liability, so I set up reusable components and clear templates, write documentation for how the build is organised, and finish with a walkthrough call. If your staff need a second session once they have used it for a while, ask. The aim is a site that does not depend on me to change a heading or add a page.

For work that involves changes beyond Oxygen itself, such as custom fields or connections to other systems, the wider approach is described on my WordPress development page.