We keep every project open and steady, so you always know who’s doing the work and what comes next.
A website for a public place takes months to make and years to look after, and how a project feels along the way matters almost as much as what it produces. So every one of ours starts the same way. You meet the senior people who will do the work, and they stay with you through launch and into the years after. We talk every week. Everything in progress sits in a shared review space, where you can leave a comment on any page by clicking the spot you mean.
The developers who build with us have worked alongside us for years, and they are the ones who answer when something needs attention after launch.
We begin by listening.
The first weeks belong to your goals and to the people your site serves. We run a workshop with your team and read your analytics and search queries. Then we sit beside the staff who update the site and watch how a page gets made. Discovery closes with a site map and a content model that names every kind of page and what belongs on it. You also get a plan for moving your content across and a schedule we’ve agreed on together.
We design the system before we design a single page.
Type, colour, spacing and the components come first, and we check each one for contrast and legibility on a phone before it goes anywhere near a page. Every template starts at phone width and grows from there. Before anyone writes code, you review the templates in the browser, and we put a clickable prototype in front of the people who will use the site to find out whether its main tasks are as easy as they look.
We build the site and bring your content with it.
The theme is built from the design system’s tokens, so what you approved in the designs is what gets coded. When a site has years of content behind it, we write scripts that move each item into the new structure and check it against the original, and anything the checks can’t settle goes to a person on our team. Every old address redirects to its new one. At launch a final run of the scripts picks up anything your staff published during the build, and you get a report of what moved and what changed.
We test the site the way your visitors will use it.
Automated accessibility checks run against every template at WCAG 2.2 Level AA. Then one of us works through each template with only a keyboard, and again with VoiceOver on a Mac and an iPhone. We time each page on a mid-range phone over a mobile connection and review the code and the hosting setup for security. Before we call the site ready, your staff run through the tasks they’ll do every week and tell us what gets in their way. Our accessibility page lists the tests we ran on this site and the date we ran them.
Your editors learn the site while it’s still safe to break things.
We train your editors on a copy of the site where they can try anything. Each of them gets a written guide and short videos for the tasks they do most, and the pages they make during training go live with the site.
After launch, we stay.
Every update goes onto a staging copy before it reaches the live site. Monitoring watches uptime and security, and we check the backups every month. When something needs attention, the people who built the site answer, within the response times written into your agreement. You get a short report each month, and each quarter we sit down together to look at how the site is doing and decide what to improve next.
You’ll always know where things stand.
We hold a 30-minute status call each week with whoever runs the project on your side. Every two weeks a written report tracks the milestones and raises any risk while there’s still time to do something about it. During design and build we also walk you through the work in a review session on the same schedule. Decisions go into a log with the date and the name of the person who made them, and the review space keeps every piece of work where you can find it.
What we make for you belongs to you.
At handover you receive the design files and the source code we wrote for your theme and blocks. The scripts that moved your content come with a written guide, so any WordPress developer can run them again. Software from other vendors stays under its own licence, and we list each one for you.