How a website project works

1. Brief and quote

You tell us about the business, the booking tool, your current site and anything with a deadline, such as an opening. We reply with questions or a written quote that lists the pages, what we need from you and a target launch date. Nothing starts until you accept it.

2. Page plan

We map every page and draw the main layouts for desktop and phone, like the concepts on the samples page. This is the cheapest moment to move things around, so it's worth a close look.

3. Design draft

We design the home page and one inner page, usually the service menu, with your colors, type and photos. You mark up what you'd change, and we revise before building the rest.

4. Build and content

We build the full site on a private preview address, add the menu, team, policies and contact details, and set up the editor for the parts your staff will change.

5. Booking tests

We tap every Book button on a phone and a desktop, check the forms, and check page speed on an ordinary mobile connection. You get the preview link to try it yourself.

6. Launch and handover

We connect your domain, set up redirects if you're replacing an older site, and send you the logins and a short guide to editing. From there you can run the site yourself or move to a care plan.

What sets the pace

Most delays come from content. The menu needs to be final, photos need picking, and policies need someone to sign off on the wording. If you gather those early, the build moves quickly. If you're short on time, tell us in the brief and we'll plan a smaller first launch with the home page, the menu and booking, then add the rest after.

What we ask for

Your details

Logins and client-facing content are used only for your project. If part of the work goes to a production partner, they work under a confidentiality agreement. See the privacy policy.