Discovery call: what it is, how to run one, and how to hold it in the lead's own language (2026)

A discovery call is the first scheduled conversation between a seller and a prospective customer, held to establish whether the prospect's problem is one the seller actually solves — before anyone demos anything. It is a listening exercise with a decision at the end: is there a fit, and if so, what is the next step?

This guide covers the call itself — what it is and isn't, a 30-minute agenda, the questions that do the work, a short script, and what should happen afterwards. The last section covers a case most guides skip: the lead who would rather answer in Portuguese, Japanese or Polish than in your language. The setup for that is three steps, uses the calendar you already have, and produces the call write-up on its own.

What a discovery call is — and what it isn't

A discovery call sits between the first contact (an inbound form, a reply to an outreach email, a referral) and the demo. Its output is a decision about fit, in both directions:

• For the seller: does this prospect have a problem we solve, the means to buy, and a reason to act now?
• For the prospect: does this vendor understand our situation well enough to be worth a second meeting?

Three things a discovery call is not:

• Not a demo. A demo shows the product; discovery finds out what to show. Running them together is the most common way to spend forty minutes presenting features the prospect never needed.
• Not an interview. The prospect is not being examined. The questions are about their situation, and a good call has the prospect talking for most of it — a seller who talks for the first several minutes has already lost the structure.
• Not a pitch. If the prospect leaves knowing everything about your product and you leave knowing nothing about their problem, the call ran backwards.

Other names for the same meeting: qualification call, intro call, exploratory call, fit call, first call. In most sales processes they refer to the same thing — the first structured conversation before a demo or proposal.

How to run a discovery call: a 30-minute agenda

Thirty minutes is enough for discovery when the time is planned. A structure that works:

Two rules keep the agenda honest. Ask before you tell: the product does not come up until you can describe their problem back to them in their words. End with a date: "I'll send some information" is not a next step; "demo on Thursday with your ops lead present" is.

Discovery call questions

The questions below are grouped by the agenda block they belong to. Fifteen is more than one call needs — pick the ones that fit and let the answers lead.

Situation

1. Walk me through how this works today, start to finish.
2. Who is involved when this happens — which teams, which roles?
3. What tools are you using for it now?
4. What made you take this call?

Problem and impact

5. Where does the current process break down?
6. How often does that happen?
7. What does it cost you when it does — time, money, customers, people?
8. What have you already tried to fix it?
9. What happens if nothing changes for another year?

Decision

10. Who else would need to be involved in a decision like this?
11. How did you last buy something in this category — what did that process look like?
12. Is there a budget attached to solving this, or would one need to be found?
13. What is the timeline you're working with — and what's driving it?
14. What would make this a "no" for you?

Next step

15. If what I've described sounds right, what would be a useful next conversation, and who should be in it?

A short discovery call script

A script is not a text to read out; it is the set of sentences that carry the call from one block to the next.

Opening (agenda and permission):

"Thanks for making the time. I'd like to spend most of this call understanding how things work on your side and where they break — and at the end I'll tell you honestly whether I think we can help. If we can, we'll pick a next step; if not, I'll say so. Does that work?"

Transition into the problem:

"You mentioned that [situation]. Where does that go wrong most often?"

Getting to impact:

"When that happens, what does it actually cost you — is it hours, is it a missed deal, is it someone's weekend?"

Transition into the decision:

"If you decided this was worth fixing, who else would need to be in the room?"

Close:

"Here's what I heard: [two sentences in their words]. Based on that, I think this is / isn't something we solve well. The useful next step would be [demo / proposal / a call with X]. Can we put that on the calendar now?"

What happens after a discovery call

Three things, in this order:

1. The write-up. What the prospect said about their situation, the problem and its cost, who decides, the timeline, and the agreed next step — in their words where possible. This is the document every later conversation refers back to.
2. The follow-up email, the same day. It restates the write-up in a few lines and confirms the next step with its date. (A separate guide covers the sales follow-up email, with templates.)
3. The CRM record. The write-up lands on the prospect's record, so the colleague running the demo next week reads it there instead of asking you.

In most teams the first and third steps are manual, which is why they are often skipped. The setup in the next section makes both of them a by-product of the call.

Discovery calls with international leads: each side in its own language

The agenda above assumes both sides share a working language. With an international pipeline that is often not the case — or it is the case on paper, while the prospect's answers to "what does this cost you?" come out shorter and vaguer than they would in the language they think in. Discovery runs on the quality of those answers.

The following setup lets the prospect answer in their own language and you ask in yours, without changing anything else about the call. It has three steps and uses the calendar you already run on.

Step 1 — A booking page in your own calendar

