Agency Discovery Call Questions for Better Sales Calls

A list of questions won't do the listening for you

Agency founders often ask for better discovery questions when the real problem is what they do with the answers.

They ask why the prospect booked. The prospect mentions a failed supplier, inconsistent enquiries, and an internal disagreement. The founder says, "Makes sense," then asks the next question on the list.

There was plenty to work with. They just didn't use it.

Good discovery establishes what is happening, what has been tried, why the change matters, and whether your work fits. Ask one question, hear the answer, and follow the part you still need to understand.

What made this worth a conversation?

Start with the reason for the meeting.

A prospect may have reached a genuine decision point. They may have been referred. They may have accepted an outbound invitation out of curiosity. Don't assume all three are ready for the same conversation.

Ask what prompted them to look at the issue now. If they mention a specific event, explore it.

"What changed after that?"

If they are simply gathering information, find out what they want to understand. You can still be useful without pretending they described an urgent buying problem.

This also helps you check whether the booking promise and the call match. A sales process starts badly when the prospect expects something different from what you intend to discuss.

What is happening at the moment?

Get the current process in ordinary language.

For a marketing agency prospect, ask how enquiries arrive and what happens to them. For a web project, ask what the current site is failing to do. For a content engagement, ask what the content is meant to achieve and what is happening instead.

Don't ask every operational question you can think of. Follow the part relevant to the service.

You should be able to explain the current situation back to the prospect without replacing it with your preferred diagnosis. If you cannot, you probably need another question before recommending work.

Can you talk me through a recent example?

Examples make vague descriptions easier to inspect.

"The leads are poor" becomes a specific enquiry, a response, a call, and an outcome. "The agency was unresponsive" becomes a particular request and what happened after it.

You may discover the buyer's interpretation is accurate. You may discover something different. Either way, you have more than a label.

An illustrative follow-up is, "What happened with the last enquiry that you thought should have become a client?"

Let the person describe the sequence. Resist the urge to finish the story for them because you have heard a similar problem before.

What have you already tried?

Ask what they did, what they expected, and what happened.

Those are separate questions. A buyer saying a campaign failed does not tell you whether the targeting was unsuitable, the offer was unclear, the measurement was weak, or the team did not follow up.

Avoid criticising the previous supplier without evidence. Your recommendation should stand on what you understand, not on making somebody else look incompetent.

This part of discovery also reveals concerns that may return later. If a previous engagement involved poor communication, ask what the buyer would need to see differently this time. Don't wait until the end to hear that they are worried about another disappointing supplier.

What does the problem prevent you from doing?

Understand the consequence in the buyer's terms.

It could be unreliable planning, wasted staff time, unused capacity, or difficulty taking on the next stage of work. Not every consequence needs to be expressed as revenue.

If numbers are relevant, distinguish measured figures from estimates. Don't take a rough answer and turn it into a precise loss claim. Don't assume every missed opportunity would have become a client.

The question is whether the issue matters enough to address, not how large a number you can attach to it.

A buyer may decide the problem is tolerable. That can be a legitimate conclusion.

Why hasn't it changed already?

Ask this with curiosity, not accusation.

The answer may reveal competing priorities, previous failed attempts, limited resources, or uncertainty about what to do. It may also reveal that the prospect's team is unable to support the proposed work.

You need to understand those conditions. Otherwise you may recommend the same kind of engagement they previously could not implement.

The FSI course material emphasises commitment to change before presenting a solution as if agreement is automatic. A prospect can want the outcome and still have a real obstacle to doing the work.

Explore the obstacle before negotiating around it.

Who else needs to be involved?

Ask how the decision would happen, not just whether the person is authorised to sign.

Someone else may need to assess delivery, budget, technical requirements, or the effect on their team. Find out what they need to understand.

If that person should join a conversation, discuss it early. Don't wait until the proposal is written to discover that the actual concern belongs to someone you have never met.

At the same time, ask what the person on the call thinks. Their support and the wider approval process are different things. A vague reference to a colleague should not make you stop understanding the contact's own position.

What would need to be true for this to work?

This question tests the practical conditions of the engagement.

Can the team provide approvals? Is the relevant data available? Is there capacity to handle the work? Are the expectations compatible with the service?

For an illustrative appointment-setting engagement, the buyer might need someone available to take meetings and follow up promptly. For a creative project, timely decisions and access to source material may be essential.

Discuss those responsibilities before describing the service as easy. A sale is not improved by leaving the difficult part of participation unexplained.

Do you think this is the right work?

After discovery and the recommendation, check whether the prospect agrees with the proposed direction.

If they hesitate, ask what doesn't fit. Don't immediately reduce scope or offer concessions.

This is the commitment-before-negotiation distinction. Establish whether the buyer wants the appropriate change, then discuss the terms of doing it. It does not mean hiding price or demanding a yes before giving commercial information.

The objection handling guide explains how to separate disagreement about the work from concerns about timing, cost, or risk.

What not to do with these questions

Don't read them as a script. Don't ask several together. Don't use them to force a predetermined conclusion.

In the FSI transcripts, one repeated correction is to stop adding possible answers before the prospect has responded. If you ask a question and immediately suggest three explanations, you may learn which option is easiest to agree with rather than what is actually happening.

Acknowledge the answer. Ask the next useful question. Explain why a detail matters when the connection isn't obvious.

The buyer should feel that you are following their situation, not processing them through a questionnaire.

Use the recording to improve the next question

After a call, find one answer you moved past too quickly. Pause there and ask what was still unknown.

Could a recent example have helped? Did you need to understand a previous attempt? Was an absent decision-maker mentioned? Did you start pitching because you recognised a familiar symptom?

Practise the question you should have asked. Keep it short enough to say naturally.

For the wider sequence, read how to structure an agency sales call. Discovery is not about having the longest list. It is about understanding enough to make a recommendation you can defend.