How to Run a Discovery Call

I define a discovery call as the first focused conversation with a prospect who has shown intent. The purpose is to understand their goals, surface real pains, confirm mutual fit, and agree on a next step.

In practice you gather context, ask targeted questions, quantify impact, and align on who decides what happens next.

Why this matters for an early stage team

• Pipeline quality: A clean discovery flow prevents zombie deals, where we see vague interest but no commitment. You protect your calendar and keep your sales pipeline honest by disqualifying early when there is no business case.
• Faster time to revenue: When every call ends with a concrete next step, cycle time shrinks. Small wins compound into earlier pilots and earlier cash.
• Sharper product insight: Discovery questions reveal workflow gaps and language customers actually use. Those inputs improve roadmap decisions and messaging.
• Stronger trust with buyers: Real listening beats pitching. Prospect talk time around half the call and steady back and forth create a collaborative tone.
• Repeatable founder-led sales: A lightweight agenda and a short script turn one good call into a process the rest of your tiny team can follow.
• Better next meeting show rates: Booking on the call with a clear purpose and a champion task raises attendance and momentum.

Our October survey of 312 founders tells the same story. 34% run ad hoc chats, 18% have a repeatable recorded process, 41% say the first goal is learn and test mutual fit, yet only 23% actually lock next steps while still on the call. Most founders already aim to mostly listen and ask 11-14 questions, which aligns with what we recommend.

A great discovery call is a business decision meeting. You diagnose, quantify, align, and then schedule.

By the end of this guide you will have a ready to use discovery call agenda, plenty of examples, and a copyable script and a simple scorecard you can run today and improve every week.

What does a great discovery call cover?

A great startup discovery call is a 30 minute conversation where you:

1. Arrive with a specific goal
2. Set a brief agenda the prospect agrees to
3. Diagnose pain with 11-14 focused questions
4. Quantify impact in time or dollars
5. Map stakeholders and the decision path
6. Book the follow up before you hop off the call (crucial)

Benchmarks for your calls:

• You should let the prospect talk more than you do. You’re not selling; you’re uncovering the pain points they already feel so you can show how your service solves them. Keep the spotlight on the prospect.
• 11-14 targeted questions spread across the call. In some calls, you may only have time to ask 4 questions, but that’s because the prospect is giving you a lot of depth and detail that will be critical. Bring your critical questions to the front.
• Frequent speaker switches. Quick back and forth beats long monologues.

Two-line purpose statement to keep you centered:

• Diagnose their pain points and problems to decide the next step
• Decide to schedule the next call

The TL;DR discovery call framework and template

There are many ways to prepare for a discovery call. Fortunately, the RAPID PAIN framework compresses research, agenda, questions, quantification, decision path and next steps into a simple sequence you can memorize.

RAPID PAIN discovery for founders

• R – Research: Gather five to seven bullets. Company focus, buyer persona, recent triggers, current tooling, one credible proof point, one hypothesis about pain.
• A – Agenda: Ask permission for a fast flow the prospect helps shape.
• P – ProbeMove from status quo to goals to blockers using open prompts.
• I – Implicate: Quantify cost and urgency in dollars or hours per month.
• D – Decision: Map process, people, budget range and buying criteria.
• PAIN: Prioritize, Align, Initiate, Next step: Recap the top two or three pains, tie to desired outcomes, then schedule the next step while you are still on the call.

Start with our mini script:

• “Thanks for taking the time. How does this agenda sound: I’d love to hear a quick overview of your goals, ask a few focused questions, and if it is a fit, agree on next steps. Does that work for you?”
• “When you think about [area], what outcome are you chasing this quarter”
• “Walk me through how you do it today, where does it slow down”
• “If nothing changes, what is the cost in time or dollars over a month”
• “Who else weighs in when you choose a tool like this”
• “It sounds like top pains are X and Y, and success would look like Z. If I show you a twelve minute demo focused on X and Y, can we get [stakeholder] on a call [date and time]?”

If you get tripped up and miss a few steps, just make sure to hit on these critical parts:

• Arrive prepared then listen with intent
• Quantify their pain, then earn the right to show
• End with a calendar invite, not a promise

Pre-call research in 7 minutes

I keep research lean and pointed. You do not need a dossier. You really just need signal that sharpens your questions and earns trust fast. Our October survey of 312 founders shows only 26 percent prep five or more datapoints. Here’s how to prep.

At the very least, grab five datapoints in one pass

