Method
Clear boundaries before production.
The aim is to remove delivery work from your team without creating another layer of ambiguity. Here is the full lifecycle from first contact to handover.
Choose the right route. One Build project, agency partnership or technical responsibility.
Submit the minimum useful context. Project Builder shows which forms are relevant and which can be skipped.
Receive or reuse the project reference. It ties later forms, review and support to the same project.
Clarify what is still unknown. Email first; call/video when it resolves decisions faster.
Agree scope and commercial terms. Deliverables, price, responsibilities, dependencies and review points before production.
Produce the work. Technology follows the project.
Review privately. A review environment lets the agreed parties see the work before production handover.
Consolidate corrections. One review route avoids fragmented contradictory instructions.
Prepare production. Hosting, domain, DNS, SSL, forms and external dependencies where launch is included.
Use the least access necessary. Delegated/restricted access first; attended remote where appropriate.
Protect existing production. Backup before destructive replacement where supported and in scope.
Deploy. Install the approved build in the agreed production environment.
QA. Test the agreed URLs, links, forms, HTTPS, responsive behaviour and integrations.
Post-launch backup where appropriate. When supported and included.
Handover. Remove temporary access unless ongoing responsibility is expressly agreed.
Support if needed. Return with the project reference and describe business impact.
No open-ended enquiry billing.
A project begins when the applicable scope and commercial terms are accepted. Filling a form does not itself start paid production.