Discovery Call

For a long time the first meeting started with the product. Forty slides, company history through feature list, and questions squeezed into the last ten minutes. The seller left feeling the meeting went well because everything got said. The buyer left without having said anything.

What happened afterward was usually the same. Twenty minutes in, someone says "we don't really have that problem," and the remaining slides stop meaning anything. They get shown anyway, because the deck took work, and the proposal sent the following week solves a problem the buyer doesn't have. Sort the lost deals at the end of a quarter by reason and half of them land under "no need" — discovered too late, in the one meeting where finding out was still possible and the seller spent it talking.

The discovery call reverses that order. Explanation moves later and the first slot goes entirely to asking. Learn the situation first and there's half as much to show, and that half maps onto a problem the buyer described in their own words an hour earlier.

The talking ratio is inverted. Roughly 30 percent seller and 70 percent customer means the call worked; the reverse means an introduction happened instead. Thirty to forty-five minutes is typical, with one or two people on each side. Larger rooms make it harder for the person doing the actual work to admit what's broken, and it's their account of the process you came for.

The questions come down to four.

1. How does this job get done right now? Ask about the process, not the tool. "We use a spreadsheet" isn't enough; "every Friday the team lead merges six sheets by hand" is the answer the next question hangs on.
2. What does that cost, in time or money? Get a number where you can. Four hours a week becomes sixteen hours a month, and that figure is the reference point when the price comes up later.
3. By when does this need to be fixed? Without a deadline, discomfort alone doesn't produce a decision. "The team doubles by June" or "our current contract ends in September" gives the deal a clock.
4. Who makes this call? The person in the meeting usually isn't the one who signs, so the budget holder and the approver get identified here rather than guessed at three weeks later.

Write down what you heard in the customer's own words. "Collaboration is inefficient" tells the next reader nothing, while "the team lead merges six sheets every Friday" is the opening screen of the product demo.

The next stage is the demo, and three things have to be true before it's worth booking. The problem described is one this product actually solves, budget and timing exist, and the next meeting has a date and a named attendee list. Miss any one of them and the demo turns into a second discovery call.

The third is the one most often skipped. A friendly call ends easily with "I'll put something together and send it over," and from then on every follow-up comes from one side only. Getting Thursday at two, with the decision maker on the invite, before hanging up carries the same conversation much further.

Not forcing a deal forward is also part of this stage. If budget doesn't exist until next year, take the deal off the board and write down the date to come back. Leaving it open inflates the total and makes the sales forecast read richer than reality. The more deals get honestly set down here, the more the remaining ones can be trusted. A pipeline of eight real deals forecasts better than one of twenty where half are waiting on a budget nobody has approved.

"Discovery is booked for next week. I'll schedule the demo after that."

We don't know their situation yet, so there's no basis for deciding what to show.

"Budget never came up in discovery and you already sent a proposal?"

The conditions for advancing weren't met and the stage moved anyway.

"We talked for 25 of the 30 minutes on that call."

A diagnosis that the asking meeting turned into a pitch, usually followed by rebooking it.

At Pagedeck, Sofia joins a first call without turning on screen share. She asks how documents get passed around today, where versions collide, and who loses how many hours to it, and writes the answers down. The urge to explain how the product fixes it always arrives partway through; answering in a single sentence and returning to the questions is the skill this meeting takes.

After the call she sends the three problems she heard back to the buyer before anything else. It confirms she understood correctly and it settles what the demo will cover. When the reply says "the second one works a bit differently on our side," that correction is what decides whether the demo lands.

Many people treat it as a rapport-building meeting. It's a first encounter and it runs like an easy conversation, so the impression is fair. But the output of this slot isn't goodwill, it's a handful of facts. Current process, cost, deadline, decision structure — come back with none of them and the call has to happen again no matter how warm it felt. Deals held together by atmosphere pile up in the pipeline until there's no way to tell which ones are real, and every one of them still gets counted in the quarterly number.

Using it to take down a feature wish list is the other frequent mistake. The customer raises features first, so writing them down looks diligent. The trouble is that a requested feature is already the customer's own solution, and accepting it as given means never hearing what's actually broken. Worse, the list hardens into a promise. A rep who collected five features the product doesn't have will say in the next meeting that a couple of them are coming soon, and the deal that closes on that sentence lands three months later on the customer success manager (CSM), the person responsible for making the customer succeed with the product.