Ten Questions I Would Ask Before Hiring a Web Design Agency

Hiring a web design agency is easier to get wrong than it should be, mostly because most businesses only find out what a good process looks like after they've already been through a bad one. Rather than list warning signs after the fact, I want to give you the opposite: a structured framework of ten questions to ask before you sign anything. Ask these on the first or second call, and you'll know within twenty minutes whether an agency has a real process or is winging it.

1. What Does Your Actual Process Look Like, Step by Step?

Ask for the stages in order — discovery, wireframes, design, development, testing, launch — and how long each typically takes. A serious agency can walk you through this without hesitation because they run it on every project. If the answer is vague or jumps straight to we will design something you will love that's a gap worth noting before you commit.

2. Who Owns the Code, the Domain, and the Design Files After Launch?

This is the single most important question people forget to ask. You want it in writing that you own the source code, your domain registration, and your content once the project is delivered and paid for. Some agencies build on proprietary platforms that effectively lock you in, making it expensive or impossible to leave later. Ask this directly, and get the answer in the contract, not just verbally.

3. What's the Realistic Timeline, and What Could Delay It?

Every agency will give you an estimate. The better question is what typically causes that estimate to slip — usually it's late content or feedback from the client side. An agency that's upfront about this, and tells you what they need from you to hit the timeline, is being honest rather than just optimistic.

4. How Many Rounds of Revisions Are Included?

Unlimited revisions sounds generous but often signals a vague scope that will drag on. I'd rather see a clear number — say, two or three structured rounds — with a defined process for anything beyond that. Ask what happens if you want changes after those rounds are used up, and what that costs.

5. What Happens After the Site Launches?

A launched site isn't a finished relationship if you need ongoing support. Ask whether the agency offers website maintenance, what it covers, and what your options are if you decide to manage updates in-house instead. Agencies that only think as far as launch day tend to build sites that are harder to maintain later.

6. Is SEO Built In, or Is It a Separate Add-On?

Some agencies treat search visibility as an afterthought, bolted on if you pay extra. I think the fundamentals — clean heading structure, fast load times, proper meta tags — should be part of the base build, not an upsell. Ask specifically what technical SEO work is included versus what would need a separate engagement.

7. Can I See a Live Site You Built, Not Just a Portfolio Screenshot?

Screenshots can hide a lot — slow load times, broken mobile layouts, forms that don't actually submit. Ask for a live link you can visit yourself, on your own phone, and test the contact form. This takes two minutes and tells you more than a polished case study ever will.

A few numbers worth knowing:

• Industry research on client-agency relationships consistently finds that unclear scope and ownership terms are among the most common causes of disputes after a website project concludes.
• Think with Google's mobile research shows that bounce probability rises sharply as page load time increases, which is why asking to test a live example on your own phone is more revealing than reviewing a portfolio screenshot.
• According to widely cited web development benchmarks, businesses that plan for post-launch maintenance from the start report fewer security issues and less downtime over time than those that treat a site as a one-time deliverable.

8. How Do You Handle Hosting, and What Happens If I Want to Move It Later?

Ask whether the agency hosts the site themselves or sets it up on infrastructure you control. Both are valid, but you need to know upfront whether moving hosts later is simple or whether it's designed to keep you dependent on them specifically.

9. What Do You Need From Me, and When?

A good agency will tell you exactly what content, images, approvals, and access they need from your side and by when, because a project's timeline usually depends as much on the client as it does on the agency. If nobody asks you this upfront, expect surprises later.

10. Can You Walk Me Through a Project That Didn't Go Perfectly?

This is a deliberately uncomfortable question, and how an agency answers it tells you a lot. Every agency has had a project hit a snag. One that can talk honestly about what went wrong and what they changed afterward is more trustworthy than one that claims everything always goes flawlessly.

If you've already been through a bad experience with an agency and are trying to figure out what went wrong, I've written separately about the specific red flags that show up when a web design agency doesn't deliver. This piece is meant to sit ahead of that — the questions that help you avoid getting there in the first place.

How to Actually Use This List on a Call

I wouldn't recommend firing off all ten questions like an interrogation. Weave them into the conversation naturally, and pay attention not just to the answers but to how comfortable the agency is answering them. A team with a real process welcomes these questions because they've answered them a hundred times before. A team that gets defensive or vague is telling you something too, even if the words themselves sound fine.

I'd also suggest asking the same ten questions to at least two or three agencies before deciding, even if you already have a favourite. It's the fastest way to calibrate what a normal, confident answer sounds like versus one that's dodging the specifics, and it usually clarifies your decision faster than another round of portfolio browsing would.

Frequently Asked Questions

What's the most important question to ask a web design agency?

Who owns the code, domain, and files after the project is delivered. This single answer tells you whether you'll have real control over your own website once it's live.

Should I be worried if an agency offers unlimited revisions?

Not automatically, but I'd ask how they define the scope of a revision versus a new request. Vague unlimited offers sometimes hide a project that never quite gets a defined finish line.

How do I know if an agency's timeline is realistic?

Ask what typically causes delays on their projects and what they need from you to avoid them. An honest, specific answer is a better sign than a suspiciously fast, no-caveats estimate.

Is it reasonable to ask for a live example instead of a portfolio screenshot?

Yes, and any agency confident in their work should have no issue providing one. Testing a real site on your own phone reveals things a curated screenshot never will.

What should be in writing before I sign with a web design agency?

Ownership of code, domain, and content; the number of included revision rounds; the project timeline; and what happens after launch, including maintenance terms, should all be documented in the contract, not left as verbal understandings.

Further Reading

• web.dev: Fast Load Times
• Google Search Central: SEO Starter Guide
• ICANN: Domain Name Ownership and Transfers

We're happy to be asked every one of these questions directly. See our own process laid out on our how we work page, browse real completed projects on case studies, or reach out through our contact page and put us through this exact list.