A SaaS discovery call script for the buyer who already uses something for that

The discovery call is booked. Thirty seconds in, the buyer says the sentence every SaaS rep knows by heart: "We already use something for that." Most reps respond by explaining what makes their product different, and that is the moment the call turns into a demo nobody asked for. A SaaS discovery call script has exactly one job. Find out whether the thing they already use is actually working, and whether the pain of keeping it is bigger than the pain of switching. Everything else is a pitch.

In our experience the deal is rarely lost to the competitor. It is lost to nothing: to no decision, to a budget cycle that closed, to a champion who went quiet in month two. Discovery is where you find out whether any of that is going to happen, and it only works if you stop selling for twenty minutes. This article covers why the incumbent is not an objection, what discovery is actually for, a five-question spine you can run on any call, scripts for the incumbent and the brush-off, and a drill for your team.

Why "we already use something" is not an objection

Every buyer worth talking to already has a tool. If they did not, they would not have the problem your product exists to solve, and they would not be on the call. So the incumbent is not a wall. It is the single most useful piece of information the buyer will give you, because a tool that has been in place for two years carries a history: what it was bought to fix, what it turned out to be good at, and the workaround someone built for the part it does not do.

The buyer usually has not put that history into words. They know the reporting is annoying and that someone keeps a spreadsheet on the side. They have not connected that to a cost, and they certainly have not connected it to you. Discovery is the process of getting them to say it out loud, in their own words, so that the gap between what the tool was supposed to do and what it does becomes the subject of the call.

The other thing to understand about the first thirty seconds is that most of what sounds like an objection is a time defense. "Just send me an email." "We will circle back next quarter." "We already use something." None of those are positions. They are the buyer protecting their calendar from a pitch they assume is coming. Argue with a time defense and you get the polite exit. Earn the next ten minutes and the defense goes away on its own.

What a SaaS discovery call is actually for

Discovery is not a feature-fit check and it is not a qualification form read aloud. A good discovery call leaves you with three things you did not have when it started.

• The gap. The specific place where the current tool falls down, described by the buyer, not inferred by you.
• The cost of the gap, in their terms. Hours chased on a Friday, renewals that slipped, a number the CFO asks for that takes a day to produce. Not your ROI model. Theirs.
• Who else feels it. The second and third name. The person who builds the workaround, the person who gets the wrong number, the person who signed the last contract.

There is a fourth thing that most discovery calls skip, and it is the one that kills the deal later: the switching cost. Migrations, retraining, integrations that took a quarter to build, a stack that works well enough. A feature comparison does not touch any of it. If you do not surface the switching cost in discovery, it surfaces in month three, usually as silence from your champion, because they did the math alone and it did not work.

And the fifth: the approvers. IT, security, procurement, legal, finance. They arrive late and unprepared because nobody asked in the first call who would need to sign. One champion and five unknown approvers is not a pipeline. It is a hope.

The five-question spine

You do not need a forty-question discovery deck. You need five questions in the right order, and the discipline to not describe your product until you have answers to all of them.

1. "What did you bring the current tool in to fix?" The original intent. This is what the buyer will compare everything against, and it tells you what they think the job is.
2. "What does it do well?" This disarms the buyer, because they expected you to attack the incumbent. It also tells you exactly what not to compete on.
3. "Where does it fall down, and what do you do when it does?" The workaround is the pain. A spreadsheet on the side, a Slack thread, a person who does it by hand. Get the workaround described in detail.
4. "What does that workaround cost you in a normal week?" In their units. Hours, people, missed things. Do not supply a number. Wait for theirs.
5. "If that went away, who else would notice?" This is the stakeholder question in disguise. The people who would notice are the people who will need to be in the deal.

Then one more, before you describe anything: "What would make switching not worth it, even if we were better?" That question does something no feature slide can. It gets the buyer to name the switching cost while you are still in the room to hear it.

The SaaS discovery call script: the incumbent and the brush-off

Three scripts. The incumbent in the first minute, the "just send me an email" brush-off, and the switching-cost question. All three are sayable as written. The product names and the numbers are placeholders.

Count the sentences the rep spent describing the product: zero. The buyer went from "it is fine" to "half my Friday" in six exchanges because the rep asked about the original intent, found the workaround, and asked for the cost in the buyer's own units. The last question opens the stakeholder conversation without using the word stakeholder.

The rep agreed to the brush-off and then turned it into two discovery questions. The buyer volunteered the switching cost and the adoption fear without being asked directly. The email that goes out now is not a brochure. It is the answer to a question the buyer asked, which is the only kind of email that gets opened.

Surfacing the switching cost before it surfaces you

Bringing in the five approvers before they bring in themselves

Late-arriving approvers are the second-biggest reason a SaaS deal dies to nothing. Security sends a questionnaire in week nine. Procurement wants three quotes. Legal redlines the data clause. Finance asks why this was not in the budget. None of it is a surprise to the buyer. It is only a surprise to the rep, because the rep did not ask.

Ask in discovery, while the buyer is still describing the last tool they bought.

• "When you brought in the current tool, who had to sign off, and which of them slowed it down?"
• "Does security have a standard questionnaire? Would it help if I got it filled in now, so it is not on the critical path later?"
• "Is there a budget line this would come from, or would it need a new one? Who owns that decision?"
• "If we got to a contract, who reads it on your side?"

Each of those is a normal question about a process the buyer has been through before. Asked in the first call, they make you look like someone who has done this. Asked in month three, they make you look like someone who is about to lose.

How to coach discovery into your team

Every rep on your team knows they should ask more questions and pitch less. Knowing it does not change what happens when a buyer says "we already use something" and the rep feels the call slipping. The reflex to explain the product is strong, and the only thing that overrides a reflex is reps against a buyer who punishes it.

Grade on the five things and nothing else. Did they get the original intent. Did they get a workaround described in detail. Did the cost come from the buyer. Did the buyer name a switching cost. Did the rep get a second name. If you want the drill run against a buyer who does not get tired and is built to protect their time, the B2B SaaS pack in OnCue puts a rep through discovery and brush-off calls against AI buyers who already pay for an incumbent and have been burned by a tool nobody adopted, and scores each call on whether the rep earned the pilot rather than pitched it. The pipeline math is straightforward: one more qualified opportunity a month, found in discovery instead of lost in month three, pays for a lot of practice.

The rep who has heard "we already use something" forty times in a training room does not flinch when they hear it on a live call. They ask what it was brought in to fix, and the buyer, who was expecting a pitch, starts talking.