Service · Direct

WordPress development, built properly

WordPress is a good choice for most content sites and a bad choice when it is installed with forty plugins and a purchased theme. We build the first kind.

Start a projectBook a call

New build, or an existing site that has become difficult to change.

01Scope

What we build in WordPress

Custom themes from your design

The theme is written for your site. Templates match the design at every breakpoint, the markup is semantic, and the front end is not carrying half a megabyte of CSS for components your site does not use. If you do not have a design yet, that is a service too.

Block editor and ACF

Editors get a set of blocks that produce your layouts and nothing else. Fields are labelled in the language your team uses, not in developer shorthand, and the ones that would break the design are not exposed. Advanced Custom Fields where structured content needs a proper model.

Plugin development

When no existing plugin does the job, or when the one that does brings four features you do not want and a settings page nobody understands. Custom plugins for post types, integrations, admin tooling and scheduled jobs — kept in your repository like the rest of the code.

Multisite

Multiple sites — regions, brands, franchises — sharing one codebase and one update path, with the parts that differ genuinely separated. Worth doing when it is right, and expensive when it is not; we will tell you which case you are in.

Moving on to or off WordPress

Migrations from another CMS, from a static site, or from a WordPress install that has become unmaintainable. Content, URLs and redirects treated as assets to be preserved. See CMS migration.

02Boundaries

What we do not do

Said plainly, because it is the difference between two very different quotes:

  • We do not build sites on page-builder plugins. They are quick to start and slow forever afterwards, and they make the site hard to move.
  • We do not sell a purchased theme with your colours applied.
  • We do not install a plugin for something that is fifteen lines of code, then leave you to update it for five years.

If a project genuinely suits an off-the-shelf theme, we will say so. Paying us to rebuild something you could have bought is not a good outcome for either of us.

03Editing

Editing it afterwards

The measure of a WordPress build is not how it looks on launch day. It is whether the person who updates it in eighteen months can do so without ringing anyone.

That means blocks that map to the layouts you actually publish, previews that match the front end, media handled automatically, and a short written guide for the people doing the editing — written for them, not for a developer.

04Engagement

How a WordPress project runs

  1. 01

    Scope. What the site does, what page types it needs, and how content is structured. The content model is agreed here, in writing, because changing it later is the expensive kind of change.

  2. 02

    Build. Theme, blocks and fields, on a staging URL you can see from early on. One named contact and a fixed check-in rhythm.

  3. 03

    Content. Either you load it, or we migrate it. Either way it happens before testing, not after, so the design is tested against real content.

  4. 04

    Launch. Redirects, analytics, search console, backups and monitoring in place on the day.

  5. 05

    Handover. Repository, deployment instructions, editor guide, and a walkthrough call.

05Upkeep

Keeping it secure and up to date

WordPress needs maintaining. Core, plugins and PHP versions move, and an unattended install is the most common way a site gets defaced.

You can run that yourself — the handover tells you how — or put it on a support agreement where updates, backups, monitoring and fixes are handled to a published SLA. It is optional and it stays optional.

06Proof

Selected work

Placeholder — invented projects, pending real client work

Fold & Co.

A block theme built from the studio’s own design, so the editors compose pages out of named blocks instead of a page builder nobody trusts.

Custom block theme · 2024

Trellis Group

Six regional sites sharing one theme and one set of components, each with its own editors and its own permissions.

Multisite + ACF · 2025

Kestrel Legal

A supplied design built to the letter, with the profile and case-type content modelled properly rather than typed into the editor as prose.

Custom theme from design · 2025
07FAQ

Questions we get asked

Is WordPress still the right choice?

For a content site that a non-technical team edits, usually yes. For an application with accounts and permissions, usually no — see web development. We answer this before the quote, not after.

Can you work on our existing WordPress site?

Yes. It starts with a written assessment: what is there, what is safe to change, and what is holding the rest of it hostage. That is a smaller commitment than a rebuild and it frequently avoids one.

Will it be fast?

A page speed target is agreed at scope and the build is held to it. Most WordPress sites are slow because of what was installed on them, not because of WordPress.

Do we have to use your hosting?

No. It runs on standard PHP and MySQL hosting. If you want it managed, hosting is available separately.

What about the plugins we already pay for?

We audit them at scope. Some get kept, some get replaced by a few lines in the theme, and some are the reason the site is slow. You get the list with a recommendation against each one.

Who owns the code?

You do. Full repository, no licence conditions of ours attached.

08Next step

Start a project

Tell us whether it is a new site or an existing one, and when it needs to be live.

Or email us at hello@felixwebsolutions.com.

Agency looking for a build partner? White-label WordPress development →