Two numbers are not a comparison
Most businesses collecting quotes for a website end up with two or three documents that are impossible to compare. Each has a number and a timeline. Neither says the same thing about what is actually being built, so the only difference visible on the page is price, and price becomes the deciding factor by default.
That is not a failure of judgement by the business. It is a failure of the documents. A proposal is supposed to make its own scope legible, and plenty of them are written to avoid exactly that.
What follows is what a proposal has to answer to be worth reading, and what tends to go wrong when it does not.
What is being built, page by page
The single most useful thing a proposal can contain is a list of the pages. Not “a five-page website” — the actual pages, named.
This sounds pedantic until you have watched a project stall over it. A business that sells four services and reads “five pages” reasonably assumes those four services plus a home page. The builder, meanwhile, priced home, about, services, contact, and one more. The four service pages the business was counting on are now a change request.
A named list also exposes something else worth knowing: whether the person quoting understood the business well enough to know what pages it needs. A proposal that lists the same five pages every business gets is telling you what happened in the conversation, which is nothing.
Who writes the words
Content is the most common reason projects stop moving, and the most common thing a proposal leaves unstated.
There are three honest answers, and any of them is fine as long as it is written down. The builder writes it. You write it. Or you supply raw material — service descriptions, notes, an old brochure — and the builder shapes it. What is not fine is silence, because silence resolves into “you write it” at the exact moment you thought the project was nearly finished.
If the proposal says the builder writes the content, it should also say how many rounds of revision that includes and what happens after those.
What happens to the site you already have
If a site exists, it has URLs. Some of those URLs have been linked to, indexed, and printed on things. A new site that changes them without redirecting the old ones sends every one of those to a dead page.
A proposal for a redesign should say explicitly whether URL mapping and redirects are included. It is a real piece of work, it is invisible to the client, and it is the first thing cut from a quote that needs to look cheaper than the one next to it.
The same applies to anything else the current site carries: analytics history, email forwarding, a domain registered somewhere nobody remembers. Ask what is being carried over and what is being left behind.
What you own at the end
At the end of the project, someone owns the domain, the hosting account, the code, the content, and any accounts created along the way. That should be you.
Arrangements exist where it is not — where the site is effectively rented and stops existing if the relationship ends. Those arrangements are not inherently dishonest, and they are sometimes cheaper up front for exactly that reason. They are only a problem when nobody said so. A proposal should state plainly who holds what, and what happens to it if you leave.
What is explicitly not included
A good proposal contains a short, unglamorous list of things it does not cover. Photography. Copywriting for pages beyond the named list. Ongoing maintenance. Third-party licence fees. Content migration from an old blog.
This section is the clearest signal of how a project is going to be run. A proposal that names its own exclusions is written by someone expecting to be held to it. A proposal with no exclusions is not more generous; it has simply moved the argument to later.
How a change in scope is handled
Scope changes on most projects, usually because the business learns something partway through. That is normal and not a problem in itself.
What matters is whether the proposal says what happens when it does — how a change is agreed, how it is priced, and whether it moves the timeline. Without that, every change becomes a negotiation conducted under time pressure by two people who each feel the other is being unreasonable.
The parts a proposal cannot honestly contain
There are things a proposal should not promise, and their absence is a good sign rather than a gap.
It cannot promise rankings. It cannot promise traffic, leads, or revenue figures, because those depend on the market, the offer, and what competitors do next. It cannot promise that the site will be finished by a date that assumes content you have not written yet.
A proposal that guarantees a search position is not describing SEO, and a timeline that does not depend on your input is describing a project where your input is not wanted.
Reading the three you have in front of you
Put them side by side and ask the same six questions of each. Which pages exactly. Who writes the words. What happens to the old URLs. What you own at the end. What is excluded. What happens when scope changes.
Most of the time, one proposal answers all six and costs more, and the difference in price turns out to be the answers. That is the comparison that was hiding behind the two numbers.
If you want a second opinion on proposals you have already received, tell us about the project — including the ones that are not ours.