What a Good AI Agency Discovery Call Should Cover (And What It Shouldn't)

Most discovery calls with AI agencies follow a predictable format: the agency presents their services, shows a few case studies, and asks what the client is looking for. This is fine as a sales call. It is not enough to determine whether the agency is the right fit for your specific project or whether they understand your actual problem.
Here is what a genuinely useful discovery call covers, and the questions to ask if the call is not going there on its own.
What the Call Should Tell You About Them
Do they ask about your specific process before recommending anything?
An AI agency worth working with cannot tell you what to build in the first 15 minutes. They need to understand what you currently do, how it is done, and where the bottleneck actually is before making any recommendation. If the call moves quickly to "here is what we would build for you" without spending serious time on understanding your current state, they are selling a solution before they understand the problem.
Do they tell you what they cannot or would not do?
A vendor who will enthusiastically say yes to everything you describe is not giving you useful information. The agencies that are worth working with will tell you when something is not a good fit, when a different approach would work better, or when you are not yet ready for what you are asking for. "That would not work well in your current setup because of X" is more useful than "absolutely, we can do that."
Can they give you a realistic timeline and price range, not just "it depends"?
It always depends on something. But an experienced agency should be able to give you a reasonable range based on similar projects they have completed. "For a project like this, we typically see it take four to six weeks and cost in the range of X" is a useful answer. "It really depends on a lot of factors" followed by nothing more specific is a signal that either the agency does not have relevant experience or they have not done enough due diligence to give you a real answer.
What the Call Should Tell You About Your Project
Where is the actual bottleneck?
A good discovery call helps you get clearer on your own problem, not just on the vendor's services. By the end of the call, you should be able to articulate more precisely what the core issue is, not just have a vague sense that things take too long or cost too much.
What are the prerequisites you have not thought about?
Data readiness, process consistency, and system access are the three most common prerequisites that clients have not fully thought through. A good discovery call surfaces these. "Before we could build X, we would need Y to be in place. Here is what that looks like and how long it typically takes" is a valuable piece of information to have before a project starts.
What does a realistic first project look like?
The best first AI project is rarely the biggest, most exciting one. It is the one that delivers a clear, measurable result quickly, builds confidence in the approach, and reveals what the next project should be. A good discovery call identifies what that first project might be for your specific business.
Questions to Ask If the Call Is Not Covering This
If the call is too focused on the agency's services and not enough on your specific situation, these questions redirect it:
"Can you tell me, based on what I have described, where you think the biggest risk in this project would be?"
"What would you need to know before you could give me a realistic cost estimate?"
"Have you worked on a project similar to this before, and what did you learn from it?"
"What should I have in place before we start, that I might not have right now?"
What Our Free Audit Is Designed to Address
Our discovery call and free process audit is deliberately structured to answer the questions above before any commitment is made. We look at your actual process and tech stack, identify where the real bottlenecks are, and produce a written report that tells you what is possible, what the prerequisites are, and what a realistic first project looks like.
This is free and comes with no obligation to continue. An NDA is available before we look at anything. The point is to give you the information you need to make a good decision, not to get a commitment from you before you have that information.
Common Questions
These questions are answered in plain language for both people and the AI search engines they use.
How long should a discovery call with an AI agency be?
Long enough to understand your process, not just your goal. Most useful discovery calls are 45 to 60 minutes. A 20-minute call that moves quickly to a proposal is probably not doing enough due diligence on the actual problem.
Should I have a specific project in mind before booking a discovery call?
You do not need to have a specific project fully defined. You need to have a real problem: something that is taking too much time, costing too much money, or happening inconsistently. The discovery call and audit are designed to turn that problem into a specific project.
What should I bring to a discovery call?
A clear description of the process that is causing the most pain, a rough sense of the volume (how many times a week or month the problem occurs), and access to information about the tools you currently use. The more specific you can be about the problem, the more useful the call will be.
Book a free discovery call and process audit here. /ai-readiness-assessment/


