29
6 Comments

How to do LinkedIn outreach without getting banned

Watched a friend lose his LinkedIn account last year. Permanent ban, using a "safe" automation tool at "safe" daily limits.

Here's what I learned from it.

1. LinkedIn doesn't care about your daily limits

Everyone asks "how many requests per day is safe", which is the wrong question. LinkedIn's detection is based on acceptance rate and reply rate, not volume. You can send 20 a day that get ignored and get flagged, or send 100 a day that get accepted and replied to and be completely fine.

The numbers that matter are acceptance rate above ~40% and reply rate above ~20%. Below that, LinkedIn's systems start treating you like a spammer, and statistically speaking, you are one.

2. What gets you flagged is bad targeting

My friend blamed the tool and switched three times before realizing the tool was just fine, his list was the problem. When you scrape 2,000 "Heads of Legal at SaaS companies" and blast them, 95% of them don't know you, don't care, and ignore you. LinkedIn watches that ignore rate and concludes you're a bot.

3. The fix: stop volume, start targeting high-intent leads

I send 125 requests a week, acceptance rate is at 72% and reply rate at 55%, zero restrictions. The 125 are people who commented on a competitor's post in the last 2 days, posted themselves about the problem I solve, or engaged with specific creators in my niche. Same ICP as everyone else, but with an additional intent filter. I'm catching them when they're already thinking about the problem.

You can identify those people either manually (works but is a bit painful) or you use IbexAI to find them at scale, every day, and on autopilot.


____

PS: Follow me on X along my building in public journey.

posted toAvatar for product IbexAI
IbexAI
  1. 1

    The point about intent over volume makes sense. Sending fewer requests to people already interested is probably easier than trying to game "safe" limits

  2. 1

    Really useful angle — LinkedIn outreach is tricky for SMBs too. With Finsight AI, I’ve seen that clarity in targeting matters more than volume. Curious how you identify high‑intent signals without triggering bans?

  3. 1

    This matches what I see on the recipient side too: volume isn't the only signal — relevance is. One underused lever is making cold contact cost something for the sender (allowlist free, strangers pay a small cover). It doesn't replace good targeting, but it changes the economics when agents can personalize at scale. Curious if you've seen reply rates hold up when people route public contact through something like that.

  4. 1

    The intent-filter point is the real takeaway here. “Safe daily limits” are often just a way to optimize spam.

    One thing I’d add: acceptance and reply rates are useful feedback signals, but they shouldn’t be treated as guaranteed thresholds. The safest approach is to make every request feel individually justified:

    • Why this person?

    • Why now?

    • What relevant context do we share?

    • Can I explain the reason for connecting without pitching?

    If the answer is no, they probably shouldn’t be on the list. High-intent signals make outreach more relevant, but thoughtful personalization and respecting LinkedIn’s rules matter more than any automation tool or daily limit.

  5. 1

    The useful reframe is that acceptance rate is a market-fit signal before it is a safety metric: if fewer than 40 percent of your ICP will accept a connection, the list is wrong and better copy will not rescue it. I would push the intent filter harder on recency, because someone who commented on a competitor's post two days ago behaves nothing like someone who did it two weeks ago, and most people score both the same. What share of that 55 percent reply rate turns into a paid conversation? That is the number that proves intent signals beat volume on revenue and not just on hygiene.

  6. 1

    Good points, especially about targeting. I've noticed that personalized outreach to people who are already engaging with a relevant topic usually leads to much better conversations than sending large numbers of generic connection requests. Quality really does seem to outperform quantity.