Website Proposal Checklist: What to Review Before Signing
A website proposal should make the product, responsibilities, money, timeline, ownership, and acceptance process understandable. If an important expectation appears only in a sales call, it is not yet part of the agreement.
Written by Anthony Barbaro, independent designer and developer in San Diego.
Direct answer
Start here.
Before signing, verify the exact deliverables and exclusions, who supplies content, revision and approval rules, payment schedule, ownership, recurring costs, launch responsibilities, support terms, and how scope changes are priced and approved.
Working document
Proposal review worksheet
Copy this list into your project notes and verify each item before committing money, access, or a launch date.
- Business objective and success criteria
- Named pages, templates, features, integrations, and exclusions
- Content, photography, migration, and accessibility responsibilities
- Milestones, feedback windows, revisions, and acceptance rules
- Payment schedule, taxes, recurring care, and third-party costs
- Domain, source code, design files, content, and account ownership
- Testing, redirects, analytics, launch, backup, and rollback work
- Warranty, maintenance, response times, cancellation, and change control
Decision detail
Make scope and responsibilities testable
Terms such as “SEO included,” “responsive design,” or “custom website” are too broad without deliverables. Ask what pages, metadata, structured data, redirects, performance work, browser support, and content tasks those phrases represent.
The proposal should identify client responsibilities too. Copy, images, legal review, platform access, and feedback can block delivery when they have no owner or deadline.
Related service: San Diego Web Design
Decision detail
Understand the complete commercial model
Separate one-time implementation, recurring care, and third-party costs. Confirm payment milestones, late approvals, cancellation terms, and whether deposits are refundable.
Projects change. A useful change-control clause explains how new work is described, estimated, approved, and scheduled before it begins. It protects both sides from surprise invoices and untracked requests.
Decision detail
Define ownership and the finish line
Confirm who owns or controls the domain, source code, design files, written content, images, analytics, hosting, and platform accounts. Note any licenses or services that cannot be transferred.
Define what acceptance means and what launch includes. Forms, analytics, redirects, backups, accessibility checks, mobile QA, and DNS changes should not be left to assumption.
FAQ
Related questions
Short answers to the follow-up questions that often appear during this decision.
Should a website proposal include every possible page?
It should identify the included pages or reusable page types and explain how additional pages are priced. Future ideas can remain outside the initial scope.
What does website acceptance mean?
Acceptance is the agreed point when defined deliverables meet the proposal’s criteria. The agreement should explain the review period, how defects are reported, and what counts as new work.
Apply this to your project