A LinkedIn AI agent with hands
See a real LinkedIn AI agent session: Claude writes every invite and message over MCP, PoliteReach sends them from your own account under 12-16/day caps.
Most demos of a LinkedIn AI agent stop at the draft. The model writes a sharp message, the founder nods, the video ends. Nobody shows the send. Sending is the part LinkedIn polices and the part chatbot wrappers quietly hand back to you. PoliteReach exists for the send.
The split is simple. Claude, connected over MCP, is the brain: it picks targets, writes every connection note and message, reads replies, drafts answers, and decides next steps. PoliteReach is the hands. A real headful Chromium browser runs in the cloud, signed into your own LinkedIn account, executing exactly what the brain approved. No extension, no injected code.
What an AI agent to send LinkedIn messages actually needs
A model that only drafts is a writing tool. An AI agent to send LinkedIn messages needs three things a chat window doesn't have: a real logged-in browser session, a way to detect invite acceptance, and limits that hold even when the model is wrong. PoliteReach supplies all three. (LinkedIn exposes no acceptance API, which is why the second one is harder than it sounds.)
The browser is headful Chromium in the cloud with one persistent device profile per account, behind a residential or ISP IP you supply and ASN-check with ipapi.is so datacenter ranges get rejected. It looks like your laptop. Acceptance is inferred by diffing: PoliteReach compares your current connections against still-pending invites and records the overlap as accepted. The caps live in the executor. A prompt can't reach them. The tools are plain MCP; Claude is the default brain, but any MCP client or custom agent can drive them.
What one agent session looks like, tool by tool
Each step in the run below is the actual MCP tool the assistant calls, not a metaphor.
Claude ingests 20 prospects, sequences attached
Claude calls the ingest tool with 20 profile URLs. Each prospect carries a personalized connection note plus prewritten Day 1, Day 3, Day 7, and Day 14 messages, all drafted by Claude and reviewed by you before anything queues. None of it changes later. Nothing is generated at send time; if a message exists, you've already read it.
PoliteReach drips the invites under caps
No tool call here; the executor takes over. Invites go out at 12 to 16 a day, jittered, averaging about 14, inside office hours, each note typed keystroke by keystroke. The cap doesn't negotiate. Claude queued 20 prospects; it could queue 500 and the daily number wouldn't move.
Claude checks acceptances by diffing connections
Two days later, a scheduled routine calls the acceptance-poll tool. PoliteReach diffs the connection list against pending invites and finds three matches, so three acceptances get recorded and three Day 1 messages get scheduled off each acceptance time. The other seventeen keep waiting. Anything still pending after 60 days gets withdrawn automatically; the window is configurable down to a floor of 7.
A reply halts the sequence before Claude sees it
One accepted prospect answers the Day 1 message. The instant that reply lands, every remaining step for that prospect stops, permanently. Claude then calls the conversation-list tool, spots the new reply, and pulls the full thread with real timestamps through the read tool. Now it drafts.
You approve the reply before it ships
Claude writes an answer in the thread's context and puts it in front of you. You edit or approve; the send tool ships it through the same cloud browser. Messages to people you're already connected with aren't invite-capped, so a live conversation moves at conversation speed. Deals aren't rate-limited.
Claude posts to your feed between runs
Before signing off, Claude calls the post tool with a short take your prospects would actually read; the tool accepts up to 3,000 characters and an optional image. Posting matters. An account that only sends invites reads as a bot; one that also talks reads as a person.
Every word PoliteReach sends existed, and was approved, before the first invite went out.
You can use AI to send LinkedIn messages and still approve every word
The division of labor is strict. You own strategy and approval: who to target, what the offer is, what each draft says before it goes anywhere. Claude proposes, PoliteReach executes, and the full action log records every step either of them took. If something feels wrong, revoke your LinkedIn session cookie and everything stops that instant, because the session is yours, not ours. That's real control.
The brain is swappable too. Change the model, the prompt, or the whole strategy any day; the executor doesn't care who wrote the words. No seats, no per-contact credits.
The caps the agent can't talk its way past
Limits are enforced in the execution layer, not in the prompt. Claude can't raise them, and neither can a prompt injection. The published set:
- 12 to 16 invites a day, jittered, averaging about 14
- Rolling 7-day counter held under LinkedIn's roughly 100-a-week line
- Invites sent during office hours only
- Optional 3-week warm-up ramp
- Per-keystroke humanized typing on every note and message
- Per-account circuit breaker that freezes jobs on a security checkpoint
- Auto-withdrawal of invites pending more than 60 days (configurable, floor of 7)
Messages to existing connections are deliberately uncapped, because invites are the action LinkedIn punishes and conversations are the point. A checkpoint on one account never pauses the others.
The caps live in the code that does the sending, so no prompt, model swap, or bad day can move them.
What a LinkedIn automation AI agent should cost
PoliteReach is in early access with no published price. So the honest comparison is stack cost, meaning what you'd spend to run the whole thing: Claude Pro or Max at $20 to $200 a month (claude.com/pricing), an ISP proxy at $10 to $30, a small server at $10 to $20. Call it $130 typical. Here's the field.
| Option | Price | Source |
|---|---|---|
| AiSDR | $250 / $900 / $2,500 per month, published | aisdr.com/pricing |
| Artisan (Ava) | ~$600/mo entry reported, billed annually; $1,000-$2,500/mo typical active spend | landbase.com |
| Regie.ai | $180/user/mo, 10-seat minimum ($1,800/mo floor) | landbase.com |
| 11x (Alice) | ~$5,000/mo reported, $50K-$60K first-year minimum; no public pricing page | getbreakout.ai |
| Seat tools (Linked Helper, Dripify, Expandi, HeyReach, Waalaxy, Skylead) | $15 (Linked Helper) to $100 (Skylead) per seat per month | vendor pricing pages |
| PoliteReach stack | $50-$230/mo running cost, ~$130 typical | your own bills |
Two caveats. The 11x and Artisan numbers are sales-quoted or reported rather than list prices, and the AI SDR platforms bundle lead databases plus email sending that this stack doesn't include. Both matter. Computed against a $130 stack, the gaps run about 7x for AiSDR's $900 Explore tier, 8x to 19x for Artisan, 14x for Regie.ai, and roughly 38x for 11x. Seat tools sit at parity. The difference there is the brain: Dripify schedules templates, while an agent reads the thread and decides the next move.
Early access, no price tag, three gaps
LinkedIn invites, messages, and feed posts on your own account, driven by the AI you already pay for — that's the surface. If it's the half of outreach you've been doing by hand, put your AI on it. Start at politereach.com.
Want outreach that stays inside the caps?
PoliteReach is in early access. Every cap it uses is published, so you know exactly what it will and won't do with your account.