"I Need to Run It By the Team" — What That Actually Means and How to Get in the Room

There is a sentence that lands at the end of a good call and quietly kills it. The demo went well. They asked sharp questions. They said the words "this is interesting" more than once. Then, right as you reach for next steps, they say it:

"Let me run it by the team."

And you say "great, sounds good" because it sounds like progress. It isn't. Nine times out of ten — and I am using that as an expression, not a measurement — what you have just heard is the most polite available way of telling you that the person on the call will not be the one arguing your case. They are not saying no. They are saying I am not going to fight for this, and I would like to end the call now.

I have been on both sides of that sentence. I have said it to vendors when I did not want to tell them I had already decided. I have heard it from buyers when they genuinely did need three partners in a room before anything moved. The words are identical. The deal outcomes are not. So the whole skill here is diagnosis, and then, if the diagnosis is good, getting yourself into a room you were not invited to.

Why this one hurts more than a price objection

A price objection is honest. It gives you something to work with. It tells you the buyer has formed an opinion about value and it is lower than your number, and now you get to have a conversation about what they are comparing you against.

"I need to run it by the team" gives you nothing. It moves the decision to a room you cannot see, held on a date you do not know, with people whose names you have not been given, who will hear a version of your pitch delivered by someone who is not paid to sell it. Every part of that is bad. The information decays the moment it leaves your call. Your contact will remember maybe the top two things you said, will describe your product in their own words, will get asked a technical question they cannot answer, and will say "I'll check with them" — at which point your deal is now two levels of hearsay deep.

And here is the part most reps miss. You do not get told when the meeting happened. You find out weeks later, in an email that says the team decided to revisit next quarter. There was no debate you could have joined. There was a two-minute agenda item at the end of a Tuesday meeting where someone said "we looked at a tool for this" and someone senior said "do we need it?" and the answer was no, because nobody in the room had felt the pain the way your contact felt it on the call with you.

So the objection is not really an objection. It is a handoff. Your job is to decide whether to accept the handoff, improve the handoff, or refuse the handoff and stay in the process.

The three flavours

Every time I have heard this, it has been one of three things. They look identical on the call. They require completely different responses.

One: genuine consensus culture

Some organisations really do decide this way, and no amount of clever objection handling changes it. Partner-led firms are the clearest example. In a law firm, a consultancy, an accountancy practice, an architecture practice, the people who own the business are also the people who bill the hours, and a decision that affects how they work is not a decision one of them makes alone. It goes to a partners' meeting. It goes to a practice group. In firms with a risk or IT committee, it goes there too, and that committee meets when it meets.

This is not a stall. It is the actual mechanism by which money leaves the building. If you push against it — "well, who really owns this decision?" — you look like you have never sold into a firm before, and your contact will start managing you rather than working with you. I wrote a whole 25-minute discovery playbook for partner-led firms partly because this dynamic is so common that if you have not mapped it during discovery, everything after discovery is guesswork.

The tell for genuine consensus culture is specificity. Ask who and they name three people without hesitating. Ask when and they know the meeting cycle: "partners meet every other Monday, so the fourth." Ask what will happen and they can predict the argument: "Sarah will want to know about client confidentiality, and Mark will say we tried something like this in 2019." People who know the room describe the room. That is a real process and you can work with it.

Two: a champion who isn't a champion yet

This is the most common and the most winnable. Your contact likes what you showed them. They believe you would solve the problem. But they have not converted "this is interesting" into "I am willing to spend my personal credibility on this," and those are two different states.

Internal capital is real. Your contact has a finite number of times they can walk into their boss's office and say "we should buy this." They are not going to spend one of those on a product they saw once, from a rep they met last week, where they cannot answer the obvious follow-up questions. Not because they do not like you. Because it is a bad bet for them personally.

The tell here is enthusiasm without detail. They are warm. They say things like "I think the team will love this." But when you ask who specifically, you get a category rather than a name — "the leadership team," "ops," "my manager and a couple of others." And when you ask what those people will push back on, they say "I don't think they'll have any issues." That answer is always false. Everyone has issues. If your contact cannot predict a single objection, it means they have not thought about the internal conversation at all, which means it will not go well.

Three: a soft no wearing a lanyard

Sometimes it is over and they are being kind. They have decided, or someone above them has decided, or they were never buying and took the call for a reason of their own. The team is a place to send you so that nobody has to say a hard thing.

The tell is vagueness plus reluctance to commit to any date. "I'll run it by the team" — when? "I'll come back to you." On what day? "Let me see how the week goes." Softness in every direction. Also watch the energy change. Real buyers get more specific as a call goes on, because they are simulating using the thing. People who have checked out get more general, because generality costs nothing.

The correct response to flavour three is not to fight. It is to make it safe for them to tell you the truth, so you stop spending time on it. More on that below.

Diagnosing it on the spot

You get one shot at this, and it is in the ninety seconds after they say the sentence. Not in a follow-up email. Email is where deals go to be politely ignored.

The first thing to do is agree. Do not push back, do not get clever, do not say "what's stopping us from moving forward today?" — that line has been burned to the ground and buyers hear it as pressure. Say something like: "Totally, that makes sense — most people in your seat would. Can I ask three quick things so I can make that conversation easier for you?"

Nobody says no to that. You have framed the questions as help, not interrogation.

Who specifically

"When you say the team, who's actually in the room?"

You want names and roles. Not "the leadership team." Names. If they give you three names, ask which one is most likely to have a strong opinion, and which one has the budget, because those are frequently different people and the gap between them is where deals die. If they cannot give you a name, you have learned something enormous: either they do not know how the decision gets made, or there is no meeting.

Follow up with: "Has this group looked at anything like this before?" If they have, that history will show up in the room whether you address it or not, and you would much rather know now that someone tried a competitor two years ago and hated it.

