"You're Too Small for Us" — Handling the Vendor Risk Objection Without Apologising for Your Company

The objection is not about you

A buyer says "you're too small for us." Or "we need an enterprise-ready vendor." Or the softer version, "I love this, but I'm not sure procurement will get comfortable with a company your size."

Every rep I have watched hears that as a personal insult. Their voice tightens. They start listing the funding round, the logos, the SOC 2, the headcount growth. And the call quietly dies, because the buyer wasn't asking for reassurance. They were telling you, fairly plainly, what they would have to defend if this goes wrong.

That is the whole thing. An exec signing a contract with a small vendor is not primarily worried about your balance sheet. They are worried about the meeting eighteen months from now where something has broken and their boss asks who chose this. They are worried about a Tuesday at 2am when the thing is down and there is nobody to call. They are worried about you getting acquired, or running out of money, or getting bored and pivoting, while their data sits inside your product and their team has built a workflow on top of it.

When you understand that, the objection stops being an attack on your company and becomes a specification. They have just told you the exact risks you need to remove. Most reps argue with the spec instead of building to it.

The two responses that lose

Getting defensive

The first failure mode is arguing about the premise. "We may be small, but we're growing fast" or "size doesn't mean reliability, actually some of the biggest vendors have the worst support."

Both of those are true. Neither helps. You are now in an argument with someone who was doing you a favour by saying the quiet part out loud, and the second you push back, they stop telling you what they actually think. The conversation goes polite. Polite is where deals go to die.

Worse, attacking incumbents makes you sound like the risk. The buyer is trying to figure out whether you are a steady pair of hands, and you've just demonstrated that you get emotional when challenged. That is a data point, and not a good one.

Overselling the funding round

The second failure mode is the fundraise flex. "We just closed a Series B led by" — and off you go, naming investors as if a term sheet is an SLA.

I have sat on the buyer side of these conversations, and here is what an experienced exec hears: this vendor has runway, for now, and is under pressure to grow, which means the price will go up and the product roadmap will chase whichever segment their board cares about this quarter. Funding announcements answer the question "will you still exist" with a maybe, and they do not touch the question "will you show up at 2am" at all.

Funding is not zero. Mention it once, in a sentence, and move on. It is context, not an answer.

Reframe it as risk transfer

Here is the reframe I use. Your buyer is being asked to take on risk. Some of that risk is real and some of it is imagined, but all of it currently sits on their side of the table. Your job in the next four minutes is not to persuade them the risk is small. It is to move as much of it as possible onto your side of the table, in writing, in ways they can repeat to their boss without you in the room.

That last part matters more than anything else I am going to say. Your champion is going to have a conversation about you that you will not attend. The question is not "can I convince this person." It is "can this person convince their CFO, their CISO, and their head of procurement, using only what I have given them." If your answer to the size objection is charm and enthusiasm, none of it survives the transfer. If your answer is four concrete mechanisms, all of it does.

So let's talk about the four mechanisms.

Move one: a named escalation path

The fear underneath "too small" is often just "nobody will pick up." Large vendors answer this with a support tier and a portal, which is honestly not much of an answer, but it is a familiar one. You beat it by being specific in a way a big vendor structurally cannot be.

Do not say "we offer white-glove support" or "you'll have a dedicated CSM." Everybody says that and it means nothing. Say who. Say a name, a role, and a path.

What I would say on the call: "Let me tell you exactly what happens if this breaks at 2am on a Sunday. You page the on-call engineer directly — not a ticket queue, a phone number that rings a human. If that person doesn't respond in fifteen minutes it escalates to our head of engineering, and after that it comes to me. My mobile number goes in the contract. That's not a nice-to-have I'm offering you because you're a big logo, it's how it works for everyone, because we're small enough that it can."

Then turn it around, gently: "When was the last time you got the CEO of a vendor with ten thousand employees on the phone during an incident?"

The smallness is the mechanism. You are not apologising for it, you are spending it. But only say this if it is true and you will actually honour it. A promise you break during an incident is worse than never having made it.

Move two: contractual exit and data portability

The second fear is being trapped. If you disappear, get acquired, triple your price, or simply turn out to be a bad fit, what happens to the customer? Most buyers have lived through at least one migration off a dead product and they remember it the way people remember a bad hospital stay.

The answer is not verbal reassurance. It is contract language, and you should be able to name it from memory.

Three things to offer, in order of how much they move the needle:

A short initial term with a clean exit. Not a three-year lock. If you believe in the product, a one-year term with a thirty-day out after the first ninety days costs you almost nothing and removes the largest single objection in the room. The buyer who can leave rarely does.

Data portability written into the agreement. Their data, in a documented format, exported on request within a defined window, at no cost, including after termination. Say the format out loud. "Full export, CSV and JSON, via API or a one-click download, and we keep the export endpoint live for sixty days after any termination." If you have a source escrow arrangement, or you are willing to set one up for a deal of this size, say that too.

Price protection. Multi-year price caps cost you nothing today and answer the "you'll jack up the price once we're dependent" worry directly.

Here is the wording that works: "I'd rather you had a genuinely easy way out than have you sign a long deal you're nervous about. So the term is twelve months, you can leave after ninety days with thirty days notice, and your data comes out in a documented format whenever you ask, including after you leave. If we're not worth renewing, I don't want to be holding you hostage — that's a terrible way to run a company this early."

Watch what that does in the room. You have just made the decision reversible, and reversible decisions get made at a much lower level of certainty than irreversible ones.

