A discovery call is where scope, ownership, testing, and handover get decided before any code is written. For developers, it is also a first test of the client relationship: vague answers here usually become vague requirements, disputed scope, and rushed testing later. The questions below are the ones that surface process problems early, while they are still cheap to fix.
A discovery call is a job interview, and it runs in both directions. The agency is learning about your business. You are learning whether you can trust them with your website, your budget, and your reputation. A pretty portfolio will not tell you that. The questions below will.
If you are hiring a web design agency, these are the questions to ask a web design agency before you sign anything. Take notes. Compare answers across agencies. Ask for the important ones in writing.
1. How will you measure whether my website is successful?
Start here, before anyone talks about colours or layouts. A good agency asks what the website is supposed to do for your business. More phone calls? More quote requests? More online orders? Fewer repetitive questions from customers? The answer changes what gets built.
Listen for specifics. The agency should talk about a baseline: where you are now, what you will track, and when you will review it together. For a local service business, ten relevant enquiries may matter far more than a thousand extra visitors who were never going to buy. For a shop, completed checkouts and abandoned carts matter more than page views.
Be wary of vague promises. No honest agency can guarantee first page rankings or a fixed amount of traffic. If someone guarantees it on a first call, that is your answer about them.
A useful follow up: "What would we measure before launch, and how would we review performance afterwards?"
2. What is your process, and what will you need from me?
Most website projects do not stall because of code. They stall because nobody agreed who was doing what, and by when.
Ask the agency to walk you through their process in plain language. Discovery, design, content, build, testing, launch. Then ask what they need from you at each stage. Photos, product details, prices, login details for a domain, approval on designs. If you run a business, you will be busy. You need to know the workload before you agree to it, not after.
At aimEncoders, a discovery call usually covers your goals, your customers, your competitors, and the pages you actually need. That conversation becomes a short written brief. The brief is what the quote is based on, so there are fewer surprises later.
Also ask what happens if you are late with something. Does the timeline shift? Does the agency move on to other work? A straight answer here saves an argument later.
A useful follow up: "What do you need from me in the first month, and what happens if I cannot provide it on time?"
3. Who will actually work on my project?
The person selling you the project may not be the person building it. That is normal in a larger agency, but you should still know who is involved.
Ask for names and roles. Who is your day to day contact? Who designs? Who writes the code? Who tests? Is any of the work subcontracted? What happens if your main contact is away?
This matters because websites are full of small decisions. Someone has to make them, and someone has to answer for them. If no one can explain who will build your site, you are buying a brand, not a team.
You should also ask how you will communicate. Weekly updates, a shared document, a chat group, or only email? Pick the setup you will actually respond to. A process you ignore is no process at all.
A useful follow up: "Who makes the day to day decisions, and who do I contact if a problem needs escalating?"
4. What exactly is included in the price, and what costs extra?
Two proposals can look similar and mean very different things. One may include copywriting, product photography guidance, and moving your old content over. The other may be design and code only, with everything else billed separately. You cannot compare them until you know what is inside each one.
Ask for the scope in writing: pages, features, forms, payment integration, booking system, blog setup, and content. Then ask for the exclusions: what is not included, and what would trigger an extra charge. Ask separately about costs that continue after launch, such as hosting, domain renewal, licences, and maintenance. A one time fee and a monthly fee are not the same thing, and they should never be blurred together.
Be honest about budget range on the call if you can. An agency that knows your range can tell you what is realistic and what is not. An agency kept in the dark will quote a dream version, and you will both waste time.
A useful follow up: "Can you list what is included, what is excluded, and which costs may continue after launch?"
5. How will you handle SEO, speed, accessibility, and testing?
This is the question that separates a website that looks finished from a website that is finished. A site can look great in a demo and still load slowly, break on a phone, hide from search engines, or fail for a customer using a screen reader.
Ask how the agency handles the basics before launch. Page speed and mobile layout. Titles and descriptions that search engines can read. Clean URLs. Forms that actually send. Links that actually work. Content that loads properly on a slow connection.
Testing deserves its own question, because it is where many projects cut corners. At aimEncoders, every site goes through QA-tested website development before launch: pages checked on mobile and desktop, forms submitted for real, links clicked, speed checked, and obvious errors fixed before a customer ever sees them. Automated checks help, but they do not replace a person clicking through the site the way a customer would.
On accessibility, listen for care rather than slogans. Automated scans catch some problems, not all of them. An agency that claims a site is fully accessible from one scan alone is overselling it.
A useful follow up: "Show me your pre-launch checklist. What do you check, and what happens to the faults you find?"
For background on speed, Google publishes Core Web Vitals guidance that explains what it measures and why it matters for visitors.
6. Who owns the website, the domain, and the accounts when the project is finished?
This question is boring until the day you need the answer. Then it is the most important question you never asked.
Ownership depends on the contract, so read that part properly. Ask who owns the design, the code, and the content. Ask who controls the domain name, the hosting account, the analytics account, and any third party tools. Ask whether you can move the site to another provider if you choose to, and what that would involve.
A healthy arrangement is simple: you own your domain, your content, and your business accounts, and you have admin access to them. If an agency insists on holding your domain or your hosting hostage, walk away. That is not a partnership. That is a lock in.
Also ask about licences. Some themes, plugins, and stock images are licensed, not owned. That is fine, as long as you know which licences continue and who renews them.
A useful follow up: "If we part ways, what exactly do I walk away with, and in what format?"
7. What happens after launch, and if we part ways?
Websites are not finished at launch. They are launched, and then they need looking after. Content goes out of date. Software needs updates. A form breaks after an update. A page needs a new price. Ask what support looks like, how fast the agency responds, and what is charged and what is not.
Our own guide to website maintenance after launch covers the routine in plain terms: updates, backups, checks, and small fixes that keep a site working instead of slowly rotting. Use it as a checklist when an agency describes their own aftercare.
Then ask the harder version of the same question. What if you want to leave? How much notice? What handover do you get? Passwords, documentation, and a site you can actually run elsewhere. An agency confident in its work will answer this calmly. An agency that gets defensive has told you something useful.
A useful follow up: "What does your first 90 days after launch look like, in writing?"
How to compare the answers
After two or three calls, the agencies will blur together unless you wrote things down. Score each one on the same seven points: business understanding, process, team, scope and cost, technical quality, ownership, and aftercare. Promises are cheap. Evidence is not. A written scope, a named team, a testing checklist, and clear ownership terms are evidence. A slick pitch deck is not.
Then ask for the short version in writing before you pay anything: what is included, what it costs, who owns what, and what happens after launch. If an agency will not put that in writing, you have your decision.
Frequently asked questions
What should I prepare before a web agency discovery call?
Bring your goal for the website, examples of sites you like and dislike, your current site if you have one, and a rough budget range. You do not need a full specification. A good agency will help you shape that.
How long should a discovery call take?
Thirty to forty-five minutes is normal for a first call. Shorter than that, and the agency probably has not learned enough about your business. Much longer, and it has turned into a sales pitch.
Should I tell a web agency my budget?
Yes, at least a range. It lets the agency say honestly what fits and what does not, and it stops both sides designing something you cannot afford.
What are red flags when hiring a web design agency?
Guaranteed rankings, no written scope, no named team, no testing process, and an agency that holds your domain or hosting. Any one of those is reason to pause. Two together is reason to walk away.
What should I ask when switching web agencies?
Ask what you own, what access you hold, and what handover the old agency must provide. Then ask the new agency what they need to take over safely, including a backup, a content inventory, and a redirect plan for changed URLs.
About the author
Muhammad Asad Ullah is the founder of aimEncoders, a Faisalabad based web development agency building custom websites, web applications, and ecommerce stores for small businesses. He works across development and quality assurance, so the sites his team ships are tested like a customer will use them, not just like a developer built them.
Top comments (0)