The questions to ask a web design agency are not about design taste. They are about ownership, scope, timelines, what happens after launch, and who is accountable when something breaks. Taste you can judge from their portfolio in five minutes. The rest is where projects go wrong, and it is all answerable before you sign anything.
Ask these in order. Note which ones get a straight answer and which get a deflection, because the pattern tells you more than any single response.
Ownership and Access
These four matter most, and most owners never ask them. Getting locked out of your own website is a genuinely common and entirely avoidable situation.
1. Who owns the website when the project ends?
You want the answer to be you — the design, the content, the code and the data. Ask whether anything is licensed rather than owned, and if so, what happens to it if you stop working together.
2. Who owns the domain and the hosting account?
The domain should be registered to your business, in an account you control, with your name on the registrant record. Hosting in the agency’s account is convenient right up until the relationship ends.
3. Will I have administrator access from day one?
Not view access. Administrator. If an agency is reluctant to give you full access to your own site, treat that as information about how the rest of the relationship will go.
4. What platform is this built on, and how portable is it?
A site built on a widely used platform can be maintained by thousands of people. A site built on a proprietary builder only that agency can work in means every future change goes through them at their rate. Neither is automatically wrong, but you should know which you are buying.
Scope and Deliverables
5. How many pages, and which ones specifically?
“A five-page website” means nothing until the five pages are named in the proposal. Get the list written down, and agree what happens if you need a sixth.
6. Who writes the content?
This is the single biggest cause of stalled web projects. If you are writing it, say so and schedule it. If they are writing it, confirm whether that means original copy, edited copy you supply, or placeholder text you will replace later.
7. Where do the images come from?
Stock, your own photography, or a shoot? If stock, who licenses it and in whose name? If your own, who is resizing and optimising them?
8. Is it responsive, and will you show me the mobile designs?
Every agency says responsive. Ask to see the mobile layouts specifically, before build, because a desktop design squeezed down is not the same as a mobile layout designed on purpose.
9. What is explicitly not included?
A good answer to this question is a long one. Copywriting, photography, SEO, ongoing maintenance, training, email setup, integrations and content migration are all commonly assumed by one side and excluded by the other.
Timeline and Process
10. What is the timeline, and what do you need from me to hold it?
Every honest timeline has client dependencies in it. Content, feedback, approvals, access to accounts. Ask for those to be named with dates so you know what you are responsible for.
11. How many rounds of revisions are included?
Then ask what counts as a round. Consolidated feedback on a whole page is normal. Fifteen separate emails over a week usually is not, and the proposal should say so.
12. Will I see it on a staging site before launch?
Yes is the only good answer. You should be able to click through the real thing, on your own phone, before it replaces your live site.
After Launch
13. What happens on launch day, and what happens the week after?
Ask specifically about redirects from old URLs, analytics and search console reconnection, form testing, and who is watching for problems in the first few days. This is where traffic gets lost in a redesign.
14. What does ongoing support cost, and what does it cover?
Updates, backups, security monitoring, uptime checks, small content changes. Get the scope and the response time in writing. A website is software; software needs maintenance.
15. What is your handover if we part ways?
Logins, files, documentation, and a clean exit. Ask now, while everyone is friendly.
Scoring the Answers
| Question area | Good sign | Warning sign |
|---|---|---|
| Ownership | You own everything, in writing | Vague, or “we hold it for you” |
| Access | Admin from day one | Access granted at handover only |
| Platform | Widely supported, portable | Proprietary with no export path |
| Content | Named owner and schedule | Assumed, unassigned |
| Exclusions | A specific written list | “Everything you need” |
| Timeline | Dependencies named with dates | A single end date |
| Launch | Redirect and tracking plan | Not mentioned |
| Support | Scope and response time in writing | Ad-hoc hourly, undefined |
Three Things to Check Without Asking
Some answers you can get yourself before the first call.
Look at their portfolio sites on a phone. Not the screenshots on their site — the actual live sites. Load them on mobile data and see what happens.
Run one of their recent builds through PageSpeed Insights. You are looking at whether performance is something they think about at all, on mobile particularly.
Check whether their portfolio sites are still live and still current. A portfolio full of sites that have since been replaced tells you something about how long the work lasts.
What a Proposal Should Contain
When the proposal arrives, read it against this list. If any of the seven is missing, ask for it before signing rather than after:
- The named page list and what each page contains.
- Who is responsible for copy and images, item by item.
- Platform, theme or builder, and ownership terms.
- Timeline with client dependencies dated.
- Revision rounds and what constitutes a round.
- Launch checklist including redirects and tracking.
- Post-launch support scope, response time and price.
Also check how payment is structured. A deposit with milestone payments against named deliverables is normal and protects both sides. Full payment upfront for a project that has not started is worth questioning.
A Note on Price
Cheap websites are usually cheap because something on the list above is missing — the copy, the mobile design, the launch plan, the support, or the ownership. That is not always the wrong trade, but you should know which corner is being cut rather than discovering it later.
Conversely, a high price is not evidence of quality. The questions above are how you tell the difference, and they cost nothing to ask.
Go In With the List
The questions to ask a web design agency are mostly about the unglamorous parts: who owns what, what is in scope, what happens the week after launch. Ask all fifteen, write down the answers, and compare proposals on substance rather than on which mockup you liked best.
If you want to see what a scoped, fixed-price website engagement looks like with those answers already written down, start with the Pricing page.