Move three: a scoped first phase with a defined success test

The third fear is scale. "You've never done this at our size." Sometimes that is true. Arguing with it is a losing game.

So shrink the surface. Not a pilot in the vague sense — a scoped first phase with a written success test, a fixed duration, and a named decision point.

The difference between a pilot and a scoped phase is that a pilot is where deals go to sit for eleven months. A scoped phase has three things a pilot doesn't: a specific team or workflow, a number or outcome that both sides agree constitutes success before it starts, and a calendar date where you either expand or stop.

Wording: "Let's not try to solve the whole organisation in one go. Pick the team where this hurts most. We run there for ninety days. Before we start, you and I write down what good looks like — if it's cycle time, we agree the baseline this week and the target. On day ninety we look at the number together. If we hit it, we talk about the next two teams. If we don't, you don't renew and I'll help you export cleanly. I'd rather find out in ninety days than in year two."

The key detail people miss: you write the success criteria with them, before the phase, and you write it down. Otherwise on day ninety the goalposts have moved and you are relitigating the whole deal.

This lands especially hard in regulated buying centres where a failed rollout has consequences beyond wasted money. When I look at how a clinical buyer evaluates a new vendor — and the healthcare demo script for a CMIO who has already killed two vendors walks through this in detail — the scoped phase isn't a sales tactic to them. It is how they run every change, because a bad change touches patients.

Move four: peer references, not logo references

The fourth move is the one almost everyone gets wrong.

When a buyer says "you're too small," the instinct is to fight logo with logo. You name the biggest company on your customer list and hope it lands. Usually it doesn't, because the buyer immediately asks whether that company uses you the way they would, and the answer is often no.

What actually de-risks the decision is talking to someone with the same job title, the same reporting line, and the same problem — regardless of company size. Your buyer isn't really asking "do big companies trust you." They are asking "has someone in my exact chair made this bet and survived it."

So offer the reference by role, not by brand: "I can put you on the phone with a VP of Ops at a company about a third your size and one at a company twice your size. Same title, same problem you've described. Talk to whichever is more useful — and ask them what went wrong, not what went well, because something always does."

That last clause is the one that changes the temperature in the room. Inviting the reference to talk about the failures signals you are not managing the conversation, which is exactly the signal a nervous buyer needs.

A warning: this only works if you have actually briefed the reference and they will take the call within a few days. A reference you cannot deliver quickly is worse than none, because the delay reads as scrambling.

This matters most in buying centres where the buyer's professional reputation is the currency. Security leaders live this constantly — when I think about how to open a conversation with a SOC leader, which is the whole subject of the cybersecurity cold call script, the underlying dynamic is identical. They are not evaluating your product in isolation, they are evaluating whether recommending you makes them look careless.

Where this goes in the call

Timing matters more than wording, and the mistake is almost always leaving it too late.

If you wait for the buyer to raise the size objection, you are answering it defensively, under pressure, at the end of a demo when everyone is tired. If you raise it yourself, early, you are answering it from strength and you own the framing.

So I put it near the top, right after discovery and before the product walkthrough. Something like: "Before I show you anything — I know we're a smaller company than the vendors you usually buy from, and I know that means if this goes badly, it's your name on it. So I want to cover how we handle that first, and then you can decide whether the product is even worth twenty minutes."

That sentence does three things. It shows you understand the actual stake, which is their credibility, not your revenue. It puts the risk conversation on the agenda when you control the pacing. And it makes everything after it feel like a straight conversation rather than a pitch.

Then deliver the four moves in about ninety seconds. Escalation path, exit and portability, scoped phase, peer reference. Do not oversell any of them. Say them flatly, like operational facts, because that is what they are.

And then stop talking. Ask: "Which of those is the one your procurement team will still push on?" Their answer tells you which of the four to reinforce with paperwork later, and it surfaces the objection you haven't heard yet.

In deals where the buyer is a fiduciary — managing other people's money, other people's health, other people's data — I move this even earlier, sometimes into the first call. The financial services demo script for wealth management buyers leans on the same logic, because with those buyers vendor risk isn't a procurement box, it's part of their own regulatory exposure.

When "too small" is real

Sometimes it is not an objection, it is a fact, and you should hear it.

If they need on-prem deployment and you are cloud only. If they need twenty-four-seven follow-the-sun coverage in three languages and you have six people. If they need a compliance certification you have not started and the audit takes nine months. If their policy genuinely forbids vendors under a revenue threshold.

In those cases, the four moves are lipstick. Say so, and say when it changes. "Honestly, we can't cover that today. We'll have it by Q3. I'd rather tell you that than sell you a maybe. Can I come back to you in June?" You will lose the deal and keep the relationship, and small companies live on kept relationships.

The thing that gets you remembered is not winning every argument about your size. It is being the vendor who was straight about what they could and couldn't do while everyone else was performing confidence.

What I'd do next

The hard part isn't knowing the four moves. It's saying them without your voice going up at the end. That takes reps, and you do not want to get those reps on a live enterprise call.

If I were building this into my week, I'd take the ninety-second version — escalation path, exit and portability, scoped phase, peer reference — and run it against a buyer persona who pushes back hard, twenty times, until it comes out flat and unbothered. That is more or less what we built DrillCall for: practising the specific moment that scares you, out loud, before it costs you a deal.

Because the buyer who says you're too small has just handed you the list of everything they need to hear. All you have to do is not flinch.