A clear path from requirements to launch and support, with review points along the way.
Use this guide when discussing a website, CRM, ERP or travel portal. Your agreement confirms the process, responsibilities, dates and commitments for your own project.
Prepare your project briefDescribe your business problem, users and current tools. Agree the first release, deliverables, exclusions, dependencies, milestones and acceptance criteria in the proposal.
Customer review: approve the scope and commercial terms before work starts.
Review the proposed pages, screens and customer journey. Consolidate feedback through the agreed project contact and record approved design decisions.
Customer review: confirm the design and identify any changes to scope.
Review agreed milestones and test the workflows against the acceptance criteria. Confirm supplier access and third-party requirements for any integrations.
Customer review: check the agreed features, record issues and approve acceptance when resolved.
Agree the launch checklist, access responsibilities, migration needs and release approval. Record domain, source-code and data ownership alongside hosting, documentation and training deliverables.
Customer review: approve launch and confirm receipt of the agreed handover items.
Confirm support channels, hours, response expectations and the maintenance work included. Agree how new requests and third-party changes are handled.
Customer review: keep the support scope and renewal terms in writing.
Review the proposal and handover checklist · Review company information
Bring your main business problem, existing tools and the people who will use or approve the system. A demo request is followed by confirmation of availability and meeting details.
Review the demo agenda