Make it easy to say no

The easier you make it to say no, the more often people say yes.

That sounds backward. It isn't. A connector who feels cornered either ignores you or does the intro badly. A connector who feels free does it well, or tells you plainly they can't.

Why pressure backfires

When you ask someone to introduce you to a buyer, you're asking them to spend their reputation. They're vouching for you to someone they know.

If the ask feels heavy, they hesitate. Maybe they barely know the buyer. Maybe the timing is bad. Maybe they're not sure you're a fit. With no easy way out, they do the safest thing. They don't reply.

And a non-reply is worse than a no. You don't know whether to wait, follow up or move on. You can't ask again without making it more awkward.

Write the exit into the ask

Say it outright. "If you don't know them well, or the timing's off, no problem at all." Put it in the first message, not the second.

Give them specific reasons they might decline, so they don't have to invent one. They might not know the person well enough. They might have a relationship they don't want to spend. They might just be busy.

Then mean it. When someone says no, thank them and move on. No guilt, no follow-up asking why. That's what makes them say yes the next time.

Make the yes easy too

An easy no only works if the yes is just as easy.

Write the note they'd forward. Keep it short and complete, so they can send it without editing. Say who you are, why this buyer, why now and what you'd want to talk about. Line by line, it's covered in the forwardable note, line by line.

Say you want to reach a new CIO at a regional hospital system, and a former colleague of yours worked with that CIO a few years back.

Your ask to the colleague might be three short sentences. You've seen the CIO just started, and you work on the kind of EHR integration work they'll likely face in the first year. You've written a short note they could forward if they're comfortable. And if they don't know the CIO well enough, or would rather not, that's completely fine.

The forwardable note underneath does the rest. It names the trigger, makes a guess about the problem and asks one easy question.

I saw you started as CIO last month, and the system has been bringing several newly acquired clinics onto its main EHR. That usually lands on IT as a stack of one-off interfaces that someone has to keep alive. My guess is integration work is eating the capacity you'd planned for new projects. Is that close, or is the bigger issue something else?

The same idea, one level down

The binary exit at the end of a Hypothesis Opening works on the same principle. "Is that accurate, or is the bigger issue something else?" makes it easy for a senior buyer to say you're wrong. Saying you're wrong is a reply. And a correction tells you the real problem.

Warm intros are no different. A connector who can say "I don't know her well enough, but try the VP on her team" just gave you a better path. You only get that answer when they feel safe giving it.

What not to do

Don't ask twice in a week. If there's no answer after a week or so, one gentle note is fine. After that, assume it's a no and find another path. The when not to ask for an intro post covers when to skip the ask entirely.

Don't ask them to "just make a quick intro" without giving them anything to send. That pushes the work back on them.

And don't mention past favors. Pressure in disguise is still pressure.

Make it light to refuse and simple to accept. Connectors notice, and they remember.