How to Respond to “You're Too Small”: 3 Honest Answers
“You're too small.”
The buyer is worried about depending on a two-person team. Three ways to turn your size into a strength without pretending to be bigger than you are.
Practice this objectionWhy buyers say it
The buyer has already pictured the worst case: you disappear, the product stops, and they're stuck explaining the choice to their boss or their own customers. They're not questioning your skills; they're sizing up the risk of relying on a handful of people. Plenty of buyers would actually rather work with a small vendor, but they need to hear that you've thought about that risk. Get defensive and you prove the doubt is justified. Stay calm, give them facts they can check, and the conversation moves from how many of you there are to how reliable you are.
What it often means
- Fear that support vanishes the day they really need it
- A boss or partner they'll have to justify the decision to
- A past vendor that shut down and left them stranded
Three answers that work
You're right, we're a team of [number]. Here's what that means day to day: when you email us, the person who wrote the code answers, not a ticket queue. What worries you most about our size, continuity or support?
Why it works: You confirm the fact instead of arguing with it, show the concrete upside right away, and the closing question tells you which fear is real so you can address that one instead of a vague objection.
Here's my offer: your data is exportable at any time, in a format you can open with any other tool. If you decide to leave next year, it takes half an hour. You're not depending on us, you're depending on the product.
Why it works: You shrink the perceived risk with something they can verify, not with reassurance. An easy exit makes the entrance easier, because the buyer doesn't feel trapped with a small vendor.
For a company your size it's actually an advantage. Every request you send lands with the person who sets the roadmap. With a big vendor you'd be an account number. Want me to show you how we handled [a similar request from a customer]?
Why it works: You reframe size as access and speed, two things a small or mid-size buyer genuinely feels. A real example, if you have one, carries more weight than any promise about the future.
Avoid this one
We're small now, but we're growing fast and we'll double in size within a year.
Why not: You're promising a future you don't control and confirming that today isn't enough. The buyer isn't purchasing your growth, they're purchasing what you do for them now. If you're still two people next year, your credibility is gone.
Example dialogue
BuyerI like your invoicing tool, but there are two of you. What happens if one of you gets sick?
YouFair question. There are two of us, and the code, servers, and backups are documented so either of us can handle everything. What worries you more: the service stopping, or nobody answering you?
BuyerNobody answering when I have an invoice that has to go out tonight.
YouThen here's the honest picture: replies come back within [average time] on business days, and you can export everything whenever you want. Want to try it for a month and judge by what actually happens?
BuyerA month's trial works for me.
Practice this objection
A simulated buyer says it to you out loud (or in writing), you answer, and you get a score plus the model answer. Free, no account, 2 minutes.
FAQ
Should I hide the fact that we're a two-person team?
No. They'll find out anyway, and you'll lose trust at the worst possible moment. Say it first, calmly, and immediately explain what you've done to reduce the risk: documentation, backups, data export, response times. Being upfront is the first proof of reliability you can offer.
What concrete things can I show a buyer who thinks we're too small?
Things they can check: your product changelog, real support response times, the data export procedure, the list of current customers if you have permission to name them. Skip promises about the future and lean on what already exists today.
When is “you're too small” just a polite no?
When the buyer asks no follow-up questions after your answers and won't accept even a small step like a trial or a demo. At that point, ask plainly whether size is the only issue or there's something else. The real reason often surfaces, and you can work on that instead.