Hiring a web team · 11 Nov 2026 · 7 min read
How to compare website quotes line by line
Two quotes for the same website rarely describe the same work. This method puts them side by side so you compare scope first and totals second.
The short answer
To compare website quotes, put each into one table covering scope, pages, design, content, platform, integrations, testing, launch, training, support and ownership. Quotes for the same site differ because each supplier assumes different things. Ask every supplier the same questions, fill the gaps, and compare what is included before you compare the totals.
Why it is hard to compare website quotes
To compare website quotes fairly, you first have to accept that they are rarely quotes for the same thing. Each supplier reads your request through its own habits. One assumes a ready-made template and another assumes a design from scratch. One includes writing the text, and another expects you to supply it. A total at the bottom hides all of this.
So the job is to turn each quote into the same shape. Once every line has an answer in every column, the differences show up as differences in scope, which you can weigh, instead of as unexplained gaps in the total.
Start by giving everyone the same brief
Quotes differ most when the briefs differ. Write one brief and send it to every supplier, with the same deadline for questions. Say what the site is for, who uses it, which pages and features you expect, who will write the content, which platform you prefer if you have a view, and when you want to launch.
If you are starting a new business and are not sure what must be on the site from day one, the guide to what a startup website needs first helps you separate must-haves from later additions. Share a budget range if you have one, because it lets suppliers propose a scope that fits instead of guessing.
A comparison sheet you can copy
Build a table with one column per supplier and one row per line below. Fill it from the quotes, and mark any row where a quote says nothing. Those blanks are your questions.
| Line to compare | What to look for | Why it changes the total |
|---|---|---|
| Scope and pages | A list of pages or page types, rather than a page count alone | More pages and page types mean more design, build and testing |
| Design | Template or custom, number of concepts, rounds of changes | Custom design takes more time than adapting a template |
| Content | Who writes the text, finds the images and loads everything in | If one quote includes writing and another does not, the totals cannot be compared |
| Platform and CMS | Which system, why, and who holds the licence | It affects cost, editing and your options later |
| Features and integrations | Forms, booking, payments and other tools, each named | Each integration adds build and test time |
| Hosting and domain | Who buys and owns them, and what hosting is included | Ongoing cost and control depend on it |
| Testing | Which devices and browsers, and which checks | Weak testing shows up after launch |
| SEO and accessibility set-up | What exactly is included | SEO can mean anything from page titles to a full structure plan |
| Launch | Redirects, backups, final checks and who does go-live | Missed steps can lose traffic |
| Training and handover | A session, written guides, documentation | It decides if you can run the site yourself |
| Support after launch | What is covered, for how long and how to reach someone | It defines who helps when something breaks |
| Ownership | Who owns design files, code and accounts on completion | It decides if you can move the site |
| Payment and changes | Payment stages and the process for extra requests | It prevents disputes |
| Timeline | Dates, and what the supplier needs from you and when | Late content is a common cause of delay |
The platform row deserves its own conversation. The guide to what a CMS is and how to choose one helps you judge the system each supplier proposes and ask why they chose it.
Why quotes for the same site differ
- Different assumptions about scope. One supplier reads a page count as that many templates, and another reads it as that many separate designs.
- Template or custom design. Adapting a template and designing from scratch are different amounts of work.
- Content. Who writes the text, sources the images and enters it all is often left unsaid. The guide to website copywriting and who writes what shows the usual split.
- Platform. Different systems carry different set-up and upkeep.
- Process and team. The number of people, their experience and the depth of testing all vary.
- Revisions. Rounds of changes, and what counts as a change, are defined differently.
- Hosting and extras. Licences, plugins and stock images may or may not be included.
- Support. A quote with ongoing care is a different product from one without.
- Risk allowance. A careful supplier adds time for the things that often go wrong.
A higher quote can include things you need that a lower one leaves out. The reverse also happens, and a higher quote may include extras you do not need. The total alone cannot tell you which. The sheet can.
What a good proposal includes
- The goals the site must meet, in the supplier's words, so you can see they understood the brief.
- A list of deliverables, page by page or template by template.
- Assumptions, such as who supplies content and by when.
- Exclusions: what is not included.
- The process, with stages, milestones and dates.
- What the supplier needs from you at each stage.
- Rounds of changes and how extra work is handled.
- Testing and launch steps.
- Training, handover and support.
- Ownership of code, design files and accounts.
- The payment schedule.
- Named contacts.
Exclusions are the most useful item and the one most often missing. A proposal that says what is not included was usually written by someone who has thought the project through.
Phrases that need a follow-up question
| Phrase in a quote | What to ask |
|---|---|
| Fully responsive | Which devices and browsers will be tested, and by whom? |
| SEO friendly | Which tasks does that cover: page titles, structure, redirects, speed? |
| CMS included | Which system, who holds the licence and who hosts it? |
| Unlimited revisions | Is there a limit in practice, such as a time window or an approval stage? |
| Custom design | Designed from scratch, or an adapted template? |
| Ongoing support | What does it cover, how do I report a problem and what happens outside working hours? |
| Content migration | Which pages are moved, and who checks them afterwards? |
| Maintenance | Does it include updates, backups and monitoring? |
Domain, hosting and ownership
Ask where the domain and hosting will be registered, and in whose name. The business should be the registered owner of its domain, and hosting should either be in your name or come with clear terms for moving the site away. The guide to domain name vs website vs hosting explains the three and why ownership matters.
At the end of the project you should receive the files, a copy of the database, the design files and the logins you need, or a written statement of how you will get them.
Support after launch, and the day the site goes down
A quote that stops at launch leaves one question open, which is who you call on the first bad day. Ask what support is included, how long it lasts, how to reach someone and what happens outside working hours. Ask whether a fault caused by the supplier's own work is fixed free of charge, and how other fixes are handled. The guide to what to do when your website goes down sets out the steps a support arrangement has to cover, so you can test each supplier's answer against it.
How to score and decide
Once the sheet is filled in, weigh what matters to you. List the lines that count most, such as fit to your brief, clarity of scope, ownership terms, support, evidence of similar work and how well the supplier communicated. Give each supplier a score from one to five on each line and see where they cluster. Treat the total as one factor among several.
Hold a short call with each supplier and ask them all the same questions. Notice how clearly they answer. Ask to see relevant examples of past work and, if you can, to speak to a past client. If the lowest and highest quotes differ widely, do not average them. Ask both to explain what is behind the gap.
Red flags
- No written scope, or a scope of a single line.
- No assumptions or exclusions listed.
- A refusal to say which platform will be used.
- No statement about who owns the finished work.
- A promise of a particular search ranking. Outside the search engine nobody controls rankings, so treat such a promise with caution.
- Pressure to sign quickly.
- Reluctance to show examples or to let you speak to a past client.
- A quote that cannot be explained line by line.
After you choose
Ask the chosen supplier to update the proposal with everything you agreed during the questions, and turn it into a contract. Do not rely on a trail of emails. If you would like a written proposal from Liftup Technologies to set beside others, the website development page describes the services. Keep your comparison sheet afterwards, because it becomes your checklist at handover.
Related guides
- How to write a website brief for a developer
- How long does it take to build a website
- Website redesign seo checklist
- Web design vs ui design vs ux design
Questions and answers
How do I compare two website quotes?
Put both into one table with a row for each line: scope, design, content, platform, integrations, hosting, testing, launch, training, support and ownership. Mark every row a quote leaves blank, ask the supplier to fill it, and compare what is included before you compare totals.
What should a good website proposal include?
It should include the goals, a list of deliverables, assumptions, exclusions, stages and dates, what you must supply, rounds of changes, testing and launch steps, training and support, ownership of the work and the payment schedule. Exclusions are the item most often missing.
Why do quotes for the same website differ?
Suppliers assume different things: template or custom design, who writes the content, which platform, how much testing, how many rounds of changes, and whether support is included. The totals differ because the work differs, which is why a line-by-line comparison matters.
Should I choose the lowest quote?
Not on price alone. A total only means something when the same work is included. A low quote that leaves out content, testing or support may cost more later, and a high one may include things you do not need. Fill in the comparison sheet before deciding.
How many quotes should I get?
Enough to see how scopes differ, but few enough to compare properly. A few well-briefed suppliers usually teach you more than a long list of vague replies. The quality of the comparison matters more than the count.
Can I ask suppliers to revise their quotes?
Yes. Asking each to quote against the same written scope is the fair way to compare. Suppliers expect questions and revisions, and how they respond tells you something about working with them.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.