LinkedIn plus cold email is crushing it for me. Here is my exact sequence
multichannel_m · 2026-01-17 · 2,670 views
Pure cold email is good. Cold email plus LinkedIn is incredible. Here is my exact multi-channel outbound sequence.
Day 1: LinkedIn connection request with no note.
Day 2: Email 1 with value prop. Short, personalized, no links.
Day 4: LinkedIn message if connection accepted — casual, reference the email.
Day 6: Email 2 follow-up with social proof.
Day 10: Email 3 breakup email.
Results: 40% higher reply rate compared to email-only sequences. Prospects who see you on both LinkedIn and email perceive you as more credible. The LinkedIn connection also warms them up so when the email arrives, it does not feel cold.
Tools: PuzzleInbox for email infrastructure. Lemlist for multi-channel sending. Apollo for data. LinkedIn Sales Navigator for prospect research.
Comments (5)
pipelineco_kate · PipelineCo · 2026-01-30
Biggest lesson when we hired our first SDRs: don't let them touch infrastructure settings. We have a dedicated ops person who manages domains, DNS, warmup, and inbox health. SDRs focus only on copy, targeting, and booking meetings. Separation of concerns.
justdan · 2026-01-31
how long does it take a new SDR to ramp up on cold email? I'm thinking about hiring but worried about the learning curve
scalingsammy · 2026-01-31
in my experience about 4-6 weeks for a new SDR to be fully productive. first 2 weeks is training (tools, ICP, messaging), next 2 weeks is supervised sending, then they're on their own. having good SOPs makes this way faster
recruitingrachel · 2026-02-01
hire for curiosity and coachability, not experience. someone who's never done cold email but asks great questions will outperform someone with 2 years of bad habits. I've seen it over and over
haileyops · 2026-02-02
make sure you standardize infrastructure before hiring. every SDR should be using the same inbox provider, same sending platform, same DNS setup. if everyone is doing their own thing you'll have a nightmare debugging deliverability issues