Get the website you wanted from day one
Whether you are building your first website or replacing one that has stopped serving you, you should end up with the same thing: a fast, accessible site you own outright and can change yourself, built on the same stack modern engineering teams use.
We build it, prove it against the standard, and hand you the keys.
What you end up with
Not a template with your logo on it. A real codebase, built for your content, that your team can run.
- A site that meets EN 301 549, the EU’s harmonised accessibility standard, and the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. We audit it in the platform before handover, so your accessibility statement is published with evidence behind it from the day you launch.
- Genuinely fast. Pages served from the edge, images optimised, no plugin stack loading four versions of the same library. Performance and accessibility pull in the same direction.
- Yours to change. Edit content without a developer, and change the code itself with Claude Code when you want something new.
- Built to stay current. Accessibility checks run automatically on every change, so the site cannot quietly drift out of conformance after we have gone.
How we build it
Delivered within 2 weeks.*See note on delivery times
Scope
One call to understand what the site does for your business, what has to carry over, and what you have always wanted it to do and never could. You get a fixed written quote after this, with no obligation.
Structure
We agree the pages, the content model and the URL structure before anything is designed. If you are moving from an existing site, this is where we map every URL you already rank for so nothing is lost.
Design
A working session on the design and on the journeys people actually take through the site. This is not a redesign unless you want one, and if you do, this is where we do it. We iterate with you until you are happy, and nothing gets built until you have signed it off.
Build
Your content, your brand. You get a live preview link from day one and watch it come together rather than waiting for a reveal.
Audit
The finished site goes through a full audit in the platform against EN 301 549 before it goes anywhere near production. Anything it finds, we fix before launch. Your accessibility statement is generated from the results.
Deploy
We put it live on your own hosting account, with your domain, SSL, and automatic preview deployments so every future change can be seen before it ships. If something goes wrong you roll back to the previous version in one click. No maintenance windows and no FTP.
Handover and training
Covered below. This is the part most agencies skip.
Note on delivery times: Most sites go live within two weeks of sign-off on scope. Larger sites, or ones with a lot of content to bring across, can take longer. We will tell you which yours is on the scoping call, before you have committed to anything.
The stack, and why it matters to you
We build on TypeScript, React and Next.js, deployed to a modern host. That is the same foundation used by teams with far larger budgets than yours, and it is deliberately boring in the places where boring is what you want.
What that buys you, in practice:
- Nothing to patch on a Friday night. There are no plugins, no admin login to brute-force, and no database sitting behind a form waiting to be injected. Most of what makes a WordPress site a security problem simply is not present.
- It does not rot. Dependencies are updated and tested automatically. A site left alone for a year still builds, still deploys and still passes its accessibility checks.
- You are not locked in. It is standard, widely used technology. Any competent developer or agency can pick it up. We are not the only people who can maintain what we built you, and we think that is how it should be.
Run it the way modern teams do
Every site we hand over comes set up for Claude Code, so changing your own website is a conversation rather than a ticket.
Ask for a new page, a change of wording, a seasonal banner, a new section on the pricing page, and it gets built, checked and previewed before it goes live. Your marketing team stops waiting on a developer for work that was never developer work in the first place.
It works because of what we hand over with it:
- Written conventions. The codebase carries its own instructions, so the assistant already knows how your site is structured and what your components are called.
- Accessibility checks in the pipeline. Automated checks run on every proposed change. Anything that would break contrast, heading order, focus handling or labelling gets caught before it can reach your live site.
- Guardrails, not a free-for-all. Changes go to a preview first. Nothing reaches production without a human approving it, and every change is reversible.
- Training that gets used. We sit with your team and show them, on your site, with your own content.
Moving from WordPress, Squarespace or Wix
Migrations are the part people dread, so we do the dreaded parts.
- Your content comes with you. Pages, posts, images and metadata, moved and checked rather than retyped.
- Your search rankings come with you. Every existing URL is mapped and redirected. This is the single most common way a site migration goes wrong, and it is the first thing we plan.
- Your team keeps editing. Content stays editable without touching code.
- You keep the old site running until the new one is signed off. The switch happens when you say so.
If you are starting from nothing instead, none of this applies and the build is faster.
Then we hand it over
The code is yours and the hosting account is in your name. Host it yourself or let us host it, and move between the two whenever you want. There is no retainer and no licence to renew: if you stop paying us, you take the site with you and it keeps running. Your team audits it in the platform the same way they would any other site.
Aftercare and training
Handover is a date in the calendar, not an email with a zip file attached.
- A training session with your team, recorded, using your site and your content. How to edit, how to publish, how to use Claude Code against your own codebase, and what the accessibility checks are telling you.
- 30 days of support after launch included. Anything broken, anything confusing, anything you want changed while you find your feet.
- Written documentation that lives in the codebase, so it is still there in a year when the person you trained has moved on.
- Your accessibility statement stays current in the platform, because your team keeps auditing there as the site changes.
- After that, only if you want it. Ongoing support is available and optional. Nothing stops working if you decline it.
How we price it
Every site is a different size, so we do not publish a number. Book a call and we will scope it with you: how many pages, what your content looks like, what has to carry over. A fixed written quote follows, with no obligation and no sales sequence afterwards. If a rebuild is not the right answer for you, we will say so on the call.
Book a scoping call