How to Respond to "I've Never Heard of Your Company"

1. Acknowledge

Agree without flinching. "That's fair, most people haven't yet" is honest and confident at the same time. Do not get defensive and do not start reciting your funding round. The buyer is testing how you handle a challenge, and a calm acknowledgement does more for your credibility than any logo would.

2. Clarify

Find out what the buyer actually needs to feel safe. Some want to know you will exist in two years; some want proof you have solved this exact problem for a company like theirs; some want to know who they will deal with when something goes wrong. "What would you need to know to feel comfortable?" gets you the specific concern. Answering the wrong one wastes the moment.

3. Reframe

Reframe from "unknown is risky" to "unknown is why you get our attention". A buyer at a small vendor talks to the people who built the product and gets changes made. At a large vendor they get a ticket number. Then give one specific, verifiable proof point for their concern: a named customer in their sector, a reference they can call, a trial with a clear exit. Specific beats impressive.

4. Ask

Offer a low-risk way to check you out. A reference call with a customer like them, a short pilot with defined success criteria, or an introduction to the person who would handle their account. Ask which would help most. Make the risk of trying you smaller than the risk of not solving the problem, and ask for the next step on that basis.

On a cold call

That's fair, most people haven't, and that's partly why I'm calling rather than waiting for you to find us. We work with [role] at [one or two recognisable or similar companies] on [specific problem]. I'm not asking you to trust us today. I'm asking whether [problem] is something you're dealing with, because if it is, it's worth fifteen minutes to see if we're credible. If not, no harm done.

On a discovery call

Completely reasonable question. Rather than give you the company history, can I ask what would make you comfortable? Is it that we'll be around, that we've done this before for someone like you, or who you'd actually be dealing with? [Listen.] Okay. On that specifically: [targeted proof point]. And I'm happy to put you in touch with [customer] who had the same question six months ago.

After a demo

I understand, and you've now seen the product, so the question is really about the company behind it. Let me be direct about what you'd get: you'd be working with [named person], who built the part you asked about, and we'd set up [success criteria] for the first ninety days with a clear exit if we miss them. Would a call with [reference customer] help, or would you rather start with the pilot and judge us on that?

Late in the deal

I hear it, and at this stage I think it's worth naming what's really at stake: if you pick us and it goes wrong, it's your name on the decision. So let's reduce that. We'll put the success criteria in the contract, you'll have a direct line to [executive], and [reference customer] is happy to talk to you about what it was like in the first six months. What else would make it a safe choice?

By email

Fair point, and I'd rather you asked than assumed. Three things that might help: we've worked with [customer] and [customer] on [specific problem], [reference contact] is willing to take a call about what it's been like, and we'd structure any first engagement with clear success criteria and an exit. If there's something specific you'd want to know about us before spending more time, tell me and I'll answer it straight.