How to choose a web agency: 12 questions that expose vague proposals
Ask these before you sign—scope, hosting, SEO ownership, handoff, and maintenance
Pretty proposals hide soft scope. The fastest way to compare agencies is not a feature matrix—it is a short list of questions that force concrete answers about ownership, risk, and what “done” means. If they cannot answer plainly, believe that.
Twelve questions worth asking
Use these in discovery calls. Write the answers down. Compare vendors on the same sheet.
12 questions that expose vague proposals
- What is explicitly out of scope in this quote?
- Who writes and approves content—and what happens if it arrives late?
- Which integrations are included, and which are discovery only?
- Who owns hosting, domains, and DNS after launch?
- Who owns technical SEO and analytics instrumentation?
- How many revision rounds are included, and what triggers a change order?
- What does handoff include: repo access, CMS training, runbooks?
- What is the care plan: response times, updates, monitoring?
- How do you handle accessibility and performance budgets?
- Who is the day-to-day owner on your side—and on ours?
- What does the timeline assume we will deliver by week two?
- Can we see a recent project with similar constraints, not just prettier ones?
What vague proposals sound like
Watch for language that feels reassuring and proves nothing. Specificity is respect.
How to score the answers
You are not hunting for perfect promises. You are hunting for shared reality: named owners, named risks, and a path when something changes.
- 1
Require assumptions in writing
If it is not in the proposal, it is not in the price.
- 2
Separate build from care
Launch cost and monthly ownership should both be visible.
- 3
Test a hard question
Ask what they would cut first if budget drops 20%. Useful partners answer without panic.
- 4
Check references for friction
Ask what went wrong and how it was handled—not only NPS praise.
Score vendors quickly
Fit matters more than brand theater
A famous agency that cannot explain your integrations is worse than a smaller studio that already ships similar work. Match portfolio to constraints, communication style to your team, and care model to your risk tolerance.
Fit checklist
- They ask about content readiness before selling animation
- They can explain trade-offs without a sales fog
- They show how change orders work before you need one
- They offer a structured intake (wizard or brief) instead of vibes
Final thoughts
Choose the partner who makes uncertainty legible. Twelve plain questions beat a sixty-page deck. If you want that conversation with Manweba, bring your constraints—we will price the work, not the adjectives.
Related Articles
How long a website project really takes (and what slows it down)
Realistic timelines by package—and the content, revision, and integration delays that stretch them
What to include in a website brief (so estimates do not explode)
Must-haves, nice-to-haves, and red flags that turn vague ideas into a priced plan
Ready to build something this considered?