How it runs

From first call to handover

  1. A call about the problemNot about what you want built — about what is not working now. Half the time the thing a client asks for is not the thing that fixes it, and that is worth finding out before anyone quotes.
  2. Written scope and a fixed quoteYou get the scope in writing: what is included, what is not, the milestones, and the price. Nothing starts until that is agreed, so there is no moving target later.
  3. Build in milestones, on a live staging linkYou get a staging URL from the first week and watch it fill in, rather than waiting in the dark for a big reveal. Problems surface while they are still cheap to change.
  4. A proper review roundYou go through it, list what is wrong, and I fix it. Feedback is expected — it is part of the build, not an inconvenience at the end of it.
  5. Handover you actually ownCode, access, a walkthrough of how to edit things, and documentation for anything non-obvious. No lock-in: you can hand it to another developer tomorrow and they will know where they are.

Before you ask

Common questions

How long does a build take?

A straightforward marketing site is usually a few weeks; a store or an application with real logic behind it is longer. The honest answer is that it depends on how ready the content is — the delay on most projects is waiting for copy and images, not the code.

What do you need from me to start?

Whatever you already have: existing site, brand assets, content, and a clear sense of what the site has to make happen. If the content is not written yet, say so at the start — it changes the timeline more than any technical decision.

Do you handle hosting and domains?

I set up and deploy to hosting, and I will recommend what suits the project. The accounts stay in your name and you keep the billing, so you are never locked out of your own infrastructure.

Can my team update the site without calling you?

That is the goal on every build. WordPress work is set up so editors can change content without touching layout, and for custom builds I hand over documentation for whatever is not self-evident.

What happens after launch?

You get a period after launch for fixing anything that turns out to be broken — that is part of the build, not extra. After that, ongoing work is either ad-hoc hourly or a monthly retainer, whichever fits how much you actually need.

What if I do not like what you have built?

You will have seen it on staging from the first week, so it should never be a surprise at the end. Review rounds are built into the process, and structural feedback is much cheaper early — which is exactly why you get the link early.

Not sure which one you need?

Describe the problem and I will tell you what it actually takes to solve it.

Start a conversation →