Updated 18 September 2026. Originally published in 2016; revised to replace outdated advice and links.
Before you agree a website project, ask what you will be able to use, edit and take with you afterwards. Clear answers make a healthier working relationship for everyone.
Separate the different assets
A domain name, design, written content, photographs, software licences and hosting account are different things. Ask who holds each one and what rights your business receives. Third-party fonts, plugins, stock images and subscription tools may have their own licence conditions.
Agree access and responsibilities
- Which text and images can your team edit?
- Who looks after updates, backups and security?
- How are domain renewals and account recovery handled?
- Can another developer work on the site if needed?
- What is included in a handover, and are there any agreed costs?
Understand monthly and project arrangements
A monthly service is not inherently a bad deal, and a one-off build does not remove every ongoing cost. Compare what is included, how long the arrangement lasts and what happens when it ends. Ask for unclear points to be explained before you commit.
For inLIFE work, project-specific ownership, payment and handover details should follow your agreed proposal and applicable terms and conditions. This article does not override those terms.
Check the website’s business information too
Agree who supplies accurate contact details, privacy information and any terms relevant to the services or transactions on the site. Requirements depend on the business and how the website operates; a generic checklist is not a compliance certificate.
Compare our website options or ask the team about a proposed project. We would rather explain the details at the start than leave you guessing later.
