discovery call

Also called: discovery meeting

An early conversation in which the seller mostly asks and listens: what problem the company has, what it costs them, who decides and who pays, and what happens next. Its goal is to learn whether there is a real deal, not to present the product.

A discovery call is an early conversation in which the seller mostly asks and listens. Its job is to find out whether there is a real deal: a problem the company is willing to pay to solve, a person who owns the budget, a date that comes from the buyer's own process, and a next step the buyer agrees to. Presenting the product comes later, and only for the problems the call uncovered.

Good discovery questions are about past events and their cost, not opinions about the future. "Tell me about the last time this went wrong" produces facts you can check; "Would your team like better English?" produces a polite yes that predicts nothing. Add questions about how the company buys: whose budget the purchase comes from, who else must agree (operations, IT security, legal, procurement) and how a similar purchase went last time.

A discovery call ends with a dated next step that has an action on the buyer's side, such as a demo with the operations director on a set day or an introduction to IT security. "Send me a proposal and I'll pass it around" is not a next step: the proposal would be priced before anyone knows what the problem costs and read without the seller in the room. Write the answers down; they become the qualification notes, the demo plan and later the proposal.

Example

Klasna for Teams sells corporate English at 800 UAH a lesson. In the first call with Pavlo, the HR and learning manager at the logistics company Veloria, a pitch-first opening ("hundreds of tutors, an AI practice partner…") ends with "send me something to read". The rerun starts with a past event instead:

Question	What Veloria said
The last time an English call went wrong?	A dispatcher misread a Polish carrier, the truck waited at the border, Veloria paid a penalty
How often?	A couple of times a month, according to Stepan, the operations director
Whose budget?	Pavlo's training budget for small courses; this size needs Yaryna, the finance director
By when?	2027 budgets close on 15 December
Who else?	Stepan for shifts, IT security for any new app

The next step: a demo for Pavlo and Stepan on Thursday 3 December, and IT's questionnaire requested the same day. Compare Cobalt: a positive call on 18 November, a proposal on 20 November, a "just checking in" on the 27th, silence by 9 December. The notes show why: nobody asked who approves the budget.

Common mistakes

Pitching in the first minute. The buyer learns nothing new about you and you learn nothing about them; "send me something to read" usually follows.
Asking about the future. "Would you use…?" invites politeness. Ask about the last time the problem happened and what it cost.
Skipping the money questions. Without knowing whose budget it is and when it closes, a friendly call is not a qualified deal.
Inventing urgency. Use dates from the buyer's own process, such as a budget deadline or a contract notice period, never a deadline you made up.
Ending without a dated step. "I'll send a proposal" is a hope; a meeting with named people on a set day is a step.

Learn it in the course

The discovery call: ask before you pitch · Why a call that opens with a pitch ends with "send me something to read", and how to run one that finds the problem, its cost, the budget owner, the buying process and a dated next step.
Case: a stalled deal, write the next three messages · Cobalt's learning lead went quiet after the first call. Find out why the deal stalled, then write three honest messages: one that helps the champion, one that asks for the process, and one that closes the loop kindly.
From founder-led selling to the first sales hire · Write down what the founders know, agree shared definitions and a service agreement between marketing and sales, choose and onboard the first salesperson, and use AI tools with human review and care for data.