CMS Development

Sites your marketing team can publish to without asking engineering. WordPress when it fits, a headless CMS with a modern frontend when it does not. For content-heavy sites and teams that publish every week.

Who this is for

  • A marketing team that waits days for a developer to change a page.
  • A site on an ageing theme that is slow, insecure, or impossible to edit safely.
  • A content operation that needs structured content reused across web, app, and email.
  • A migration from one CMS to another without losing URLs or rankings.

What is included. Tick what you need.

Artefacts, not adjectives. Each is something you can point to at the end. Tick the ones your project needs and send the list with your enquiry; we reply with a written scope.

Technologies we use for this

The relevant slice of our technology matrix. Nothing here that we cannot staff today.

  • React
  • Next.js
  • TypeScript
  • Vue
  • Nuxt
  • Tailwind CSS
  • Redux Toolkit
  • TanStack Query
  • Vite
  • Three.js and React Three Fiber

How we deliver it

The five steps every engagement goes through, in the form they take for this service.

  1. Scope

    A call with an engineer, then a written scope: what is in, what is out, and what it costs.

  2. Architecture

    Data model, API contract, and infrastructure plan, approved before code is written.

  3. Build

    Templates and components built against real content, reviewed with your editors every week.

  4. Harden

    Tests on the paths that matter, error tracking, a performance pass, and a security review.

  5. Launch and hand over

    Production deployment, monitoring, documentation, and every repository transferred to you.

Questions we get asked

Can non-technical staff edit the site?

That is the point of the build. Editors get structured fields with clear names, preview before publishing, and roles that stop accidental changes to layout.

Can you migrate our existing content?

Yes. We export, clean, and import it, keep every URL or redirect it, and verify rankings do not drop after the switch.

Headless or traditional WordPress?

Traditional WordPress is right when the site is the product and the team knows it. Headless is right when content must feed several channels or performance and security are the priority. We recommend one in the scope.

Will the site be fast?

We set a performance budget in the scope and test against it on a mid-range phone over a slow connection, not a laptop on office wifi.

Do you provide hosting and maintenance?

We deploy to hosting in your name and can run a maintenance retainer for updates, backups, and security patches, or hand the documented setup to your team.

Tell us what you are building.

We reply within one business day with how we would build it, what it would cost, and which engagement model fits.

  1. 01
    Tell us what you are building

    A short form or an email. No deck required, and "not sure yet" is a fine answer.

  2. 02
    A call with an engineer

    Within one business day. Technical questions get technical answers, from the person who would build it.

  3. 03
    A written scope and quote

    Fixed price where the scope is defined. The document is yours whether or not you go ahead.