Quick answer
Website and app handover should leave your team with working access, the files it needs and a clear support agreement. Check domains, hosting, source code, app-store accounts and records. Agree who handles updates, backups, faults, renewals and later features.
What should your team receive?
Ask for a short guide to editing content, adding users, viewing enquiries, making backups and reporting faults. Check important tasks with your team using suitable sample data.
- Confirm working access for the right staff members.
- Locate source code, design files and operating instructions.
- Record accounts, licence requirements and renewal dates.
- Name who reviews access, updates, backups and performance.
What does support actually cover?
Separate fault fixes, technical updates, content changes and new features. Ask what is included, what is excluded and how extra work is quoted.
Agree where faults are reported, support hours, who investigates and when a case is escalated. A response deadline tells you when someone replies; it does not automatically promise a repair by that time.
Can the backup be restored?
Ask for a restore demonstration using non-sensitive sample data. Record who can start it, how often backups are made and how long they are kept. Agree how failures are monitored and what information might be lost between backups.
Check whether included change hours expire and how urgent help outside office hours is charged. A support contact or monthly fee alone does not explain these limits.
Your planning worksheet
Use this table to prepare the same brief for each provider. Add the person responsible and the current status for each item. Enter costs only from written quotes, in HKD, with the billing period.
| Item to plan | Details to give the provider | What to check |
|---|---|---|
| Accounts and source files | Domain, hosting, code, stores, analytics and owner | The right staff members can use the accounts |
| Renewals and restoring service | Billing period, renewal owner, backups and restore process | Record renewals and demonstrate an agreed restore exercise |
| Support after launch | Defects, upkeep, content changes and new features | List included work, exclusions and who handles urgent problems |
Example project scenario
Illustrative planning example; not a completed customer project.
A business takes over a website and app. Staff check hosting and store-account access, find the source files and record renewal owners. A private recovery exercise is agreed separately. The support plan distinguishes a broken feature from a requested design change.
Common questions
Is owning the source code enough?
You also need usable files, account access, instructions and the required software or licences. A new provider must be able to understand and operate the service.
Does maintenance include unlimited changes?
Only if the agreement says so. Define included work, support hours, exclusions and approval for extra work.
Are content updates part of maintenance?
Ask whether staff make edits themselves or the provider offers an update service. Agree the amount of work, approval and price.
What should a maintenance contract specify?
List covered systems, updates, monitoring, backups and recovery. Agree response and repair expectations separately, escalation, renewal payments and account access if you change provider.
Download the planning worksheet (CSV)
Find a provider through TechQuotations
TechQuotations connects Hong Kong buyers with IT service providers. Use your brief to discuss the work and compare proposals. You choose the provider and agree the terms directly. A request does not guarantee a quotation.
Explore suitable providers through TechQuotations