LinkedIn outbound that runs on your busiest week
We build a LinkedIn outbound system that runs the same sequence every weekday whether anyone is thinking about it or not. Daily caps sit below the platform's own limits, every prospect is checked against the CRM first, and any reply pulls that person out of the sequence immediately. Twelve weeks produced 960 conversations and zero platform restrictions.
What this looks like before we arrive
- Outbound only happens on quiet weeks, so pipeline arrives in bursts and then stops
- Nobody tracks who has already been contacted, so people get messaged twice
- Replies land in a personal inbox next to recruiters and spam, so good ones go cold
How we build it
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. Nobody is chased forever, and any reply ends the sequence for that person immediately.
The constraints matter more than the sequence
Daily caps sit well below the platform's own limits. The gaps between actions are randomised rather than fixed, it only runs inside working hours in the account's own timezone, and nothing goes out at weekends. Across 4,820 requests that produced zero platform restrictions. The caps are the reason, not luck.
Replies triaged before you see them
Every reply is classified on arrival into interested, not now, and not a fit. That one step changes the founders' morning. They open five conversations that matter instead of scrolling fifty. Not now was the most common answer, and those people went onto a quarterly follow-up list instead of the bin.
In practice
Where we have shipped this
Questions we get asked
Will this get my account restricted?
It has not so far. Caps sit well below the platform's own limits, gaps are randomised, and nothing goes out at weekends. Across 4,820 requests over twelve weeks there were zero platform restrictions on either account.
Do I still have to write the messages?
We write them together, in your words. We will not put a generated message under your name. What gets automated is the sending, the tracking and the triage, not the thinking.
What did the last one actually produce?
Two service businesses, twelve weeks, no SDR hired: 41% of 4,820 requests accepted, 960 conversations, 214 calls booked, $612K pipeline and $518,000 closed.
Which part of your operation eats the most hours each week?
Tell us. You get a written answer on what to automate first, free, whether or not we ever work together.