A website redesign quote can look thorough and still leave out work that matters after launch. Before comparing prices, ask each provider to identify what will be delivered, what you must supply, and what happens if something goes wrong.
The useful comparison is not simply the number of pages or the quoted price. It is the scope of responsibility: who handles content, technical setup, testing, launch, and the first round of fixes.
Start with the outcome, not the page count
Write down the job the new site needs to do. For a service business, that might mean making services easier to understand, improving local search discovery, or helping visitors send a usable inquiry. A ten-page site without a working contact path may be less valuable than a smaller site with a clear next step.
Ask the provider to describe how the proposed structure supports those outcomes. If the proposal only lists a homepage and several interior pages, the business problem may not have been scoped yet.
Check these six areas in every website redesign proposal
1. Content responsibility
Who writes or revises the copy? Who selects photographs, obtains permissions, and checks factual claims? Does the price include moving existing content, or only placing material you provide? Clarify how many review rounds are included and what counts as a new request.
2. Design and mobile behavior
Ask what is included in the design review: navigation, page templates, mobile layouts, readable typography, and contact calls to action. A mockup is not the same as a tested mobile website. Request an explicit mobile QA step before launch.
3. Search and URL continuity
For an existing site, ask for a URL inventory and a plan for pages that will move or disappear. Who handles redirects, page titles, descriptions, indexing settings, and basic internal links? A redesign should not casually discard URLs that people or search engines already use.
4. Forms, integrations, and measurement
Specify every contact form, email destination, newsletter connection, scheduling request, or payment integration. Who tests a real submission from start to finish? If analytics are included, define which actions are measured and how a successful inquiry is distinguished from a button click. See our guide to website form lead tracking for a practical verification method.
5. Launch and ownership
Confirm who controls the domain, hosting, WordPress administrator access, backups, licenses, and analytics accounts. Ask who will perform the launch, verify HTTPS and redirects, and check the site after DNS changes. Ownership should be clear even if the same provider continues to maintain the site.
6. Support after launch
Separate a genuine defect in the agreed deliverable from a new feature request. Ask for the correction window, response expectations, and ongoing maintenance options. A proposal that says “support included” without defining its boundaries is hard to compare fairly.
A simple way to compare two quotes
Make a three-column comparison: Included, Owner supplies, and Not included / priced separately. Place each of the six areas above into one column for each provider. Where a line is vague, ask for a written clarification before accepting the proposal.
For example, “SEO setup” might mean only entering page titles in one quote, while another includes a URL mapping, redirects, metadata, and post-launch checks. Neither description should be assumed from the label alone. The clarification makes the price difference understandable.
Turn vague proposal language into something you can verify
Two quotes can use the same terms while promising very different work. Before deciding, ask the provider to translate broad descriptions into specific deliverables and a way to confirm they were completed. You do not need an exhaustive technical contract; you do need a shared understanding of what the price covers.
- “SEO setup”: Ask whether this means only writing page titles, or also reviewing existing URLs, mapping redirects, checking indexability, and confirming basic internal links. Identify who is responsible for the content and who checks the finished pages.
- “Mobile-friendly design”: Ask which templates and interactions will be tested on smaller screens, including navigation, contact forms, buttons, and text readability. Agree on who reviews and signs off on mobile behavior.
- “Content migration”: Request a list of what moves: services, articles, images, documents, testimonials, and important existing URLs. Clarify whether rewriting or cleaning up weak content is included or separately scoped.
- “Launch support”: Identify who checks contact-form delivery, HTTPS, redirects, important integrations, and analytics after launch. A homepage loading is not proof that a business website is functioning end to end.
- “Training and maintenance”: Ask what training covers, which accounts you retain, how long the initial correction period lasts, and what ongoing support costs after that period.
A useful quote states both what is included and what is excluded. When an item is undecided, record the assumption and who must make the decision. Otherwise, two reasonable people may read the same sentence and believe it promises different things.
Use an acceptance checklist before the final payment
Before work begins, write down a few tests that will tell you the agreed scope is complete. For example: the important pages work on mobile; the contact form delivers a genuine inquiry to the correct destination; old priority URLs either remain accessible or redirect intentionally; and the business has the agreed access to its domain, hosting, WordPress administration, and analytics.
These are illustrative checks, not a claim that every provider includes migration, analytics setup, or ongoing maintenance. The written scope decides which tests apply. A business may reasonably commission a narrowly defined landing page rather than a full redesign, but it should understand what will still need attention afterward.
If a proposal leaves an essential item out, request a written addition or a separate estimate rather than relying on a verbal assurance. This keeps the decision grounded in deliverables and reduces the chance that an inexpensive-looking quote becomes expensive through change requests and missed responsibilities.
Questions to send before you sign
- Which specific pages and templates are included?
- Who supplies, edits, and approves the final copy and images?
- Will existing important URLs be preserved or redirected?
- Who tests mobile layouts, forms, and contact email delivery?
- What accounts and assets will our business own at handoff?
- What happens if a defect is discovered just after launch?
These questions do not require a large technical specification. They require clear answers that both sides can use when the project is underway.
Choose the proposal with fewer unanswered questions
A lower price may be the right choice when the work is intentionally narrow and the business can supply missing pieces. A higher price may make sense when it includes content, migration, testing, and launch support that would otherwise become separate projects. Compare responsibilities before comparing totals.
If you are planning a WordPress redesign and want help defining the work before requesting a quote, request a discovery conversation with Grassroots Consulting.
Built in collaboration with ChatGPT.
