Web development agencies: how to hire & what to expect

Cost tracks scope and risk more than “agency brand.” A marketing site or focused landing-page build often lands in the low-to-mid five figures; a redesign with CMS, integrations, and content migration climbs from mid five into six figures; a product rebuild or multi-surface web app can run into six figures over months. Quotes without a written brief are noise — ask for ranges against must-haves, nice-to-haves, and who owns hosting, SEO, and post-launch support. Compare senior hours and delivery assumptions, not the headline number alone.

Fixed bid fits clear, stable scope: known pages, stack, and acceptance criteria. Time-and-materials (or a cap-plus-T&M) fits discovery-heavy work, evolving product backlog, or integrations you have not fully mapped. Prefer fixed when you can freeze requirements; prefer T&M when change is the norm — but insist on a not-to-exceed, a change-order process, and weekly burn visibility. Many engagements start with a short fixed discovery, then price build once unknowns shrink.

Judge evidence, ownership, and approach — not jargon. Ask for 2–3 case studies on a similar stack or problem (CMS, e-commerce, auth, APIs), who will own architecture day to day (name + role), and a one-page technical approach for your constraints. Probe how they handle accessibility, performance budgets, environments, and handoff to your team or ops. A strong agency explains trade-offs in plain language and welcomes a short paid spike or architecture review before a big commit.

Build in-house when web delivery is core to how you compete and you need daily context that compounds over years. Buy an agency when you need speed, specialized skills (CMS, platform migration, accessibility), or surge capacity before you could hire and ramp. Hybrid is common: keep product/brand ownership internal, use an agency for a rebuild or specialty slice, then staff maintainers. Keep repos, domains, analytics, and vendor accounts under your org either way.