Compare the website you will receive, as well as the price
A redesign quote should show what will change, what remains, what moves and what you receive at completion. Without that detail, two prices may describe different projects.
This guide assumes you have decided to renew the website. If that decision is open, first compare a focused fix, partial renewal and a rebuild. Understanding the scope needed helps assess proposals.
Write a short description of the intended result: what visitors need to do on the new website and what your team needs to manage. “Update the design” may explain the initial motivation without describing the complete project.
A checklist for reviewing redesign scope
Use this worksheet across the proposals you compare. Projects do not need every item; identify what applies and make unresolved details visible.
| Project area | Define | Evidence of completed work |
|---|---|---|
| Design and pages | Page types and required variations. | Reviewed designs and pages applied to intended cases. |
| Content and languages | What stays, is rewritten, translated or created, and who supplies it. | Loaded and reviewed content in included languages. |
| Functions | Enquiries, search, catalogue, checkout or booking journeys. | Tests of those journeys and their outcomes. |
| Data and connections | Information moving and systems connecting. | Checked data and tested connections. |
| Transition | Addresses, launch, measurement and owners. | A change plan and pre- and post-launch checks. |
| Accounts and documentation | Access your team needs to continue. | Tested access, documentation and training where included. |
| Follow-up support | Duration, channel and work covered after delivery. | Clear terms for reporting and handling issues. |
“SEO included” or “complete website” needs to become specific tasks and deliverables. The quote need not become a technical manual, but it should explain included work and information missing from the estimate.
Establish who prepares content and how it will be loaded
Check what the proposed page count means. A service page, product category and product page may need different designs, data and editing arrangements. Ask how existing variations will be handled too.
Separate the tasks: deciding what to keep, writing, translating, sourcing images, preparing documents and loading them into the system. “Content migration” does not establish whether reviewing or rewriting content is included.
Identify who supplies each material and how it will be reviewed before launch. Record how missing copy or images affect planning, so last-minute decisions do not alter delivery without assessment.
Review what needs to keep working through the change
List functions that must be retained: forms and their recipients, search, products, orders, bookings, private access or connections with other systems. Include existing or planned needs; features do not need adding to justify the project.
For data migration, define which information moves, its date and how it will be checked. Where new data arrives during preparation, plan how it reaches the final version. Our provider handover worksheet helps organise owners and dependencies.
If addresses change, define what happens to old pages. Our migration preparation guide covers that work. Keeping useful access routes and reviewing indexing are concrete tasks, separate from promising unchanged Google rankings.
Separate initial price, recurring costs and additional work
Compare the amount, applicable taxes, payment terms and items dependent on missing information. Identify hosting, domains, licences and other services that renew afterwards.
- Which third-party costs are included and which are separate?
- Which account contracts each service and who receives renewal notices?
- Which design or content review rounds are included?
- How will a new function arising during the work be estimated and approved?
- Which conditions may change timing or estimates?
No single price range makes every redesign comparable without its scope. A cheaper proposal may cover less work; another may add tasks you do not need. The worksheet makes those differences understandable before deciding.
An example: two proposals to renew a catalogue
Fictional comparison without prices or results attributed to clients or providers.
A business wants a better catalogue presentation and easier product enquiries. One proposal includes design and loading content the business supplies. Another also includes reviewing product data, moving it, preparing search and checking enquiry delivery.
Before comparing amounts, the business needs to decide which tasks its team will perform and which to commission. It may combine the first proposal with internal work or assess the second as a broader scope.
This does not establish which option is better. It makes the tasks visible so the business can check whether each will deliver the website it needs.
Agree how delivery will be reviewed before launch
Prepare a list of pages and journeys to review on phones and computers with the team. Include essential functions and the administration tasks you will use afterwards. Record outcomes and open items; an approved design does not establish that forms deliver messages or the catalogue can be updated.
Include ease of use: people completing a form should understand each field and how to correct errors. The W3C forms tutorial explains labels, instructions and notifications. These checks help review the experience as well as visual appearance.
Identify who authorises launch, who checks the change and what follow-up support is available. If estimating a function or connection needs prior investigation, define that delivery before commissioning implementation. For a smaller improvement, use our optimisation quote guide.
Nodo91 can help you understand the website’s condition and assess technical aspects of a proposal. Tell us about the renewal you are preparing and we can discuss a suitable review. Assessment and implementation each have their own scope and quote.