Maintenance, Hosting and Warranty: Know What You Are Paying For
Build, hosting and maintenance are often bundled together in the proposal, which makes it hard to see what you will pay each year. Ask the agency to split them out. The build is a one-off. Hosting and domain renewals are annual. Maintenance is an ongoing service with its own terms. A bundled quote can look cheaper at the start and cost more over three years if the renewals are not clear.
Be clear about the warranty too. Most agencies fix bugs in the work they delivered for a short period after launch. Find out how long that period lasts, what counts as a bug, and what happens to changes that are not bugs. A defined window protects you from paying for basic fixes, and it protects the agency from endless requests.
Data Protection and Cookies
If the developer will handle personal data, such as form submissions, customer accounts or analytics, the contract should cover UK GDPR. Ask whether the agency will act as your processor, and whether a data processing agreement is included. It should describe the types of personal data, the purpose, security measures, any sub-processors such as hosting providers, and how data is deleted when the project ends.
Cookies and tracking need attention as well. UK rules under the Privacy and Electronic Communications Regulations (PECR) and UK GDPR require consent for many non-essential cookies. Check who sets up the cookie banner and consent logic, and make sure it is part of the acceptance criteria. A site that tracks visitors without consent can create problems that outlast the project.
Content, Deadlines and Silence
Delays in content are one of the most common causes of late projects and disputed invoices. If the contract does not say who supplies copy, product photos and approvals, and by when, it can be unclear whether a missed deadline is your fault. Write the schedule into the contract, with a process for what happens if your content is late. Also check that the supplier warrants it has the right to use every image, font and piece of text it includes.
Handover and Exit: What You Should Receive
Ownership on paper means little if you cannot use what you own. A proper handover should give you everything needed to run the site without the agency. Use this list when the project finishes, or before you change suppliers.
Source files and code. A full export of the code, the database and any configuration, in a repository you control.
Design files. Editable files for layouts, graphics and the style guide, not just exported images.
Accounts and credentials. Admin access to the domain, DNS, hosting, CMS, analytics, Search Console and email, all registered in your name.
Licence register. Every theme, plugin, font and stock asset, with its licence terms, renewal date and cost.
Documentation. Notes on how to deploy, update and back up the site, and who to contact for each service.
Backups. A recent, tested backup, kept somewhere you can reach independently of the agency.
How Providers Describe Website Ownership
A quick search shows plenty of material on website contracts, and each source has a different angle. The table below compares a few, and where each falls short for a business buyer.
Source type | What it offers | Gap for a business buyer |
|---|
UK legal firm guides (for example, Sprint Law) | Clear coverage of IP assignment, third-party licences, payment conditions and termination | General rather than specific to a platform or price band |
Contract-focused agency guides (for example, eSEOspace) | Practical clauses for code, accounts, hosting and exit | Few figures or sources, and it recommends a lawyer review before use |
Platform licence explainers (for example, InstaWP on GPL) | Clear explanation of software licences | Does not address who owns the finished site or its accounts |
GSS Tech Solutions website | Lists website development, e-commerce, WordPress and Shopify work, with a process that runs to post-launch support | The services page does not say who owns the site, hosting or domain. The footer links to Terms & Conditions, which you should read before signing |
Table 3: How the main sources approach website ownership, and where each leaves gaps.
The honest test of any provider is whether it puts ownership terms in writing before you pay. Ask for a draft contract early, and ask the questions in this article. Good agencies answer them plainly.
Frequently Asked Questions
Should the domain name be registered in my company’s name?
Yes, wherever possible. The registrant is the legal owner of the domain, so registering it to your company, with a business email as the contact, protects you if the relationship ends. If the agency has already registered it, ask for a transfer as part of the handover.
Who owns the website after launch?
It depends on the contract. The code and design are owned by whoever created them unless the contract assigns them to you. The accounts, domain and hosting should already be in your name. Ask for the ownership terms in writing before you pay the final invoice.
Is WordPress free to use for a client website?
The WordPress core is GPL-licensed, so it can be used commercially. Premium themes and plugins carry their own licences, which may include annual renewals or restrictions on the number of sites. Check each licence before you rely on it.
Can I take my website to another agency?
Usually, if you own the code, the accounts and the licence register, and if the contract allows handover. Without those, a new agency may need to rebuild the site or negotiate access. That is why exit terms matter as much as the build itself.
Do I need a lawyer to review a web development contract?
For a small brochure site on a standard template, a careful review of the checklist may be enough. For a larger or business-critical build, a solicitor with IP and technology experience can save far more than their fee by spotting problems early.
The Bottom Line
A website is more than a design. It is a set of files, accounts and licences, and the contract decides who controls each one. Before you sign, check who owns the code and designs, where the domain and hosting are registered, which third-party components you rely on, and how you will leave if the relationship ends. A few clear clauses now can save you weeks of frustration and a lot of money later.
Want a Web Development Contract You Can Read Easily?
At GSS Tech Solutions, we build websites, web applications and e-commerce stores for UK businesses, from discovery and design through to launch and post-launch support. Ask us for our full terms before you commit, and we will walk you through who owns what, which accounts sit in your name, and how handover works. Clear terms are easier to live with than surprises.
Call +44 203 599 8122 or visit gsstechsolutions.co.uk to book a free consultation.