How to Evaluate a Web Agency Proposal

You've received a proposal. It looks professional. It has a timeline, a price, and a list of deliverables. Now what?

Most business owners approve proposals based on feel. That's not the right filter. Here's what to actually look at.

Does the Scope Match What You Asked For?

A good proposal should reflect the conversation you had, not a generic template with your name dropped in. Check whether the deliverables match what you actually discussed. Are the number of pages right? Is the functionality you mentioned included? Are there things you discussed that didn't make it in?

If the scope doesn't match the conversation, ask why. Sometimes there's a good reason. Sometimes they weren't listening.

Is the Pricing Explained?

A price is not a quote. A quote explains what the price is attached to. Good proposals break down what the cost includes: design, development, revisions, content setup, testing, launch support.

If you can't tell what you're paying for, ask for it broken out. The answer will tell you whether they've actually scoped the project or they're guessing.

What Happens If Things Change?

Projects change. Clients add things. Timelines shift. A proposal that doesn't address what happens when that occurs was never fully thought through.

Look for: how are additional requests handled? What's the revision policy? Who owns the delay if timelines slip?

Who Will Actually Do the Work?

Some agencies sell with one team and build with another. Some outsource parts of the work without disclosing it. Ask directly: who will be working on this project? Will you have a consistent point of contact? Who do you call if something goes wrong?

What's Not Included?

This is the question most people forget to ask. Copywriting? Photography? Hosting? Ongoing maintenance? SEO setup after launch? Third-party integrations? These often live outside the proposal and show up as additional costs later.

A transparent proposal lists what's excluded as clearly as what's included.

What Happens After Launch?

Launch is not the end. Ask what happens if something breaks in the first 30 days. Is there a support period? Does the agency offer ongoing maintenance, and at what cost? Do you own the code and the content when it's done?

The Simplest Test

Read the proposal out loud. If it sounds like something you'd understand when explaining it to someone else, it's probably clear. If it's full of technical terms you'd have to look up, jargon that sounds important but doesn't say anything, or vague promises about results, slow down.

Good proposals make you feel informed. Not impressed.