How we build
The whole thing, start to finish: the first call, a written scope, a staging link you can open any time, launch day, and the month after.
Start to finish
No stage is a black box. At every one you know what we are doing, what we need from you, and what you walk away holding.
We ask how the business actually gets work today — who phones you, what they ask, and what you are tired of explaining for the hundredth time. No deck, no pitch.
We write down what we heard, what we would build, and what it costs — in plain English, page by page or screen by screen. If something in it surprises you, we got the call wrong.
We collect what we need — logo, photos, the words you already use, and access to your domain and any tools you run on — and stand up a staging site.
Work ships to staging in reviewable pieces. You see the homepage before the whole site exists, and the booking form before it is wired up.
We test on real phones and real browsers, check speed and contrast, then go live on a quiet weekday morning — never a Friday afternoon.
How long the whole thing takes depends entirely on what we are building. A site that answers your five most common questions and a system that quotes, schedules and invoices are not the same job, and pretending they run to the same clock helps nobody. Your proposal carries a dated schedule for your project — rather than an estimate published here that could not possibly know it.
What it costsYour side
Most of the delay on a project is not the code. It is waiting on something only you have.
It goes into the first call, one kickoff session, and a look at staging between stages. Concentrated at the start, then light — you are reacting to work, not producing it.
What the main button should say, who gets the enquiry when someone fills in the form, and which day it goes live. We make the rest and show you.
Photos of real work rather than stock, your actual prices or service list, and the questions customers ask you most often.
Not a committee. Projects stall when a page sits waiting on an approval nobody is quite authorised to give.
How it's built
None of this is an upgrade or a line item. It is what the work is.
Most of your customers arrive on a phone, so that is what gets designed and tested first — not a desktop layout squeezed down afterwards.
Pages are built to load on cellular data in a parking lot, not just on office wifi. Speed is a feature people only notice by its absence.
Real contrast, keyboard navigation, and structure a screen reader can follow. It is how the markup gets written, not a checklist run at the end.
Proper titles, clean structure, and the local details search engines and map listings need in order to understand what you do and where you do it.
Analytics wired in from launch, so you can see which pages bring the calls and which ones nobody reads. What you change next is then evidence, not opinion.
We build on widely used, well-documented technology, so another developer could pick your project up and know where they are. Nothing depends on us being available.
Code, domain, hosting and accounts are in your name from the start. If you ever leave, you take all of it with you and nothing stops working.
After launch
Launch day is not the end of the job. Things need updating, a page needs adding, something breaks, or the business changes and the site should say something different.
Our Care Plan covers the ongoing side of that, so when something comes up there is already a developer who knows your project — not a stranger quoting to learn it first. What it covers, and what it costs, is in the footer of every page.
It is optional. Everything is in your name either way, and if you would rather host it yourself or hand the whole thing to another developer, nothing about the way we built it stops you.
How support worksTell us what you're trying to get done.We'll tell you what it takes.
