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.

Related planning guides

Next step: Put these decisions into one project brief, then ask providers to respond to the same scope.