Questions to Ask Before Hiring a Web Development Agency

A capable agency runs projects to a process, not to mood and availability.

• What are the stages of the project, from start to launch?
• What is the expected timeline, and what could extend it?
• What do you need from us, and by when, to keep to schedule?
• Who is our point of contact, and who actually does the work?
• How do we review progress, and how often?

Vague answers here, such as “a few weeks” or “we will keep you posted,” usually mean there is no process. Without a process, the timeline is a hope rather than a plan.

Ownership is where businesses get quietly trapped. By the end of the project, the company should own everything outright.

• Who owns the code, the design, and the content when the project is finished?
• Will the domain, hosting, and all accounts be registered in our name and under our control?
• If we part ways, what do we keep, and what stays with you?
• Are there ongoing licences or subscriptions we will depend on, and what happens if we stop paying them?

The right answer is that the business owns all of it and can take it anywhere. Anything less means the agency keeps leverage over a company that has already paid.

Most of what separates a durable site from a fragile one is invisible at launch. These questions bring it into view.

• How do you make sure the site is fast on a normal phone and connection?
• How do you test the site across devices and browsers before launch?
• Could another developer maintain this site later, and how do you keep it that way?
• How is the site structured for search engines and for accessibility?

An agency that handles these well will answer specifically. An agency that does not will reach for reassurance, such as “do not worry, it will be fast,” or name a single tool, such as “we install a caching plugin.” Specificity is the signal.

A website is not finished at launch. It is only beginning to be used.

• What support do you provide after the site goes live, and for how long?
• What does support cost once the project is over?
• Who is responsible if something breaks, and how quickly do you respond?
• Will we be able to update the site ourselves, and will you show us how?

The purpose of these questions is to learn the cost of the relationship after the invoice, before that cost becomes a surprise.

How an agency communicates during the sales conversation is the best preview of how it will communicate during the project.

• How will we communicate, and how quickly do you usually reply?
• What happens if we are not happy with something you have delivered?
• How do you handle changes we request mid-project?
• Can you put the scope, timeline, and inclusions in writing?

An agency comfortable being held to its word answers these without hesitation. Reluctance to commit anything to writing is the most reliable warning sign there is.

Some answers are worth ending the conversation over:

• Evasiveness about ownership of the code, accounts, or domain.
• Refusal or inability to give a timeline with stages.
• No plan, and no clear cost, for support after launch.
• A quote far below every other, with no explanation of what is different. The reasons a low quote ends up costing more are covered in a separate Targetiv article.
• Pressure to decide quickly, or discomfort putting anything in writing.

None of these are about skill. They are about how the agency will treat the business once it has been paid, which is the part of the relationship that lasts longest.

For a faster first screen, these questions cover most of the risk in a single message:

• What are the stages and timeline of the project, and what do you need from us?
• Who owns the code, content, domain, hosting, and accounts at the end, and will everything be in our name?
• How do you ensure the site is fast on mobile, and how do you test before launch?
• What support do you provide after launch, and what does it cost?
• Could another developer maintain the site later?
• Can you put the scope, timeline, and inclusions in writing?

The replies, and the speed and clarity of them, reveal most of what is worth knowing before a single call.

• The questions that predict a project’s success concern process, ownership, and accountability, not price or portfolio.
• A capable agency runs to a process and can describe its stages, timeline, and what it needs from the client.
• The business should own all code, content, domain, hosting, and accounts at the end, with no leverage left behind.
• Specific answers on performance, testing, and maintainability signal competence. Reassurance and single-tool answers do not.
• Settle the cost and shape of after-launch support before it becomes a surprise.
• Reluctance to put scope and timeline in writing is the clearest warning sign of all.