Start a project→WordPress thatan engineer built.
Custom themes, custom plugins, custom post architecture. No page-builder sprawl, no forty plugins holding the layout together — a build your editors can run and your next developer can read.
What the work covers
Six things, done properlyCustom theme, no builder
A theme written for your content model, with a Gutenberg block library your editors can compose pages from without breaking the design.
Custom plugin engineering
Business logic lives in a versioned plugin, not in the theme — so a redesign later doesn't take your functionality with it.
Content architecture
Post types, taxonomies, and field groups modelled around how your team actually publishes, not around a demo import.
Speed as a requirement
Query audits, object caching, an image pipeline, and an asset budget agreed before a line of CSS is written.
Migrations and rescues
Moving off a builder, off a broken theme, or off a host that keeps falling over — with redirects mapped and rankings held.
Handover that sticks
Repo, staging, deploy pipeline, editor docs, and a walkthrough recording. You own everything the day we finish.
PHP 8.3 · WordPress · ACF Pro · Gutenberg · WP-CLI · Composer · GitHub Actions
How it runs
Four stages · no black boxAudit and model
We go through the existing site, the content, and the edit workflows, then write the content model and the block inventory.
Design the system
Block-level design, not page mockups — every state, every breakpoint, signed off before build.
Build in the open
Weekly staging deploys. You click a real site each Friday rather than reading a status report.
Migrate and hold
Redirect map, rank monitoring, and two weeks of active watching after go-live.
“They rebuilt a site four agencies had layered plugins onto. First time in years our editors could publish without filing a ticket.”
What it costs
Full pricing →Marketing site
from $9,000Platform build
from $28,000Rescue sprint
from $3,500Questions we get asked
Answered plainlyEither. Roughly half our WordPress work is picking up someone else's build. We start with an audit and tell you honestly whether fixing is cheaper than rebuilding — sometimes it is, and we say so.
Not for new builds. We build native Gutenberg blocks, which are faster and don't lock you into a licence. If you already run a builder and want to keep it, we'll work inside it and say what it costs you in speed.
You do, from day one, in your own repository. No proprietary framework, no licence that expires if you leave us.
That's the point of the block library. Editors compose pages from approved blocks, so new pages look like the design system rather than a workaround.
Two weeks of active monitoring is included. After that, most clients move to a monthly care plan — updates, backups, security, and a set number of development hours.