Deliverables to Demand When Your Website Launches (and Why It Isn't Yours Without Them)

On launch day everyone is pleased and nobody is thinking about paperwork. The real problem arrives two years later: you want to switch providers, or move your email, or simply update a price — and you find the domain is registered to an agency that no longer replies. That's the most expensive ending a web project can have, and a twenty-minute checklist prevents it.

Deliverables aren't bureaucracy. They're the difference between having bought a website and having rented one without realising. Here's the full list, what to check on each item, and how to confirm that what you were handed actually works.

The four non-negotiables

If you can only fight for four things, make it these. Without them you don't control your own site, however much you paid for it.

1. 01The domain in your name. Registered with your email as the administrative contact, not the provider's. Log into the registrar and confirm it yourself — why this matters so much is in why your own domain matters.
2. 02Hosting logins. Your own username and password, with an administrator role. Not a "we manage that for you", which in practice means you can't leave.
3. 03The code, or access to the CMS. Depending on how it's built: repository plus deployment credentials, or a CMS admin account with full permissions.
4. 04Original photos and source files. Full resolution and in editable formats. A logo delivered only as a PNG is useless for printing a billboard or embroidering a uniform.

The full list, item by item

Look at the right-hand column: a deliverable isn't a file sent by email, it's something you can use without help. "We sent you the credentials" and "we confirmed together that you can log in" are two very different levels of handover.

Analytics and verification: who owns what

This point gets skipped almost every time, and it hurts later. If Google Analytics and Search Console were created inside the provider's account, your entire data history leaves with them the day you switch. And history can't be recovered: there's no way to export three years of behaviour into a new property.

• Analytics: the property should live under your own Google account, or at minimum have your email as a full administrator.
• Search Console: verified in your name. This is where penalty and indexing warnings land.
• Google Business Profile: owned by you, with the provider as a manager if needed. Never the other way around.
• Social accounts: created with your email, with the provider added as an administrator.

The general rule is simple: you are the owner, the provider is a collaborator. Any setup where that's inverted is a dependency that will cost you money the day you want to change. What to actually look at in those tools afterwards is covered in website metrics that matter.

The documentation that actually helps

A forty-page manual nobody opens isn't documentation — it's an elegant way of not training you. What you need is short and very specific, aimed at the three or four things you'll be changing yourself.

• How to edit the copy on a page and publish the change.
• How to upload or replace an image without breaking the layout or the loading speed.
• How to add an entry to the blog or catalogue, if you have one.
• Where form submissions go and how to change the destination address.
• What to do if the site goes down: who to call, and with what details.
• When the domain and hosting expire, and who renews them.

Maintenance, backups and continuity

Closing the project isn't the end of the site — it's the start of its working life. Put in writing what happens next, even if you decide not to buy maintenance from whoever built it.

• Who renews the domain and hosting, and on whose card. An expired domain takes your email down with it.
• Where the backups live and how they're restored — the full detail is in website backups and continuity.
• Who renews the security certificate, if it isn't automatic. See SSL and basic website security.
• What support covers in the first months: fixing the build's own bugs shouldn't be billed as extra.
• What counts as an included change and what counts as new work, defined so both sides read it the same way.

Signs you're not going to be handed anything

• "We'll take care of the domain" with no further explanation. Ask whose name it ends up in.
• There's no written quote listing deliverables. If it isn't written down, it doesn't get delivered.
• The price is monthly and nobody says what happens if you leave. That model can be fine, but you need to know — the comparison is in subscription vs one-time payment.
• They refuse to give you panel access "so you don't break anything". It's your website; the risk is yours to take.
• Photos only arrive at web size. Without originals you can't reuse them for anything printed.

All of this negotiates far better at signing than at closing. Ask for it as an annex to the quote from day one: a serious provider has no problem signing it, and the reaction to that request already tells you plenty. How to read that signal and others is in how to choose a web design agency.