Custom website development

We build each site around the job it has to do, then we host it and look after it. The same people do all three.

Start a project

What is included

How we go about it

  1. Start with the job

    We ask what the site has to do for the business and who has to keep it up to date. That decides the platform. We do not start from a favorite tool.

  2. Build it lean

    Small pages, sized images, clean markup and accessibility from the first commit. Speed and search are built in, not added at the end.

  3. Launch, then stay

    We move the domain, set up hosting and backups, and keep the site patched. You are not handed a login and wished luck.

Where we have done it

A good fit when

Work that used it

Websites questions we get

Both. WordPress suits teams that publish often and want a familiar editor. A static site suits pages that change less and need to be very fast and hard to attack. We recommend one after we understand how you work.

Yes. We map every existing address to its new one, keep what is ranking, and set up redirects before launch so links and search results keep working.

Yes. We set up the editor around the things you change most, and show you how to use it. For anything bigger, you reach the people who built it.

A static site is built ahead of time into plain pages and served from a global network. Our favorite home for one is Cloudflare Workers. There is no database to attack and very little to slow it down, and the code lives in GitHub and deploys automatically. When your team needs to edit pages, a small content editor such as PagesCMS handles it without the weight of a full WordPress install. It suits sites that change by the week, not the hour. This site is built that way.

Yes. Most clients have us host and maintain what we build, so there is one team responsible for the code, the server and the security.

Often paired with

Need help with websites?

Tell us what you have and what you need. A sentence or two is enough to start.

Start a project