The Discovery Call Framework That Saves Projects

Half of failed consulting projects fail before the contract is signed. The client said one thing, I heard another, we both agreed, and three weeks in we realized we were building different projects. The discovery call is where this gets prevented. Here is my framework.

What Discovery Is Not

Discovery is not a sales pitch. It is not demoing past work. It is not convincing the client to hire you. It is a structured conversation to determine if this project is actually a good fit for both sides.

Some of my best discovery calls end with me recommending the client hire someone else. That happens when the real problem is not something I can solve well. Being honest here builds more trust than any pitch could.

The Six Questions

I ask these in order:

1. What are you trying to accomplish? (the outcome, not the output)
2. What happens if you do nothing? (reveals urgency and real priority)
3. How will you measure success? (surfaces metrics we must track)
4. What have you tried already? (avoids repeating failed approaches)
5. Who else is involved in this decision? (reveals the approval chain)
6. What is your timeline and budget? (both, not one)

Each answer shapes the proposal. Skip any question and the proposal is guessing.

Listen for the Real Problem

Clients describe their proposed solution, not their problem. 'We need a new CRM.' That is the solution they have already decided on. My job is to ask 'what is the CRM going to do that the current one cannot?' and keep asking until we hit the actual problem.

Often the real problem is not technology. It is a sales process issue, a team communication issue, or a data quality issue. A new CRM will not fix those.

Document Everything

I take notes live and email a summary within two hours. The summary includes:

• The goal in the client's words
• The measurable success criteria
• Constraints I heard (budget, timeline, team)
• My initial read on feasibility
• Next steps

This email is where scope creep gets prevented. When a request lands outside the documented goal, I reference the email and have a grown-up conversation about change orders.

The Red Flags

I walk away when:

• The client cannot articulate success
• The timeline is aggressive with no flexibility
• Budget is vague and kept vague on purpose
• Multiple stakeholders disagree on the goal in the same call

Taking a bad project costs more than saying no. The best clients respect you more when you walk away from a bad fit.

After the Call

Discovery is 60 minutes max. If I need more time, it means the client has not thought through the project enough. I suggest they do that first and come back when they can answer the six questions.