Discovery Call Framework
How to run effective discovery calls that uncover real customer needs and qualify opportunities
Discovery Call Framework
A well-run discovery call is the foundation of every successful deal. This guide walks you through a repeatable framework for uncovering what a prospect truly needs, qualifying whether they are a fit for Project Green, and setting the stage for a compelling demo.
Preparation
Before you pick up the phone or join the video call, invest time in understanding who you are speaking with. Research the prospect's company size, industry vertical, number of office locations, and any public information about their AV or collaboration technology stack. Look at their LinkedIn presence, recent press releases, and any prior interactions your team has had with them.
Review the account history in your CRM. If a colleague has spoken with this prospect before, read the notes so you do not ask questions they have already answered. Nothing erodes trust faster than making a prospect repeat themselves.
Prepare a short list of hypotheses about what their pain points might be based on their industry and company profile. For example, a large enterprise with dozens of meeting rooms likely struggles with visibility into device health across sites. A university campus probably deals with inconsistent AV experiences across lecture halls. These hypotheses give you a starting point, but stay open to what the prospect actually tells you.
Finally, confirm the logistics. Know who will be on the call, what their roles are, and how much time you have. If you only have 20 minutes, your approach will be different than if you have a full hour.
Opening the Call
The first two minutes set the tone for the entire conversation. Start by thanking the prospect for their time and briefly confirming the agenda. A simple opening might sound like: "Thanks for making time today. I'd love to spend the first part of our conversation understanding your current setup and what's driving your interest, and then we can talk about how we might help. Does that work for you?"
Avoid jumping straight into a pitch. The goal of discovery is to listen, not to sell. Establishing this upfront earns trust and gives you permission to ask deeper questions later.
If there are multiple people on the call, take a moment to understand each person's role and what they hope to get out of the conversation. A facilities manager will care about different things than an IT director, and both will differ from a CFO. Knowing who cares about what helps you tailor your language throughout.
Key Questions to Ask
Current Setup
Understanding the prospect's current environment is essential before you can position Project Green effectively. Ask about the number and types of meeting rooms and collaboration spaces they manage. Find out what AV equipment they use today -- video conferencing systems, displays, control panels, audio systems -- and whether they have a mix of vendors or a standardized stack.
Ask how they currently monitor the health and status of these devices. Many prospects will reveal that they rely on reactive approaches: someone reports a problem, and then IT scrambles to fix it. This is exactly the pain point Project Green addresses, but let the prospect describe it in their own words rather than leading them to it.
Dig into how many sites or buildings they manage, whether those sites are in one geography or spread globally, and whether there is a centralized IT team or distributed support staff. These details directly influence how you position the platform's multi-site and multi-tenancy capabilities.
Pain Points
Once you understand the current setup, guide the conversation toward the challenges they face. Open-ended questions work best here. "What's the biggest headache for your team when it comes to managing meeting room technology?" or "If you could wave a magic wand and fix one thing about your current AV management process, what would it be?"
Listen for recurring themes: lack of visibility, too much time spent on reactive troubleshooting, difficulty proving the value of AV investments to leadership, inconsistent user experiences across rooms, and the challenge of managing multiple vendor dashboards. These themes map directly to Project Green's value propositions.
Do not rush this section. The more clearly you understand their pain, the more precisely you can tailor the demo and proposal. Take notes and reflect back what you hear: "So it sounds like your team spends a significant amount of time just figuring out which rooms have issues before they can even start fixing them -- is that right?"
Decision Process
Understanding how the prospect makes purchasing decisions is just as important as understanding their technical needs. Ask who else is involved in evaluating and approving a solution like this. Find out whether there is a formal procurement process, an existing budget allocated for AV management tools, or whether this would need to be a new budget request.
Ask about their timeline. Are they actively evaluating solutions now, or is this an early-stage exploration? Is there an event or deadline driving urgency, such as a new building opening, a campus expansion, or a contract renewal with their current vendor?
Clarify their evaluation criteria. What matters most to them -- ease of deployment, breadth of device support, cost, integration with existing IT systems, or something else? Knowing this helps you prioritize what to emphasize in the demo and proposal.
Timeline and Budget
Be direct but respectful when discussing timeline and budget. You might say, "Do you have a sense of when you'd ideally want something like this up and running?" or "Has your team set aside budget for this type of initiative, or would we need to build a business case together?"
If the prospect is vague on budget, that is a signal, not a dead end. It may mean they need help quantifying the cost of their current approach so they can justify the investment. Offer to help with that: "We've helped other organizations calculate the true cost of reactive AV support -- would it be useful if we put together a quick analysis for your environment?"
Understanding timeline and budget early prevents surprises later and helps you prioritize your pipeline effectively.
Active Listening Techniques
Discovery is only as good as your ability to listen. Resist the urge to jump in with a solution the moment you hear a pain point. Instead, let the prospect finish their thought, then reflect it back to confirm understanding. Phrases like "It sounds like..." or "If I'm hearing you correctly..." show that you are engaged and help the prospect feel heard.
Take written notes during the call rather than relying on memory. Note not just what they say but how they say it -- if a particular pain point comes with visible frustration or urgency, that is a strong buying signal worth flagging.
Ask follow-up questions that go one level deeper. If a prospect says "We have trouble keeping our rooms working," ask "Can you walk me through what happens when a room goes down? Who gets notified, how long does it typically take to resolve, and what's the impact on the people trying to use that room?" This depth of understanding is what separates a good discovery call from a great one.
Pay attention to the language the prospect uses. If they talk about "uptime" and "SLAs," they are thinking like an IT operations team. If they talk about "user experience" and "employee satisfaction," they are thinking like a workplace experience team. Mirror their language in your responses and in the demo.
Qualifying the Opportunity
Not every prospect is a fit, and that is okay. Use the information you have gathered to assess whether this opportunity is worth pursuing. Consider the following qualification criteria: Does the prospect have a genuine pain that Project Green solves? Is there a decision-maker engaged or accessible? Is there budget or a realistic path to budget? Is the timeline reasonable?
If the answer to most of these is yes, move the conversation forward with confidence. If key elements are missing -- for example, no budget and no urgency -- be honest about it internally and adjust your investment of time accordingly.
A well-qualified pipeline is more valuable than a large one. It is better to spend your energy on ten well-qualified opportunities than fifty that go nowhere.
Next Steps and Follow-up
Never end a discovery call without agreeing on clear next steps. If the conversation went well, propose a tailored demo as the logical next step: "Based on what you've shared, I think a focused demo showing how Project Green handles multi-site monitoring and proactive alerting would be really valuable. Can we schedule that for next week?"
Send a follow-up email within 24 hours that recaps what you heard, confirms the next steps, and includes any materials you promised. This shows professionalism and keeps momentum going.
If additional stakeholders need to be involved in the next meeting, ask the prospect to introduce you or to include them on the calendar invite. The sooner you engage the full decision-making group, the shorter your sales cycle will be.
Document everything in your CRM immediately after the call while details are fresh. Future you -- and your colleagues -- will thank you.