How to Choose a Web Development Agency: 12-Point Checklist

Why the Wrong Agency Costs You 6-12 Months

A bad web development agency doesn't usually fail loudly. It fails slowly — a launch date that quietly slips by a month, then another month, a build that technically works but breaks the moment real users with real browsers and real devices touch it, or a site that launches on time but is so difficult to maintain that every future change becomes its own small crisis.

By the time the problems are undeniable, you're usually 4-6 months into a relationship, have already paid a meaningful portion of the budget, and face a genuinely difficult choice: keep pushing forward with a team that's already shown you who they are, or start over with someone new and absorb the sunk cost. Either path typically adds another 6-12 months before you're back to where you thought you'd already be — and that's before accounting for the time spent finding, vetting, and onboarding a replacement team from scratch.

There's also an internal cost that's easy to underestimate going in: the credibility of whoever championed the hiring decision. A project that visibly stalls or underdelivers doesn't just cost the business time and money — it makes the next request for budget or buy-in from that same person noticeably harder to get approved, regardless of how reasonable the underlying decision-making actually was. Choosing well the first time protects more than the project itself.

This is exactly why the evaluation process before you sign matters more than most buyers treat it. A thorough discovery and vetting process that takes an extra two or three weeks is a rounding error compared to the months you'll lose if you skip it and pick wrong.

There's also a compounding effect that most first-time buyers underestimate. A delayed launch doesn't just push back your go-live date — it pushes back every downstream plan that was built around that date: a marketing campaign timed to coincide with launch, a fundraising milestone tied to a working product demo, a sales team waiting on new collateral that depends on the new site. By the time the website itself is six months late, the actual business cost is usually several multiples larger than the development invoice alone would suggest.

The good news is that almost every failure mode we've seen play out with a bad agency was visible in hindsight during the evaluation phase, if someone had known what to look for. That's the entire purpose of the checklist below — not to make hiring an agency feel adversarial, but to replace gut feeling with a specific, repeatable process that surfaces the same information a six-month bad experience would eventually surface, except before you've signed anything.

The 12-Point Evaluation Checklist

This is the exact list we'd want a prospective client to run any agency through — including us. If an agency can't answer most of these clearly and specifically, that's information, not an accident.

Red Flags to Avoid

Some warning signs are subtle. Others are obvious once you know to look for them — and most prospective clients only learn to recognize them after getting burned once.

• A quote that's dramatically lower than every other agency you've talked to, with no clear explanation for the gap
• Reluctance to put a senior team member on the actual kickoff call — you only meet the people who'll do the work after signing
• No questions about your business, your customers, or your goals before jumping straight to a proposal
• A portfolio full of screenshots with no live links, or links that no longer work
• Pressure to sign quickly, paired with urgency language that doesn't match the actual stakes of the decision
• Vague or evasive answers about who specifically owns the code and hosting once the project ships
• No written contract, or a contract that's entirely one-sided in the agency's favor on revisions and ownership
• An unwillingness to provide even one reference you can speak with directly

“The agencies most eager to start tomorrow are often the ones who most need you to sign before you have time to think it through.”

The bait-and-switch on team composition deserves particular attention because it's both common and hard to catch in a single meeting. An agency's founder or senior account lead pitches the deal, demonstrates deep expertise, and earns your trust — then, once signed, the actual day-to-day work gets handed to whoever's available, who may be a junior hire several levels below the person you evaluated. Ask explicitly, by name if necessary, who will be doing the actual work, and ask to meet them before signing, not after.

Pricing that's dramatically below every other quote you've received deserves the same scrutiny as pricing that seems too good to be true in any other context, because it usually is. The gap is being absorbed somewhere — junior talent doing senior-level work, corners cut on testing and QA, a thinner discovery process that will surface as scope disagreements later, or a business model that depends on volume over depth. None of that means the cheapest option is automatically wrong, but it does mean the burden is on them to explain the gap convincingly, not on you to assume it's a great deal.

Questions to Ask in the Discovery Call

The discovery call is where most of the real signal lives — not in the polished deck, but in how specifically and honestly an agency answers questions they weren't given in advance.

About the team

• Who exactly will be working on this, day to day?
• How many other active projects is that person or team carrying right now?
• Is any part of this work subcontracted, and if so, which part?

About the process

• Walk me through your last project of similar scope, stage by stage.
• What's the single most common reason your projects run late?
• How do you handle a client who wants to add scope mid-project?

About the outcome

• What happens in the first 30 days after launch?
• Who owns the domain, hosting, and codebase once we're live?
• If we wanted to leave in a year, how hard would that transition be?

Listen as closely to how an agency answers these as to what they actually say. A team with a real, lived process will answer specifically and quickly, often with a concrete example from a past project. A team without one will answer in generalities, pivot toward reassurance rather than specifics, or take noticeably longer to respond because they're constructing an answer in real time rather than recalling one. Neither tone nor confidence is a reliable signal on its own — specificity is.

How to Evaluate a Portfolio Properly

Most buyers evaluate a portfolio the way they'd browse a gallery — does it look nice? That's the wrong question. A portfolio screenshot tells you almost nothing about whether the site performs well, was delivered on time, or is actually easy for the client to maintain today.

Click through to the actual live site, not just the case study page. Check how it loads on your phone over a real mobile connection, not just on the agency's office Wi-Fi. Look at the site's actual structure — does navigation make sense, do forms work, is content easy to find — rather than just the hero section that was clearly built to be screenshotted.

