Service 05

A build your team can look after.

The platform gets chosen after we understand how your team publishes and what the site has to connect to. Sometimes that is a headless CMS with a custom front end, sometimes WordPress, occasionally Webflow. What matters more than the choice is that adding a page six months later does not break the layout.

How long
Usually 8 to 16 weeks
Who runs it
Dave Curtin directs, with long-standing development partners
What you get

What the engagement includes.

  1. 01Technical architecture
  2. 02React, Next.js or CMS implementation
  3. 03Accessible component systems
  4. 04Content modelling and migration
  5. 05Performance engineering
  6. 06Deployment and handover
Common questions

The things people ask before they call.

Which platform will you use?

That depends on how your team publishes and what the site has to connect to. Often a headless CMS with a custom front end, sometimes WordPress, occasionally Webflow. The decision comes after the requirements, not before.

Can our team edit the site ourselves?

Yes. The editing experience is designed as carefully as the public site, so adding a page later cannot break the layout. Your team is trained before handover.

What does it cost and how long?

Builds usually take 8 to 16 weeks, depending on how many templates and integrations are involved. Cost follows from that scope.

Do you work with our existing developers?

Often, yes. Where there is an in-house team, they receive a documented component system and I stay available while they take it on.

Not sure this is the right service?

Describe the situation and I will tell you whether this is the right piece of work, whether something smaller would do, or whether it is too early.

Start a projectSee everything we do