A web design proposal may promise a modern look, a better mobile experience, and a launch date. But if you run a cleaning service, landscaping company, or home repair business, those promises do not tell you whether customers will still find the right services, request estimates, or reach you when the new website goes live.
Before signing, look for something more useful than a polished presentation: a written description of what will be delivered, what your business must supply, how the finished work will be checked, and what happens if the plan changes.
A proposal does not need to predict every design decision. It does need to make the important business decisions visible before money and deadlines are committed.
Start with the problem the redesign is supposed to solve
Ask the designer to explain what is not working now and what the project will improve. “Make the site more professional” is a preference, not a testable objective.
Useful objectives might include making service coverage easier to understand, fixing confusing quote-request steps, improving mobile navigation, or giving staff a straightforward way to update business hours. These are examples of work a redesign can address, not guaranteed outcomes.
A worthwhile proposal should identify which problems are supported by a review of the existing site and which are assumptions that still need discovery. It should also distinguish a complete rebuild from targeted changes to a few pages. A small business may not need a new platform to improve an unclear service page.
Ask for a page-by-page scope, not just a page count
“Five-page website” can mean very different things to different providers. Request a list of pages or page types and the specific work planned for each.
For example, clarify whether the scope includes:
- A homepage with service navigation and a clear inquiry path.
- Individual pages for core services, or one combined services page.
- A service-area page that accurately explains where the company works.
- An About page, contact page, and any required business information.
- Existing blog or resource pages that must remain available.
The proposal should state whether page layouts are custom-designed, adapted from templates, or reused across similar services. It should also explain what happens if the business discovers it needs another service page midway through the project.
A page count without a page list is not an adequate definition of scope.
Find out who is responsible for every piece of content
A redesign often involves more writing and preparation than the initial proposal makes obvious. A new layout still needs accurate service descriptions, genuine project photographs, customer information, and decisions about which older pages to keep.
Ask three direct questions: Who writes or edits the copy? Who supplies and licenses the photographs? Who enters and checks the final content on the website?
If the designer expects the business to provide everything, the schedule should allow time for that work. If copywriting is included, specify which pages, how many rounds of review, and whether the business approves factual claims about its services, licenses, service areas, or guarantees.
Also identify content that will not move to the new site. Removing an old page without reviewing its purpose or traffic can create avoidable problems.
Make functionality and integrations specific
A proposal that says “contact form included” should explain what the form actually does. Does it send an email? Does it capture a service address? Does it produce a confirmation for the customer? Who receives the inquiry, and how will delivery be tested?
The same applies to online booking, payment links, review feeds, live chat, CRM connections, and scheduling tools. Ask whether the quote includes setup, configuration, testing, subscription charges, and troubleshooting after launch.
If the designer is not supplying a particular feature, that exclusion should be obvious. A third-party tool that requires an additional monthly subscription is not the same as a feature included in the quoted project price.
For a service company, prioritize the functions that help customers understand the work and get in touch. Do not buy a complicated system simply because it appears in a demonstration.
Require a clear plan for existing URLs and search traffic
A redesign that changes only styling is different from one that changes page addresses, merges services, or moves the site to a new platform.
If URLs will change, ask for a list of existing pages and their intended destinations. Google’s site-move guidance describes mapping old URLs to new ones, preparing and testing the new site, using appropriate redirects, updating internal links, and monitoring the transition.
Your proposal should make it clear who will perform those tasks and who will check that they work. It should also identify who preserves or reconfigures analytics and Search Console access.
Do not accept a promise that rankings will stay exactly the same. Google notes that significant site moves can bring temporary fluctuations while pages are recrawled and reindexed. The practical commitment is to manage the transition carefully, not guarantee a search position.
Define what “finished” means before the final invoice
“Launch-ready” should have an agreed meaning. A business owner should be able to test the result without having to evaluate code.
Consider asking for a prelaunch review that covers:
- The main pages on common phone and desktop screen sizes.
- Business phone numbers, links, service areas, and opening hours.
- Contact and quote forms, including whether test inquiries reach the right inbox.
- Navigation, important buttons, and any booking or payment steps.
- Redirects for changed URLs and the absence of unintended search-blocking settings.
- A walkthrough showing how an authorized staff member can update routine content.
The proposal should identify who performs the checks, who can approve the site, and how defects discovered before acceptance will be handled. A review period and a limited number of reasonable revision rounds can protect both parties from a vague, open-ended finish line.
Clarify ownership, licenses, and account access
A website contains several different assets: the domain registration, hosting account, content management system, design elements, photographs, code, analytics, and subscription-based tools. Paying for a redesign does not, by itself, establish ownership of every component.
The U.S. Copyright Office explains that copyright generally begins with the creator, although certain works made for hire and transfers can change who owns the rights. Ownership and licensing therefore deserve explicit written terms, particularly when independent contractors and third-party assets are involved. The correct legal treatment depends on the actual agreement and circumstances.
Ask what your business is receiving: ownership of specified final work, a license to use it, access to editable files, or a combination. A designer's reusable tools, licensed fonts, stock images, and software subscriptions may be subject to different terms.
Also ask who will control the domain, hosting, CMS administrator account, analytics property, and any code repository. Your business needs an understandable handoff plan even if the designer continues providing support.
Separate the project price from continuing costs
A proposal should distinguish the one-time redesign fee from charges that continue after launch. Request a breakdown of what is included and what is billed separately.
Common areas to clarify are domain renewal, hosting, paid plugins, software subscriptions, content updates, security maintenance, backups, technical support, and future changes. Do not assume that a “free year” of a tool means the ongoing subscription will be affordable or optional.
For payments, look for a schedule tied to understandable milestones: an initial deposit, an approved design stage, a working review version, or completed handoff. The milestones should be specific enough that both sides know what triggers an invoice.
Ask what happens if the project is delayed because the business has not supplied content, or because an agreed deliverable is unfinished. The proposal should not leave those situations to a dispute after work has begun.
Ask how changes and early termination will be handled
No project scope is perfect on day one. You may decide to add a page, replace the booking process, or revise the service navigation after seeing an early design.
The useful question is not whether changes are allowed. It is how their cost and schedule impact will be approved.
Ask for a written change process that states what qualifies as additional work, how a revised price is communicated, and who can authorize it. Also clarify what each party receives or owes if the project ends before launch: completed work, paid-for assets, account access, remaining charges, and any relevant licenses.
For larger or complicated contracts, an attorney familiar with the relevant jurisdiction can review the terms. This guide is a practical buying checklist, not legal advice or a substitute for the agreement itself.
Compare proposals by what they deliver, not just their totals
Two agencies may quote very different prices because they are proposing different work. One may include copywriting, migration, testing, training, and a defined support period; another may quote only the new design and page build.
Before comparing totals, ask each provider to clarify the same core questions: Which pages are included? Who supplies the content? What will work on launch day? How will existing URLs be handled? What rights and account access transfer to the business? What ongoing charges remain?
If an answer is missing, request a written clarification before signing rather than relying on a conversation you may remember differently later.
The strongest proposal is not necessarily the longest or the cheapest. It is the one that lets you see what you are buying, what you must contribute, what you can verify at handoff, and what responsibilities remain afterward.
Sources and Further Reading
Related service: Explore services
