What we do
You design it, we build it in Craft, and it launches under your name. This page covers how that runs: the three steps, the block kit your client ends up with, the standards every build ships with, and the things we won't do.
Three steps
no surprises
You send the Figma
Auto layout, variables, or a flat file with good intentions: within a day we tell you what's ambiguous, before anyone commits to a date.
We build it in Craft
Componentised to match your design system. You get a staging link on day one and it stays current, so there's no big reveal at the end.
We host it, or hand it over
Launch under your name, then leave it on our hosting with updates and backups handled, or take the repo and walk, with no lock-in and no exit fee either way.
You get a kit,
not a page
Every section in your Figma becomes a block in a Craft Matrix field. The result is a page builder made from your design system: your spacing, your type ramp, your components, and nothing else.
So the build covers more than the pages you drew. When the client needs a campaign page in eight months, they stack the blocks you already designed. Nobody calls us, nobody opens Figma, and the page can't go off-brand because there's nothing off-brand in the picker.
- Hero4 variants
- Split featureimage left / right
- Card grid2 / 3 / 4-up
- Pull quotewith attribution
- Logo bandauto-scrolling
- Rich textstyled to the brand
- CTA band2 variants
- + Whatever else the file contains
Built properly,
not just quickly
Nobody asks for these and everybody notices when they're missing. We don't list "responsive" as a feature, because it's 2026.
Accessible by default
WCAG 2.2 AA on every build, done as we go rather than at the end when it costs more. Proper focus states, sensible heading order, keyboard paths that work, and contrast checked against your palette.
Lighthouse 90+
All four categories, on the templates people land on, with Core Web Vitals in the green. A bad score gets treated as a bug and fixed before launch.
No more plugins than you need
Every plugin is a licence, an upgrade path and a security surface. We use the handful that are better than what we'd write, and write the rest, so your client isn't renewing twelve subscriptions.
Hosted with us, or not
From £75 a month, with Craft and plugin updates inside your major version included in the fee, so the site stays patched without anyone approving each one. Or hand the repo to whoever you like. Both are fine.
Things we
won't do
It's more useful to know what a partner won't do than what they can. Here are ours. None of them are negotiable.
We won't contact your client
Not for a testimonial, not for a case study, not to "check in" after launch. It's in the contract.
We won't design anything
No brand, no UI, no suggestions about your type choices. You design it, we build that.
We won't sell your client SEO
Or ads, or strategy, or a retainer. A build partner with its own plans for your client isn't a partner.
We won't build in anything but Craft
No WordPress, no Webflow, no Shopify. It costs us work and it's why our estimates hold.