# Discovery call: six questions and one of three outcomes https://salesbond.app/blog/discovery-call-small-team-pipedrive/ Published: 2026-10-05 · Updated: 2026-10-26 A discovery call is the first real conversation with a buyer, and its only job is a decision: does this person have a problem we solve, and what happens next. It ends with one of three outcomes. The deal moves forward with a dated next step, it is paused with a date and a reason, or it is closed as not a fit. The outcome is written into the CRM before the rep opens the next tab. If the call ended and the deal looks the same as it did that morning, discovery didn’t happen. A meeting did. ## What a discovery call is, and what it is not Tuesday, 11:00. Noor, one of four reps in a team with no SDR and no sales ops, has a calendar entry that reads “Intro call, Halvers”. The call happens and runs long. On Wednesday the manager, Ruth, opens the deal in Pipedrive: stage “Contact made”, a call activity marked done, and a note that says “good call, interested, sending info”. Nothing else changed. Is Halvers qualified? Ruth can’t tell. By Friday, neither can Noor. That was a first call. A discovery call is the same thirty minutes with a different ending. It isn’t a demo; you show nothing. It isn’t a questionnaire either, although most guides on this topic lean that way. Pipedrive’s blog offers [63 sales discovery questions](https://www.pipedrive.com/en/blog/sales-discovery-questions), HubSpot splits its list into [set the stage, qualify, disqualify and establish next steps](https://blog.hubspot.com/sales/discovery-call-questions), Salesforce packs the method into the [POWERFUL mnemonic](https://www.salesforce.com/blog/sales/what-is-a-discovery-call/), and Revenue.io breaks the call into [seven components](https://www.revenue.io/blog/the-ultimate-sales-discovery-call-guide). All of them are worth a read. None of them decides anything on its own, because a question list has no ending. Discovery is finished when the rep can say which of three outcomes applies, and the deal shows it. What goes into the note after the call is a separate, shorter question, and we’ve covered [the minimum a sales call note needs](https://salesbond.app/blog/sales-call-notes-minimum/) already. Here we care about the decision. It lives in fields, not in prose. ## How we run the thirty minutes The order matters more than the wording. Two minutes of context, about twenty of questions, five of saying the outcome out loud to the buyer, and the rest for writing while it’s still fresh. Reps who leave the writing for “after lunch” produce the Halvers deal above. The six questions we actually ask, in this order: 1. What made you take this call this week, rather than a month ago? 2. What does that cost you today? Hours, money, lost deals, people who complain. 3. What have you already tried, and why didn’t it stick? 4. If this gets fixed, who notices first, and who has to sign off on buying anything? 5. What would make you say no to us? 6. If we turn out to be a fit, what is the next step on your side, and by when? Question two is where the buyer names the problem in their own words, and those words go into the note verbatim. If the answer comes back vague, ask one [probing question](https://salesbond.app/blog/probing-questions-sales-calls-answer-log-crm/) and write the follow-up answer into the note in the words the buyer used. Question four finds the decision. Question six produces the date. Question five is the one most teams skip, because it feels like inviting the objection. It is inviting the objection. In a first call that’s exactly where you want it: cheap to hear now, expensive to discover at proposal. If the buyer asks for price before you get to question five, here is [what to say when price comes up early](https://salesbond.app/blog/first-call-price-question-pipedrive/). If your team runs a named method, the questions map onto it without much effort. We have written separately about [SPIN in Pipedrive](https://salesbond.app/blog/spin-selling-pipedrive/), [Gap Selling fields](https://salesbond.app/blog/gap-selling-pipedrive/), [MEDDIC for small teams](https://salesbond.app/blog/meddic-small-sales-teams-pipedrive/) and [BANT](https://salesbond.app/blog/bant-sales-pipedrive/). None of them changes the ending of the call, only the route to it. The last five minutes are the part that makes it discovery. The rep says what they heard and what they think should happen: “Here is what I understood. Your invoicing runs on two spreadsheets, your controller is the one who signs, and you want this decided before the new fiscal year. I suggest a working session with the controller on the 14th.” Or, just as valid: “Honestly, I don’t think we are the right fit for this, and here is why.” The buyer corrects or agrees. Either way the outcome is now spoken, not inferred. A word on tooling. Pipedrive’s Nova records and transcribes meetings and drafts CRM updates in deals, people and organizations ( [Pipedrive product updates, Nova release, September 2026](https://www.pipedrive.com/en/product-updates)). That helps with the note. It doesn’t help with the decision, because a transcript holds everything the buyer said and no verdict of it’s own. The rep still picks one of three. ## Three outcomes, and how each one looks in Pipedrive Every discovery call we run ends in exactly one of these. Not two, not “let’s see”. **Forward.** The buyer named a problem we solve, we know who decides, and there is a next step with a date. In Pipedrive that is a stage change (out of “Contact made” into whatever your pipeline calls the qualified stage) plus a scheduled activity for the agreed date. The [next activity](https://salesbond.app/blog/pipedrive-next-activity/) is the part people forget. A stage change without a dated activity is a promise to nobody. **Paused, with a date.** The problem is real, but the timing isn’t. A budget that opens in spring, a system migration that has to finish first, a controller on leave until the 20th. A contract with the current vendor is the same kind of pause, so [ask for the contract end date and the notice deadline](https://salesbond.app/blog/incumbent-contract-end-date-pipedrive/). The wrong move is to leave the deal in the second stage for four months, where it sits in every pipeline report as if someone were working it. For a short pause, one activity dated to the agreed day, with the reason in its subject, is enough. For a long one, convert the deal back into a lead so the pipeline count stays honest. Pipedrive carries the deal’s fields, activities (done and scheduled) and notes over to the lead; the deal’s history and labels stay behind ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)). That means the follow-up date survives only if you put the activity on the deal before you convert it. We’ve written about [sending a deal back to leads](https://salesbond.app/blog/pipedrive-convert-deal-to-lead/) in more detail. Either way the deal no longer looks like a live opportunity to whoever runs the forecast. **Not a fit.** The buyer has no problem we solve, or the person who decides is out of reach and the buyer can’t bring them in, or the price conversation ended the way it ends when there is no budget. Mark the deal lost, with a reason you can count later. Out of the box, Pipedrive takes lost reasons as free text; a user with the Deals admin permission can switch on predefined lost reasons, so reps pick from a fixed list ( [Pipedrive: lost reasons](https://support.pipedrive.com/en/article/lost-reasons)). We’d switch it on and keep the list short: “problem we don’t solve”, “no reachable decision-maker”, “budget below floor”, “timing, no date”. Free text feels more honest and is useless in a quarter, because nobody can count it. There’s more on setting that list up in [lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/). If you already use a “No decision” reason for [deals that stall without an answer](https://salesbond.app/blog/no-decision-deals-pipedrive/), check whether “timing, no date” is the same reason under another name. One list, one wording. Notice what the three outcomes have in common. Each one is a stage, a dated activity or a lost reason, and all three can be filtered. A note can’t. That is the the whole reason we keep the outcome out of the note. To see the outcome in one place, add a custom field on the deal called “Discovery outcome” with three options: Forward, Paused, Not a fit. Pipedrive supports custom fields on deals and lets you filter by them, and leads use the same fields as deals, so a “Paused” value survives the conversion to a lead ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). Blank means the call hasn’t been decided yet, and blank is the value the manager looks for. If your team already records call results in the activity’s Outcome field, that works too; we wrote about [the activity Outcome field](https://salesbond.app/blog/pipedrive-activity-outcome-field/) separately. The point is the same: one field, three values, filterable. ![Diagram: a discovery call ends as forward, paused or not a fit, and no recorded outcome means discovery is not finished.](https://salesbond.app/wp-content/uploads/2026/10/discovery-call-small-team-pipedrive-2.png) ## Disqualifying after discovery is finished work, not a failure Most reps in a small team hate this outcome, and most managers accidentally train them to. If the Friday pipeline review celebrates deals moving forward and frowns at deals marked lost, reps learn to push everything forward and let the pipeline sort it out later. Later costs more. Clari’s guide makes the point from the forecasting side: weak discovery shows up as forecast risk, deals that look alive and are not ( [Clari: sales discovery call questions](https://www.clari.com/blog/sales-discovery-call-questions/)). For a team of four with no analyst, it shows up as something simpler. A rep’s Tuesday afternoon goes to a buyer who was never going to buy. So “not a fit” after a discovery call counts as a result in our team, and we say so out loud. A rep who closes a fair share of first calls as not a fit is doing discovery. A rep who moves every first call forward is doing calendar. When to say it on the call: - Twenty minutes in, the buyer still can’t name what is wrong in their own words. Curiosity is not a problem. - The problem is real, and we don’t solve it. Say who might, if you know. - The person who decides isn’t on the call, the buyer can’t say when they could be, and the buyer doesn’t hold the budget either. - The honest answer to question five is a dealbreaker you can’t change, like a required integration you don’t have or a price floor they won’t cross. The sentence itself can be short. “I don’t think we are the right fit for this, and I’d rather tell you now than after a proposal. The reason is X.” Buyers remember that. Some of them come back a year later with a different problem, and they come back to the rep who didn’t waste thier time. The manager’s job here is to never count a “not a fit” against the rep. Count the deals with no outcome instead. ## A weekly filter: first call done, no outcome Fifteen minutes, once a week, one saved filter. This isn’t a call review and it isn’t a grading exercise; if you want to score how the call went, that’s [a different routine with a scorecard](https://salesbond.app/blog/sales-call-review-scorecard/). This filter asks one question per deal: which of the three? The filter in Pipedrive, built on the custom field above: - Discovery outcome is empty - The deal is open and sits in your first-call stage or the one right after it - The deal was created more than a week ago What comes back is the set of deals that should have had their first call by now and still carry no decision. Most of them had the call and nobody decided. A few never had the call at all, which is worth a sentence too. Ruth goes through the list with each rep, one sentence per deal: “Halvers, which of the three?” If Noor answers “forward, working session on the 14th”, Ruth sets the field and the next activity on the spot, or Noor does. If Noor answers “paused, their migration finishes in January”, same thing, with a date. If the answer is “I’m not sure”, that’s the useful case. The call wasn’t discovery, and the fix is a second, shorter call that asks only questions four and six. Week to week the list should shrink. If it doesn’t, the field is being skipped, and the honest fix is to stop relying on willpower. Since the July 2026 Activities release, an admin can require the Outcome, Priority or Note field before an activity can be marked done ( [Pipedrive product updates, Activities release, July 2026](https://www.pipedrive.com/en/product-updates)). That moves the decision to the moment the call activity is closed, not the end of the week. We have a longer piece on [which fields are worth making required in Pipedrive](https://salesbond.app/blog/required-fields-pipedrive/), the short version is that one required field at the right moment beats five optional ones. What you don’t need for any of this: a transcript of every call, a twenty-field qualification form, or a score from one to ten on how the call felt. A small team has no one to maintain that, and a form nobody maintains is a form everybody skips. Noor’s Halvers deal, by the way, ended as “Paused, January”. Ruth found out at the weekly check, in about forty seconds, because the field was blank and she asked. That’s the first step for your team too: add the field this week, save the filter, and next week ask “which of the three?” about every deal on it.