How to Disqualify in Minute Six Without Burning the Relationship

13 min read

Most reps either cling to zombie deals or bail rudely. Here are the four disqualifiers worth acting on in minute six, and the exact language that keeps the account alive.

Every hour you spend on a deal that was never going to close is an hour you took away from a deal that could have. That is the whole argument. It is not about being tough or having standards or any of the other things people say when they talk about disqualification. It is arithmetic on your calendar.

And yet almost every rep I have watched would rather keep a dead opportunity in the CRM than kill it. I understand why. A dead opportunity in the CRM still looks like pipeline on a Monday forecast call. A killed one looks like you did something wrong. So reps carry zombie deals for months, sending "just circling back" emails to a person who was never going to buy, because the alternative feels like admitting failure.

The other failure mode is worse, and it comes from reps who have read a bit too much about disqualification and decided it makes them sound decisive. They hear one bad answer and they get cold. The tone shifts. The call ends four minutes early. The prospect can feel the exact moment they stopped being worth talking to, and they remember it, because being demoted mid-conversation is memorable. That rep did not disqualify. They quit, rudely, and they burned an account that might have been a real buyer two quarters later.

What I want to give you here is the third option. Disqualify fast, say so out loud, explain the reasoning, hand the person something useful, and set a trigger so the account comes back around to you instead of disappearing. Done right, the prospect ends the call thinking you are the most honest salesperson they have talked to all year. That is not a consolation prize. That is the asset.

Why minute six

Six minutes is not magic. It is just about how long it takes to get through your opener, your reason for the call, and the first two or three real questions if you are not padding. By minute six you should know whether the person you are talking to owns the problem, whether anything has changed in their world recently, whether they are roughly the size of company your product was built for, and whether there is a structural reason money cannot move.

You will not have certainty. You will have signal. The point of minute six is not to make a final judgment, it is to decide whether the remaining nineteen minutes of the call are an investment or a donation.

Most reps do not get there by minute six because they spend the first ten minutes performing rapport and the next ten minutes pitching. Then at minute twenty-two, when the prospect says something that would have been disqualifying at minute four, the rep has already sunk enough emotional cost into the call that they argue with it. I have done this. You talk yourself into a deal because you already spent the time. That is the sunk cost fallacy with a headset on.

So front-load the questions that can kill the deal. Not the questions that build the deal. The ones that kill it. If your discovery has a natural order, put the disqualifiers at the top of it. This is the core structural idea behind the 25-minute discovery playbook for selling into VPs, SDR managers and CROs — the sequence is built so the questions with the highest kill probability come early, while you still have the whole call to spend on whatever survives them.

The four disqualifiers worth acting on immediately

There are a hundred yellow flags in a discovery call. Most of them are noise. These four are the ones I act on the same day.

No owner

Somebody has to own the problem you solve. Not care about it. Own it. Owning means it is their name attached to the outcome, their quarter that looks bad if it does not improve, their budget line or their direct request into someone else's budget line.

The tell is when a prospect describes the problem in the third person. "Yeah, the team struggles with that." "I think ops has looked at this." "It's definitely a pain point for us." Notice there is no first-person verb anywhere. Nobody is doing anything about it. You are talking to a tourist.

The question that surfaces it fast: "If this got fixed, whose number moves?" Then the follow-up, which is the one that actually matters: "And is that you?"

A no-owner call is not always a dead account. It is a dead conversation with a live account. Which is a completely different thing, and it changes what you say next, as I will get to.

No event

Companies do not buy because a problem exists. They buy because something changed and now the problem costs more than the change costs. A new VP. A missed quarter. A failed audit. A system that broke. A contract that renews in ninety days. Somebody left and took the tribal knowledge with them.

If nothing has changed, you are selling into a status quo that has already survived everything you are about to describe. The prospect has lived with this problem for years. They will live with it for one more year. Your deck does not create urgency; an event does.

Ask directly: "What made this worth a conversation now, as opposed to six months ago?" If the answer is a shrug, or worse, "I just thought I'd hear what you have," you have a curiosity call. Curiosity calls can be lovely. They do not close.