What will they object to

"When you take this to them, what's the first thing you think they'll push back on?"

This is the single most useful question in the whole conversation. It does three things at once. It forces your contact to actually rehearse the internal pitch while they are still on the phone with you — which is the only rehearsal they will ever get. It surfaces the real objection, which is very often not the one they raised with you. And it tells you which flavour you are dealing with, because people in a genuine consensus culture answer instantly and specifically, and people who have already decided against you answer with nothing.

If they say "probably cost," ask cost compared to what. If they say "whether we have time to implement," ask who would have to do the work. If they say "I honestly don't know," say: "That's fair — in firms like yours it's usually one of two things, either security and data handling or whether it survives contact with people's existing habits. Which of those two is more your world?" Give them a menu when they cannot generate an answer.

What happens if they say no

"And if the team says not now — what happens then? Does the problem go away, or does it just sit there?"

This is the honesty question. It is not aggressive because it is asked with the assumption that a no is survivable. What you are testing is whether the pain is real. If the answer is "then we carry on as we are, it's fine," you have flavour three and you should be grateful, because they just saved you a quarter of follow-ups. If the answer is "then we're still stuck doing this manually and it gets worse in Q1 when volume goes up," you have a real deal and a real reason for your contact to fight.

And when the answer tells you it is over, say so kindly: "Sounds like this isn't a priority right now, and that's completely fine — would you rather I close it off and check back after the new year?" Reps are terrified of that sentence. It is the most respect-earning thing you can say, and in my experience it flips a surprising number of soft nos into an honest conversation about what would actually have to change.

Now arm them

Diagnosis without action is just a nicer way of losing. If you have decided the deal is real, your contact is now about to represent you in a room you are not in. Treat them like a colleague who has been handed a presentation with no slides.

The one-page internal case, in their language

Send one page. Not a deck. Not a proposal. One page, in the body of an email so nobody has to open an attachment, written the way they would write it to their own boss, not the way your marketing team writes.

It should have the problem in their words — literally quote them from the call, because when your contact reads their own sentence back they will use it in the meeting. It should have what changes, concretely, described in terms of the work rather than the software. It should have the cost, stated plainly, with no games. It should name the two objections they told you would come up, and answer them in two lines each. And it should say what the next step is, so the meeting has a decision to make rather than a topic to discuss.

The test for this page is simple: could your contact forward it without editing it, and would it still sound like them? If it reads like a vendor wrote it, it will get forwarded with an apology attached, and an apology is a bad opening.

Offer ten minutes, not another demo

Here is the line that has got me into more rooms than anything else: "There's usually one technical question that comes up in these meetings that neither of us can predict. Would it help if I joined for ten minutes at the start, answered whatever comes up, and then dropped off so you can talk properly without me in the room?"

Every part of that matters. Ten minutes is small enough to grant. "At the start" respects their agenda. "Then dropped off so you can talk properly" is the unlock, because the real reason you are not invited is that the room wants to be able to say uncomfortable things about you. Promising to leave removes the objection to your presence.

And when you do get in the room, understand that it is not a demo. It is a hearing. A committee of senior people does not want to be walked through features; they want to test whether you are a risk. I broke down how to handle exactly that kind of audience — managing partner, practice chair, risk committee, all with different fears — in the legal demo script for multi-stakeholder rooms, and the principle travels beyond law: answer the most senior person's unspoken question first, which is usually "what happens to me if this goes wrong?"

If they will not let you join, offer the fallback: a fifteen-minute prep call with your contact the day before, where you play the sceptical partner and they practise the pitch. Some of the best deals I have worked ended with a champion who could handle the room better than I could, because we had rehearsed the argument twice.

Never leave without a date

The non-negotiable. "When's the meeting?" Then: "I'll call you the day after — Thursday, is the morning or the afternoon better?" Book it while you are both on the phone. Not "I'll follow up next week." A date, in both calendars, tied to a specific event.

If they cannot give you a meeting date, that is the diagnosis. There is no meeting. Ask gently: "Is it on the agenda already, or is it a case of finding the right moment?" Finding the right moment means it is not happening, and you now know to work on a second thread rather than waiting.

The version of this you cannot beat, only navigate

Some rooms will never let you in. Partner votes, regulated procurement, committees that meet quarterly and do not take vendors. Do not treat these as failures of technique. Treat them as facts you should have found in discovery, which is why I push so hard on mapping the decision mechanism early rather than at the end. If you are selling into law firms, the 25-minute legal discovery diagnostic exists mainly to force that mapping before you have invested three calls. For a more straightforward committee — a RevOps buyer with a CRO and a finance sign-off — the SaaS discovery playbook covers the same ground in a shorter chain.

The general rule: the earlier you learn who else has to say yes, the less this objection can hurt you. If you asked in discovery — "walk me through how a decision like this normally gets made here, who else ends up involved?" — then "I need to run it by the team" is not a surprise, it is the step you were both expecting, and you have already built the case for it. If you never asked, you are hearing about the room for the first time at the worst possible moment.

What I would do next

Pick your three questions and say them out loud until they sound like you rather than like a script. Who specifically. What will they push back on. What happens if they say no. That is it. The reason reps do not ask these is not that they do not know them — it is that the moment arrives at the end of a call, the buyer sounds friendly, and asking feels like ruining a nice mood. So you say "sounds good" and hang up.

That is a rehearsal problem, not a knowledge problem, and it is why I built DrillCall — so you can run the same objection twenty times against an AI buyer who is warm and vague and keeps sending you back to a team that may not exist, until asking "who's actually in the room?" costs you nothing. If you would rather not, find a colleague, have them say the sentence, and practise the next ninety seconds until they are boring. Either way, do not let the first time you try it be on a deal you care about.