How to Choose a Web Development Agency (Without Getting Burned)
How to choose a web development agency without getting burned — vetting, proposals, red flags, contract terms, and the 20 questions you must ask before signing.
Choosing a web development agency is high-stakes. The right one becomes a long-term partner. The wrong one costs you 6 months and $50,000 with nothing to show for it. We've been on both sides — we've hired agencies, and we've been hired by brands. This is the playbook we wish every client had when they came to us.
01Decide: agency, freelancer, or in-house
Three options, each with a clear use case. Agency: full team, fixed-scope proposals, fastest path to a working product. Best for 0→1 builds, complex projects, mid-to-large budgets ($5K–$250K). Freelancer: single point of contact, no backup, no accountability. Best for small tweaks, ongoing maintenance, budgets under $5K. In-house: full context, expensive ($200K+/year per engineer in the US), best for long-term core IP. Best for Series A+ brands with sustained build needs. Most brands start with an agency, transition to in-house at Series A, and use freelancers for ongoing tweaks.
02Vetting: the 20 questions
Before signing, ask these 20 questions. (1) Show me 3 projects you built in the last 12 months — and the metrics before/after. (2) Who specifically will work on my project — and what are their LinkedIn profiles? (3) Can I talk to 2 of your recent clients? (4) What's your fixed-scope proposal process? (5) What happens if scope changes mid-project? (6) What's your typical timeline for a project like mine? (7) What's your communication cadence — Slack, Loom, weekly calls? (8) Do you sign NDAs and IP assignment? (9) What's your post-launch support and warranty? (10) Who owns the code, design files, and intellectual property? (11) What does success look like — and what does failure look like? (12) What tools do you use for project management? (13) How do you handle scope creep? (14) What's your revision process? (15) Who handles the design — in-house or contracted? (16) How do you handle feedback rounds? (17) What's your policy on subcontractors? (18) What happens if the project is late? (19) What's your refund policy? (20) How do you measure success post-launch? If they can't answer these clearly and quickly, walk away.
03Reading the proposal
A good proposal has five sections. (1) Goals and success metrics — clear, measurable, time-bound. (2) Scope of work — explicit list of deliverables, with what's in and what's out. (3) Timeline — milestones, dates, dependencies, and what triggers delays. (4) Pricing — fixed total, with payment schedule tied to milestones. (5) Terms and conditions — IP, NDA, warranty, post-launch support. A bad proposal is vague on goals, vague on scope, has no timeline, has hourly rates instead of fixed pricing, and is full of legal boilerplate. The proposal is the contract; if it's vague, the engagement will be vague.
04Contract terms that matter
Five contract terms to negotiate. (1) IP assignment — you own everything on final payment. Make this explicit. (2) NDA — mutual, before any confidential discussions. (3) Payment schedule — typically 30% upfront, 30% at midpoint, 40% on launch. Never pay 100% upfront. (4) Warranty — minimum 30 days post-launch bug-fix warranty. We offer 90 days. (5) Post-launch support — what's included, what's extra, what's the hourly rate. Other terms: kill fee (what you pay if you cancel), late delivery penalty, change order process, governing law. Get a lawyer to review if the contract is over $25K.
05Red flags
Seven red flags. (1) No portfolio or portfolio is all stock images. (2) Won't share client references. (3) Vague proposal with no fixed scope. (4) Long contracts with cancellation fees. (5) Outsources to anonymous contractors (most 'agencies' are really Upwork resellers). (6) 'We'll figure out the details later' — agencies that don't ask detailed questions are not the right fit. (7) Bad-mouths previous clients or competitors. Trust your gut. If something feels off, it usually is.
06What success looks like
A successful agency engagement has three signals. (1) Process — clear milestones, predictable cadence, no surprises. (2) Communication — Slack/Loom updates, weekly demos, fast response to questions. (3) Outcomes — they hit the metrics you agreed on (leads, conversions, ranking, AOV). The best agencies will tell you when an idea won't work, will push back on bad decisions, and will be your long-term partner, not just a vendor. The relationship matters as much as the work.
Frequently asked questions
Agency — quick answers
- 01How do I choose a web development agency?
- Vet agencies on five criteria: portfolio (real, recent, relevant work), process (fixed-scope proposals, written briefs, clear milestones), team (who specifically will work on your project), post-launch support (warranty, ongoing maintenance, growth services), and cultural fit (communication style, values, working hours). Get 2–3 proposals and compare.
- 02How much should I pay a web development agency?
- Marketing site: $1,200–$25,000. Shopify store: $5,000–$30,000. Custom web app: $25,000–$100,000. SaaS MVP: $25,000–$150,000. Hourly rates: $50–$400. Get 2–3 proposals and negotiate the rate, not the scope. Avoid T&M for large projects — use fixed-price with clear deliverables.
- 03What questions should I ask a web agency?
- The 20 essential questions are: portfolio, team, client references, proposal process, scope changes, timeline, communication, NDA/IP, warranty, ownership, success metrics, project management, scope creep, revisions, design handling, feedback rounds, subcontractors, late delivery, refund policy, and post-launch success measurement. If they can't answer these clearly, walk away.
- 04Should I hire an agency or freelancer?
- Hire an agency for 0→1 builds, complex projects, and budgets over $5K. Hire a freelancer for small tweaks, ongoing maintenance, and budgets under $5K. Hire in-house for sustained build needs at Series A+. Most brands start with an agency, transition to in-house at Series A, and use freelancers for ongoing tweaks.
- 05What are red flags in a web agency?
- Red flags: no portfolio or stock-image portfolio, won't share client references, vague proposal, long contracts with cancellation fees, outsources to anonymous contractors, 'we'll figure out the details later,' bad-mouths previous clients or competitors. Trust your gut. If something feels off, it usually is.