"I'm not the decision maker": what to say

The objection is so common for a simple reason: it is almost always accurate. In Forrester's 2026 buyer research a typical purchase decision involves 13 internal stakeholders and nine external influencers, and the number rises with the size of the deal. Gong Labs reports that 77 percent of deals involve multiple contacts, that won deals have twice as many buyer contacts as lost ones, and that across 1.8 million analysed opportunities multithreading lifted win rates by 130 percent in deals over 50,000 dollars. The person telling you they do not decide is telling you something true of nearly every deal. The question is what you do with it.

Three things the objection can mean

The first version is literal: the person is a user, a project lead or a middle manager, and the decision rests with a leadership team or a procurement function. Forrester found that procurement professionals are decision makers in 53 percent of buying cycles. The second version is a polite no: the person does not want the conversation and points up the ladder rather than say so. The third is a test, deliberate or not, of how you react when you do not get what you want. All three are best handled the same way for the first thirty seconds; only then do the paths diverge.

The mistake: asking to be put through

The instinctive follow-up is to ask who does decide, ideally with a request to be put through to them. It feels efficient and is almost always wrong. The person on the line feels bypassed, the decision maker gets a call with no context, and you have turned a potential ally into someone who would rather you went away. Gong Labs' data on executive meetings points in the same direction: after a discovery call you are 22 percent less likely to earn a next step with an executive than with a non-executive, because reps arrive with tactical questions and a generic deck. The executive wants someone who already understands the business. That understanding comes from the person who just told you they do not decide.

The fix, in three steps

Step one: acknowledge it and keep them talking

'It's rarely one person who decides something like this, so that makes sense. Can I ask what your role is when something like this comes up?' That sentence does two things: it takes away the pressure of having to be the decision maker, and it gives the person a reason to keep talking. Most people answer with their role, and their role is information you need.

Step two: map the process, not the org chart

Ask how decisions like this usually get made at their company: who is involved, when in the year, and what settled it last time. 'How did it go the last time you changed supplier for something similar?' gets you far more than 'who is your boss'. You get the process, the timeline and the criteria in one answer, and you get them from someone who was there.

Step three: offer a way in, together

Do not ask for permission to contact the decision maker. Propose something the person can carry forward themselves: 'Would it help if I sent a one-pager you could take internally, and then we grab twenty minutes together with whoever owns this?' A joint meeting rather than a handover. The person keeps control, the executive gets context, and you keep your seat at the table.

Four lines, four situations

• On the cold call: 'Perfect, then I don't need to sell you anything. Can I ask two quick questions about how it works today, so I know whether it's even worth raising with anyone else?'
• In the discovery meeting: 'Who else will have a view on this, and what do they usually care about most?'
• After the demo: 'What would you need from me to show this internally when I'm not there?'
• When it sounds like a no: 'It sounds like this isn't the right moment for you. Is it the timing, or the topic itself?'

When it really is a polite no

If the answers to your process questions stay short, if the person cannot say who owns the area, and if every proposed next step is met with 'send me something and I'll get back to you', it is a no. Take it. Ask if you can check back in after a given date, note what would have to change, and spend your time on the next call. Treat a polite no as an objection to be overcome and you lose both the deal and the right to call again.

Practise the line until it comes without thinking

The objection lands mid-sentence, and what you say back is decided by habit, not by anything you have read. So practise it in a roleplay where the customer actually says the line. In Salesprep you meet AI customers who interrupt with exactly this line, both in the Cold call module, included in every plan with three free calls, and in the Follow-up module, available on Pro and up. Objection handling is one of seven scores, with a written comment on what you said and what you could have said instead.