Ownership of code and accounts

Ask who will own the source code, domain, hosting account and business data, and whether they can be transferred. The answer should be explicit in the proposal or agreement. You should also know where access is stored and what happens if the working relationship ends.

A clear scope and proposal

Request a written proposal that identifies pages, functions, content responsibilities, integrations, revision process, testing, release conditions and final deliverables. The price and schedule should follow that confirmed scope. Clear exclusions are useful because they prevent assumptions on both sides.

Portfolio and references

Review live websites rather than presentation images alone. Open them on a phone, test the main journeys, inspect loading behaviour and ask what the developer actually designed and built. A strong answer distinguishes the person’s contribution from the client’s content or another supplier’s work.

Communication and post-launch work

Find out who makes technical decisions and who answers your questions. Direct access to the person responsible can simplify decisions, while a larger team can help when the project needs several disciplines at once. In either case, agree how issues, maintenance, access and future changes will be handled after release.