"I need to run it by my boss" is one of the most common moments in a sales call, and good objection handling here decides whether your deal moves forward or quietly dies in someone else's inbox. These sales scripts and discovery questions are for founders doing founder-led sales, engineers moving into customer-facing roles, SDRs and AEs who keep hearing this line after what felt like a great call.
The problem isn't the boss. The problem is that your champion is about to pitch your product to someone you've never met, without you, using whatever they remember from a 30-minute call. That's the part you can fix.
What "I need to run it by my boss" usually means
The same sentence can carry very different meanings. Before you respond, figure out which one you're hearing:
- A real approval step. They like it, but someone else signs. This is the good version.
- A polite exit. They're not convinced and the boss is a soft way to say no.
- They don't know how to sell it internally. They want it, but they can't explain the value in their manager's language.
- The boss has a specific concern (budget, risk, timing) that your contact already knows about but hasn't told you.
Each one needs a different next step, so your first move is a question, not a pitch.
Step 1: Acknowledge, then ask one discovery question
Don't argue with the process. Respect it, then get information.
"Makes total sense, most teams want a second set of eyes on this. Can I ask: when you bring it to them, what do you think their first question will be?"
This one question does a lot of work. If they answer quickly and specifically ("she'll ask what it costs compared to what we pay now"), you're in version 1 or 4. If they hesitate or go vague ("oh, just the usual"), you're probably in version 2 or 3.
Follow-up discovery questions that help:
- "How do decisions like this usually get made on your team?"
- "Has your manager looked at anything like this before? How did that go?"
- "Is there anything you're still unsure about yourself before you take it to them?"
That last question is the honest one. It gives a hesitant buyer permission to raise their own objection, which is far better than having it surface later as "my boss said no."
Step 2: Arm your champion
If it's a real approval step, your job is to make your contact look good in front of their manager. Most deals stall here because the champion has to translate your pitch from memory.
Sales script:
"When you bring this up, what would make it easiest for you? I can write a short summary in your words: the problem you described, what changes, and what the first step would cost. You can edit it or forward it as-is."
Then actually write it. Keep it to five lines:
- The problem, in the exact words they used on the call.
- What it costs them today (time, missed deals, rework), only if they told you.
- What changes if they move forward.
- The smallest first step and when it ends.
- The one open question you expect from the boss, with an answer.
No feature list. No adjectives. Managers skim, and a short note in their own team's language gets read.
Step 3: Ask to be in the room (without being pushy)
The strongest move is to join the conversation, but you have to offer it as help, not as a demand.
"Totally fine if you'd rather take it on your own. If it's useful, I'm happy to join for the last 15 minutes to answer the technical or pricing questions, so you don't have to carry those."
If they say no, don't push. Ask instead:
"Fair enough. What would you need from me to feel confident answering whatever comes up?"
For engineers and solutions engineers moving into sales: this is where your background helps. Offer to cover the technical questions specifically. Champions often say yes to "I'll handle the security and integration questions" when they'd say no to "can I pitch your boss?"
Step 4: Lock a next step before you hang up
"I'll get back to you" is how deals disappear. Close the call with a date, not a hope.
"When are you seeing them? Great, how about I put 15 minutes in our calendars for the day after, so you can tell me what they said and we figure out the next step together?"
This is a closing technique in the honest sense: you're not forcing a decision, you're closing on a next step. If they won't commit to even a short follow-up, that's information. You're probably hearing version 2.
Handling the polite exit version
If your discovery questions suggest "my boss" is really a soft no, name it gently:
"Can I be direct? Sometimes 'I need to check with my boss' means 'I'm not sure this is right.' If that's the case, I'd much rather hear it now. What's giving you pause?"
A real objection on the table is something you can work with. A vague one is not.
Sales call checklist for multi-stakeholder deals
Use this before and after any call where approval comes up:
- [ ] I asked who else is involved in the decision early in the call, not at the end.
- [ ] I know what the boss's first question will be.
- [ ] I asked whether my contact still has doubts of their own.
- [ ] I offered a short written summary in the buyer's words.
- [ ] I offered to join for part of the internal meeting.
- [ ] I proposed the smallest possible first step.
- [ ] We have a dated follow-up in the calendar.
Prevent it next time
The best way to handle this objection is to surface it in discovery, before your pitch. Early in the call, ask:
"Besides you, who else usually weighs in on something like this?"
Asked early, it's a neutral process question. Asked at the end, it feels like you're trying to get around your contact. Asking early also lets you shape the whole call around what the decision maker cares about.
Practice it out loud
Knowing these lines is easy. Saying them calmly when a call you thought was going well suddenly stalls is harder. Founders and new reps often either rush to "can I talk to your boss directly?", which feels pushy, or accept "I'll get back to you" and never hear back.
Sales practice fixes this. Rehearse the acknowledge-and-ask line until it's automatic, then run a sales role play where a colleague plays a hesitant champion and gives you the vague version of the objection.
Wrapping up
"I need to run it by my boss" isn't a rejection. It's a handoff. Find out what it really means with one good discovery question, give your champion a short summary they can forward, offer to help in the room, and leave every call with a date.
If you want to rehearse moments like this against virtual customers that push back like real buyers, that's what we're building with Maya, our sales coach, at Kulissa.
![Mobile Manipulator Architecture — Ch.03: End Effector Interface [KR]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8bgy8xuxjijwmlbkcad5.png)
![Mobile Manipulator Architecture — Ch.04: Gripper Architecture [KR]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0wjfle73fjb2648pkj78.png)