What you're agreeing to when you pay a deposit.

The proposal we send you is the agreement. It lists what we will build, what we will not, how long it takes, what it costs and what we need from you. Paying the deposit accepts that scope and these terms. There is nothing else to sign.

If anything in the proposal is wrong or missing, say so before you pay. Changing it afterwards is a scope change, which is fine — it just has a number attached.

Projects are 50% to start and 50% at launch, unless the proposal says otherwise. Retainers are billed monthly in advance.

The deposit reserves your place in the schedule. It becomes non-refundable once we have delivered the first work — design direction, architecture or a first build — because that work is real whether or not you continue.

The balance is due when the site or application goes live. Ownership of the code, the domain and the accounts transfers to you at that point.

The proposal's scope is the whole job. Anything outside it — a page that was not listed, a feature that appears halfway through, an integration nobody mentioned — is a change.

Changes are quoted and approved before they are built. You will never find out about extra cost from an invoice. If a change is small enough that quoting it would take longer than doing it, we will just do it.

Each package includes a set number of revision rounds, stated in the proposal. A round means you collect your feedback and send it in one go; we work through it and send it back.

Feedback arriving in a drip over several days is several rounds, not one. Rounds beyond the included number are billed as an add-on at the rate in the proposal.

Your timeline starts when your materials arrive, not when you pay. Text, images, logos and account access are on the critical path, and we cannot start without them.

If materials are more than 30 days late the project is paused and returns to the schedule when they arrive, at the next available slot. The deposit stays valid; the original dates do not.

You do. On final payment you own the code, the content and the design, outright. The domain and the hosting account are registered in your name from the beginning, so they were never ours to transfer.

We keep the right to describe the work and show it publicly as a case study, unless you ask us not to — just say so and we will not.

Third-party costs stay yours: domain registration, hosting, paid fonts, stock images, API subscriptions. We will always tell you before anything is bought.

Every project includes a support window, stated in the proposal — 14 days on Launch, 30 on Build. That covers anything broken and small corrections, not new work.

After it ends you can run the site yourself with the documentation provided, or keep us on the Care plan. There is no lock-in either way, and nothing auto-renews without you choosing it.

Either of us can end the project in writing. You pay for the work completed to that point; we hand over everything produced so far and the accounts in your name. Nothing is held hostage.

We build carefully and test before launch, but no one can promise software is free of faults. Our liability is limited to what you paid us for the project. We are not liable for lost business, lost data you have not backed up, or a third-party service changing or failing.

Ask before you pay rather than after. Nothing in here is designed to catch you out, and anything unclear is something we would rather fix in the wording than argue about later.