One caveat. Sometimes the event exists and the prospect has not framed it as one. They will tell you about the new CFO or the migration or the person who quit without connecting it to your product. Your job is to test whether it is an event before you decide there is not one. But you get one test, not five.

Wrong scale

This is the easiest one to spot and the one reps most often ignore, because a small deal still feels like a deal. Your product has a shape. Below a certain size the customer cannot get value out of it and will churn. Above a certain size they need things you do not have and the deal dies in security review or dies at implementation, which is worse than dying in discovery.

What makes wrong scale hard is that reps only think about it in headcount or revenue. Usually the real dimension is something else — number of locations, number of carriers, number of alerts a day, number of crews in the field. When I look at the discovery playbook for freight and 3PL brokerage buyers, the scale question is not "how big are you," it is about load volume and how many carriers they touch, because that is the axis where the product either works or does not.

Figure out your axis. Ask about it in the first six minutes. And when the answer is out of range, say so, because a prospect who is too small this year may be exactly right next year and they will remember that you told them the truth instead of taking their money.

Structurally blocked budget

Note the word structurally. "We don't have budget" is not a disqualifier, it is a sentence prospects say reflexively, and half the time it means "I have not asked yet." Structurally blocked means the money cannot move regardless of how much they want it to. A hiring and spend freeze that runs through the fiscal year. A signed multi-year contract with an incumbent that does not have an exit clause. A parent company that consolidated purchasing for this category. A procurement process that only opens once a year and closed last month.

Those are facts about the world, not objections. You cannot sell your way through a fact.

The question I like: "If you decided next week this was the right thing to do, walk me through what would actually have to happen for money to move." A prospect with accessible budget answers that in one or two sentences. A prospect with structurally blocked budget answers it with a story, and the story has a wall in it.

The four questions in one place

Whose number moves if this gets fixed, and is it yours. What changed that made now the time. How big is the thing that matters — the trucks, the crews, the loads, the alerts, the reps. And if you decided next week, what would have to happen for money to move.

That is minute six. Four questions, asked conversationally, not fired like a checklist. You can ask all four inside a normal-sounding conversation if you have practiced them enough that they do not sound like a form.

Domain matters for how you phrase them. Asking a SOC manager what changed is a different conversation than asking a general contractor, and the cybersecurity discovery playbook frames the event question around things like a recent incident, a tooling consolidation or an audit finding, because those are the events that actually unlock spend in that world. The construction and trades playbook has the opposite problem — the owner question has to get past the fact that everybody on the jobsite says the problem belongs to somebody in the office. Same four disqualifiers. Different words.

The language that closes the loop

Here is the part reps get wrong. When you decide to disqualify, you have to say it out loud. Not fade. Not "let me send some information over." Say it.

The shape I use is: based on what you've told me, I don't think this is a fit right now, here's why, here's when to call me.

Out loud it sounds like this:

"Can I be straight with you? Based on what you've just told me, I don't think this is a fit right now. You've got the incumbent contract through the end of next year and no way out of it, and honestly the value we'd bring only shows up once you can actually move. If I kept selling you for the next twenty minutes I'd be wasting your afternoon.

What I'd say is this. Around September, when you start looking at that renewal, that's the moment this becomes a real conversation. I'll make a note and reach out then. And if anything changes before that — if the renewal moves up, or you get told to cut the spend — you have my number and I'd pick up.

One thing before I go, because you mentioned the reporting problem. That's not something we solve, but here's what I've seen other people in your seat do about it."

Four parts. The verdict, the reason, the trigger, the gift.

The verdict has to be unhedged. "I don't think this is a fit right now" — not "it might not be a perfect fit at this moment in time." Hedging makes people argue with you, which is the opposite of what you want.

The reason has to be specific and it has to come from something they said. This is what separates a real disqualification from a brush-off. When you reflect back their own words as the reason you are stepping away, they feel heard rather than rejected. It also means that if you got it wrong, they will correct you on the spot — and sometimes they do, and the deal comes back to life with better information. That is a feature.

The trigger has to be a specific condition, not a date. "I'll follow up in Q3" is nothing. "When you start scoping the renewal" is something, because it puts the next conversation on a real event in their world.

