Most website proposals look clean and professional, and many are still unsound.
When you’re staring down a 5- or 6-figure web project, a good proposal should give you confidence. But agencies hand many founders and teams polished PDFs that use vague language and inflated timelines. The pricing doesn’t match the work.
Five red flags show up most often in the agency proposals we see. Each flag below pairs a line from a proposal with what it means and what to ask.
1. Vague deliverables
The proposal says:
“Modern, responsive website with intuitive UX and compelling visuals.”
This is filler. There’s no accountability in those words. If the scope doesn’t define which pages it includes or what content the agency creates, you’re flying blind. The same goes for scope that never says what success looks like. Vague language lets agencies promise the world and walk back scope later.
Questions to ask:
- Can you list every page and deliverable in this project?
- Who is responsible for each?
- What isn’t included?
2. Front-loaded strategy, light execution
The proposal says:
“4-week discovery phase with stakeholder interviews and user persona development.”
We often see overweight strategy phases that pad early hours to justify cost, or that signal an agency that doesn’t know how to move fast with clarity. The phase might also mean the people doing strategy won’t be around for design or dev.
Questions to ask:
- Who is running strategy and are they involved through launch?
- Will any of this duplicate internal work we’ve already done?
- Can we streamline or skip phases if we’re already clear on goals?
3. Generic timelines
The proposal says:
“8 to 12 weeks, depending on feedback cycles and scheduling.”
They haven’t thought through your constraints. Or they’re leaving room to blame you for delays. Real timelines set stages against real workstreams and responsibilities. Generic ones let scope balloon and deadlines slip without anyone accountable.
Questions to ask:
- What does week-by-week look like?
- Who is responsible for approvals and content?
- What happens if we miss a deadline on our side?
4. Oversized team roster
The proposal says:
“Your team: Creative Director, UX Strategist, UI Designer, Project Manager, Front-End Dev, QA Lead.”
A long list of titles says nothing about value. We often see junior people doing the work while senior names are there for show. More people can add overhead and confusion, and slow communication.
Questions to ask:
- Who is doing the work?
- Will I speak to the designer/developer directly?
- How many projects is this team handling right now?
5. No risk framing
The proposal says:
“We’ve launched dozens of sites for clients you’ll recognize.”
They’re selling on logos and past wins without proving how they’ll protect you. A good partner tells you what could go wrong and how they’ll prevent it.
Questions to ask:
- What are the most common risks you see on projects like this?
- How do you ensure we don’t miss our launch goal?
- When things go sideways, how do you respond?
Final thought
A proposal shows how an agency works and communicates under pressure. If it isn’t clear or specific, the build won’t be either. If it names no owner, nobody will own the work later.
