How a project runs, start to handover

The sequence

1. Fit check. A short call, or straight to an inquiry if the published price already answers your question.
2. Discovery Sprint, for scoped work — a paid engagement producing the scope, the architecture and a fixed-price proposal. See the Discovery Sprint article.
3. Build, against the agreed scope and exclusions list.
4. Handover — code, infrastructure and documentation, in your accounts.
5. Thirty days of post-launch fixes, included.
6. Retainer, if you want ongoing cover. See choosing a retainer.

What we need from you

• Timely feedback and approvals at each milestone
• Content, assets and access we cannot produce ourselves
• One named point of contact who can make decisions

Delays here are the single most common cause of a timeline slipping, which is why they are listed in the terms rather than left implicit.

How we price the work

Fixed scope, fixed price. Every package lists what it includes. If the scope is fixed, so is the price — you are not billed for our estimating error.

What is excluded is written down. Each tier carries an explicit exclusions list. Nothing is 'assumed included' and then invoiced later.

Change orders are priced before they start. New scope mid-project gets a written change order with its own price and timeline. You approve it before we build it.

Payment schedule. 40% to start, 40% at the agreed midpoint milestone, 20% on handover. Retainers are billed monthly in advance and cancellable with 30 days' notice.

You own the code. Full IP and source-code ownership transfers to you on final payment. No licence, no lock-in, no hosting hostage.