On this page 9 sections
Choosing a web development agency is easier when you compare the work you will receive, not just the price on the first page of a proposal. A good partner should be able to explain the site's purpose, what is included, how decisions will be made, and who will look after it after launch.
You do not need to know how to code to ask useful questions. Begin with what your customers need to do on the site and what your team needs to manage.
Short answer
- Write a short brief that describes the site's users, main tasks, content and deadline.
- Ask each agency the same questions about scope, process, testing, ownership and support.
- Compare what is included and excluded, not only the total price.
- Look for clear answers and relevant evidence. A confident sales pitch is not a delivery plan.
Start with the job your site must do
Before requesting quotes, decide what a successful site would allow people to do. A local service business might need visitors to understand its offer and send a useful enquiry. A shop needs customers to find products, pay and know what happens next. An internal portal may need staff to complete a process securely.
Write down the pages and functions you think you need, but distinguish a must-have from an idea to explore. Note who will supply words, photographs, product details and legal text. Tell agencies whether you need your team to edit the site after launch and whether the site must connect to other systems.
A brief does not have to dictate the technical solution. It gives each agency the same problem to solve and makes their proposals easier to compare.
What to ask each agency
Ask who will do the work and who will answer your questions. Find out how the agency learns about your business, presents designs, handles feedback and records decisions. Ask what you will review before development goes too far and how many review rounds are included.
Ask how they will check the site on a phone, with a keyboard and with a slow or failed connection. A site should be usable by the people you want to reach. Ask how forms will be tested, how contact requests will reach your team, and what happens when something breaks after launch.
Discuss ownership plainly. Will your business control its domain name, hosting account, content and analytics accounts? Can you export the site and move to another provider? Who holds the login details, and how will access be handed over? These answers matter if the relationship changes later.
Finally, ask what support means. Does the quote include updates, backups, security maintenance, training or content changes? What response time applies to a broken form? A promise to "support the site" is too vague unless the services and costs are written down.
How to compare proposals
Put each proposal against the same checklist: discovery, design, content, build, integrations, testing, launch and support. A cheaper proposal may rely on your team writing all the copy or entering every product. A higher price may include those jobs. Neither is automatically better; you need to know which work remains with you.
Check the assumptions and exclusions. What happens if you add a page, change a design after approval, or discover an integration is harder than expected? If the price is fixed, the scope and change process should be clear. If the work is billed by time, ask for an estimate, a budget limit and regular progress reports. Ask to see a relevant live site and speak to a client where possible. Try the site as a visitor: find information, use the mobile menu and submit a test enquiry only with permission. Look for evidence of the work you need, not a portfolio full of unrelated visual styles.
Red flags
Be cautious when an agency cannot explain what it will deliver, who will do it, or what it needs from you. A deadline that assumes all content is ready may not suit a business that has not written its pages. A quote that omits testing or handover leaves important work undefined.
Be wary of guarantees about search rankings, sales or launch dates without a clear scope. Also ask questions if the agency insists on owning your domain or refuses to explain how you would move the site. The issue is not whether a provider offers a managed service; it is whether you understand and accept the arrangement. A poor fit can be a matter of communication rather than skill. If ordinary questions receive only jargon, imagine how a difficult decision or urgent fault will be handled.
How to make the decision
Shortlist a few agencies that understand the kind of project you have. Send the same brief, hold a conversation with each, and write down the differences. Score them against your priorities: relevant work, clarity, working relationship, total cost, ownership and support.
Choose the team whose proposal you can explain back in plain language. Before signing, confirm the deliverables, milestones, payment schedule, responsibilities, acceptance process and post-launch arrangement in writing. A clear agreement protects both sides and makes the work easier to manage.
How we can help
We build and support websites, and we are happy to answer these questions about our own work. Our Web Development service explains the kinds of sites we build.
If you are comparing options, send us your brief. We can tell you what we think is needed and what we would leave out.
Reviewed on 29 October 2026. This is a buyer's checklist rather than a market survey. For independent standards to discuss with an agency, see W3C's accessibility guidance (opens in a new window) and Google's Search Essentials (opens in a new window).
Let's work together
Ready to talk?
Tell us what you need. We'll reply within 2 working days. Get in touch