What you actually get at the end

Most website quotes describe a process. Discovery, design, build, launch. Very few describe an inventory, and the inventory is what you are actually buying. A project can be delivered exactly as promised and still leave you holding less than you assumed, because nobody wrote down what “delivered” included.

The list below is what a complete delivery looks like. Not every item applies to every project, and several are legitimately negotiable. The point is that each one should be a decision made at quoting stage rather than a discovery made at the end.

The live site, and access to it at handover

The obvious deliverable, with two non-obvious conditions attached to a smooth website handover.

You should have an administrator account, in your own name, with your own login credentials, tested by you logging in before final payment. Not an editor account, not a shared login, and not access mediated through the supplier. If the site runs on a platform where the top-level account is the billing account, that billing account should be yours.

You should also have a written description of what your account can and cannot change, because this varies enormously between builds and is almost never explained. Some sites hand you full control of templates. Some hand you a set of editable fields. Both are defensible. Only one of them matches the sentence “you can update it yourself”, and you should know which you have before the invoice is settled.

The domain and the hosting, in your business name at handover

These two decide whether you can leave, and they are the items most commonly held by the supplier out of convenience rather than intent.

The domain registrant record should show your business, matching your registered entity name and business registration, in a registrar account you can log in to today. You can verify this yourself through auDA’s public .au WHOIS service or through the registrar directly. Read the registrant field specifically, not the administrative or technical contact, and not what the invoice says.

The hosting account should be in your name with your billing details, even where the supplier manages it day to day. Managed hosting bought through a supplier is a perfectly normal arrangement. Managed hosting you cannot log in to is a dependency, and dependencies are cheap to fix at the start and expensive to fix during a dispute. The full treatment is on who owns your website.

Design source files and code, handed over with the rest of the files

Source files are the editable originals: the design document with its layers and components intact, not a set of exported images. Without them, the next person who touches your brand has to recreate rather than continue.

Code means the templates, stylesheets and custom functionality, delivered in the repository they were developed in, with history. A zipped folder of files is better than nothing. A repository transferred to an account you control is the version that lets a new developer understand what was done and why.

For sites built on a hosted platform where there is no code in the conventional sense, the equivalent deliverable is a full content export and a written record of the configuration.

Licences for anything commercial, listed as part of the handover process

Themes, plugins, page builders, fonts and stock photography are licensed rather than owned, and no clause in your contract with the designer changes the terms the licensor set.

What you should receive is a written list: every commercial component in use, whose account holds the licence, when it renews, what renewal costs exclusive of GST, and what stops working if it lapses. Font licences are the ones that catch people, because web font licences are frequently capped by domain or by traffic and are not always transferable. Stock imagery is the other, because some licences do not transfer to a new owner at all.

Handover documentation, and the content itself

Documentation does not need to be a manual. It needs to record where everything lives, how to perform the tasks you will actually perform, what the backup arrangement is, and what renews when. A recorded walkthrough of the real site does most of this work in twenty minutes, and sharing that recording alongside the written document is one of the simple best practices that separates a smooth handover from one you are still untangling questions from months later.

The written content is a deliverable too, and copyright in it needs to be dealt with explicitly if a copywriter produced it. So does the photography, whether commissioned, licensed or supplied by you.

What a post-handover follow-up should still cover

A handover is rarely a single clean instant — a short, defined post-handover window, where the supplier remains reachable for questions about how to use what was handed over, is a reasonable and common practice, and it should be agreed as part of the handover process itself rather than negotiated informally after the fact once the relationship has already moved to “closed”. What that window covers, and for how long, is worth confirming as a written line item alongside everything else on this page, not assumed to be indefinite goodwill.

What “you own it” usually excludes

The phrase is in almost every proposal. It is rarely dishonest and it is frequently incomplete. Read it against the carve-outs it commonly hides.

Ownership contingent on final payment, which is reasonable, but which should say so plainly and should state what happens if the project stops part-way. Ownership of the finished output but not the source code or the build configuration. Ownership of the site but not the design files it came from. A licence to use rather than an assignment of copyright, which is a materially different thing. And ownership of everything except the supplier’s own framework or component library, which is sometimes the part doing the heavy lifting.

None of those is automatically unfair, and a supplier who reuses a proprietary framework across clients has a legitimate interest in keeping it. The failure is one of sequencing. A carve-out agreed at the start is a commercial term. The same carve-out discovered at handover is a dispute, and the shape of Australian agreements that avoid it is covered on web design contracts in Australia.