How to Read a Website Redesign Proposal Before You Sign
A website redesign proposal should tell you what will be delivered, what is excluded, how work will be approved, and what your business receives at handover. If those points are vague, comparing the bottom-line price alone will not tell you whether two proposals cover the same job.
This guide explains what to look for in a web design proposal before you sign. It is a practical review framework, not legal advice. Contract language, intellectual-property terms, privacy requirements, and liability questions should be reviewed by a qualified attorney when they matter to your project.
Start by translating the scope into a deliverable list
“Website redesign” can describe very different projects. One proposal may cover a new visual system, rewritten content, development, analytics, redirects, training, and launch support. Another may cover page templates and development only. Both can honestly use the same headline.
Turn the scope section into a list you can count and verify:
- Which pages or page templates are included?
- Is content being written, edited, migrated, or merely pasted into layouts?
- Are forms, calculators, directories, ecommerce, scheduling, or other integrations included?
- Does the work include mobile and accessibility review?
- Are analytics, consent tools, search-console verification, redirects, and metadata part of launch?
- How many design concepts and revision rounds are included?
- Who supplies photography, illustrations, fonts, and paid software?
Then look for an acceptance standard next to each major deliverable. A phrase such as “new contact form” describes an output. “Form sends a test submission to the named inbox, displays a confirmation, and is checked on current desktop and mobile browsers” describes how the parties will know it works. Atlassian’s overview of project deliverables and acceptance criteria{target=“_blank” rel=“noopener noreferrer”} makes the same useful distinction: define what completion means for each deliverable.
The proposal does not need to predict every implementation detail. It should be specific enough that you can point to the document when someone asks whether a page, feature, migration task, or test was included.
Read the exclusions as carefully as the inclusions
Exclusions are not automatically a warning sign. Clear exclusions often make a proposal more useful because they expose assumptions before work begins. The problem is an important task that is neither included nor excluded.
Common areas to clarify include:
- Copywriting and content entry.
- Product, staff, or location data cleanup.
- Stock images, custom photography, video, and licensing.
- Premium plugins, hosting, domains, email, and other recurring fees.
- Third-party integrations and vendor support.
- Accessibility or compliance work beyond the stated testing scope.
- Search-engine migration tasks, including URL mapping and redirects.
- Post-launch maintenance, edits, and support.
Ask what happens when the team discovers work outside the stated scope. A useful change process identifies who can request a change, how its cost and schedule effect will be shown, and who must approve it before work starts. Without that process, a small request can quietly become a disputed assumption.
Pay attention to dependencies as well. If your team must deliver approved copy by a certain date, provide system access, or make one decision-maker available, the proposal should say so. A timeline based on unnamed client inputs is not a complete timeline.
Find the approval and launch checkpoints
A proposal should show how the project moves from one stage to the next. Typical checkpoints may include discovery, sitemap or content architecture, design, development, content entry, testing, launch approval, and post-launch verification.
For each checkpoint, ask:
- What will we review?
- Who can approve it?
- How long is the review window?
- What counts as a revision rather than a new request?
- What happens if a dependency or approval is late?
This matters because “two rounds of revisions” is ambiguous without a unit. It could mean two consolidated rounds for the whole project, two rounds per page template, or two individual comments. The proposal should also explain whether unused rounds carry forward and how contradictory feedback from several stakeholders will be handled.
Launch deserves its own checklist. Confirm who has authority to approve launch, who controls DNS and hosting changes, what is backed up, what will be tested immediately afterward, and what the rollback plan is if a critical path fails. Our website redesign SEO migration checklist covers the search and redirect details that can be easy to miss when the visual design gets most of the attention.
Confirm ownership, access, and recurring costs
Do not treat “you own the website” as the end of the ownership discussion. Ask what that means for each component:
- Domain registration and DNS.
- Hosting account and billing.
- Source code and repository.
- Design source files.
- Written copy, photography, and licensed assets.
- Analytics, tag management, search tools, and advertising pixels.
- CMS administrator accounts.
- Plugin, theme, font, and software licenses.
Some assets may be transferred, some may be licensed, and some may remain part of the provider’s reusable system. The proposal should distinguish those categories and state any ongoing fee or usage restriction. ICANN explains that registrants manage their domain settings through a registrar and enter into a contract governing the registration; its information for domain registrants{target=“_blank” rel=“noopener noreferrer”} is a useful reason to verify that the business—not an individual vendor’s private account—is the intended registrant.
For code, identify whether you receive a repository, an export, or only access to a hosted service. GitHub documents a formal process for transferring a repository{target=“_blank” rel=“noopener noreferrer”}; whether that process applies to your project or not, the proposal should say who controls the working repository during and after the engagement.
List recurring costs in one place. A lower build price can still come with separate hosting, maintenance, plugin, image, email, or platform fees. You are not looking for every future price to be fixed forever. You are looking for visibility into what must continue for the delivered site to operate as proposed.
Make the handover a named deliverable
Handover should not mean receiving a password in the final email. A useful handover package can include:
- A list of systems, account owners, billing owners, and renewal dates.
- Named user access for the business instead of shared credentials.
- Source files or repository access promised in the agreement.
- A current backup or export and instructions for restoring it.
- Documentation for forms, integrations, analytics, and routine content edits.
- License and subscription details, including what is transferable.
- A redirect map and launch record.
- Training and a defined period for correcting launch defects.
The exact list depends on the stack. The important point is that the proposal names the handover artifacts, who prepares them, and when delivery is complete. If the provider will continue maintaining the site, the business should still know which accounts it owns and what it would need if the relationship ended.
Compare proposals on a normalized scorecard
Before choosing, put each proposal into the same table. Use rows for scope, content, integrations, revision rules, testing, migration, ownership, recurring costs, launch, handover, support, timeline, and price. Mark each cell as included, excluded, unclear, or optional.
This does not turn a complex decision into a perfect number. It exposes why totals differ and gives each provider the same questions to answer. A proposal that costs more may cover more. A proposal that costs less may be the better fit because your team can own the excluded work. The scorecard helps you compare the actual arrangement instead of comparing labels.
If a proposal still leaves material questions open, ask for written clarification or a revised scope before signing. Robben Media can help you translate business goals into a reviewable redesign scope. Request a proposal review through our website design services page, or contact us to discuss your project.
Jeremy Johnson
Owner
Jeremy co-owns Robben Media and directs strategy for every client engagement. With a Computer Engineering degree from Missouri S&T, he brings deep technical expertise in web development, SEO, and automation. Before acquiring Robben Media in 2023, Jeremy led marketing and branch management in the mortgage industry. He believes marketing should be measured by revenue generated, not impressions reported.