How to Choose a Web Development Agency: 12 Questions to Ask

Choosing a web development agency is a strange purchase. You are paying a significant amount for something you can't see yet, from people you have probably just met, and the quality of the work often only becomes obvious months later, when the site is slow, hard to update, or locked inside an account you don't control.

We're an agency ourselves, so we know this article could easily turn into a sales pitch. We'll try hard not to let it. These are the questions we'd want a friend to ask before hiring anyone, including us. A good agency will be happy to answer all of them clearly. If an agency gets defensive or vague, that tells you something too.

Below are twelve questions, what a good answer sounds like, the red flags to watch for, and a simple way to compare proposals side by side.

Questions about how they work

1. What does your process look like, step by step?

A good answer describes clear phases: discovery, planning and scope, design, development, content, testing, launch, and support. Ask what you receive at each stage and when you are expected to give feedback. Discovery matters most; an agency that quotes a fixed price before understanding your goals is guessing.

Good sign: they ask you lots of questions about your business, customers, and goals before talking about technology.

2. Who will actually do the work?

Some agencies have in-house teams, some use freelancers, and some outsource most of the work. Any of these can work well, but you deserve to know. Ask who your main contact is, who writes the code, and whether that person will still be around after launch.

3. What is the realistic timeline, and what could delay it?

Timelines vary hugely with scope. A simple brochure site might take a few weeks; a custom web application or a complex store can take several months. The honest answer includes dependencies: delays usually come from late content, slow feedback rounds, or scope changes, not just development. Ask how they handle each.

4. How and how often will we communicate?

Ask about the tools (email, Slack, a project board), how often you'll get updates, how quickly they typically respond, and whether you can see work in progress on a staging site. Regular demos of working software beat long status reports.

Questions about ownership and technology

5. Who will own the code, domain, and hosting accounts?

This is the question we'd put at the top of the list. You should own your domain name, your hosting account (or have it in your name), your analytics and Search Console properties, and the rights to the code and design once you've paid. If an agency registers your domain in its own name, you may struggle to leave later.

Good sign: they set up accounts in your name and add themselves as users, and the contract states that ownership transfers on payment.

6. What tech stack do you recommend, and why for us?

There is no universally best stack. WordPress, Shopify, a headless setup with Next.js, or a fully custom application can all be the right answer. What matters is the reasoning. A good agency explains trade-offs in terms of your needs: who will edit content, how much you'll grow, what integrations you need, and what it costs to maintain. Be wary when every client gets the same answer. If you're running a store, our comparison of Shopify, WooCommerce, and headless may help you ask sharper questions.

7. How do you handle performance and SEO?

Ask whether they test Core Web Vitals before launch, how they handle redirects from your old site, whether they set up metadata, sitemaps, and structured data, and how they prevent a traffic drop during migration. A beautiful site that loads slowly or loses its search rankings is an expensive problem. Our technical SEO launch checklist shows the kind of detail you should expect.

8. How do you approach accessibility?

Ask which standard they build to (WCAG 2.2 AA is a common target), how they test, and whether they use real keyboard and screen reader checks. If the answer is "we install a plugin", keep asking. Our guide to web accessibility for small businesses explains why.

Questions about money, support, and contracts

9. What happens after launch?

Websites need updates, security patches, backups, and the occasional fix. Ask what's included after launch, for how long, and what ongoing support costs. Clarify whether bugs discovered after launch are fixed for free and for how long. Also ask whether you can manage the site yourself, or hire someone else, if you want to.

10. How do you price projects?

Common models include:

• Fixed price: predictable, but only as accurate as the scope. Changes usually cost extra.
• Time and materials: you pay for hours used. Flexible, but needs trust and good reporting.
• Retainer: a monthly fee for ongoing work. Good for continuous improvement.
• Phased: a paid discovery phase, then a fixed price for the build. We like this because the estimate is based on real understanding.

Ask what's not included: content writing, photography, stock images, third-party licenses, hosting, and premium plugins often aren't. For a deeper look at what drives cost, read how much a custom website costs.

11. Can I see relevant work and talk to past clients?

Look for projects similar in complexity to yours, not just pretty screenshots. Visit the live sites and check how they load on your phone. If possible, ask to speak with one or two past clients about communication, deadlines, and how problems were handled. Every project has problems; what matters is how they were handled.

12. What does the contract say about scope, changes, and ending the relationship?

Read the contract carefully, and have a lawyer review it if the project is large. Look for a clear scope, a change request process, payment milestones tied to deliverables, intellectual property terms, warranty or bug-fix periods, and what happens if either side wants to end the engagement early, including how you get your files and access.

Red flags to watch for

• A firm quote after a ten-minute call, with no discovery.
• Guaranteed first-page Google rankings. Nobody can honestly guarantee that.
• Reluctance to put your domain, hosting, or code in your name.
• Proprietary page builders or platforms that only they can maintain, without a clear exit path.
• Vague answers about who does the work.
• No mention of testing, backups, security, or mobile performance.
• Pressure tactics, like a discount that expires tomorrow.
• A portfolio with no live links, or live sites that are very slow.
• Large upfront payments with no milestones.

One red flag isn't always a deal breaker, but several together usually are.

How to compare proposals side by side

Proposals are rarely written the same way, which makes comparing them hard. Put them into a simple table so you are comparing like with like:

Criteria	What to look for
Understanding of your goals	Do they restate your problem accurately, in business terms?
Scope and deliverables	Pages, features, integrations, and content clearly listed
Exclusions	What you'll need to provide or pay for separately
Timeline and milestones	Realistic phases with review points
Ownership	Domain, hosting, code, and accounts in your name
Performance, SEO, accessibility	Specific commitments, not vague promises
Support	Post-launch warranty period and ongoing costs
Total cost of ownership	Build cost plus hosting, licenses, and maintenance over two to three years

The cheapest proposal is often the one with the most exclusions. The most expensive isn't automatically the best. Look for the proposal that shows the clearest understanding of your business and the fewest unanswered questions.

Key takeaways

• Make sure you own your domain, hosting, accounts, and code.
• Choose agencies that ask about your business before recommending technology.
• Ask specifically about performance, SEO, and accessibility, and expect specific answers.
• Understand the pricing model and what is excluded.
• Plan for life after launch, not just the launch itself.
• Trust how an agency handles hard questions; it predicts how they'll handle problems.

FAQ

Should I hire a freelancer or an agency?

Both can be excellent. Freelancers are often more affordable and flexible; agencies usually offer more capacity and continuity. Ask the same twelve questions either way, especially about support and what happens if the person you work with becomes unavailable.

Is it a bad sign if an agency charges for discovery?

Not at all. Paid discovery often leads to more accurate estimates and fewer surprises, and the output, usually a scope and plan, should be yours to keep.

Want to ask us these questions?

We're happy to be put through this list. You can read about how we work on our services page, or contact us to talk through your project. No pressure, and we'll tell you if we're not the right fit.