A stack of gray papers and a pen on a dark desk, with one blue sheet

Website Development Proposals: How to Read and Compare Them

You sent a brief to several agencies and got back a pile of files: a three-page spreadsheet from one, a polished slide deck with a single number at the end from another, a five-line email from a third. The totals differ several times over, and it's hard to know which one to trust.

This is the second part of our conversation about money. The first covered what drives the cost of a website: type, templates, design, integrations, content, tech stack. This one is practical: how to read a specific website development proposal, what belongs in the estimate, which signals should worry you, and how to compare agency quotes so you choose a partner rather than the shortest "Total" line.

What a website development proposal contains

Every agency formats it differently, but a complete proposal has a recurring set of sections. A missing one isn't always bad news, but it's a reason to ask.

The most revealing section is the first one. If it's full of generic phrases that would fit any client, nobody actually looked at your problem. An estimate without understanding describes someone else's project, even if the numbers look reasonable.

How to read a website cost estimate

The total is the last thing to look at. First, figure out exactly what you're being asked to pay for.

Work and deliverables for each phase

A line that says "Design" tells you nothing. A line that says "Design: two homepage concepts, layouts for eight page types, mobile versions, UI kit" is something you can verify. For every phase, the estimate should make clear what you get at the end: a document, a prototype, layouts, a working section on a staging server.

Look separately for the things that often get lost: migrating content from the old site, setting up goals in Google Analytics, redirects, a content management panel, staff training. If those lines are missing, ask whether they're folded into other items or not included at all.

Hours and roles

If the estimate is broken down by hours, look at the proportions rather than the absolute numbers. Testing gets almost nothing, and the CRM integration is priced like an evening's work? That's either optimism or a future extra invoice. Check whether there's a project manager and an analyst in the estimate: without them, that work lands on you.

Assumptions and exclusions

This is the most underrated section of any proposal. Phrases like "copy and photos provided by the client," "ERP integration via an existing client-side API" or "up to two rounds of revisions per layout" directly change the final number. Two proposals with the same total and different assumptions are two different prices.

Pricing models: fixed price, T&M and phased estimates

The pricing model in a proposal isn't a formality. It decides who answers for an inaccurate estimate and how changes are handled during the project.

Fixed priceT&MPhased
What's fixedThe sum for a defined scopeThe rate and reporting rulesThe price of the next phase, a range for the rest
What to look forDetailed scope and a change processAn hours estimate, report format, capsWhat the first phase delivers
Red flagFixed price for a large project with no spec or prototypeNo estimate, not even a rangeA first phase with no clear deliverable

A fixed price is convenient for budgeting, but it always includes a buffer for uncertainty, and every change goes through a change order. T&M is more flexible but requires transparent reporting and trust. For complex work the phased model is often the most honest: discovery and a prototype at a fixed price first, then an accurate estimate for development.

How to compare web agency proposals

Laying three proposals side by side and picking the middle price is the most common approach and the riskiest one. Here's an order that works better.

  1. Put everything in one table. Rows are the work items: discovery, prototype, design, front end, back end, integrations, content, testing, data migration, analytics, support. Columns are the agencies. Empty cells immediately show who skipped what.
  2. Bring them to the same scope. Ask the agencies with missing rows to estimate the missing work. Only then can the totals be compared.
  3. Compare the assumptions. Who's counting on your copy, who's counting on a ready API, who budgets two rounds of revisions and who budgets five.
  4. Compare timelines against scope. If one agency promises the same scope noticeably faster than the rest, ask how: a bigger team, ready-made components or skipped phases.
  5. Judge their grasp of the problem. Who asked questions before estimating, who suggested ideas of their own, who spotted a risk you hadn't thought of.
  6. Look at similar projects. Not the prettiest ones, but the closest in substance: a catalog, integrations, a customer portal.

Compare scope, assumptions and understanding of the problem, not totals.

After building that table, it usually turns out the cheapest proposal simply describes a smaller site, and the most expensive one includes work you don't need yet. That's a good outcome: now you know what to negotiate about.

Red flags in a proposal

None of the points below is a verdict on its own, but if several add up, treat the proposal with caution.

Questions to ask an agency before signing

A good development agency answers these calmly and specifically. Evasive answers are information too.

Put the answers to these questions in the contract or an appendix to it. A verbal agreement protects neither you nor the agency when, three months later, there's a dispute about what was in scope.

How we prepare proposals at Sphere

We start by getting to know the client's business, so we ask questions before estimating: what's the site's goal, who's the audience, which systems does it need to exchange data with, who's preparing the content. We lay out the estimate along the phases of our process: discovery and structure, design, development and testing, launch and growth.

If the task is complex and the inputs are thin, we say so directly and suggest starting with discovery and a prototype: after that, the development estimate stops being "give or take a factor of two." Sphere, a digital agency, handles custom website development end to end, from research to support. To see the kind of problems we've worked on, visit our web development projects.

FAQ

Can I ask a web agency for a discount after receiving the proposal?

You can, but it's more useful to discuss scope than a percentage. Ask which work could be moved to a second phase or simplified without hurting the result. A discount with no change in scope usually means savings on something invisible: testing, the mobile version or documentation.

Why do proposals from different agencies for the same project differ several times over?

Because every agency fills in what's missing from the brief in its own way: the number of templates, the depth of design, integrations, copy, testing. Until the proposals are brought to the same scope, their totals can't be compared.

Is it normal for an agency not to give an exact price right away?

For a complex project, yes. It's more honest to give a range and suggest starting with a discovery and prototype phase, after which the development estimate becomes precise. What should worry you is the opposite: an exact figure for a large project based on two paragraphs of description.

What must a proposal include?

A restatement of the problem in the agency's own words, the scope by phase with the deliverable of each, a broken-down estimate, a timeline, the pricing model, a list of assumptions and exclusions, revision and warranty terms, the team and similar projects.

Let’s discuss your project
Related reading