A LinkedIn outbound playbook that doesn't feel like spam
tech2gtm · · Updated · 5 min
Short answer
LinkedIn outbound works when the sender's profile is credible, connection requests are short and specific, the first message comes only after acceptance and adds value, and LinkedIn is combined with email in one sequence instead of running as a separate campaign.
01
Fix the profile first
Prospects check the sender's profile before replying. The headline should say who you help and with what, not a job title alone.
Post occasionally about the problem you solve so the profile looks active.
02
Requests and follow-ups
Keep connection requests under 200 characters, or send none at all. Mention one real reason to connect.
After acceptance, wait a day, then send something useful: a short insight, a relevant example, a question. Avoid pitching in the first message.
03
Combine with email
A common pattern: profile view, connection request, email on day 3, LinkedIn message on day 5, email follow-up on day 8.
Stay within LinkedIn's weekly invitation limits to protect the account.
04
Implementation check
A LinkedIn outbound playbook should define connection, follow-up and email steps as one sequence. Log each touch in the CRM, avoid duplicate outreach and give every follow-up a reason tied to the account's context.
From practice: Gaming İstanbul / GIST
For Gaming İstanbul / GIST, partnership outreach and communications had to reach partners, sponsors and audiences at once. Each group needed its own message; one generic note to everyone would have been ignored.
Technical takeaway: split LinkedIn sequences by stakeholder type, not just by job title, and write the connection request around why that group specifically should care.
Frequently asked questions
How many connection requests per week are safe?
Staying well under LinkedIn's weekly invitation limit, often around 100, keeps accounts safe.
Should I add a note to connection requests?
Test both. Blank requests often have higher acceptance; short specific notes can lead to better conversations.