Two website design quotes can look very different even when both promise a business website. One may include copywriting, content entry and testing; another may cover only the design and setup. The useful comparison is the work and responsibility each quote includes. This checklist helps you ask clearer questions before committing.
Give every designer the same brief
Write down the purpose of the site, the pages you expect, the features you need and what you can supply yourself. A five-page information site and a booking website are different projects. If each designer receives a different description, the prices will be difficult to compare fairly.
List the deliverables in plain language. Instead of asking for an advanced contact system, explain whether you need a basic enquiry form, file uploads, appointment selection or integration with another business tool. Our small business website checklist can help you prepare that brief.
Check what happens to your content
Ask who writes the service descriptions and whether image sourcing, editing and uploading are included. Find out how many pages will be populated before launch. A finished layout with placeholder text is different from a site ready for customers to use.
For an existing website, ask whether the designer will review and move current content. If addresses change, the proposal should explain how important old URLs will be handled. Content migration can take substantial work, especially when pages contain outdated information or files that need replacing.
Separate the build price from ongoing costs
Request a list of recurring items: hosting, domain renewal, paid themes, plugin licences and any support agreement. Clarify which accounts belong to you and which are managed by the provider. A low initial quote can become less attractive if essential recurring costs are unclear.
Ask what happens if you change providers. Will you receive the website files, database and appropriate account access? Are any features tied to licences that stop working or lose updates when the agreement ends? The answer may be reasonable, but it should be written down before you agree.
Define revisions, testing and handover
Check how feedback is collected, how many revision rounds are included and what counts as a change in scope. Ask what the designer needs from you and how delayed content affects the schedule. A useful timeline identifies dependencies rather than simply promising a launch date.
The quote should also explain testing. Look for checks of mobile layouts, navigation and the main enquiry or purchase journey. Agree what handover includes: access, basic editing guidance, a list of paid tools and instructions for getting support.
Know the boundary between fixes and maintenance
Ask how faults discovered after launch are handled and how that differs from new requests. Changing a service description, adding a feature and repairing an implementation error are different jobs. Review our website maintenance checklist to identify ongoing tasks you may want covered.
Choose the proposal that makes the scope, responsibilities and ongoing commitments clear. Vosweb agrees the platform, pages, features and scope before building. View our design and care services or discuss a website brief.