Most WordPress sites are built like this—a starter theme, a page builder, a dozen plugins to paper over the gaps, and somewhere, a designer crying.
We don’t build like that. Themes are written from scratch around the Gutenberg block editor, the way Automattic intended. Custom blocks for the parts that matter. Native blocks for the rest. No drag-and-drop bolted on top of a CMS that already has its own.
What you ship is a site editors can actually edit, developers can read in three years, and PageSpeed treats kindly. The Figma file translates the first time. There is no plugin in your install you cannot explain.
Fixed scope. Real timelines. Every engagement is a Figma file in and a working WordPress site out—the boring magic in between is the part we charge for.
A custom WordPress theme written from scratch around the Gutenberg block editor. Native blocks where they fit. Custom blocks where they don't.
Everything in PKG-01, plus a typed content model. ACF Pro field architecture, custom post types, taxonomies, and an editor UI your client will actually use.
WordPress as the editor, Astro or Next.js as the front-end. The CMS your team knows, the performance your users deserve.
Every project moves through the same five steps. Fixed sequence, clear deliverables, no “phase 2” surprises. The whole point of doing it the right way is that you can see exactly where the work is at any given moment.
We take your Figma file, your existing content if you have it, and a conversation. Out comes a written scope, a block plan, and a fixed timeline.
Every design element is sorted: native Gutenberg block, custom block, or theme-level pattern. You see this list. You approve it. Then we build.
Theme written from scratch. Custom blocks built as needed. ACF wired where you need typed fields. Sensible defaults, opinionated structure.
Pixel diff against Figma. Lighthouse audits. WCAG checks. Editor walkthrough with your team. We don't ship until the gaps close.
Deployed to your host of choice. Documentation handed over. Editor training session if you want one. Support window included.
Inherited a WordPress mess? Hit Lighthouse 23? Editor screams every time they hit publish? We diagnose first, fix second, and tell you the truth either way.
Tools we built for our own builds, opening up to the WordPress community. None of these are shipped yet—we’ll holler when they are.
A scaffolding kit for building custom Gutenberg blocks the right way—native APIs, no React gymnastics required.
Quality-of-life tooling for sites that lean on Advanced Custom Fields. Less repetition. Cleaner schemas.
Drop-in webhook + revalidation glue between WordPress and Astro or Next.js. The boring part, done.
Small fixes to the WP-Admin experience that make Gutenberg feel like the editor it was always supposed to be.
One reply within a business day. No sales process, no proposal pipeline. We’ll either tell you it’s a fit and quote it, or tell you who else would do it better.