LINKEDIN OUTREACH — CASE STUDY

221 LinkedIn requests. Zero restrictions. One account.

NavSaver, our own product

16.6%acceptance rate from cold sales leaders in the US and UK
221connection requests logged, Sep 23 to Oct 10, 2026
15sending days, daily volume 11 to 20, never over cap
25 minminimum gap between sends, enforced by process
25prospects accepted and entered sales conversations
19Open Profile InMails sent alongside, 0 credits used
0warnings, CAPTCHAs or restrictions in the whole run

How it worked

STEP 1

Hard cap of 20 requests a day plus a rolling 24 hour cap

STEP 2

Minimum 25 minute gaps, every message typed by hand

STEP 3

Prospect research first, estimated seat potential 5 to 25

STEP 4

Pitch plus at most 2 follow-ups, then permanent silence

OUTCOME

16.6% acceptance rate from cold sales leaders in the US and UK

Meet NavSaver

NavSaver is our own product: LinkedIn Sales Navigator team seats at $25 a month against LinkedIn's $120, activated before payment, sold to sales teams who buy seats in bulk. The entire sales channel was one LinkedIn account and one operator.

The challenge

Two problems at once. First, the offer itself: a $120 product for $25 sounds like a scam to a stranger, so trust, not reach, was the bottleneck. Second, the account was the whole business. LinkedIn restricts accounts that behave like bots, and a restricted account ends the channel overnight.

Every shortcut that raises volume lowers trust or risks the account. The operation had to be built the slow way on purpose.

The solution

Human pace, enforced by process

Twenty connection requests a day, hard cap, plus a rolling 24 hour cap tracked alongside it. A minimum of 25 minutes between sends, and the measured gaps ran longer: on September 30 the first two sends sat 39 minutes 45 seconds apart, and later gaps that day measured 32 minutes 42 seconds and 32.2 minutes. Every message typed by hand, never pasted, because paste patterns are a bot signal. Full-cap days closed at 20 of 20 on September 29 and again in the October 7 and October 10 runs, with zero warnings, zero CAPTCHAs, zero restrictions.

Across 15 sending days from September 23 to October 10, daily volume ran from 11 to 20 requests, never once above the cap.

Research before requests

Every prospect was a bulk buyer by profile: sales leaders, recruiting heads and agency founders in the US and UK, each researched with an estimated seat potential of 5 to 25 seats before a request was ever sent. The split came out at 120 US and 99 UK requests.

Discipline after the accept

Every accepter got a pitch and at most two follow-ups, spaced days apart: 9 follow-ups went out on October 7 alone, and by September 29 every one of the 9 accepted connections then on the board had received its pitch. After the second follow-up, permanent silence unless they reply. Invites nobody accepted were withdrawn after 15 days: the pending pile was 119 on September 25 and 137 by October 7, with 2 declines recorded.

Alongside the requests, 19 of a planned 50 Open Profile InMails were sent (9 on October 5, 10 on October 7), using zero InMail credits, because Open Profiles do not consume them.

The results

The return is the asset itself: 25 live sales conversations and 19 InMails sent at zero credit cost, while the single account that carries the entire channel stayed completely clean. A restricted account would have zeroed the channel overnight. It never came close.

Honest note: those conversations did not turn into orders inside that window, and we will not pretend otherwise. What the run proved is the operating system: an outreach channel that runs at full pace for weeks without endangering the account it depends on. That is the part most teams get wrong, and it is the part that is actually hard.

FAQ

Why send so slowly?

Because the account is the asset. A flagged account sends nothing at all. Twenty human-paced requests a day, every day, beats two hundred bot-paced requests once.

What daily volume is safe on LinkedIn?

For a real account doing cold outreach, our operating cap is 20 connection requests a day with natural gaps of at least 25 minutes, and we withdraw stale invites after 15 days. Tools that promise hundreds a day are spending your account, not theirs.

Why withdraw unaccepted invites?

A growing pile of pending invites is one of the signals LinkedIn reads as automation. Withdrawing at 15 days keeps the account profile clean and the list honest.

By the numbers

connection requests logged, Sep 23 to Oct 10, 2026221
sending days, daily volume 11 to 20, never over cap15
minimum gap between sends, enforced by process25 min
prospects accepted and entered sales conversations25
Open Profile InMails sent alongside, 0 credits used19
warnings, CAPTCHAs or restrictions in the whole run0

Bars are scaled so very small and very large numbers fit on one chart. The values printed are exact.

THE ROI
25

live sales conversations opened, while the one account the whole channel depends on stayed at zero warnings

25 conversations opened, 19 InMails at zero credit cost, and the account never took a single warning.

What was built

The concrete pieces this engagement shipped, in one list.

Your mail is being sent unauthenticated. Here is the full fix.

Lower stack cost. Back in the inbox. Built to send at any scale.

We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.

Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.

Free · Written plan + fixed price · No sales call required

More case studies

Lead dataA US M&A advisory firm (name withheld)
46,000

prospects matched on LinkedIn, 93% of the final list

151,218 rows in. 49,373 decision-makers out.

READ CASE STUDY →

ROIValid decision-maker leads at $0.067 each in the pilot, then all 49,373 scored for $1.54 total.

InfrastructureA US advisory firm's cold email program (name withheld)
100%

sender health at the end of the wave, with 1 hard bounce in the final campaign

30 inboxes. 1,596 sends. Zero burned.

READ CASE STUDY →

ROIZero inboxes burned: 1,596 sends delivered and the pool ended at 100% health, ready for the next wave.

OutreachPartner outreach for a US advisory firm (name withheld)
Step 2

the follow-up, not the first touch, produced the first interested partner reply

The first yes did not come from the first email

READ CASE STUDY →

ROI958 sends across the wave produced an interested partner and a $1,000 logged opportunity.

Copied
Free tools Get an inbox plan