Google Calendar's appointment schedules produce a public booking page; a prospect picks a slot and it lands on your calendar. Google documents that a personal Google Account or a Workspace account can create one, that the schedule has a description which "displays: on your booking page, in confirmation emails, in event descriptions", and that the conferencing options are "Google Meet video conferencing, in-person meeting, phone call, none / to be specified later" — with the note that "to use a third-party conference service, select None / to be specified later" (checked September 2026).

Any scheduler with a description field that travels into the confirmation email works the same way.

Step 2 — One reusable InterMIND link in the description

Create one ad-hoc meeting in InterMIND and copy its link (it looks like intermind.com/abc-def-ghi). Paste it into the booking page description. From then on it is in every confirmation and calendar invite the scheduler sends.

One link serves every discovery call, permanently: when a call ends, the next prospect who opens the same link starts a fresh session on it. Two properties make the link safe to publish:

• Nobody walks in. An anonymous visitor lands in a waiting room and joins only when you approve them; there is no setting that turns that approval off, and an unanswered request is denied automatically after 5 minutes.
• Nothing carries over. Ad-hoc rooms delete their chat when a session ends, and keep only the latest session's recap — one prospect's call leaves nothing for the next one to find.

Step 3 — Each side picks a language

The prospect opens the link in a browser, types a name and picks their language; you pick yours. From then on each participant hears the other in their own language, and chat messages are translated per participant too. Voice and chat cover the same 23 languages: English, Russian, Spanish, French, German, Italian, Portuguese, Polish, Dutch, Czech, Hungarian, Danish, Finnish, Icelandic, Norwegian, Romanian, Swedish, Ukrainian, Japanese, Korean, Turkish, Chinese (Simplified) and Hindi.

The prospect installs nothing, creates no account, and pays nothing — only the host's side of the room carries a plan.

What you get afterwards

When the session ends, InterMIND generates a recap — a title, an overview, key takeaways, sectioned points with timestamps, action items, open questions and topics — and emails it to the registered participants. That is the write-up from the section above, produced without anyone writing it. Add your CRM's inbound address to the meeting's Recap copy field and the same email is BCC'd there, landing on the prospect's record because the participants stay in the To field — the address the CRM matches against.

One honest boundary: a prospect who joined without an account receives nothing after the call — no recap, no history. There is no delivery channel for them. Your follow-up email is the record they get, which is one more reason to send it the same day.

Where the limits are

The constraints that decide whether the free plan is enough for a discovery pipeline:

The window is a rolling 30 days, and the voice-minute pool belongs to the host's account — four 30-minute discovery calls use up Basic's 120 minutes. A team running discovery weekly is on Pro from the start.

FAQ

What does a discovery call mean? A discovery call is the first scheduled conversation between a seller and a prospective customer, held to find out whether the prospect's problem is one the seller solves — their situation, what breaks, what it costs, who decides and when. It ends with a decision about fit and, if there is one, a dated next step, usually a demo.

Is a discovery call an interview? No. An interview examines the person; a discovery call examines the situation, and the prospect does most of the talking. The seller's job is to ask, listen, and at the end say plainly whether there is a fit. If the prospect leaves feeling tested, or the seller leaves having presented rather than listened, the call was something other than discovery.

What is another way to say "discovery call"? Qualification call, intro call, exploratory call, fit call or first call. Teams use them interchangeably for the same meeting: the first structured conversation before a demo or a proposal.

How long should a discovery call be? Thirty minutes is enough when it is planned — roughly three minutes for agenda and permission, nine for the current situation, eight for the problem and its cost, six for the decision process, and four to summarize and agree the next step. Calls run long when the demo creeps in; keep the product out of it until you can describe the problem back in the prospect's own words.

What happens after a discovery call? Three things: a write-up of what the prospect said, a same-day follow-up email restating it and confirming the next step with a date, and the write-up landing on the prospect's CRM record so the next person in the process reads it there. With a room that generates the recap and BCCs it to the CRM, the first and third steps happen without anyone writing them.

Can I run a discovery call when the lead prefers a different language? Yes, without an interpreter and without changing the call. Put one InterMIND meeting link in your booking page description; the prospect joins from the confirmation email, picks their language, and you pick yours. Each side hears the other in their own language across 23 languages, and the recap arrives in your inbox afterwards.

Does the prospect need an account or an app to join? No. They open the link in a browser, type a name, pick a language and wait for you to approve them. Nothing to install, no account to create, nothing to pay — the host's plan covers the room. A prospect who joins without an account does not receive the recap, so the follow-up email is the record they keep.

Try it

• Start a meeting and copy its link — the link you would paste into a booking page description.
• Try the live demo — hear the translation before you set anything up.
• See the multilingual support setup — the same three steps, applied to customer calls.
• See the book-a-demo flow — the same setup behind a "Book a demo" button, with our own page as the example.

Sources: Google Calendar Help, Create an appointment schedule — account eligibility, where the description displays, and the conferencing options including "None / to be specified later" for third-party services. checked September 2026.