• Industry and business model: A quick About page skim, plus the latest press snippet.
• Team size and who does what: LinkedIn headcount, plus titles inside your function.
• Role of your contact: Tenure, scope, what they own weekly. You may not find this, but at least take a look.
• Current tools: Footer badges, careers page, screenshots in docs, job posts, and using online services like BuiltWith.
• Recent trigger: Funding, launch, hiring burst, new geography, regulatory change.

You can also raise the bar in the same seven minutes

• Write two plausible pains from public signals: For example, a new territory launch plus lean team may suggest they need help with leads or attribution.
• Prepare 3 industry-literate questions: For example, for fintech, you could ask about audit trails and who signs off on data retention. Online trade blogs and publications are a great place to find this context.
• Note one relevant proof point: For example, a similar 5-person team cut user onboarding hours by 38 percent.

Workflow I use

1. Set a seven minute timer.
2. Open the company site, LinkedIn, and one news tab.
3. Type findings into your calendar invite notes so they sit on screen during the call.
4. Bold your two hypotheses and three questions so your eyes land there first.

Key takeaway. Arrive with context you can prove in one sentence.

Open strong with an agenda, context and set the tone in 60 to 90 seconds

Start confident and light. Then show you value time.

Say this

• One-line micro rapport that is relevant: “I saw the new warehouse go live in Dallas. Congrats on the opening.”
• Confirm the plan and invite adds: “Here is what I propose. Quick goals, a few focused questions, and if it is a fit, agree on next steps. Anything you want to add before we dive in?”
• Set the talk balance for success: “I will keep my part tight so you can react and steer.”

You want to make sure you talk about half of the time. Your opener primes that balance. Ask first, talk second, and keep your sentences short so the prospect jumps in.

Top discovery questions that surface real pain

Your questions want to move in a clean arc, from high-level goals and process, through bottlenecks, impact and attempts..

Grab a few questions from our discovery call question bank:

1. “What outcome would make this a win by end of quarter”
2. “Walk me through your current process step by step”
3. “Where does it stall or get reworked”
4. “How often does that happen”
5. “What have you tried to fix it”
6. “What changed that made you look again”
7. “If you leave it as is for 30 days, what breaks or slips”
8. “Roughly how many hours or dollars does this burn monthly”
9. “Who feels the pain most day to day”
10. “Who signs off when you buy tools like this”
11. “What evaluation criteria will matter most”
12. “If we solved X and Y, what would you want to see next”

It can be easy to read these questions off all at once, or even send as a pre-read, but that’s not the goal

• Space your questions. Never stack three in a row.
• Aim for frequent speaker switches. Quick back and forth keeps energy high.
• Mirror a keyword to invite depth. “You mentioned refactoring. Where does that start?”
• Log one quote per pain in your notes. You will read back those exact words later.

Quantify the pain. Turn talk into a business case with 3 prompts

Most founders told us they quantify sometimes or not yet. 21% do it regularly and it shows in their follow-ups. Here is a quick calculator you can share aloud as you type.

Prompt one. Frequency
“How many times per week does the bottleneck happen”

Prompt two. Per-incident cost
“Per incident, how long does it take or what is the rough dollar impact”

Prompt three. Rollup
“Over a month or quarter, what is the total”

Say the math back so it feels real

• “Three incidents per week at forty minutes is two hours a week. Roughly eight hours a month.”
• “At eighty dollars per hour across two people, that is around twelve hundred eighty dollars a month.”
• “Missed SLA penalties last quarter were $3,000. That is the risk if this slips again.”

Key takeaway. Always convert friction into time or money the buyer already tracks.

Get to a quick qualification without being robotic

Pick a lane based on the deal opportunity. Keep it human and crisp.

Here are some simple sentences you can say that get through the tough questions:

• Budget range: “Teams we help land between A and B per month. Are we in the right ballpark?”
• Authority: “Who else usually weighs in on a tool like this?”
• Need: “If we solved X and Y, what changes for you next month?”
• Timeline: “When do you want this live and helping the team?”

When dealing with multi-stakeholder calls or higher average customer value, use these prompts:

• Metrics: Which metric will you point to when this works?”
• Economic buyer: “Who controls the line item and signs the order?”
• Decision criteria: “What must be true to pick a vendor?”
• Decision process: “What meetings and docs sit between today and a yes?”
• Identify pain: “Which two pains are priority one for the pilot?”
• Internal Champion: “Who will drive this internally with you?”

Our survey shows 31% of small teams and startups already use mashups of questions. Write your version in a note template so you ask the same four checks every time. Consistency makes coaching yourself possible.

Key takeaway. Qualification protects everyone’s time and sets clean expectations.

