What a fair website quote should include

A fair website quote breaks the work into clear parts: the scope and deliverables, the timeline and milestones, how revisions and change requests are handled, who owns the site and its accounts, and what support you get after launch. When these parts are written down, you can see exactly what you are paying for and compare quotes on equal terms. When they are missing, the gaps usually reappear later as extra charges or disagreements.

This guide explains what each part of a website quote breakdown should contain and which gaps to look out for. It does not list prices, because they vary by country, provider and scope. If you are comparing quotes for a new website, our website service page explains how we work.

Scope and deliverables in a website quote breakdown

The scope describes what will be built. Deliverables are the specific things you will receive. This is the most important part of any quote, because everything else depends on it.

1. Pages and templates. A list of pages, or at least page types, such as home, services, individual service pages, about, contact and blog. Note which pages share a layout.
2. Design. Whether the design is custom or based on an existing theme, how many key pages will be designed, and in what form you will review them.
3. Features. Each feature named and briefly described, such as contact forms, bookings, payments, customer accounts or a newsletter sign-up.
4. Content. Who writes the text, sources the images and adds content to the site. If the provider moves content from an old site, say how much.
5. Integrations. Connections to other systems, such as a CRM, booking tool or payment gateway, with what each connection does.
6. Search engine basics. Whether page titles, descriptions, redirects from an old site and basic structured data are included.
7. Testing. Which devices and browsers will be tested, and whether speed and accessibility checks are included.
8. Training and documentation. Whether your team will be shown how to update the site, and what written guidance you will receive.

Look for a list of assumptions and exclusions. A quote that says what is not included is usually more trustworthy than one that seems to include everything.

If quotes differ widely, check whether some describe a web application rather than a website, and our comparison of websites and web applications explains the difference.

Timeline and milestones

A clear timeline shows when things happen and what the provider needs from you along the way.

1. Phases. The main stages, such as discovery, design, build, content, testing and launch.
2. Milestones. Points where you review and approve work, such as approving the design before building starts.
3. Your responsibilities. Dates for providing content, feedback and access to accounts. Delays on your side move the timeline, and a good quote says so.
4. Payment schedule. When payments are due, often linked to milestones such as a deposit at the start, a payment at design approval and the balance at launch.
5. Launch date. A target date, with the conditions that must be met to reach it.

Be cautious if a timeline has no milestones or no dependencies on you. Real projects always depend on decisions and content from the client.

For a redesign, compare the milestones with the stages in our guide to the website redesign process.

Revisions and change requests

Most disagreements in website projects come from changes: small ones that add up, or big ones that arrive late. A fair quote explains how both are handled.

Revisions

Revisions are changes to work already delivered, within the agreed scope. For example, adjusting a design after your first review.

• How many rounds are included at each stage, such as design and content.
• What counts as a revision and what counts as new work.
• How feedback should be given, ideally as one consolidated set per round.

Change requests

Change requests add or alter scope, such as a new feature or extra pages.

• How changes are requested and estimated. Ideally in writing, with a cost and time estimate before work starts.
• How they affect the timeline. New work may move the launch date.
• How they are priced. For example, at an agreed rate or as a separate fixed quote.

A clear change process protects both sides. You avoid surprise bills, and the provider avoids unpaid extra work.

Ownership, hosting and access

Ownership terms are easy to overlook when a project starts well, and very hard to fix if it ends badly.

1. Website ownership. The quote or contract should confirm that you own the website, its content and its design once paid for.
2. Code and files. You should be able to receive a full copy of the site's files and database.
3. Domain name. The domain should be registered in your business's name, with your contact details.
4. Hosting. State whether hosting is included, who the host is, whose name the account is in and what it costs after the first period.
5. Licences. List any paid themes, plugins or services, who holds the licences and what they cost to renew.
6. Access. You should have administrator access to the website and the key accounts, even if the provider manages them day to day.
7. Third-party accounts. Analytics, search console, email and payment accounts should belong to your business.

If a provider is reluctant to put these in writing, treat that as a warning sign.

Support after launch

A website needs care after launch. A fair quote explains what happens then.

1. Warranty period. A period after launch during which bugs in the delivered work are fixed at no extra cost. Ask how long it lasts and what it covers.
2. Maintenance. Software and security updates, backups and monitoring, with how often each happens.
3. Content changes. Whether small edits are included, and how larger changes are handled.
4. Response times. How quickly urgent problems, such as the site going down or a form failing, will be handled.
5. Costs. Ongoing support is often a monthly or yearly arrangement. It should be priced separately from the build so you can compare it clearly.
6. Ending the arrangement. What happens if you move to another provider, including handover of files and accounts.

Ongoing costs matter as much as the build cost. Our guide to how much a business website costs explains the running costs to expect.

How to compare quotes fairly

1. Send the same brief to every provider. Otherwise you compare different projects. Our guide on how to write a website brief explains what to include.
2. Put the quotes side by side using the sections in this guide: scope, timeline, revisions, ownership and support.
3. Note what is missing from each quote and ask about it.
4. Ask about assumptions. Two quotes may differ because one provider assumed you would supply all content and the other did not.
5. Compare total cost over time, including hosting, licences and support, not only the build.

Once a provider is chosen, our website launch checklist helps you check the finished site before it goes live.

Summary

• A fair quote lists pages, design, features, content, integrations, testing and training, with assumptions and exclusions.
• It sets out phases, milestones, your responsibilities and a payment schedule.
• It explains included revisions and how change requests are estimated and priced.
• It confirms your ownership of the site, domain, hosting, licences and key accounts.
• It describes warranty, maintenance, response times and ongoing costs separately from the build.

A clear quote is the foundation of a good working relationship with any web developer. If you'd like a detailed quote for your website, you can tell us about your project here.