Our process

The same five steps, every project.

Most web projects go wrong in predictable ways: scope that was never written down, “done” that was never defined, and a change agreed in a chat message that nobody priced. This is the process we run to prevent those. It's published in full so you can hold us to it.

Why this is public

Anyone can say they use AI coding agents; you can’t verify it and it won’t be a differentiator for long. A written process you can read before you hire us is something you can actually check, and something you can hold against whoever else you’re considering.

The five steps

Each step has a condition for starting, something it produces, and a checkpoint it has to pass before the next one begins. We don’t wave a checkpoint through to move faster, because each one exists to prevent something that costs more later.

01

Call

30 minutes, free

One conversation, not a series of them. We ask what you're trying to build, what happens if you do nothing, roughly what budget you're working with, and what's driving the timeline. Then we go deeper on the same call: walk us through the last time the problem actually happened, step by step. The general description is always tidier than the reality, so we put numbers on it while you're there. How often, how long, who does it, and what it costs when it goes wrong.

What you get: An honest answer about fit, and a written summary within 24 hours asking “did we get this right?” Any misunderstanding surfaces before it's priced in. If we're not the right people, we'll say so and point you somewhere better.

02

Plan

Within a week

We turn the call into a written quote and proposal: the problem in your words, what we'll build, what we won't, objective acceptance criteria, a timeline, and the price. Scoping is part of quoting, so you are not charged for it. We send our AI use disclosure alongside it, unprompted. If anything is still fuzzy, we map that part of the process with you before pricing it rather than guessing.

Checkpoint: A written quote and proposal: scope, price, timeline, exclusions, and what done means. Nothing is built until you approve it.

What you get: A fixed price against a fixed scope, in writing, that you can read without a lawyer and compare against anyone else's.

03

Build

2 to 4 weeks for a marketing site

We collect access, confirm who decides, put a weekly demo in the calendar, and record the starting numbers so the result can be measured later rather than asserted. Then every week you get something you can click, plus a short written update: what shipped, what's next, what we need from you, and anything at risk. Anything outside the agreed scope goes through a written change order with a price before the work happens, never a chat message.

Checkpoint: Before any release ships, a checklist is run against it: every AI-generated file read by a human, authentication, authorization, and payment paths reviewed line by line, tests passing on the critical paths, a licence and provenance scan, no secrets in the repository, dependency vulnerabilities checked. The completed checklist is committed to your repository.

What you get: A working demo every week, so the gap between what you pictured and what exists is never more than seven days wide.

04

Launch

Week of launch

We handle the domain, the security certificate, and your analytics setup, then test on real phones before anything goes live. Then everything transfers: source code and repository ownership, a deployment you control, written documentation, a recorded walkthrough you can replay, a software bill of materials, and credentials moved across securely. Our access is removed or reduced, and we confirm that in writing.

Checkpoint: We test against the acceptance criteria from the Plan, not a new set invented at the end. You have 10 business days to accept or report a defect in writing, and anything failing those criteria is fixed at no charge.

What you get: Everything needed to run, change, or hand the site to someone else. Nothing locked to us, and a standard for “done” that was set before the work started.

05

Report

Monthly, optional

The build includes 30 days of post-launch support for bug fixes. After that, the $99/mo care plan is the ongoing mechanism: hosting, security, backups, uptime monitoring, small content edits within two business days, and a report every month. Leads you got, where they came from, what we changed, what worked, and the one fix we'd make next. Plain English, month to month, cancel any time. New pages, new features, and redesigns are separate project work, quoted in writing like the first build.

What you get: A monthly report telling you what the site is actually doing for your business, and no obligation to keep paying for it.

What it costs to run this

Custom websites start at $999. The final number depends on scope and you get it in writing as a quote and proposal before any work starts. Payment plans and financing are available. You own the site outright once the build is paid for: the design, the code, the content, the domain, and your customer data.

Step five is the only recurring cost, and it is optional. The care plan is $99 a month, month to month, cancel any time. Full detail is on the pricing page.

The four rules behind it

If you remember nothing else from this page, these are the commitments that matter most. They’re the ones worth asking any developer about, not just us.

  • Nothing is built before the written quote is approved. Not a prototype, not a head start. A fixed price on an undefined scope is how both sides end up unhappy.
  • A working demo every week. Not a status email. If what we’re building has drifted from what you pictured, you find out in seven days, not seven weeks.
  • Scope changes go in writing, with a price, before the work happens. We will not build something agreed verbally and invoice you for it afterwards.
  • Nothing ships without human review. There’s a completed checklist in your repository for every release.

What we need from you

The timelines above assume a couple of things, and it’s fairer to say so up front than to explain it later:

  • One person with authority to approve scope and sign off deliverables
  • Responses to questions and feedback within about five business days
  • Availability for a weekly demo, usually 30 minutes
  • Access to the systems we're integrating with, at the start of the build rather than mid-build

Where those slip, timelines move day for day. That isn’t a penalty. It’s the only way a fixed date can be honest when half the inputs are outside our control.

Related

How we use AI explains what the coding agents do, what a human does, and the two limitations most studios won’t mention. Services and pricing shows what this process produces, and what it costs.

Start with a call.

Thirty minutes, free, no obligation. You'll leave with a clear view of what your project would take, whether or not you work with us.

Start a project