How to review a web design proposal
The nine things to check in every studio proposal, and the red flags that should make you walk away.
A good web design proposal tells you what you are buying, what it costs, when it will land, and who is doing the work. If any of those four are missing or vague, the proposal is bad. The best ones fit on 4 to 8 pages, price the work either fixed or in a clear range, name the people involved, and are dated with an expiry.
Reviewing a proposal is a 30-minute job if you know what to look for. Most buyers spend two hours getting confused by pretty PDFs. Here is the checklist we would use in your position.
What a proposal is for
A proposal turns your brief into a scoped plan. It is not a contract, but it becomes one when you sign. Anything in the proposal binds the studio to deliver. Anything not in the proposal is out of scope and will cost extra later.
What to check
1. Is the scope specific? Not "a modern marketing website" but "5 unique page designs, CMS for the blog, contact form with CRM sync, launch on Vercel." If you cannot tell what is included from the proposal alone, the studio does not know either.
2. Is the price fixed or in a range? For fixed-scope work, expect a fixed price. For open scopes, expect a range with a ceiling. Be wary of anything that says "we will estimate as we go."
3. Does the timeline have milestones? A good proposal lists dates: kickoff, first designs, first revision, dev handover, staging, launch. A bad proposal just says "8 to 10 weeks."
4. Who is on the project? Names, roles, and rough share of their time. Four senior partners at 10% each is not four senior people. It is 40% of one senior person spread thin.
5. What are the payment terms? Standard is 30/40/30 or 50/50. Anything front-loaded (100% upfront) is a red flag unless you have worked with them before.
6. What does out-of-scope work cost? Every studio hits scope creep. A good proposal has a clear rate for extra work. A bad one does not mention it.
7. What are the assumptions? A serious proposal lists what it assumes about your side: content ready by X date, one round of feedback, decision-maker available for reviews. If assumptions fail, the timeline slides.
8. What happens at handover? Documentation, editor training, code repo access, DNS transfer, three months of light support. If handover is vague, you will be paying to relearn your own site later.
9. Is there an expiry? A proposal without an expiry is one that will be renegotiated in six months when the studio's rates have gone up. Expect 30 to 60 days.
Red flags
- No fixed price and no rate card. They will bill whatever they feel like.
- Vague scope with lots of "and more." Every "and more" costs extra later.
- Named partners on the pitch, nobody named on the delivery. The A-team pitches, the B-team builds.
- Timelines that ignore your calendar. Studios that miss your Christmas break will miss your other constraints too.
- Discount pressure. "This price is only good this week." Real studios do not need to push you to sign.
What to do with a proposal you like
Sign it, but before you do, ask three clarifying questions in writing. The studio's response is the last piece of data you need. Fast, specific answers mean they will run the project well. Slow, vague answers mean the opposite.
What to do with a proposal you do not
Say no in writing, with a reason if you can articulate one. It is the most useful thing you can do for the studio and for yourself. Vague ghosting is what makes the industry harder for everyone.
See also: How to write a website brief, How to choose a web design studio in 2026, Pricing design work in 2026.