When you're doing founder-led sales, one objection shows up earlier and more often than almost any other: "You're a bit small for us." Sometimes it's said out loud, sometimes it hides behind "we only work with established vendors." This post is a practical objection handling guide with sales scripts for that exact moment, written for founders, engineers moving into customer-facing roles, and SDRs at early-stage startups.
The goal isn't to argue the buyer out of their concern. The concern is often fair. The goal is to find out what "too small" actually means to this person, and then answer that specific risk.
What "you're too small" usually means
In practice, the phrase is a label stuck on one of a handful of real worries. Before you answer, you need to know which one you're dealing with:
- "Will you still exist in a year?" Continuity risk. They don't want to migrate twice.
- "Who do I call when it breaks?" Support risk. They picture a two-person team on holiday.
- "Will this pass security and procurement?" Process risk. They've been burned by a vendor review before.
- "Will my boss question this choice?" Personal risk. Nobody gets blamed for picking the big name.
- "I'm not actually interested." A polite exit, using size as the excuse.
Each one needs a different answer. Responding to all five at once ("we're well funded, we have great support, we're SOC 2 ready, and lots of people trust us") sounds defensive and usually isn't even true for a young company.
Step 1: Acknowledge, then ask a discovery question
Don't flinch and don't oversell. Agree with the part that's true, then ask.
"That's fair, we are a small team, and I'd rather talk about it now than have it come up in procurement. When you say small, what's the part that worries you most: that we won't be around, support, or getting through your vendor review?"
That one question does a lot of work. It shows confidence, it treats the buyer as reasonable, and it turns a vague objection into a specific one you can actually handle.
If they answer with something vague like "just in general," try one more:
"If we were twice the size tomorrow, what would be different for you?"
Their answer tells you what they really need to see.
Step 2: Answer the real risk with something concrete
Here are short sales scripts for each version. Only use what is actually true for your company. Inventing traction to win this objection is the fastest way to lose the deal later, and your reputation with it.
Continuity risk
"Totally reasonable. Two things we do for that: you can export all your data at any time in a standard format, and we keep the setup light so switching away wouldn't be a project. Would it help if I showed you the export now?"
You're not promising you'll exist forever. You're lowering the cost of being wrong.
Support risk
"The upside of a small team is you'd be talking to the people who built it. Here's how support works today: [actual channel, actual response time you can keep]. What response time would you need for this to work?"
Let them set the bar, then tell them honestly whether you can meet it.
Process risk
"Let's find out early. Can you send me your vendor questionnaire, or tell me who owns it? I'd rather know now what we can and can't answer than surprise you in three weeks."
Asking for the questionnaire yourself is one of the strongest moves in founder-led sales. It signals you aren't hiding anything.
Personal risk
"If you brought this to your manager, what would they ask first? Let's make sure you have an answer for that."
Now you're helping your champion sell internally, which is the actual job.
The polite exit
If none of the questions get traction, test it directly:
"It sounds like size might not be the real blocker. Is this just not a priority right now? Totally fine if so, I'd rather know."
A clear no is worth more than a stalled maybe in your pipeline.
Step 3: Shrink the commitment
Small companies win against "too small" by making the first step smaller than the risk. Offer a scoped trial, a single team, a fixed end date, or a clear exit:
"What if we started with one team for four weeks, with a check-in at week two and a clean way out if it's not working? That way the risk is four weeks, not a contract."
This is a closing technique that works because it's honest about the trade-off. You're not pretending to be big; you're making size matter less.
A quick objection handling checklist
Use this before and after calls where size might come up:
- [ ] I know which of the five risks the buyer actually means.
- [ ] I acknowledged the concern before answering it.
- [ ] Every claim I made about support, security or continuity is true today.
- [ ] I asked for the vendor questionnaire or the procurement owner.
- [ ] I offered a smaller first step with a clear end date.
- [ ] I asked what their manager would need to hear.
- [ ] I got a clear next step or a clear no.
Practice it before it costs you a deal
The hard part of this objection isn't knowing the words. It's staying calm when someone tells you, in effect, that your company isn't serious enough. Founders and engineers new to sales tend to either get defensive or start over-promising, and both kill trust.
The fix is sales practice: say the acknowledge-and-ask line out loud until it feels boring, then do a sales role play where the buyer pushes back twice. Have a colleague play a skeptical procurement lead, or run it with a recorded call and review where your voice tightened. A few reps make a real difference on the call that matters.
Wrapping up
"You're too small" is rarely about size. It's about a specific risk the buyer can't see an answer to yet. Find the risk with one good discovery question, answer it with something true and concrete, and make the first commitment small enough that size stops mattering.
If you want to rehearse objections like this one against virtual customers that push back like real buyers, that's what we're building at Kulissa.
Top comments (0)