Quick answer
Launch is the start of operating a digital service. Before final acceptance, make sure your business can access the domain, hosting, content manager, app-store accounts, analytics and payment service. Confirm who controls the source code, design files and customer data under the contract.
Practical scope
Ask for a short handover guide: how staff update content, create users, view enquiries, back up data and report faults. Test critical actions with your own team, including a form submission, purchase or booking as relevant. Agree which defects the developer will fix, how quickly support requests are handled, and how new features are quoted.
Keep a list of recurring charges and renewal dates. Assign an internal owner to review access, backups, security updates and performance. A clear handover reduces dependence on a single supplier and helps the service improve after release.
What to define before requesting proposals
- Access to domain, hosting, code, stores and analytics
- Source files, documentation and deployment process
- Backups, monitoring, security updates and incident contacts
- Warranty, support response and recurring renewals
Questions to ask service providers
- Can your staff complete critical tasks without the developer?
- Which defects are covered after launch and for how long?
- How can another provider maintain the service later?
How to assess the answers
Complete a handover test before final acceptance. Ownership on paper is insufficient if the business lacks working access, documentation and recovery steps.
Separate four kinds of aftercare
Specify defect correction, technical upkeep, routine content changes and new feature development separately. “Support included” does not establish that all four are covered. For hosting and domains, list account ownership, renewal responsibility and how your team obtains access.
Agree service expectations in writing
- Where faults are reported and what information is needed.
- Acknowledgement and investigation expectations, distinct from resolution.
- Backup responsibilities and the agreed restoration process.
- Included work, exclusions, recurring charges and escalation contacts.
Can you assume content updates are maintenance?
No. Ask whether staff edit content themselves or the supplier provides an update service. Define the volume, approval process and charge before relying on it.
Account and support handover register
Copy these items into your brief, adapt the requirements and assign an owner and status. Examples illustrate planning decisions, not customer case studies. Fill cost fields with HKD quotations you obtain and state the billing period.
| Decision / item | Information to provide | Acceptance / comparison check |
|---|---|---|
| Accounts and source files | Domain, hosting, code, stores, analytics and owner | Your nominated staff have appropriate working access |
| Renewals and recovery | Billing period, renewal owner, backups and restore process | Record renewals and demonstrate an agreed restore exercise |
| Aftercare | Defects, upkeep, content changes and new features | Separate included work, exclusions and escalation contacts |
Download the editable worksheet (CSV)