LinkedIn Outbound System: 960 Replies, $518K Closed, No SDR

Two service businesses were doing their own outbound, and both had the same problem. It only happened on quiet weeks. Delivery came first, correctly, so the pipeline moved in bursts and then stopped for a fortnight.

Underneath that were three smaller failures. Nobody tracked who had already been contacted, so people got messaged twice, occasionally by both founders. Replies landed in a personal LinkedIn inbox next to recruiters and spam, so good ones went cold. And because nothing was measured, neither founder could tell you which message was working.

We built a system that runs the sequence every weekday whether anyone is thinking about it or not. Five touches over eleven days: a profile visit, a connection request with a note, a first message two days after they accept, a follow-up, and a close-the-loop message that stops politely.

The constraints matter more than the sequence. Daily caps sit well below the platform's own limits. Gaps are randomized rather than fixed. It runs inside working hours in the account's own timezone, and nothing goes out at weekends. Every prospect is checked against the CRM before a request is sent, so anyone already in pipeline never receives a cold message. Any reply pulls that person out of the sequence immediately, so nobody gets followed up after they have answered.

Replies are classified on arrival into interested, not now, and not a fit. That single step changed the founders' day. They open five conversations that matter instead of scrolling fifty.

Over twelve weeks: 4,820 connection requests, 41% accepted, 960 real conversations, 214 calls booked, $612K of pipeline and $518,000 closed. Zero platform restrictions on either account, which given the caps was the point. "Not now" was the biggest bucket at 44%, and those 422 people went onto a quarterly follow-up list instead of the bin.