Questions to Ask Before Hiring a Web Design Agency

The most useful questions to ask a web design agency before hiring it cover five areas: relevant past work, the people and process behind the project, exactly what is included, who owns the finished site and its parts, and how support and later changes are handled. Clear answers to these reduce the chance of surprises halfway through the build or a year after launch. Below, each area is broken into specific questions, with notes on what a clear answer tends to look like.

It helps to do some background reading on any agency on your shortlist first. The same habits described in this guide to researching a company before a deal apply here: look at the firm's own channels, public records and how long it has been trading.

1. Past work and fit

Can you show projects similar to ours?

A portfolio of attractive sites says little if none of them resemble your needs. Ask for examples of a similar size and type: an online shop if you sell products, a booking system if you take appointments, a content-heavy site if you publish often. Visit the live sites, not only the screenshots, and try them on a phone.

Can we speak to a past client?

Many agencies will connect you with a client who agreed to be a reference. Ask that client how the project ran, how problems were handled and whether the site was easy to manage afterwards.

2. People and process

Who will actually work on our site?

The person who pitches is not always the person who builds. Ask who designs, who develops, who writes or edits content and who manages the project. Ask whether any part is passed to freelancers or subcontractors, and if so, how their work is checked.

What are the stages, and what do you need from us at each one?

A typical project moves through discovery, structure and wireframes, visual design, build, content entry, testing and launch. A clear answer explains what you review at each stage, how feedback is collected and how many rounds of revisions are included. Ask for a timeline in phases and which delays on your side would push it back.

3. What the quote covers

Two quotes can look similar and include very different things. A side-by-side checklist makes comparison easier:

Item	Ask whether it is included
Number of page templates	Is a limit set, and what counts as a template?
Copywriting and editing	Do they write text, edit yours, or only place it?
Images	Are photos sourced, licensed or shot, and who pays for licences?
Forms, booking or shop features	Which functions are part of the build?
Accessibility checks	Is the site tested for keyboard use, contrast and screen readers?
Testing	Which browsers and devices are covered?
Content migration	Will existing pages be moved over, and how many?
Training	Will your team learn to edit pages and add content?

4. Content responsibilities

Content is the most common cause of slipping deadlines. Agree early on who writes each page, who supplies product or service details and who approves the final text. If you are writing it yourself, ask for a content plan listing every page and its purpose. If you sell products, the patterns in these product description examples show the level of detail a shop page usually needs, which helps when estimating how much writing is involved.

5. Ownership of the finished site

This is the area people most often skip, and the one that causes the most trouble later. Ask each question directly and get the answer in writing:

• Domain name. Is it registered in your business's name, with you holding the login?
• Hosting. Where will the site live, who holds the hosting account and can you move it elsewhere?
• Design files. Will you receive the original layouts, logos and graphics in editable form?
• Code. Who owns the custom code once the project is paid for? Are any parts licensed rather than owned?
• Accounts and logins. Will you have administrator access to the site and to any connected services?

Rules on intellectual property and contracts differ between countries; check the terms that apply to you, and take advice if the agreement is unclear.

Local businesses often find it easier to compare agencies they can meet in person. An Auckland company, for example, might shortlist a few studios that offer Website Design Auckland and put the same set of questions to each, so the answers can be weighed side by side.

6. Handover and support after launch

What happens in the weeks after the site goes live?

Ask whether there is a period during which bugs are fixed without charge, and what counts as a bug as opposed to a new request.

Who looks after updates, security and backups?

Websites need software updates, security patches and regular backups. Find out whether this is included, offered as an ongoing plan or left to you. If it is left to you, ask for written instructions.

7. Contract terms and changes

Finally, read how the contract handles change. Useful points to clarify:

1. How is a change to the agreed scope requested, priced and approved?
2. How are payments staged, and what triggers each one?
3. What happens if either side wants to end the project early?
4. What happens to work in progress, files and access if the relationship ends?

An agency that answers these questions plainly, and is happy to put the answers in the agreement, gives you a firmer base for the project than one that keeps the details vague. Keep your notes from each conversation, compare them at the end and choose the team whose answers were the clearest.