Table of contents
- Quick answer: What makes a good web development agency?
- AI agencies vs traditional agencies vs strategic operators in 2026
- Get clear on these 6 things before calling any agency
- How to evaluate an agency portfolio (most founders do this wrong)
- Red flags that mean walk away immediately
- The scenario test that reveals everything
- The 15 questions to ask every agency
- Technology choices: WordPress vs Webflow vs Custom
- Weighted agency scorecard
- Selection process (14 days)
- Contract terms to negotiate before signing
- Reference check questions that reveal the truth
- Warning signs during the engagement
- Related reading
Here’s a story that happens more often than you’d think: A SaaS company paid $65,000 for a beautiful website. The design won awards. The animations were smooth. The copy was clever. But six months after launch, they’d generated exactly three qualified leads from organic traffic.
The problem? The agency was great at design but terrible at strategy. They built what looked good in their portfolio, not what would actually drive business results. No conversion optimization. No technical SEO. No analytics implementation. Just a pretty website that didn’t work.
Most web projects fail not because the design is ugly, but because the agency didn’t understand the business problem they were solving. They focused on aesthetics over outcomes.
This guide is the procurement layer of a website project: how to evaluate agencies, compare proposals, and reduce hiring risk. It is not a full website strategy or redesign blueprint. For the broader planning process, start with Small Business Website Guide 2026: Plan, Build, Launch.
Quick answer: What makes a good web development agency?
A good web development agency can prove these five things before you sign anything:
- Business-first discovery: They ask about your sales process before they talk about design
- Conversion focus: They care about lead quality, not just how pretty the site looks
- Technical competence: They can explain their QA process and show you their code standards
- Realistic planning: Their timeline accounts for your content delays and approval process
- Post-launch support: They have a plan for the first 90 days after launch, not just launch day
Key takeaway: A good agency asks about your sales process before they talk about design. If the first conversation is about aesthetics, not business outcomes, keep looking.
For full project context, read How to Get a Professional Website Built for Your Small Business (2026 Guide).
AI agencies vs traditional agencies vs strategic operators in 2026
| Agency type | How they use AI | Typical cost | What you get |
|---|---|---|---|
| AI speed shop | AI does everything, minimal human oversight | $5,000–$15,000 | Fast but generic, weak strategy |
| Traditional agency | Little to no AI, all manual | $30,000–$80,000 | Solid but slow and expensive |
| Strategic operator | AI for acceleration, humans for strategy | $15,000–$50,000 | Fast execution with strategic depth |
Critical question: “Show me exactly how you use AI in your process.” Specific workflow with named tools and human review steps = strategic operator. Can’t explain it = they’re either lying about using AI or using it recklessly.
Get clear on these 6 things before calling any agency
Most founders waste weeks talking to agencies before they know what they actually need. Resolve these first:
- Success metric — “We need to generate 30 qualified leads per month within 6 months” beats “we want a better website”
- Realistic budget — Don’t play games. If you have $20,000, say so. Agencies can work with constraints but can’t read minds
- Decision maker — If you need board or executive approval, say that upfront. Surprise stakeholders in week 6 kill projects
- Content situation — Do you have copy, photos, and brand guidelines ready? Or is the agency starting from scratch? This changes cost and timeline significantly
- Integrations — CRM, scheduling, payments, e-commerce — list them now, not in week 8 when the developer says “that’s an extra $5,000”
- Timeline — If you need to launch before a trade show in 8 weeks, say that. Hard deadlines require different scoping conversations
How to evaluate an agency portfolio (most founders do this wrong)
Most founders look at portfolio screenshots and think “that looks nice.” That’s admiring design, not evaluating capability.
What to actually test: Pick 3 sites from their portfolio and run them through Google PageSpeed Insights (are they actually fast?), try to convert (are forms working?), and check their organic rankings (is SEO actually working?).
Real example: An agency showed a gorgeous portfolio. We tested 5 sites. Three had broken forms. Two loaded in 8+ seconds. One wasn’t mobile-responsive. Their portfolio was a lie.
Strong portfolio signals:
| What to look for | Strong signal | Weak signal |
|---|---|---|
| Results evidence | ”This site went from 8 to 34 qualified leads/month in 6 months — here’s the data" | "Here’s a beautiful site we built” |
| Process transparency | Can show strategy docs, wireframes, A/B test results | Only shows final designs |
| Client longevity | Sites still running 18+ months after launch, client came back for phase 2 | One-and-done projects |
| Technical explanation | Can explain why they chose the tech stack | ”Whatever you want” |
| Active references | Client will take a reference call | ”We’ve lost touch with them” |
Key takeaway: Test portfolio sites in PageSpeed Insights and try to submit their forms. A beautiful screenshot means nothing if the live site is broken.
Red flags that mean walk away immediately
| Red flag | Why it matters | What to ask |
|---|---|---|
| No discovery phase — straight to mockups | They’re guessing at your needs | ”What discovery do you run before design?” |
| Fixed low price with vague scope | Hidden exclusions = surprise bills later | ”Give me a scope document with explicit exclusions" |
| "Guaranteed rankings” or “guaranteed traffic” | Lying or black-hat tactics | Walk away immediately |
| Two-week launch promise for complex site | They’ll miss by months | ”Show me a detailed timeline with dependencies” |
| No QA process or testing plan | You’ll launch with broken forms and bugs | ”Can I see your QA checklist?” |
| No SEO migration plan on redesign | You’ll lose traffic | ”How do you handle redirects during migration?" |
| "Unlimited revisions” with no process | Timeline balloons, project never ends | ”How many revision rounds are included?” |
| Won’t name who’s doing the work | Outsourcing with no quality control | ”Meet the actual developers before signing” |
The three-strike rule: Three or more of these red flags = don’t invest in a second call.
The scenario test that reveals everything
Send this exact scenario to every agency you’re considering:
“Our current website gets decent traffic but leads are low quality. We need to improve conversion rates in the next 90 days without rebuilding everything from scratch. How would you approach this?”
Strong agency response
“First I’d want to see your analytics — where traffic comes from and where it drops off. Then your lead quality data — what makes a lead good vs. bad for you?
Based on that, I’d optimize your top 3–5 landing pages: stronger copy, clearer CTAs, better trust signals. We’d also look at your forms — are you asking for too much?
First 30 days: optimize key pages and fix technical issues. Days 30–60: test different approaches. Days 60–90: scale what works. We’d track qualified lead rate, not total leads. Should cost $12,000–$18,000 depending on page count.”
Why this is good: Asked questions first. Has a clear process. Focused on outcomes. Gave a realistic price.
Weak agency response
“Yeah, we’d do a full redesign. Your site looks outdated. We’d start with discovery, then design, then development. Probably 12–16 weeks. Our packages start at $35,000.”
Why this is bad: No questions asked. Jumped to an expensive full rebuild. Selling a standard package, not solving your problem.
The 15 questions to ask every agency
On strategy:
- “How do you define success for this project?” (Good: qualified leads, conversions. Bad: launch date or “modern design.”)
- “Show me a similar project with actual results.” (Good: numbers — leads, revenue, conversion rates. Bad: just designs.)
- “Who specifically will work on my project?” (Good: named people with roles. Bad: “our team of experts.”)
On process: 4. “What’s your QA process before launch?” (Good: detailed checklist — browser, mobile, forms, speed, SEO. Bad: “we test everything.”) 5. “How do you handle content? Do you write it or do we?” (Clear breakdown with timeline implications, or the project will stall on your end.) 6. “What happens if we need changes after you start building?” (Good: clear change-order process. Bad: “we’re flexible” = surprise bills.) 7. “How do you prevent our SEO from tanking during redesign?” (Good: redirect strategy, URL mapping, traffic monitoring. Bad: “we’ll handle it.”)
On cost and timeline: 8. “What’s included in your price and what costs extra?” (Good: line-item breakdown with explicit exclusions. Bad: “everything’s included.”) 9. “What’s your typical timeline, and what could delay it?” (Good: realistic with named dependencies. Bad: “6–8 weeks” with no caveats.) 10. “How do you use AI in your process?” (Good: specific tools and workflows with human review. Bad: vague or defensive.)
On accountability: 11. “What happens after launch? What’s included for support?” 12. “Can I talk to 3 past clients?” (Good: immediate yes with contacts. Bad: hesitation.) 13. “What’s your refund or exit policy?” (Good: clear early termination terms. Bad: no refund, you’re locked in.) 14. “How do you handle missed milestones?” (Good: recovery plan protocol. Bad: defensive or blames clients.) 15. “What technology stack will you use, and why?” (Good: explains tradeoffs for your needs. Bad: “whatever you want.”)
Technology choices: WordPress vs Webflow vs Custom
| Platform | Pros | Cons | Best for | Typical cost |
|---|---|---|---|---|
| WordPress | Huge ecosystem, flexible, easy to find developers | Requires ongoing maintenance, security management | Complex sites, e-commerce, custom functionality | $15K–$50K build + $100–$500/month maintenance |
| Webflow | Fast to build, marketing-team friendly, built-in hosting | Higher ongoing costs, smaller developer pool | Marketing sites, portfolios, simpler business sites | $10K–$35K build + $50–$300/month hosting |
| Custom (Next.js, Astro, React) | Maximum performance and flexibility | Most expensive, requires technical resources to maintain | SaaS products, complex web apps, high-traffic sites | $30K–$150K+ build |
Red flag: If an agency only offers one option, they’re selling what they know, not what you need. For detailed pricing by scenario, see How much does a business website cost in 2026?.
Weighted agency scorecard
Score each criterion 1–5, multiply by weight. Any must-have below 3/5 is a material risk.
| Criterion | Priority | Weight | 5/5 looks like |
|---|---|---|---|
| Strategy quality | Must-have | 20% | Discovery tied to commercial outcomes |
| Conversion architecture | Must-have | 20% | Clear buyer-journey page plan and KPI logic |
| Technical QA and launch controls | Must-have | 20% | Explicit standards, tests, and acceptance criteria |
| Delivery governance | Must-have | 15% | Named owners, weekly cadence, escalation process |
| Team transparency | Must-have | 10% | Assigned roles and accountability map |
| Post-launch support model | Must-have | 10% | Stabilization window, optimization rhythm |
| Design quality and brand fit | Nice-to-have | 3% | Strong but context-appropriate visual quality |
| Exact industry familiarity | Nice-to-have | 2% | Useful but not a substitute for process |
Decision rule: Score below 75/100 = poor fit. 75–85 = acceptable, verify weak areas. 85+ = strong fit, check references.
Selection process (14 days)
| Days | Activity |
|---|---|
| 1–3 | Align internally on goals, budget, and success metric |
| 4–8 | Run structured discovery calls with 3–4 agencies using same scenario and questions |
| 9–11 | Score proposals with weighted scorecard, clarify exclusions |
| 12–14 | Reference checks and contract negotiation |
Contract terms to negotiate before signing
| What to negotiate | Why it matters | What to ask for |
|---|---|---|
| Exit clause | You need an escape hatch | ”Terminate after 90 days with 30 days notice and payment for completed work” |
| Scope definition | Prevents surprise charges | Detailed document with explicit inclusions and exclusions in the contract |
| Change order process | Controls scope creep | ”All changes require written estimate and approval before work begins” |
| Payment milestones | Protects against incomplete delivery | 30% deposit / 40% at design approval / 30% at launch. Never 100% upfront. |
| Ownership | You own everything | ”Client owns all code, designs, content, and all account access” |
| QA and acceptance | Defines “done" | "Launch requires completion of QA checklist and client sign-off” |
| Post-launch support | Prevents abandonment | ”Agency provides 30-day stabilization with defined response times” |
Red flags in contracts: 100% upfront, no exit clause, agency retaining code/design ownership, vague scope, automatic renewal clauses.
Reference check questions that reveal the truth
Don’t just ask “would you work with them again?” Ask these:
- “What specific results did you see — leads or revenue, not rankings?”
- “What was the biggest problem during the project, and how did they handle it?”
- “Did they hit their timeline? If not, what caused the delay?”
- “Did the final cost match the initial quote? If not, why?”
- “What would you change if you could do it again?”
- “If you were hiring them again, what would you negotiate differently in the contract?”
Specific answers with numbers and honest assessments of problems = trustworthy reference. “They were great, really professional” = tells you nothing.
Warning signs during the engagement
| Warning sign | Action |
|---|---|
| Missed deadlines with no proactive communication | Escalate immediately, demand written recovery plan with dates |
| Lots of meetings, no shipped work | Require weekly shipped-work log with screenshots |
| Constant scope confusion | Reconfirm scope in writing, document everything |
| QA issues discovered in the last week | Pause launch, demand proper QA completion |
| Can’t see the site until it’s “done” | Demand staging site access immediately |
| Team changes with no heads-up | Require formal handoff and updated contacts |
The 30-day checkpoint: Two or more warning signs in the first 30 days = cut losses early. It does not get better at month 4.
FAQ
How many agencies should we evaluate?
Talk to 3–4. Fewer = weak comparison data. More than 5 = decision fatigue.
Run the same scenario test and score each one with the same weighted matrix — consistency is what makes comparison credible.
Should we prioritize industry experience over process quality?
Process quality matters more. A disciplined agency with strong process can learn your industry in weeks. An agency with industry experience but weak process will still deliver a mediocre site.
Exception: highly regulated industries (healthcare, finance, legal) where compliance is critical.
Is fixed bid better than hourly?
Fixed bid when scope is crystal clear, content is ready, and you want budget certainty. Time and materials when requirements are still evolving or integrations have significant unknowns.
Best approach for most SMBs: Paid fixed-price discovery ($3,000–$8,000) to clarify scope, then fixed-price implementation. This minimizes risk on both sides.
Should we hire offshore or local?
Location matters less than process maturity, communication quality, and accountability. A well-structured offshore team outperforms a local agency with weak process every time.
What matters: Is there a named project manager? What is the communication cadence? How are missed milestones handled?
Is paid discovery worth it?
Almost always yes. Benefits: the agency takes requirements seriously (not just a sales pitch), you get realistic estimates, you can walk away after discovery if it’s not a fit, and you prevent the expensive change orders that a vague initial scope creates.
Discovery that costs $5,000 and prevents a $30,000 mistake has a clear ROI.
What if the agency misses early milestones?
Address it immediately — missed early milestones predict bigger problems. Schedule an urgent call, ask why, demand a written recovery plan with specific dates and owners.
If they miss two milestones with no good explanation and no credible recovery plan, exit. Sunk cost fallacy is expensive.
Related reading
- How to Get a Professional Website Built for Your Small Business (2026 Guide)
- How much does a business website cost in 2026?
- How to choose an SEO agency (red flags to avoid)
Need help evaluating proposals? We review web development proposals for SMBs, score delivery risk, and help you make the right choice without the sales pitch. Request a proposal review →