Quotes for a business website: how to compare offers that are actually different

Three quotes for a business website almost always come back with three very different numbers. The difference is rarely the price of the same thing: it's that the three offers describe three different jobs. Comparing them by total means choosing the cheapest among proposals that don't do the same things.

This guide puts them on the same footing. It doesn't contain reference prices — they depend too much on scope to be useful — but the questions that make the answers comparable.

First step: ask everyone for the same thing

If the quote request is generic (“I'd like a quote for a website”), every vendor imagines a different job, and they're each right to. Before comparing, it's worth putting four things in writing and sending them to everyone.

• The goal: what should happen because of the website. “Receive qualified quote requests” leads to a different project than “present the company.”
• The number of pages, and which ones. You don't need the final sitemap, just the order of magnitude and any special pages (a configurator, a private area, a catalog).
• The languages, if more than one. Multilingual isn't a checkbox: it changes content, structure, and management.
• Who supplies the content. Copy, photos, and translations are a cost item. If it isn't stated who produces them, every offer will assume a different answer.

The line items that should be kept separate

A single total hides the differences. Asking for the quote to be broken down lets you see where the vendors think differently — which is the information you need.

Setup costs and recurring costs don't add up the same way

An offer that's more expensive at setup can cost less over three years, and vice versa. To compare them, you need to separate what you pay once from what you pay repeatedly, and look at a realistic time frame — three years is a good measure for a business website.

• What's included in maintenance: security updates, bug fixes, small content changes? These are three different things and are often called by the same name.
• What's excluded. This is the most informative part of the quote, and the part that's often missing: ask for it explicitly.
• How much a change outside the contract costs, and with what response times.
• What happens if you change vendor: what you take with you, and in what form.

What you're handed over, and how you know it's finished

A quote should say not only what gets done, but what ends up in your hands and under what conditions the work counts as complete. Without written criteria, delivery turns into a negotiation.

• The list of what gets delivered: the published website, the admin credentials, the source files if included, the documentation.
• Who ends up owning the domain and hosting, and in whose name they're registered. This is the point that causes the most problems when you change vendor.
• The acceptance criteria: what checks are done before it's called finished — forms working on phone and computer, speed, behavior in the languages covered.
• The timeline, and what happens if it slips for reasons on your side (late content) or theirs.

A comparison matrix

Put the three offers in columns and the items above in rows, and the differences become readable. An example of what the comparison looks like when the scope is the same — the values are illustrative, meant to show the format, not to suggest prices.

Read this way, the offer with the lowest total can turn out to be the most expensive: if the copy is your responsibility and the website can't be edited without technical work, the real cost includes someone to write it and a vendor to call for every update.

When the lowest total really is the right choice

It happens, and it's worth saying: when the scope is small and clear, when you already have the content, when no integrations are needed, and when the website isn't the main channel your customers come from. In that case, paying more for capacity you won't use doesn't make you more credible.

What this guide doesn't cover

This is about buying a website. Choosing and pricing a business management system follows different logic — the weight is on managing it over time more than on building it — and is covered separately.