How to choose a web design agency
Choose a web design agency that can turn your business requirements into a usable, maintainable website. Evaluate relevant live work, the proposed team, content responsibilities, accessibility, performance, integrations and ownership. Agree on acceptance tests and support before discussing the launch party.
The portfolio tells you whether you like the agency's work. Due diligence tells you whether you want to operate it.
Describe what the website must accomplish
Identify the important users and their tasks. A buyer may need to compare products, request a quote or complete an order. A job candidate may need to find a role and apply. Your staff may need to publish a page without waiting for a developer.
Write down the existing failures and how you know they occur. Separate aesthetic preferences from commercial or usability problems. “The site feels old” can be a valid design concern, but it does not establish that a rebuild will improve sales.
Ask whether the right intervention is a rebuild, a targeted redesign or fixes to the current site. A good agency should be able to justify the scope it recommends.
Inspect live work, including the ordinary pages
Request projects with comparable content volume, integrations and editing needs. Visit them on a phone. Try navigation, search and a key form. Review pages beyond the home page, including error states and long-content layouts.
Ask what the agency was responsible for. It may have supplied design while another team built the site, or it may have inherited important constraints. Discuss who maintains it now and whether later changes explain any current issues.
Have the agency describe one project where it reduced scope. A practical answer shows how it weighs user needs, budget and maintenance rather than automatically reaching for a more elaborate build.
Put acceptance criteria in writing
| Area | Useful acceptance evidence |
|---|---|
| User journeys | Agreed tasks completed successfully on relevant devices |
| Content management | Staff demonstrate routine edits without developer help |
| Integrations | Test records reach the right system with correct data |
| Accessibility | Defined standard, scope, manual testing and issue resolution |
| Performance | Agreed measurement approach and representative page results |
| Search migration | URL mapping, redirect tests and indexing checks |
| Recovery | Tested backups or recovery procedure and named responsibility |
Decide who accepts each area and how defects affect launch. A project cannot reliably be “done” if nobody agreed what done means.
For forms, test delivery to the destination system, validation, spam handling and failure messages. A form that displays “thank you” while losing inquiries is particularly committed to the wrong kind of conversion optimization.
Make accessibility a tested requirement
Specify the intended WCAG version and conformance level with your legal and accessibility requirements in mind. WCAG 2.2 provides testable criteria, but no generic accessibility promise settles every legal obligation. Ask how the agency tests keyboard use, focus, forms, text alternatives and representative assistive-technology journeys. WCAG 2.2 standard.
Automated checks can identify some problems. Require a human testing scope too. Ask which templates, content and third-party components were tested and what the remaining limitations are.
Content editors can introduce new issues after launch. Include practical training and guidelines so your team can preserve the work rather than unknowingly undoing it.
Measure performance under useful conditions
Google's Core Web Vitals assess loading, responsiveness and visual stability. Its “good” thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile of visits. Web Vitals guidance.
Use those as part of a performance discussion, not as a promise that one score determines commercial success. Ask which devices, page types, third-party scripts and traffic conditions are represented.
Distinguish laboratory testing from real-user data. A new site may not yet have enough field data. Agree on prelaunch tests and a post-launch measurement plan rather than treating a single desktop screenshot as the permanent state of the site.
Protect content and search equity
Establish who inventories content, rewrites it, migrates it and checks it. Copy often becomes the hidden critical path because everybody assumed someone else was writing it.
For a site with existing traffic, require a redirect map and a review of important pages, metadata, internal links and indexing controls. If the agency excludes SEO, another person still needs to own migration risk.
Do not let a temporary staging restriction become an accidental production block. Make the launch checklist include search accessibility and analytics verification.
Clarify ownership before files exist
The agreement should distinguish final designs, source files, custom code, reusable agency components, stock assets, fonts, plugins and subscriptions. Decide which items are transferred and which remain licensed, with the applicable conditions.
Paying for a build does not answer every copyright question. In the United States, commissioned work has specific rules, and “work made for hire” is not a universal label for everything a contractor creates. Obtain explicit rights appropriate to the deliverables. U.S. Copyright Office, works made for hire.
Keep domain registration and critical accounts under appropriate business control. Ask whether another qualified developer could maintain the site with the documentation and access supplied at handoff.
Budget for the website you will own
Request recurring hosting, software, security, maintenance and enhancement costs. Separate the defect-correction period from ongoing improvements. Define urgent incident response and who deals with third-party failures.
Finally, meet the project lead and technical lead who will do the work. Give them your requirements and ask what they would simplify, what could delay launch and what your team must provide.
Use the general agency scorecard to compare finalists. The right agency should leave you with a website your customers can use and your business can sustain, including on the entirely unglamorous Tuesday six months after launch.