Align and propose the smallest valuable next step

Wrap up with the call with appreciation, clarity and momentum. Our survey shows only 23% schedule while still on the call. Move that number for your team today.

Run a two minute recap

• “Here is what I heard. Top pains are A, B, and C.”
• “Impact over a month looks like D hours and E dollars.”
• “Success for you is X by the end of next quarter.”

Offer the smallest step that proves value

• A focused 12-minute demo on the two pains they named.
• A pilot scoping call with clear success criteria.
• A technical validation session for data, security or workflow fit.

Make it mutual so commitment travels both ways

• Add one champion task: “If you send sample data and invite ops, I will tailor the demo to your flow.”
• Confirm evaluation criteria in writing: “I will summarize the three criteria you gave me so we both measure the same thing.”

Book the next call live

• “Would Tuesday at 10 or Wednesday at 2 on your calendar work better?” If they say No, ask for them to propose a time.
• Send the invite on the call. Add the agenda and the champion task in the description. People skip meetings without agendas.
• If a second stakeholder is required, propose 2 holds while on the call so rescheduling does not stall progress.

Key takeaway. Creating next steps are valuable when they are small, specific, and scheduled.

Example discovery call scripts

Let’s walkthrough a few examples of what good discovery calls look like.

Example A. DevTools SaaS to a VP Eng with a 12-person team

• Context I bring: New feature launch this month and hiring 2 backend roles. Development hours surged in the last sprint.
• Pain surfaced: Flaky tests block deploys 2-3 times per week which burns 6-9engineering hours each week.
• Quick quantification: About 30 hours per month at $150 per hour, which is around $3,000 dollars, plus a morale hit in the on-call rotation.
• Flow I run
  1. Opener: Goal for today. Quick goals from your side. A few focused questions from me. If it lines up we agree on next steps. Good to go?
  2. Probe: Walk me through the path from commit to deploy. Where do retries pile up? How often does a flaky run block a release?
  3. Implicate: If nothing changes for the next month how many hours do you expect to lose and where does that show up in cycle time?
  4. Decision map: Who else weighs in on CI tooling and reliability fixes. Would your staff engineer join a focused follow-up?
  5. Align: Top pains I heard are triage time and blind spots in CI trends. Success for you is fewer blocked deploys this month.
  6. Next step: I can show a 12 minute demo on flaky test triage and insights? If I invite your staff engineer for Wednesday at 2, will that work?
• Key moves to steal: Quote their phrasing for the pain. Tie wasted hours to how your offering could reduce it. Invite the technical expert early.

Example B. Fintech compliance tool to a Head of Ops at a lending company

• Context I bring: New product line for SMB lending and a headcount freeze.
• Pain surfaced: Manual KYC reviews. Four full-time reviewers. SLA misses in onboarding.
• quantification: They have a 25% rework rate, which delays activations and pushes revenue out of the month.
• Flow I run
  1. Opener: I saw the new lending vertical. Congrats on the launch. My goal is mutual fit and a clean next step if the fit is real.
  2. Probe: Which steps create the most rework in KYC? What triggers a manual review?How many accounts slip past the SLA each week?
  3. Implicate: If the rework rate stays near 25%, what does that mean for activation and month-end targets?
  4. Decision map: Who owns the risk model? Who approves vendor changes? Does the CFO want to see the pass rate math?
  5. Align: Top pains I heard are manual queue spikes and missed SLAs. Success is faster activations without adding headcount.
  6. Next step: Let us run a 10 account sandbox with agreed pass or fail criteria. We invite the CFO so the math is clear. Thursday morning or Friday afternoon work?
• Key moves to steal: Define pass or fail in writing. Hold the sandbox to ten accounts. Bring finance into the loop when SLAs tie to revenue.

One more script you can copy for any call:

• “If we focus the next call on your top two pains, I can keep the walkthrough under 12 minutes and show only what matters.”
• “If this lands, would you be comfortable getting your decision maker on that call so we capture requirements in the room?”
• “Before we hang up, let us pick a time now. Tuesday 10 or Wednesday 2?”

Bottom line. Make the next step small and scheduled.

Objections and edge cases

Hesitation and tension is normal. Treat each line as a chance to realign on outcomes. Here are quick plays I rely on:

“We do not have budget”

• Align on impact: “Totally fair. Given the $3,000 per month in wasted time let us anchor on the problem first.”
• Confirm range: “Teams we help usually land between A and B per month. Does that range feel in bounds for the impact we outlined?”
• Propose a pilot tied to a win: “If we cut the wasted hours by half in 30 days, we move forward. If not, we part ways, no hard feelings. Are you open to a pilot on that basis?”

