Website & Development
What Should Be in Your Website Contract and SLA?
Copy for AI
A website contract fixes what you get, for what price, and by when.
The SLA (service level agreement) covers life after launch: support, response times, availability and maintenance.
The verdict: a good web development contract makes scope, change orders and ownership watertight. The SLA and the exit clause decide whether you stay free for years.
Together, these two documents prevent the classic pitfalls:
- a project that overruns
- an invoice that comes in higher than expected
- a supplier you can’t reach once the site is live
Below is a concrete checklist: scope, change orders, deadlines, support, uptime, warranty and exit.
This is deliberately not legal advice. It’s a practical guide, so you know what to watch for before you sign.
Want the bigger picture of a website project? Read our guide to building a B2B website.
What is the difference between a website contract and an SLA?
The contract is about building your site; the SLA is about running it afterwards.
The contract covers the build
It governs the project: what’s being made, by whom, for what amount and within what timeframe.
It describes the one-off delivery and everything that leads up to it. A sharp website brief makes that part much easier to write.
The SLA starts at launch
It sets out how quickly your supplier responds to problems and what falls under maintenance.
It also fixes how available your site should be, and what that costs per month or per year.
Rule of thumb: if a topic isn’t written down, assume you’ll argue about it later.
Which clauses belong in the web development contract?
Scope, price, planning and ownership that leave no room for interpretation. Work through these points before you sign.
Scope and deliverables
A list of what’s being built precisely:
- number of pages or templates, and languages
- integrations such as CRM, newsletter and forms
- the CMS, and who supplies the content
The more concrete it is, the less argument afterwards.
Price and payment schedule
Fixed price, hourly rate or a mix, and when you pay, for example in phases.
Watch out: check what’s not included, such as stock photos, licences, premium plugins or hosting. Our list of the hidden costs of a website shows where those usually sit.
Planning and deadlines
Milestones with dates, and what happens in case of delay.
Also record that the planning depends on your input. Slow feedback or late content is the most common cause of overrun.
Change orders
The most important clause against runaway invoices. It’s short.
Agree three things:
- how additional work is determined
- that it’s estimated in advance and approved in writing
- at what rate it’s billed
For example, say you ask for a calculator page halfway through. With this clause, you get a written estimate first, so it never lands on your invoice as a surprise.
Revisions
How many feedback rounds are included in the price, and what an extra round costs.
Endless polishing without a limit is expensive for everyone.
Ownership and intellectual property
Who owns the design, the code and the content after payment?
Agree that all rights transfer to you the moment the invoice is paid. This ties straight into your exit position further on.
Liability
A reasonable limitation of liability is normal, but read what’s excluded.
An agency that works honestly will want to nail these points down itself. Ambiguity is just as annoying for the builder as it is for you.
See how we approach projects in web design.
Before you sign, run through our questions to ask a web designer.
What belongs in the SLA after launch?
The arrangements for support and maintenance after delivery, which you live with for years.
A few thousand euros in build costs pale next to years of support. So read this part just as thoroughly as the build quote.
Support and reachability
How do you report a problem: email, ticket or phone? During which hours?
And does that also apply outside office hours?
Response and resolution times
The heart of an SLA.
Good arrangements distinguish by urgency: a site that’s down deserves a faster response than a typo.
Watch the difference between two times:
- Response time: when someone starts on it
- Resolution time: when it’s actually fixed
Nobody can honestly promise a fixed resolution time for problems that lie partly outside their control.
Maintenance
What falls under the monthly fee: CMS and plugin updates, security patches, backups, small content changes?
And what falls outside it and is billed separately? Our checklist for a website maintenance contract goes clause by clause.
Backups and recovery
How often are backups made, where are they kept, and how quickly can your site be restored after an incident?
Tip: ask when the last restore was tested. Our guide to website backups explains why that test matters.
Security and updates
Who keeps the platform safe and up to date?
With a headless or CMS choice the division of responsibility differs, so make it explicit. The basics are in our piece on website security.
Performance
If need be, agree that the site keeps loading fast. Slow pages cost you leads.
Google’s Core Web Vitals thresholds give you numbers you can write down:
- LCP: within 2.5 seconds
- INP: 200 milliseconds or less
- CLS: 0.1 or less
Google measures each at the 75th percentile of page loads. Here’s what that check looks like on a live site:
PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.
So even a fast site can miss one threshold.
Run the same check with our website speed test. Our explanation of Core Web Vitals shows what you can demand.
Put the numbers in writing.
How do you read the uptime and warranty arrangements?
Uptime is the promised availability of your site, usually a percentage per month or year.
What the percentages really allow
The higher the percentage, the less downtime is allowed. The step from 99% to 99.9% looks small, but it isn’t:
Those figures come from the standard availability table on Wikipedia: 99% allows about 3.7 days of downtime a year, 99.9% about 9 hours.
The details under the figure
More important than the exact percentage are three details:
- Exclusions: is planned maintenance left out of the measurement?
- Measurement: how, and by whom, is downtime measured?
- Remedy: what do you get if the standard isn’t met?
Here’s how a real SLA answers those. Cloudflare’s Business SLA promises 100% uptime, yet credits are the “sole and exclusive remedy”. They’re capped at one month of fees in any 12 months, and you must report an incident within five business days.
Our guide to choosing web hosting shows where that responsibility usually sits. And uptime monitoring gives you your own measurement, not just the supplier’s.
The warranty
The warranty governs something else: faults in the delivered work are fixed free of charge within an agreed period.
Watch the distinction:
- Bug: the supplier built something wrong, and fixes it for free
- Change: you want something different, and that’s a change order
A reasonable warranty period after delivery is customary.
Make sure it states what does and doesn’t fall under warranty. Then a genuine fault can’t be presented as paid extra work.
Why is the exit clause so important?
It decides whether you’re free to leave or stuck with your supplier, and it’s perhaps the most important point of all.
Ownership of everything
Code, design, content and database must be yours.
Ask whether you receive a full export or copy on departure. Our explainer who owns my website goes through each asset.
Domain and accounts
Your domain name, hosting and all accounts must be in your name, not only in that of the agency.
This is a classic pitfall: companies that don’t manage their own domain are in a weak position. You can check who the registrant is in a public lookup:
Notice period
How far in advance must you cancel the SLA, and are there costs attached to stopping early?
Handover
Does your supplier help with a clean handover to a new party, and on what terms? Our step-by-step for a transfer to a new agency shows what to ask for.
Vendor lock-in
Does the agency build on a mainstream platform or in a closed system that only they can work with?
Open and transferable is always safer. A mainstream open source CMS is the classic example:
WordPress.org, October 2026. WordPress says it powers over 43% of all sites on the web, so many parties can take it over.
Our guide to CMS vendor lock-in explains how to stay future-proof.
An honest partner makes leaving easy, precisely because good service should be the reason you stay.
Want to move to another platform or agency later? Our guide on website migration without losing rankings helps you do it without damage.
Leaving should be easy; staying should be your choice.
Don’t forget the data processing agreement
If your supplier processes personal data for you, the GDPR requires a written data processing agreement.
That happens, for example, via forms, a CRM integration or analytics.
It isn’t an optional extra but a legal obligation under article 28 of the GDPR. The agreement states, among other things:
- that the supplier acts only on “documented instructions” from you
- how the data is secured
- that data is deleted or returned, at your choice, when the work ends
Our GDPR-compliant website checklist covers the rest of your site.
So ask for it explicitly. A professional agency has it ready.
Which clauses should you check first?
Use this table when a quote lands on your desk:
| Clause | What to ask | Red flag |
|---|---|---|
| Scope | Which pages, templates, languages, integrations? | ”Website as discussed” |
| Change orders | Written estimate and approval before work? | Extra work billed afterwards |
| Ownership | Do all rights transfer on payment? | Agency keeps code or design |
| Response times | Different times per urgency level? | One vague “as soon as possible” |
| Uptime | What’s excluded, and what’s the remedy? | A percentage with no definitions |
| Exit | Export, domain in your name, handover terms? | Domain registered to the agency |
| Data processing | Is an article 28 agreement attached? | ”Not needed for a website” |
Comparing two offers side by side? Our guide on comparing website quotes helps you weigh them fairly.
The short summary
A good website contract makes scope, change orders, deadlines and ownership watertight. No surprises during the build.
The SLA governs life after launch: support, response times, uptime, maintenance and backups. That’s the largest part of your site’s lifespan.
Then check three more things:
- Warranty: free fault repair, no disguised extra work
- Exit clause: ownership of code, content and domain keeps you free
- Data processing agreement: required if personal data is in play
Anything unclear? Keep asking questions: an honest partner is happy to explain.
Frequently asked questions
Can the contract and the SLA be one document?
Yes. Many agencies do. They use one agreement with separate chapters. That’s fine, as long as each part is clear and nothing is left unwritten.
What uptime percentage should a website SLA promise?
No single figure is right. 99.9% allows about 44 minutes of downtime a month. What’s excluded and what you get if it’s missed matter more.
Who should own the domain name?
Your company. Always. Register the domain, hosting and accounts in your own name, so a change of supplier never depends on their cooperation.
Do I need a data processing agreement with my web agency?
Yes, if they process personal data for you, for example through forms, a CRM integration or analytics. Article 28 of the GDPR requires it.
Not sure whether a quote or SLA is sound? Get in touch with us: send it over and we’ll go through the clauses with you.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.