Two website redesign quotes can cover the same number of pages and still describe very different projects. One might assume you will supply approved copy and images. Another might include research, writing, integrations and moving the old website safely.
A useful budget conversation starts with the work that must happen, not an unsupported price range.
Describe the business problem
Write a short statement explaining why the site needs attention. Perhaps visitors cannot understand the services, staff cannot update product information, or enquiries arrive without enough detail.
Then describe an observable result: customers can find the right service and submit a usable enquiry from a phone. Avoid treating a visual refresh as proof that sales will improve.
If you are still deciding whether to rebuild, our guide to signs a website needs a redesign provides discussion prompts. Separate genuine functional problems from preferences about appearance.
Count the content and connections
Prepare an inventory of existing pages. Mark each one keep, rewrite, merge or remove. A ten-page website needing new photography and technical copy may involve more work than a larger site using approved material.
List every connection: enquiry forms, booking systems, payments, email subscriptions, stock feeds and customer records. For each, identify its owner and what a successful test looks like.
Migration also belongs in the scope. Record old URLs, important downloadable files and anything customers have bookmarked. Ask who will map changed addresses and check the result.
Separate the build from running the website
Request two clearly labelled sections in each quote: delivery work and ongoing services. The second should explain hosting, licences, backups, maintenance, support and content changes.
Ask what happens when a paid licence expires or a supplier relationship ends. Establish who controls the domain and accounts. A low initial fee can be hard to compare when essential responsibilities sit outside the proposal.
For a hypothetical consultancy, a contact form and six approved service pages may be enough for launch. A client portal could be a later project. Splitting them only helps if the first release works independently and the later connection has been considered.
Give suppliers the same brief
Send every supplier the same goals, page inventory, integrations, available assets and preferred timeline. Ask them to identify assumptions, exclusions, review rounds, dependencies and acceptance checks.
Before accepting, work through one customer journey and one staff editing task together. This exposes gaps that a page count misses. Keep a record of who supplies each item and when it is needed.
For website design and development, DonutLabs can help turn that inventory into a practical scope. The aim is a proposal you can compare and a website your team can operate after launch.
