01
WordPress websites
A site your team can actually run. We build in Elementor or Gutenberg depending on who will edit it and how often, keep the structure legible, and hand over something you can change without calling us.
What you actually receive
- A working site on your hosting, with the theme and any custom code in your repository.
- Editing set up for the people who will actually use it, with the patterns and templates they need.
- Accessibility checked against WCAG 2.2 AA before launch, with the findings written down.
- Core Web Vitals measured on real pages, not a synthetic homepage score.
- A written handover: how it is put together, what to touch, what not to.
Elementor or Gutenberg? It depends who edits it.
This is the first real decision on a WordPress build, and the honest answer is that neither wins on principle. It turns on who touches the site after launch.
- Elementor suits you when
- A marketing team needs to build new pages without a developer, layouts vary a lot page to page, and you accept a heavier front end in exchange.
- Gutenberg suits you when
- Content is structured and repetitive, you want the lightest possible output, and you would rather have a small set of tidy blocks than unlimited freedom.
- Either way
- We build reusable patterns instead of one-off pages, so the twentieth page costs a fraction of the first.
- What we will not do
- Install both and let them fight. Pick one, and let the site be coherent.
What this is not
- We do not build on a page builder you have not agreed to.
- We do not add a plugin for something twelve lines of code would do.
- We do not keep your site hostage. Everything is yours, including the source.
- Typical duration
- 3 to 8 weeks
- Engagement
- Fixed scope, staged payments
- Starts with
- A paid discovery week on larger builds
Four stages, start to handover
- 01
A brief, then a conversation
You send four short answers. We read them and reply within one working day, either with questions or with a straight answer about whether we are the right studio for it.
- 02
Scope written down
What is being built, what is not, what it costs and when. If we cannot describe it clearly enough to price it, that is a sign the scope is not ready — and we will say so.
- 03
Build, in the open
Work lands in your repository from the first week. You see progress as commits and working previews, not as a status meeting.
- 04
Handover that survives us
Documentation for the next developer, the accounts in your name, and a walkthrough with whoever has to run it. Then a support window while you settle in.
Ready when you are.
Four short questions, about two minutes. A reply within one working day.