Lorixen.
EN

How to Compare Three Web Development Quotes Fairly

Short answer: Quotes look different because each provider prices a different project. To compare them fairly, rebuild every quote on the same list of deliverables, then add the exclusions, ongoing costs and ownership terms that vendors often leave out. Ask all three the same follow-up questions in writing, and score the assumptions behind each number, not only the total. The quote that looks cheapest is often the one that has left the most work out, so compare what you will actually receive.

Why the totals do not match

Three providers can quote $3,000, $9,000 and $18,000 for what looks like the same website, and all three can be reasonable. The difference usually sits in the scope. One includes content entry, one includes a year of hosting, one assumes you will supply every image and one prices testing on only two browsers. The number tells you almost nothing until the work is described in the same terms.

Imagine a bicycle repair shop in Galway (called Spoke and Chain here, a made-up name) collecting three quotes for a site with a service booking form. The first is $2,800 and covers a template with five pages. The second is $6,500 and covers a custom design, a booking system and a training session. The third is $11,000 and includes the content writing, photography and a support plan. None of them is wrong. They are simply three different projects.

Step one: normalise the scope

Create one sheet with a row for each deliverable you need. Keep the rows concrete: number of pages, number of forms, payment method, email notifications, user accounts, content migration and staff training. Then fill in each quote against those rows. If a vendor does not mention a row, write "not stated" rather than assuming it is included.

Once the sheet is complete, you will see the real gaps. A quote that appears cheaper may simply be missing four rows, which you would have to buy later from someone else.

Step two: check the exclusions

Exclusions are where fair comparisons go wrong. Look for lines such as "content not included", "stock images billed separately", "testing on a single device" or "domain and hosting at the client's cost". Each exclusion is a cost you still have to find, so give it a value in your sheet, even if the figure is an estimate.

Ask each vendor to list every exclusion in writing. A vendor who says "none" should still confirm what the project does not include, because exclusions are where most misunderstandings begin.

Step three: add the ongoing costs

The first build is only part of the cost over a three-year period. Add a row for each recurring item: hosting, domain renewal, software licences, plugin or template fees, email sending, security updates and support. Use the same period for every quote, such as the first 36 months, and state any price assumptions in the sheet.

A simple test helps. If one provider includes hosting for the first year and another does not, add the hosting cost to the second quote so both totals cover the same year.

Step four: ask the same follow-up questions

Send all three providers the same short list. Keep the questions identical so the answers are comparable.

  1. Who owns the source code, design files and accounts when the project ends?
  2. How many revision rounds are included before go-live?
  3. What is the process for a change request after launch, and how is it priced?
  4. Which browsers, phones and tablets will you test before delivery?
  5. What is the response time for a fault during the first 60 days?
  6. Which parts of the project depend on you supplying content, and by when?

Ask for the answers in writing and within a set number of days. Vendors who answer quickly and in detail are often the ones who will deliver on time.

Step five: score the assumptions

Every quote rests on assumptions about timing, content, feedback and scope. A vendor that assumes you will reply to feedback within two days has built a schedule on that promise. Give each assumption a simple rating: realistic, optimistic or unclear. Then count how many unclear assumptions each quote contains.

A useful final score combines three parts: the normalised price, the cost of exclusions, and an allowance for unclear assumptions. You do not need a precise formula. The point is to make the reasoning visible, so you can explain your decision to a partner or board. Keep the sheet and your scoring notes together in one file. When a vendor sends a revised quote later, you can update the matching row and see at once whether the gap has moved. Date each revision in the sheet, so the history of the bids stays visible.

A simple comparison sheet

Row Vendor A Vendor B Vendor C
Deliverables (pages, forms, features)
Exclusions with estimated cost
Ownership of code and accounts
Hosting and domain for 36 months
Support length and response time
Revision rounds and change pricing
Unclear assumptions (count)

What to do when the numbers still disagree

If the normalised quotes are still far apart, the cause is usually one of two things. Either the brief was too loose, so each vendor filled gaps differently, or one vendor has misunderstood the work. Rewrite the brief with the rows from your sheet, send it back to all three and compare again. This takes a few days, but it protects you from a decision based on mismatched projects.

FAQ

Should I always choose the middle quote?

No. The middle quote is only a good choice if its scope matches your needs and its assumptions are realistic. Use the sheet to decide, not the position of the number.

Can I ask a vendor to revise a quote?

Yes. Vendors expect questions and often update a quote when the scope is clearer. Ask them to resend the full revised quote rather than a note with changes.

What if a vendor refuses to answer the follow-up questions?

Treat that as information. A provider who will not put ownership, testing and support in writing may find the same answers difficult to deliver later.

A live quote is easier to judge with a second pair of eyes, so the enquiry form is a good place to begin.

Sources

WhatsAppBook a call