How we work
Eight steps, and no reveal at the end.
You see the site as it is built, on a link you can open on your own phone. Nobody should have to approve a description of a change when they could approve the change itself.
A conversation, not a brief
We start by asking what the site has to achieve and where the business currently loses time or enquiries. Most useful answers come out of describing a normal Tuesday, not from filling in a requirements form.
Scope and a written estimate
You get a page listing what is included, what is not, what we need from you and when, and what it costs. If something is uncertain we say so and price it separately rather than hiding it in a round number.
Structure before decoration
Wireframes and the content plan first. Changing a grey box takes minutes. Changing a finished page takes a week, and that is the difference between two rounds of feedback and six.
Design system, then screens
Colour, type, spacing and components defined once with contrast checked. Then the pages, which come together quickly because the pieces already exist.
Build in the open
Every change gets a preview URL you can open on your own phone. You watch the site come together rather than waiting for a reveal at the end. AI does the mechanical typing at this stage, which is why it moves quickly; a person reviews every line before it reaches the preview.
Measure before launch
Core Web Vitals, accessibility, structured data and every page title checked against the built output rather than against our intentions. We fix what fails before you see it.
Launch with a way back
Redirects mapped, DNS planned, the old site kept ready to restore. We switch at a quiet hour and watch Search Console for the following weeks.
Handover that means something
Source code, credentials, a written guide and a walkthrough. You can carry on with us or without us, and that is deliberate.
Ways to work with us
Four arrangements, depending on what you need.
Most first projects are fixed scope. The others exist because not every problem is a new build.
Fixed scope project
A defined site or application for an agreed price, in stages. Suits most first projects, where both sides want the number known up front.
Suits: Websites, redesigns, first versions of an application.
Monthly retainer
An agreed block of hours each month for changes, new pages, improvements and support. Unused hours are visible in the report rather than quietly absorbed.
Suits: Sites that change every week, growing product teams.
Audit and advice
A one off review of speed, accessibility, SEO or code quality, with a written report and a prioritised list. No obligation to have us do the work.
Suits: Deciding whether to fix or rebuild, or checking another vendor's work.
Rescue work
Taking over a project that has stalled, or a site whose original developer has gone. We start with an assessment, because sometimes the honest answer is to start again.
Suits: Abandoned builds, inherited codebases, urgent breakage.
Ready to start?
Tell us what you have now and what is not working. The first conversation is free and there is no obligation after it.