Choosing a web development partner is one of the most consequential decisions a company makes. Get it right, and you have a site that drives revenue for years. Get it wrong, and you spend months in frustration, blow your budget, and end up with something that does not work. Here is how to evaluate an agency before you sign anything.
Start With Technical Due Diligence
Before you look at a portfolio or sit through a pitch, run the agency's own website through Google Lighthouse. If their site scores poorly on performance, accessibility, or best practices, that tells you more than any case study ever will. An agency that cannot optimize its own site is unlikely to optimize yours.
Ask about their technology stack and why they chose it. A good agency will have a clear rationale for their technical decisions, not just "we have always used this platform." They should be able to explain the trade-offs of their approach and why it fits your specific needs.
Request code samples from a previous project, or at minimum, ask to see the code structure of a delivered site. You do not need to be a developer to evaluate this. Show it to a technical advisor or freelance developer and ask for their honest assessment. Clean, well-organized code is a strong indicator of professional standards. Spaghetti code is a warning sign that will cost you in maintenance down the road.
Ask specifically about their approach to performance, security, and accessibility. These are not optional extras. They are fundamental requirements that separate professional agencies from hobbyists.
Evaluate Communication Patterns Early
The sales process is a preview of the working relationship. Pay attention to how the agency communicates before the project starts, because that pattern will continue after you sign.
How quickly do they respond to emails? Do they answer your questions directly or give vague, non-committal responses? Do they push back on ideas when they have a better approach, or do they agree with everything you say? An agency that never pushes back is either not experienced enough to know better or not confident enough to share their expertise. Neither is a good sign.
Ask about their communication cadence during a project. Weekly status updates should be the minimum. You should know who your primary point of contact will be, what project management tools they use, and how they handle urgent issues. If they cannot articulate a clear communication process, expect chaos once the project starts.
Pay attention to project tracking as well. Professional agencies use tools like Asana, Linear, Jira, or Basecamp to manage tasks and timelines. If an agency relies on email threads and verbal agreements, scope creep and missed deadlines become much more likely.
References Tell You What Portfolios Cannot
A portfolio shows you the finished product. References tell you what it was like to get there. Always ask for references, and always call them.
The single most revealing question you can ask a reference is: "Would you hire the same team again for your next project?" The hesitation, enthusiasm, or qualification in their answer tells you everything you need to know.
Follow up with questions about the project timeline. Did it finish on time? If not, why? Were there surprise costs? How did the agency handle problems when they came up? Was the handoff smooth, or did you feel stranded after launch?
Be wary of agencies that cannot provide references. It means either they have not done enough work to have satisfied clients, or their clients were not satisfied enough to recommend them. Both are problems.
Contract Red Flags
The contract is where many companies get burned. Before you sign, make sure you understand several critical terms.
First, you should own the code. This seems obvious, but some agencies retain ownership of the code they write and license it back to you. That means if you leave, you cannot take your website with you. Make sure the contract explicitly states that all code, designs, and content become your property upon final payment.
Second, look for a clear scope change process. Every project has scope changes. The question is how they are handled. A professional contract will define how change requests are documented, estimated, and approved before work begins. Without this process, you end up with surprise invoices or an agency that quietly reduces quality to absorb unplanned work.
Third, milestones should be tied to payments. Paying 100 percent upfront gives the agency no incentive to deliver on time. A typical structure is 30 to 40 percent upfront, with remaining payments tied to specific deliverables: design approval, development completion, and final launch. Never pay more than 30 to 40 percent before seeing tangible work.
Finally, check the termination clause. What happens if you need to end the relationship mid-project? You should be able to walk away with whatever has been completed, without paying for work that has not been done.
The Post-Launch Question
Many companies focus entirely on the build and forget to ask about what comes after launch. A website is not a project that ends. It is an ongoing asset that needs maintenance, updates, and improvements.
Ask whether the agency offers maintenance plans and what they include. At a minimum, you need security updates, performance monitoring, and bug fixes. Some agencies include content updates, analytics reporting, and ongoing optimization in their maintenance packages.
Documentation is another critical post-launch deliverable. When the project is complete, you should receive clear documentation that explains how to update content, manage users, and perform common tasks. Without documentation, you are dependent on the agency for every small change, which gets expensive quickly.
Training is equally important. Your team should be comfortable making basic updates and changes without needing to call the agency. A good partner will provide training sessions and screen recordings that your team can reference.
The best agencies see the launch as the beginning of the relationship, not the end. They know that a website performs best when it is continuously improved based on real data and user feedback.
Frequently Asked Questions
How many agencies should I evaluate before choosing one?
Three to five is the sweet spot. Fewer than three does not give you enough comparison points to make an informed decision. More than five creates diminishing returns and decision paralysis. Start with a broad list based on research, then narrow to your top candidates for detailed conversations and proposals. Make sure each agency on your shortlist represents a slightly different approach or strength so your comparison is meaningful.
What is a reasonable timeline for a website project?
A straightforward marketing website typically takes 8 to 12 weeks from kickoff to launch. Complex projects with custom functionality, integrations, or extensive content can take 3 to 6 months. Be wary of agencies that promise delivery in 2 to 3 weeks for anything beyond a simple landing page. That timeline usually means they are using a cookie-cutter template with minimal customization, or they are cutting corners on testing and quality assurance.
Should I go with the cheapest or most expensive option?
Neither price extreme is a reliable indicator of quality. The cheapest option often cuts corners on performance, accessibility, testing, or post-launch support. The most expensive option may be overcharging for the same work or including services you do not actually need. Evaluate value, not price. Ask each agency to break down their estimate so you can see where the money goes. The best choice is usually the agency that clearly articulates what you are getting, why it costs what it does, and how it will deliver measurable results.
Does it matter if the agency is local or remote?
Communication quality matters more than physical proximity. A remote agency with excellent project management, clear communication processes, and reliable availability can be a better partner than a local agency that is disorganized. That said, if your project involves complex stakeholder workshops, in-person discovery sessions, or ongoing collaboration with multiple internal teams, having at least a few face-to-face meetings can be valuable. Many successful projects use a hybrid approach: an initial in-person kickoff followed by remote collaboration.