Compare website development quotes only after they cover the same pages, features, content and responsibilities after launch. Then check the agency’s work, how you will edit the website and the criteria for accepting the finished project. If one quote includes copywriting and migration while another covers page construction alone, the price difference does not yet tell you which offers better value for your business.
This guide includes a comparison worksheet and a worked example for clarifying missing information. You can use it when choosing an agency or agreeing a new project with an existing supplier.
Which requirements should be the same in every quote?
Send each supplier the same short brief. Explain who the website serves, what visitors should be able to do and who will edit the content. Include the pages, languages, forms and connections to other systems. If you already have a website, provide its address.
A page count alone does not define the scope. Five simple text pages are a different task from a catalogue with filters, bookings or customer accounts. Separate the number of distinct page layouts from the number of entries, such as services, products or articles.
Our website project brief guide can help you prepare this list. Record what you already have: a logo, photographs, copy, domain, hosting and access to the existing website. Identify anything that still needs to be created as a separate task.
How can you compare three quotes in one worksheet?
For each item, record whether it is included, excluded or unclear. Note the page in the proposal or the follow-up email that confirms the answer. A blank field means you have not received an answer; it does not mean the work is included.
Copy the following worksheet into a shared document. In columns A, B and C, enter each supplier’s answer and the page number or email date supporting it.
| Item to check | Quote A | Quote B | Quote C | Confirmation to request |
|---|---|---|---|---|
| Pages and languages | To complete | To complete | To complete | List of pages, layouts and translations. |
| Copy and photographs | To complete | To complete | To complete | Who creates, sources and uploads them; the amount of content. |
| Features and integrations | To complete | To complete | To complete | Tasks, limitations and external services. |
| Content editing | To complete | To complete | To complete | CMS demonstration and training scope. |
| Mobile experience | To complete | To complete | To complete | Agreed devices and tasks to test. |
| SEO and migration | To complete | To complete | To complete | Specific checks, existing URLs and redirect plan. |
| Contact forms | To complete | To complete | To complete | Fields, spam protection and delivery test. |
| Access and licences | To complete | To complete | To complete | Accounts to hand over and applicable licence terms. |
| Maintenance and backups | To complete | To complete | To complete | Support tasks, backups and recovery procedure. |
| Price, schedule and handover | To complete | To complete | To complete | Payments, extras, dependencies and acceptance criteria. |
Avoid counting ticks without considering their importance. If generating enquiries is the main purpose of the website, an unclear form delivery process matters more than an extra animation. Identify essential items first, followed by useful additions and features that can wait.
What does a comparison of different scopes reveal?
Imagine a company needs a bilingual website covering five services, a blog and a contact form. It has an existing website with twenty URLs to preserve. These fictional quotes explain the comparison process; they do not represent real agencies, clients or market prices.
| Item | Quote A | Quote B | Quote C |
|---|---|---|---|
| Content | The client supplies final copy and translations; uploading is included. | Copywriting is included; translation is quoted separately. | Only mentions “content upload”. |
| Existing URLs | An inventory and redirects for twenty URLs are included. | Migration is excluded from the base scope. | Mentions “SEO optimisation” without migration details. |
| CMS and handover | Editing services and blog posts, with a demonstration. | Blog editing; the agency changes service pages. | Does not specify what the client can edit. |
Quote A may suit a company with all its copy ready. Quote B may help when writing is needed, but migration and translation still require clarification. Quote C needs a precise specification first. None is automatically best: ask all three suppliers to cover the same required work before comparing totals.
Record the initial build, recurring costs and potential extras separately. For a broader explanation of those items, see our guide to website development costs and ongoing expenses.
How should you assess an agency’s portfolio and working process?
Open several published projects and complete a task similar to one your customer will perform. On a phone, find a service, open the menu and reach the contact information. Ask what the agency delivered: design, development, content, integrations or maintenance. A screenshot alone does not explain its contribution.
Request an administration demonstration using a test account. Ask the supplier to change a service description, upload a photograph and publish an article. If every small edit requires an agency request, you should understand that before choosing the solution.
You can explore our website portfolio and identify the functions that matter to you. Visual similarity to the site you want is a useful reference, but it cannot replace a description of your requirements.
What should “SEO and testing” mean in a proposal?
Ask for the tasks behind that label. For a new website, these might include page titles and descriptions, clear content structure, indexability checks and an XML sitemap. For a redesign, separately agree an inventory of existing URLs, preservation of useful content and redirects where addresses change. Our website redesign SEO checklist explains these checks in more detail.
Google recommends checking an SEO provider’s experience and working methods and warns that nobody can guarantee a first-place ranking. Ask for deliverables and a measurement approach instead of a promised position.
Agree checks of important pages on a phone, menus and forms, and performance measurements for specified URLs. The report should state what was tested and under which conditions. One unexplained score does not document the quality of an entire website.
Also check visible keyboard focus, clear form labels and readable enlarged text. W3C’s preliminary accessibility checks help identify basic problems, but passing them does not establish that a website is fully accessible.
Who prepares content, and which tasks cost extra?
Assign a responsible person to each task and record when their input is needed. A delivery period means something different if it starts with the deposit rather than receipt of all content. Agree how many revision rounds are included and how extra work is approved.
Request a list of the domain, hosting, plugins, fonts and other paid services, with the person responsible for each account and renewal. Specify the access and documentation you will receive at handover. Address rights to code, content and materials explicitly in the agreement and check the relevant licence terms.
Describe post-launch support through specific tasks. Responding to an issue, resolving it, uploading new copy and adding a feature are different commitments. Record what maintenance includes and how requests outside that scope are estimated.
How do you agree when the website is ready for handover?
Acceptance criteria should be tasks you can verify with the supplier. For example:
- An editor can change and publish a service description through the agreed CMS.
- A visitor on a phone can find the contact page and complete the form.
- A test enquiry reaches the agreed inbox and the visitor sees a clear confirmation.
- Agreed old URLs lead to the appropriate replacement pages.
- The agreed access credentials and operating instructions have been handed over securely.
- A documented backup and recovery procedure is available.
Record any remaining corrections, their owner and the agreed deadline at handover. This keeps the conversation tied to a checkable result instead of different interpretations of “the website is finished”.
How should you make the final choice?
Align the scope, clarify unknown items and see the most important functions demonstrated. Then compare price, schedule, communication and post-launch responsibilities. A useful proposal lets you understand what you will receive and how you will check it.
If you are planning a project, our website development page explains our process and packages. Send the same requirements list you use for comparisons so we can relate the proposal to specific pages, features and responsibilities.
