Discovery and scope
Every engagement begins by reviewing the current process, user roles, data sources, integrations and intended outcomes. Deliverables, exclusions, timeline and responsibilities are clarified in a written scope.
Design and development
User journeys and the technical approach are made visible before development. Working versions are shared progressively, and changes are assessed in terms of impact, time and priority.
Testing and acceptance
Functionality, permissions, mobile compatibility, performance and critical business flows are reviewed. The launch plan is implemented after customer acceptance scenarios have been completed.
Launch and data migration
Domain, hosting, access, backup and any required data migration are planned according to the project scope. Responsibilities and rollback steps are clarified before go-live.
Maintenance and support
Bug fixes, performance work, security updates and further development may continue under a separate support scope. Response times and support channels are defined by the selected service level; general statements on the website do not on their own constitute a commitment to 24/7 support.
Customer responsibilities
The customer is responsible for providing accurate information and access, verifying ownership of content and data, giving interim approvals on time, and obtaining third-party licences. Details are set out in the project contract.