“Can you send over more info first?”

• Qualify the info request: “Yes, absolutely. To make it useful, what would you need to see to green light a pilot?”
• Clarify recipients: “Who else should be on that email so the decision path is clear?”
• Insert a time box: “I will send a one page summary and the 3 criteria we discussed. Would next Tuesday be a good day to discuss and decide on the pilot?”

“We don’t have anyone in charge of that area” (No clear buyer)

• Surface the last purchase: “When you picked your current analytics tool, who was it who signed the order and who made the short list?”
• Name the economic buyer: “Sounds like the CFO approves the line item. Would you be comfortable inviting that person to our next call so we agree on criteria and requirements together?”
• Put a hold on the calendar: “If I propose two slots that fit their schedule, can you forward the invite?”

Edge cases I plan for

• Time check at minute twenty five: “We have five minutes. I will recap pains and next step options so we land well.”
• Scope creep: “That is a related problem. Let us keep today focused on A and B so we make a clean call on next steps.”
• Security questionnaire: “I will send the SOC 2 summary and our data flow diagram after this call. Does your team require any other documents before a pilot?”

Bottom line. Objections are requests for clarity. Reply with impact and a next step.

The after-call routine that compounds learning

Five minutes now saves fifty minutes later. I treat my notes like a product that improves each week.

Where founders store insights today

In our survey, we found that small teams and founders store customer details in many different places:

• 33% store them in Google Docs or Notion
• 24% use a CRM
• 12% use specialized or industry tools

My point is to pick one system and stick to it for a month. Don’t onboard a full CRM software suite until you scale.

Minimal fields to capture

• Pains ranked one to three
• Quantified impact with the math shown
• Any asks from the prospect
• Decision path with names and roles
• Next step with date and purpose
• Champion notes with one quote in their words

Follow-up email skeleton you can paste

• Subject: Your goals, plus the top two pains we discussed
• Line 1: Quick thank you and a one line recap of the goal you shared
• Line 2: The pains in your words plus the quantified impact we calculated
• Line 3: The desired state we agreed to and the single metric that proves it
• Line 4: The next step time and place that we booked live
• Line 5: The champion task and the attachments or links you promised

Bottom line. Save the math, the process and next step.

Now, take the first step

You have everything you need to run a crisp, 30 minute discovery call that finds real problems, tests mutual fit, and lands a next step without sounding salesy.

Start with 7 minutes of prep, open with a tight agenda, ask 11-14 focused questions, quantify the cost, map the decision path, and book the follow up before you say goodbye. Use the scripts, the objection plays, and the after call routine to lock learning into your system of record.

Run one discovery call within 2 days, make one improvement to your discovery call system by Friday, and keep iterating until your discovery calling becomes your advantage.

FAQs about how to run a discovery call

What is a discovery call and when should I book one?

A discovery call is the first focused conversation with a prospect who has shown intent, and you should book it after an inbound hand raise or a qualified outbound trigger so you can diagnose goals, pain, and fit before proposing anything.

How should I structure a 30 minute discovery call?

Open with a 60-90 second agenda the prospect agrees to, spend most of the time probing goals and bottlenecks, quantify impact, map the decision path, then recap and book the next step while you are still on the call.

Which discovery questions consistently reveal level 10 pain?

Ask what outcome matters this quarter, how the work is done today, where it stalls, how often it happens, what they have tried, what breaks if nothing changes, who feels it most, and who signs off when tools are chosen.

How can I quantify impact in dollars or hours without harming rapport?

Use simple prompts that invite their math, ask frequency per week, time or cost per incident, and total over a month, then say the calculation back in plain language so the business case feels shared not imposed.

Should I discuss price on the first call?

Yes, using a range, and anchor with a realistic monthly or project budget ranges tied to the quantified impact. Confirm whether that ballpark is viable so you protect everyone’s time and avoid surprises later.

How do I uncover stakeholders and the decision path?

Ask who else usually weighs in on a tool like this, who controls the line item, what meetings and documents sit between today and a yes, and which criteria will decide the vendor.

How do I end the call so the next meeting actually happens?

Recap top pains in their words, restate the quantified impact and success definition, propose the smallest valuable next step, add a champion task, and send the calendar invite on the call with the agenda in the description.

What follow ups and artifacts should I send after the call?

Send a concise recap email with goals, pains, the math, success criteria, the scheduled next step. Aim to send this email within 2 hours of the call ending.