List the assets separately
Domain registration, DNS, hosting, email, application code, design files, databases, licenses, customer data, analytics, payment accounts and app-store publisher accounts are different assets. Ownership of one does not automatically confer ownership of the others.
Write ownership and licensing terms before work begins
The agreement should state whether source code is delivered, whether reusable components remain licensed, which third-party materials are included, and what can be transferred. Do not assume any particular arrangement without written terms.
Define what a launch handover includes
Depending on scope, this may include administrator access, content instructions, repository access, architecture notes, backup procedures, DNS details, service accounts, training, known limitations and outstanding tasks.
Separate hosting from maintenance
Hosting keeps the environment available; maintenance may include software updates, security patching, backups, uptime checks, technical support and content changes. New features or major redesigns are typically separately quoted.
Agree on issue priority and response windows
A support contract should distinguish a broken checkout from a minor spelling issue, say how incidents are reported, identify support hours and describe whether emergency coverage is included. Never assume 24/7 coverage or guaranteed restoration unless contracted.
Plan for renewal, migration and exit
Keep an inventory of recurring subscriptions and renewal dates. Define how backups, data export and access transfer will work if the client chooses another provider. Migration effort may require its own estimate.
Questions to prepare before requesting a quote
- Who owns domain, hosting, code, database and publisher accounts?
- Which access credentials and documents will be handed over?
- What is included in any agreed defect-remediation period?
- Which updates, backups, content edits and monitoring are included?
- Who pays third-party subscriptions and usage?
- What are support hours, response priorities and exclusions?
- Can data be exported or transferred to another developer?
Example: how this affects a real project
A booking site launches successfully but later needs a payment-provider upgrade. Without a defined maintenance owner and a tested recovery path, a routine integration change could interrupt reservations. A written care agreement reduces uncertainty about responsibility.
Frequently asked questions
Is maintenance mandatory?
Not necessarily. The client can take responsibility or appoint another provider, subject to the project’s ownership, licensing and transition terms.
Does a one-time website price include unlimited edits?
No. Revision rounds, support and new features depend on the agreed scope.
Do I automatically receive all source code?
The project agreement must specify that along with third-party restrictions and any licensed reusable components.
Next step
Start a project — Tell us what you need.
Explore our services · View the development process · Back to all guides