Every so often a prospect tells me, “I’m not the right person for this.” It used to end the call. I’d thank them, ask for a referral, and wait for a name that rarely came. I now treat that line as the start of the qualifying conversation.

When someone says they aren’t the decision-maker, they’re usually bracing for a pitch they can’t approve. They expect me to push toward a budget conversation they have no authority to have. So I stop pitching and say something true: “Fair enough. You’re probably the person who feels this problem most, though. Walk me through what happens on your side when a new starter’s paperwork is late.”

That reframe does two things. It validates their role, because I’m treating them as the expert on how work actually gets done, not as a gatekeeper. It also removes the pressure. They don’t have to defend a purchase. They only have to describe their day, and most people are happy to do that.

The other common dead end is “Everything’s fine.” Almost nobody’s workflow is actually fine. People say it on a cold call because it closes the topic. I don’t argue with it. I ask a question specific enough to be answered with a fact:

  • “Who does that step today, and roughly how long does it take them?”
  • “When that goes wrong, how do you usually find out?”
  • “What did the last time it broke cost you, in hours or a missed deadline?”

Each question moves the conversation from a vague feeling to a process. Once someone describes the process, qualification mostly takes care of itself. You learn who touches the work, how often it happens, what it costs, and whether anyone has a reason to change it.

Say a prospect tells you the team is “in a good place” and a new tool isn’t a priority. Accepting that ends the call. Asking who handles the handoff between two systems each week might surface a person who spends most of a morning re-keying data and has already flagged it twice. That is a qualified conversation. It has a named pain, a named owner, and a frequency.

The same principle applies to the “I’m busy” objection. Acknowledge it first, then ask one question. Something like: “I’m jumping into a meeting too, so I’ll be quick. Is this already something your team is trying to fix, or has it just not come up?” The answer takes one sentence, and that sentence tells you whether an email is worth sending. You avoid mailing someone with no problem, and you give a relevant follow-up to the one who has it.

A few things I’ve learned to watch for:

Don’t ask the question as a test. If it sounds like a trap, people give you the polite answer.

Let silence work. After a good question, wait. The first answer is often the safe one. The second is usually the real one.

Record your own calls. Tone problems, like upward inflections at the end of statements that should sound certain, are easy to miss live and obvious on playback. Listening back to pitches outside your usual platform catches things that compressed audio hides.

Treat “not the right person” as a reason to ask about the process, not only a reason to ask for a referral. Often the right name comes up naturally once you understand the work.

The objection doesn’t disappear. You just stop treating it as the end of the conversation. Ask the person in front of you how the work actually happens. They almost always know, and once they tell you, you’ll know whether there’s a conversation worth having.