Research-based planning guide
Web design proposals: domain ownership, access and handoff
A web design proposal should explain who controls the domain, hosting, website files, accounts and ongoing services. Resolve access and handoff before signing. A finished page is only part of the deliverable if the business can't renew its domain, change providers or recover an essential account.
On this page
List the assets separately
“You own the website” can leave important details unanswered. Ask about the domain registration, source files, design assets, written content, licensed media, analytics and any software subscription used to operate the site.
Some assets may be licensed rather than transferred. Ask what happens if the designer's subscription ends or you move the site. The agreement should identify limitations without hiding them behind a broad ownership statement.
Use an access-and-handoff sheet
| Asset | Confirm before launch |
|---|---|
| Domain | Registrant details, renewal responsibility and recovery method |
| Hosting | Account control, billing and migration access |
| Website | Source or export format and what it includes |
| Analytics | Business-controlled access and appropriate roles |
| Forms and email | Delivery destination, account control and ongoing charges |
| Licensed components | Renewal costs and transfer restrictions |
Keep recovery arrangements under the business's control. Don't put passwords into a proposal, email thread or public project document; use an appropriate secure sharing process.
Define the final demonstration
Ask the designer to show how ordinary tasks work: editing a page, receiving a form submission, checking a backup and finding support contacts. Confirm whether documentation and training are included.
Test the contact path with a clearly identified test message before launch. Seeing a success screen doesn't establish that the business received the inquiry. Also verify the telephone and booking links people will actually use.
Separate handoff from maintenance
Ask what support continues, what it costs and how cancellation works. Clarify security updates, backups, content changes and third-party charges separately. A maintenance plan shouldn't be confused with ownership or account recovery.
For a redesign, include redirects and access to the old site in the plan. Google's site-move guidance explains why URL changes need deliberate handling.
Read the redesign migration checklist and small-business website guide. To discuss a website project, bring your current platform, account-access situation and the actions customers need to complete. A useful proposal makes those responsibilities visible before production begins.