Pay particular attention to how a case study describes the problem it solved. A strong case study is specific: it names the actual constraint the client faced, explains the reasoning behind the approach taken, and is honest about tradeoffs. A weak case study reads like marketing copy applied retroactively to a finished project — "we built a beautiful, modern website that exceeded expectations" — without ever describing what problem the work was actually solving or why the specific decisions made sense for that client's situation.

It's also worth asking what the project looked like six months or a year after launch, not just on launch day. A site can look impressive at the moment of handoff and still be poorly built underneath — slow to update, fragile when new features get added, or quietly accumulating bugs that never get fixed because the underlying code wasn't structured to be maintained by anyone other than the original builder. If an agency stays in touch with past clients well after launch, ask them directly how the site has held up.

Pricing Models Explained

Web development pricing generally falls into three models, and each one shifts risk between you and the agency differently. Understanding which model you're actually being offered — and what it implies about incentives — matters more than comparing raw numbers across quotes.

None of these models is inherently better — the right choice depends on how well-defined your project actually is. A genuinely fixed-scope marketing site is well suited to fixed pricing. A platform that will keep evolving based on user feedback is poorly suited to it, because every fixed-price contract for a moving target eventually turns into a change-order negotiation.

Whatever model you choose, ask explicitly how the agency handles the gap between estimated and actual effort. A fixed-price project that runs over the agency's internal estimate shouldn't become your problem unless the scope itself changed — that's the entire point of fixed pricing, and an agency that quietly pads every subsequent project to compensate for past underestimates isn't pricing fairly. Conversely, an hourly arrangement where hours seem to expand indefinitely without clear, itemized justification deserves the same scrutiny you'd apply to any other open-ended expense.

Communication and Project Management Expectations

The gap between agencies that feel easy to work with and ones that feel like a constant struggle almost never comes down to technical skill — it comes down to communication discipline that was either established clearly upfront or never discussed at all.

1. Agree on a communication cadence before the project starts — weekly syncs, async updates, or both
2. Establish a shared project board so progress is visible without needing to ask for a status update
3. Clarify response time expectations for both sides, including what happens outside business hours across time zones
4. Define what counts as a 'milestone' clearly enough that both sides agree when one has actually been hit
5. Set expectations for how feedback gets given and incorporated — vague feedback produces vague revisions

The clearest early signal of how a project will actually run is how the agency handles communication during the sales process itself, before any contract is signed. An agency that's slow to respond, vague in its answers, or inconsistent about who you're talking to during the courtship phase is showing you, in miniature, exactly how they'll communicate once you're a paying client and the relationship has lost its novelty. Pay close attention to this period — it's the most honest preview you'll get.

Project management tooling matters less than the discipline behind it. A team using a simple shared spreadsheet with rigorous, consistent updates will serve you better than a team using sophisticated software that nobody actually keeps current. Ask to see what the actual project tracking will look like for your engagement specifically, not a generic screenshot from their marketing materials.

Foreign Market Considerations

Hiring an agency based in a different country or time zone than your own adds real considerations beyond the usual evaluation — none of them disqualifying on their own, but all of them worth addressing directly before you sign.

• Time zone overlap: how many real-time overlap hours exist, and is that enough for the cadence this project needs?
• Language and communication clarity: is written and spoken communication clear enough for nuanced feedback, not just basic instructions?
• Cultural and market fluency: does the team understand your market's specific user expectations, payment norms, and compliance requirements (GDPR for the EU, accessibility standards, etc.)?
• Currency and contract terms: is pricing quoted in a currency and contract structure your finance team can work with cleanly?
• Legal and IP considerations: does the contract clearly establish that you own the code, content, and IP once delivered, regardless of jurisdiction?

None of these are reasons to avoid a foreign agency outright — some of the most senior, cost-effective development talent in the world works outside whatever market you're selling into. They're simply questions that deserve a direct, specific answer before you commit, the same way you'd want clarity on any other significant business relationship that crosses borders.

In practice, working across a real time difference often produces better documentation discipline than working with a team in your own time zone, simply because the gap forces it. A team that can't rely on quickly grabbing someone for a five-minute hallway conversation has to get better at writing things down clearly the first time — decisions get recorded, expectations get set explicitly, and less depends on someone remembering a verbal conversation from three weeks ago. That discipline tends to benefit the project regardless of where everyone happens to be sitting.

The Real Cost of Cheap Agencies

The cheapest quote is rarely the cheapest outcome. A lower hourly rate or fixed price usually reflects one of a few realities: junior talent doing the actual work regardless of who's selling it, a thinner process with less discovery and planning, or a business model that depends on volume and fast turnaround rather than depth on any single project — none of which are obvious from the quote itself.

This isn't an argument for always choosing the most expensive option either — plenty of overpriced agencies deliver mediocre work while trading on brand reputation alone. It's an argument for evaluating price relative to the 12-point checklist above, not in isolation. A quote that's meaningfully below market rate deserves the question "what, specifically, are we not getting for this price" before you accept it.

The SEO foundation point deserves particular attention because it's one of the most expensive corners to cut, and one of the least visible at launch. A site built without proper semantic HTML, without attention to Core Web Vitals, without a sane URL structure, or without basic schema markup will look identical to a properly built one in a browser on launch day — the gap only becomes visible months later, in search rankings that never materialize, or in a technical SEO audit that reveals the site needs substantial rework before it can compete. By the time that gap is visible, the cost to fix it is almost always higher than building it correctly the first time would have been.

There's a useful framing for thinking about this tradeoff: treat the cheapest quote and the most expensive quote both as data points that need explanation, not as signals to act on directly. The agency that explains, specifically and convincingly, what you're getting for the price — whether that price is low or high — deserves more trust than one that simply asks you to take the number on faith. Price is informative, but only once you understand what's actually behind it.