The gift is the part almost nobody does. Give them one useful thing on the way out that has nothing to do with your product. A benchmark you are allowed to share, a vendor who actually does solve their problem, a way other people have handled it. This costs you nothing and it is the difference between being remembered as honest and being remembered at all.

Setting the trigger so it actually fires

A disqualified account that you never touch again is a wasted call. The whole point of doing this cleanly is that the account comes back to you.

So when the call ends, do three things while it is fresh. Put a task on the trigger condition, not a generic follow-up date. Write the one sentence that explains why you disqualified, in their words, in the notes — future you will not remember and will otherwise open the record cold. And send the recap email the same day, with the disqualification stated in writing.

That email matters more than people think. It reads something like: "Good talking to you. As I said, I don't think we're the right move for you while the current contract is in place. I've made a note to come back to you when you start scoping the renewal. Here's the thing I mentioned on the reporting side. If anything changes sooner, just reply to this."

You have now created a piece of written evidence that you told a stranger not to buy from you. When you call back in two quarters, that email is your opener, and it is the strongest opener you will ever have. Nobody hangs up on the person who talked them out of a purchase.

One more thing on hygiene. Disqualified is not the same as closed lost, and if your CRM does not let you distinguish them you should fight for a field that does. Closed lost means they bought something else. Disqualified with a trigger means the account is in a queue, waiting on a condition. Those are different lists and they deserve different treatment.

The manager problem

Some of you are reading this thinking your manager will not like it, because your manager counts opportunities. That is a real constraint and I am not going to pretend it is not.

What I would do is get ahead of it with the data you have. Not invented data — your own. Pull the deals you carried past sixty days that went nowhere and look at what they had in common. In my experience it is almost always one of these four things, visible on the first call, ignored because the rep wanted the meeting to count. Show that to your manager as a pattern and the conversation stops being "Tim wants to kill pipeline" and starts being "our first calls are not asking the right questions."

And be honest with yourself about the other reason reps hang on. It is not the forecast. It is that a maybe feels better than a no. A pipeline full of maybes is a pipeline you never have to be judged on. Killing deals early is uncomfortable precisely because it forces you to go find real ones.

Practise the exit, not just the entrance

Here is what I notice about reps who bail rudely. They are not rude people. They just have never once rehearsed what a graceful exit sounds like. They have practised the opener a hundred times and the objection handles fifty times and the disqualification zero times, so when the moment arrives they improvise, and improvised bad news comes out cold.

Say the four-part script out loud until it sounds like you. Then run the harder version, where the prospect pushes back — "well, hang on, maybe we could find budget" — and you have to decide in real time whether that is new information or politeness. That is the rep you want to be by the time it happens live.

If you want reps to actually build the reflex rather than nod at it, that is the kind of thing I would put on a DrillCall scenario and run weekly: an AI prospect who gives you one of the four disqualifiers somewhere in the first six minutes, and a rep who has to catch it, name it out loud, and land the exit without going cold. It is a five-minute rep and it is far cheaper than learning it on a live account you would have liked to keep.

The goal is not to disqualify more. The goal is to spend your week on deals that can close, and to leave every other conversation in a state where the person would take your call again. Those two things sound like they are in tension. They are the same skill.

Practise these calls

The playbooks behind this post — a scripted opener, the objections you will actually hear, and an AI buyer to run it against.

About the author

Timothy Yang

Founder & CEO, DrillCall

I build products by getting on the phone. Four businesses built and exited, including a micro-task marketplace with 170,000+ users, and the common thread in every one was the same: nothing moved until I picked up the phone and sold. Cold outreach, discovery calls, closing. The unglamorous work that actually creates revenue. Right now I am building DrillCall, an AI-powered voice training platform where sales reps practice live calls against realistic AI buyer personas, 310 of them across 31 industries, and get a scorecard after every call. Think flight simulator, but for cold calls. I also run Vibe Coding Club, a community of over 3,500 builders shipping products with AI, and I have spent time inside AWS and Dell, so I have seen how enterprise sales machines work from the inside as well as from the founder seat. What I care about: expected value thinking, fast iteration, and talking to customers before writing a line of code.

← All posts