Straight answers, including the awkward ones.

It is an estimate, and it holds if the scope holds. If the project grows, or needs paid third-party services we did not plan for, the figure moves, and we tell you before it does, not after.

Hosting, domains, plugins, APIs and software licences. We bill these separately at exactly what they cost us. We do not mark them up.

We talk about what you are building and who it is for, then write the scope down together. You approve a design before any production code exists. Then we build, test on real devices, and hand over with hosting and SEO configured.

Revisions inside the agreed scope are part of the job. Changes outside it are billed at our daily rate by time required, so a two-day change adds two days to the invoice. We always tell you which side of the line a request falls on before we start it.

You can scrap it, but it is not refunded or credited, because the work was done. This is the most common source of friction on projects, which is why we push hard on getting the scope right before anyone opens an editor.

The deadline moves by however long we were waiting. After fourteen days of silence or missing assets the project goes dormant; restarting may carry a fee and gets scheduled around our other work.

Usually, for a rush fee. Speed comes out of somewhere, normally our evenings, and it is priced accordingly.

Three milestones: a non-refundable advance before work starts, a payment when the first major update or prototype is delivered, and the balance on completion before final handover.

No. All payments are non-refundable, and the rate is locked once the advance clears. We would rather say that plainly on a public page than bury it in a contract.

We do, until final payment clears. At that moment ownership transfers to you completely. We may show the finished work in our portfolio; if a project is confidential, tell us before we start and we will agree that in writing.

Thirty days of warranty from handover covers bugs and functional errors at no charge. It does not cover new features or design changes; those are new work.

Either a monthly management contract, priced openly on our pricing page, or our standard hourly rate as things come up. Most clients take the contract because it costs less than paying by the incident.

We configure them as part of handover. The accounts are yours and billed to you at cost. We do not sit in the middle of your infrastructure or hold it hostage.