What AI Actually Does in LinkedIn Outreach, and What Breaks
AI drafts openers and sorts replies, but sending stays separate. Here is what breaks in DIY LinkedIn outreach, from blank variables to 48-hour restrictions.
What does AI actually do in LinkedIn outreach?
Four jobs, and sending is not one of them. AI reads the prospect's profile and recent posts, drafts a first line that references something real, classifies the reply that comes back, and drafts the response. The connection request itself still goes through an automation layer or a browser session that LinkedIn sees as you.
Keep those two layers separate when something breaks. If accept rate slides from 25% to 12%, the writing is suspect. If the account picks up a restriction, the sending layer is suspect. People rewrite prompts for a week while the actual problem is a cloud server in Frankfurt logging into an account that has always logged in from Lisbon.
Reply classification saves more hours than the opener does. At 440 invites a month and a 25% accept rate you get 110 new connections, and at our 12 to 18% first-message reply rate that is 13 to 20 replies to read. Six are "sure, send me info", five are "not right now", three are "we already use Clay", two are irrelevant. Sorting that and drafting the first pass is where the hours go.
What breaks when you build it yourself?
Five things, reliably: duplicate contacts when lists come from two sources, rate limits that trip after the first good week, replies piling up unanswered, profile scrapes returning empty fields so the personalised line reads "I saw your work at ", and the account picking up a temporary restriction that pauses everything for 48 hours.
Getting a flow that sends takes a weekend. Keeping it alive is the part nobody posts about. LinkedIn changes a DOM element, the scraper returns null, and your sequence sends 40 messages with a blank placeholder before anyone notices. The fix is a validation step that kills any message containing an empty variable, which takes ten minutes to write once you know you need it.
The 48-hour pause is the expensive one. On a 20-a-day account that is 40 invites you never sent, and at a 3 to 5% meeting rate those 40 invites were worth one or two meetings. Restrictions also tend to arrive in the week you finally got the copy working.
How do you stop messaging the same person twice?
Pick one dedupe key and normalise it before anything enters the queue. LinkedIn gives you a vanity URL and a numeric URN for the same person, and two exports from two different sources will hand you one of each. Strip the protocol, strip trailing slashes, lowercase it, and dedupe on that.
The second duplicate source is time. Someone you invited in March who never accepted is still in your CRM as "contacted". If your new list pulls from a fresh search, they come back through the front door. A suppression table with a date column solves it. Anyone touched in the last 90 days is excluded, regardless of outcome.
The third is the comment-to-DM loop, where the same person comments on three of your posts in a fortnight and gets three DMs. Any tool worth running checks against prior sends before it fires, and most of the ones marketed as comment-to-DM do not.
How many invites a day can you send before LinkedIn stops you?
LinkedIn does not publish a number, and it moves with account age, profile completeness and how people respond to you. What we run: 20 to 25 a day on a warm account, 5 to 10 on a new one for the first two weeks. That is 440 to 550 invites a month from one profile.
Going to 200 a day buys you about nine days. Then invites stop going out and the restriction notice arrives. LinkedIn is conservative with volume even inside its own products: recruiters on Hiring Pro get five AI-composed InMails per day.
Three warm profiles at 25 a day is 1,650 invites a month, roughly 50 to 82 meetings at a 3 to 5% rate, and also three inboxes of replies landing on whoever owns them. Founders add the second seat for the volume and then discover the second seat is mostly more reading.
Does sending more invites get you proportionally more meetings?
No, because accept rate falls as personalisation thins. A team posting in r/SaaS reported 22% connection acceptance on AI-assisted outreach, which sits at the bottom of our 20 to 30% band. At 440 invites a month, here is what that chain produces.
| Step | Our benchmark | At 440 invites a month |
|---|---|---|
| Connection accepted | 20-30% | 88 to 132 new connections |
| Reply to first message | 12-18% | 11 to 24 replies |
| Reply to a follow-up | 5-8% | 4 to 9 more replies |
| Meeting booked | 3-5% of invites sent | 13 to 22 meetings |
Expandi ran the numbers across 13.2 million connection requests from 13,302 accounts and breaks acceptance down by industry, which is worth checking before you decide your 19% is a disaster. If you sell to engineering leaders, 19% may be the ceiling.
At 20 invites a day you can look at every profile. At 200 you cannot, so the opener goes generic and accept drops to 12%. You now send 920 invites to land the same 110 connections, and the account carries five times the behavioural load to get there.
Can LinkedIn tell you used AI to write the message?
Probably not from the prose, and that is not where the risk sits. Restrictions follow behaviour: login from a new IP, 60 invites in 40 minutes, identical message bodies, click patterns with no mouse movement. LinkedIn ships AI-written InMails inside its own Recruiter products, so the writing itself is not the trigger.
The thing people notice is sameness. If four people in the same Slack group get a message opening with "Your post on hiring ops really resonated", they compare notes and screenshot it. Vary the opener structure, not just the variables inside it, and cap each template at a few dozen sends before it gets retired.
Accept rate is also a profile problem more than a copy problem. A prospect reads your headline and your banner before they read anything you sent. If your headline says "Founder | CEO | Helping businesses grow", fix that first with the LinkedIn headline rewriter and run the same copy again.
What should AI write and what should you still write yourself?
AI should write the personalised opener, the reply classification, and the first draft of every response. You should write the offer line, the objection answers, and anything involving a number about your own business. The offer is the one sentence that decides whether someone books, and it is worth twenty minutes of your time, once.
The practical version: give the system five objections you hear weekly with the answer you use on calls. "Too expensive" gets the ROI framing. "We use Clay already" gets the complementary framing. "Not now" gets a dated follow-up rather than a pitch. Without that file, a model answers "too expensive" by asking for a call, and the thread dies at message two.
Is it cheaper to build it in n8n or buy an AI SDR?
Depends on whose hours you are spending. A tutorial will show you the flow in an hour. Budget 20 to 30 hours for a version you trust with a live list, which at $100 an hour is $2,000 to $3,000 of founder time, plus roughly 4 hours a month on repairs and the scraping and enrichment credits on top.
The build ends. The replies do not. Twenty replies a week at six minutes each is two hours a week, eight hours a month, 96 hours a year. At $100 an hour that is $9,600, and it recurs in any month where the sequence is actually sending.
Gelee is a LinkedIn-native AI SDR that handles outreach, replies in your voice, objections from your playbook and the booking, including a preset that DMs everyone who comments on a watched post and then replies publicly once the DM lands. Setup is 15 minutes, there is no self-serve signup, and pricing is shared on a demo call.
Who should build their own?
Anyone technical, sending under 200 invites a month, on one account, for themselves. At that volume the whole thing is a Google Sheet, an n8n flow and an hour a week, and paying anyone for it would be silly. The same is true if you are automating a workflow you have never run manually.
Agencies running outreach across 15 client accounts are a different case. HeyReach plus Clay is a common pairing there, and a multi-account dashboard with per-client inboxes is something to buy rather than build. Gelee is also wrong for you if your buyers are not on LinkedIn, if your average deal is small enough that one meeting a week would not cover the tool, or if you want to keep writing every message yourself.