Contracts for website work in the AI era: ownership, hosting and exit terms
Short answer: A website contract should say, in plain words, who owns the domain, the content, the code and design, the hosting and analytics accounts, and any AI-made material, and what happens to each if the work ends. Ownership of the finished work should be tied to full payment. The handover list and a deadline for it belong in the contract, not in an email. This page gives the clauses to cover, sample wording to adapt, and how to get it signed. It is information, not legal advice: have a lawyer review the final version.
You build or buy websites, and you want a contract that settles who owns what and how anyone can leave, now that an AI tool may write part of the work.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Start with the answer. A website is not one thing, so a contract cannot say "the client owns the website" and stop. It has to name each part: the domain name (the address), the content (text, photos, product data), the code and design (what makes the site look and work), the accounts (hosting, analytics, search tools, forms) and, since AI tools are now part of many builds, the AI-made material and the prompts used to make it. Then it has to say when each part changes hands and what the client gets if the relationship ends. The sections below give you each clause, a sample line to adapt, and the failure it prevents.
This is a practical guide, not legal advice. Contract law, copyright and consumer rules differ by country and state. Use the clauses as a checklist for a conversation with a lawyer, and check local law.
This page may contain affiliate links from which Blur Studio earns commissions.
Why AI changes the contract
Three things are new. First, a hosted site builder may keep the site on its own servers, so the agency cannot always hand over a working copy. Second, the person who built the work may have used an AI tool, so the question "who wrote this" has a new answer. Third, the AI tool has its own terms about your inputs. A marketing consultancy, R3, published ten areas that client and agency contracts should address for generative AI (reported by Adweek, an advertising trade news site, in May 2024): where AI is used, rights to AI outputs, control over inputs and ownership of prompts, accuracy checks, review process, oversight of any models the agency builds, alignment with client IP policies, confidentiality, how time and fees are worked out when AI does much of the work, and compliance by subcontractors. That is a consultancy's list, not law, but it is a good prompt list. Law firm commentary adds a few more: assign or license the deliverables, carve out the agency's own tools and templates, make sure the AI tool's terms do not conflict with what you promise the client, and ban the use of client data to train AI.
What the law says about AI-made work is also not settled in the way many people assume. The US Copyright Office, the federal body that registers copyrights, said in its January 2025 report on copyrightability that AI tools that merely assist a human do not remove protection for the human's work, that purely AI-generated material is not protected, that the amount of human control is judged case by case, and that, with current technology, prompts alone do not give enough control. So never write "the client owns all AI output" or "the agency owns it" as a fact. Write what you will assign, what you will license, and that you give no promise the output can be copyrighted. For a clause aimed only at AI use, see the AI clause for an agency contract.
Part 1: who owns the site, the content and the domain
| Part | Safest default | Sample wording to adapt |
|---|---|---|
| Domain name | Registered in the client's own account, client as registrant, from day one | "The domain is registered in the Client's name and account. The Agency acts as a technical contact only." |
| Content the client supplies | Stays the client's. Client warrants it has the right to use it | "The Client owns the materials it supplies and confirms it has the right to use them on the site." |
| Content the agency creates | Assigned to the client on full payment | "On receipt of full payment, the Agency assigns to the Client its rights in the content created for the Client under this agreement." |
| Code and design | Assigned or licensed, with the agency's own tools and templates kept out | "The Agency keeps ownership of its pre-existing tools, templates and know-how and grants the Client a perpetual licence to use them as part of the site." |
| AI-made material | Say which parts are AI-assisted, assign the human-authored parts, license the rest, give no copyright promise | "Some content may be drafted with AI tools and reviewed by the Agency. The Agency assigns its rights in it to the extent it has any, and makes no promise that AI-generated material can be protected by copyright." |
| Hosting, analytics and search accounts | Client is the owner, agency is a named user | "All accounts are opened in the Client's name. The Agency is added as a user and removed on request." |
Tie the assignment to full payment. A common mistake is to say ownership passes on delivery. Delivery and payment are not the same moment, and a client who has the files but disputes the last invoice has little reason to pay. One sentence, "ownership passes on receipt of full payment, not on delivery", removes that leverage problem. The same point is made in the freelancer and small agency contract template.
The domain clause deserves extra care. ICANN, the body that sets domain rules, says on its registrant benefits and responsibilities page that the registrant takes sole responsibility for the registration and use of the name, must give accurate contact details and must answer the registrar (the company that registers the name) within 15 days. The registrant on the record is who the registrar treats as the owner. If the agency registered the name in its own account, the client is a customer of the agency, not the owner. Ask the question early, and see how to check who owns your website code for an existing site.
Part 2: hosting and care terms
If the agency hosts the site, or sells a monthly care plan, the contract needs a short hosting and care section. It should state:
- Who holds the hosting account and in whose name it is billed.
- What is included each month: updates, backups, security patches, uptime monitoring, a set number of small edits. Name the number of edit hours, and what happens when the client goes over.
- What is not included: new pages, redesigns, new features, paid plugins or tools, content writing.
- Third-party costs: who pays the platform subscription, and who is told if the platform changes its price. Hosted builders do reprice, and Webflow changed its plan prices in 2026 (check its pricing page), so the contract should say who carries a price rise.
- Backups: how often, where they are kept, and who can ask for a copy. Webflow's own terms say you alone are responsible for backing up your website content, so do not assume the platform does it for you.
- Response times: for example "we reply within one business day". Do not copy an uptime percentage into the contract unless you control the hosting and can meet it.
- Security basics: who is told, and how fast, if there is a breach. Match any timing you promise to your real process.
Part 3: platform risk, named in the contract
When a site is built on a hosted builder, the agency does not control everything. The platform's terms decide what is possible. Read the terms of any platform before you promise a client a handover. As of November 2026, the terms and help pages say, in short:
- Squarespace, a hosted site builder, says your content stays yours but grants it a perpetual, irrevocable licence for limited purposes, may suspend accounts, and its terms contain no export procedure. Its help centre describes only a limited export to a WordPress file (check the current page).
- Framer, a visual site builder, says in its terms that the customer keeps ownership and that its licence ends when the content is removed. Its help centre says it does not offer HTML export for self-hosting.
- Webflow, a visual site builder with hosting, says you keep ownership of your content, says it has no duty to back it up, and says that if a website designer dies or cannot be reached it may be unable to transfer the account or export the content to the client.
- Wix, a hosted drag-and-drop builder, says in its help centre that for a site to work properly it needs to be hosted and operated on Wix's servers, though you can connect a domain bought elsewhere. Read its terms of use for ownership and termination before you promise anything.
The practical rule: owning your content is not the same as being able to take a working site away. The contract should state which platform the site is built on, that its terms apply, and what the client will receive at exit (see the next section). A clause that promises a "complete copy of the site" is a false promise on a platform that has no export. For each platform's export rules, read the lock-in and export guide and cancelling or exporting from a platform.
Part 4: export and exit terms
Exit terms are the clauses that matter most on the day you wish you had written them. Include:
- A handover list: domain and registrar login, hosting login, CMS (content management system, the place you edit pages) admin login, analytics and search tool ownership, code repository access if there is one, design files, a content export, and a list of paid tools with renewal dates.
- A deadline: for example "within 14 days of a written request and payment of any undisputed invoices". There is no legal standard for this number, so pick one you can meet.
- Transition help: a set number of hours at a stated rate for the new provider.
- What the agency keeps: its own tools, templates and prompts, as in Part 1.
- No hostage clause: the agency may not withhold the domain or accounts over a dispute about fees, apart from content still unpaid for, as agreed.
- Deletion: when the agency deletes the client's data, and the client's right to ask for confirmation.
On domain transfers, ICANN's transfer policy gives hard limits worth writing around. A registrar may deny a transfer within 60 days of the name's creation or of a previous transfer. After a change of registrant, the registrar must apply a 60-day transfer lock unless the registrant opted out first. If the holder asks, a registrar without self-service must release a lock and provide the authorisation code within five calendar days. So the contract should say: change the registrant details before the end of the project, not on the day of the dispute, and ask for the code early. Check the policy page and your registrar's current process.
Clause checklist to copy
- Parties, scope and what is excluded
- Price, deposit, payment dates, late fees
- Number of design rounds and what a change request costs (see the change order template)
- Client responsibilities: supplying content, answering within a set time, warranting it may use that content
- Ownership by part (table above), passing on full payment
- AI use: which phases, which tool types, no client data used for training, human review of output, no copyright promise
- Third-party tools and platform terms, and who pays them
- Hosting and care scope, backups, response times
- Confidentiality
- Limits on liability, including accuracy of AI-assisted content after review
- Subcontractors bound by the same terms
- Handover list, deadline and transition help
- Term, ending the agreement, and effect on accounts and fees
- Governing law and how disputes are handled
Signing it online
Get the contract signed before any work begins. Most business contracts can be signed electronically, but rules differ by country and by document type, so check local law for yours. A tool such as QuickSigner, an electronic signature service for sending a document to be signed online from any device, keeps the signed copy, the signing time and the signer details together, so you can find it when a client says they never saw the clause. Whatever tool you use, store the final signed PDF with the project file and note the date in your project record. See getting contracts signed online without printing for the steps.
Red flags in a contract you are asked to sign
- The agency registers the domain or hosting in its own name and the contract is silent on transfer.
- "All rights remain with the Agency" with no licence back to the client.
- A clause that lets the agency delete the site, or lock it, over any dispute.
- No handover list, or a handover that depends on "the Agency's discretion".
- A monthly fee with no stated scope, so the client cannot tell what is covered.
- Silence on AI, when the price is clearly based on AI doing much of the work.
How I'd approach this
I would keep the contract short and make the ownership table and the handover list the two parts nobody can miss. Two to four pages is enough for most website work. Put the table in the body, not in small print, and send the handover list with the signature request so it is read.
First week: take your current contract and mark it against the 14-point checklist above. Fix three things first: domain in the client's name, ownership passing on full payment, and a handover list with a deadline. If you buy rather than sell, send these three questions to every agency you use today: whose name is the domain in, who is the owner on hosting and analytics, and what do I receive if I leave. Then have a lawyer review the final text once and save it as your template.
If you want a custom client portal where contracts, approvals and handover lists live together, Blur Studio builds the custom version, with connections to your CRM (customer records tool) and calendar and ongoing care. See what that includes. You can run everything on this page with ordinary documents and a signing tool.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Who should own the domain name, the agency or the client?
The client, from day one, registered in the client's own registrar account with the agency as a technical contact. ICANN's registrant responsibilities page says the registrant is responsible for the registration and use of the name, so the name on the record matters. Check local rules for your country-code domain.
Does the client automatically own AI-written content?
Do not assume so. The US Copyright Office's January 2025 report says purely AI-generated material is not protected, and that human contribution is judged case by case. Write what you assign, what you license, and that you do not promise the output can be copyrighted. Ask a lawyer about your country's rules.
Do I have to tell the client that I use AI tools?
No general law requires it that I know of, but many clients now ask, and the R3 list of contract areas includes where AI is used. Saying which phases use AI and that a human reviews the output builds trust and avoids disputes. See the AI clause for an agency contract.
Can I promise a client a full export of a site built on Wix, Framer or Squarespace?
No. Wix says in its help centre that the site must run on its servers, Framer says it does not offer HTML export for self-hosting, and Squarespace describes only a limited export to an XML file for WordPress. State what you can deliver, such as text, images and a list of pages, and name the platform and its terms in the contract. Check each platform's current help page.
How long should a handover take?
Write the number down. There is no legal standard, so pick one you can meet, for example 14 days after a written request. Tie it to payment of undisputed invoices.
What should a hosting and care agreement include?
Who holds the hosting account, what is covered each month, what is not, backups, response times, who pays platform fees, and how a platform price rise is handled. See the hosting section above, and how to price builds and retainers when AI cuts the hours.
Can I sign a website contract online?
In many places, yes, for ordinary business contracts, but rules differ by country and document type, so check local law. Use an electronic signature tool that keeps the signed file and the signing record, and store the signed copy with the project file.
Is this page a contract template I can copy as it is?
No. It is a checklist with sample lines to adapt. Terms depend on your location, your client and the platform, so have a lawyer review the final contract once and reuse it as your template.
More in this topic: Websites: agency delivery, quality control and margins (10 guides) →
Sources
- ICANN: Transfer Policy
- US Copyright Office: Copyright and Artificial Intelligence, Part 2 (Copyrightability), January 2025
- Adweek Wire: 10 areas where gen AI needs to be addressed in client-agency contracts (R3, May 2024)
- Webflow Terms of Service
- Squarespace Terms of Service
- Framer Terms of Service
- ICANN: Registrants' Benefits and Responsibilities
- Wix Help Center: Exporting or embedding your Wix site elsewhere
- Framer Help: Can I export my website to HTML and self-host it?
- Squarespace Help: Exporting your site