Measured per conversation, as HeyReach's own benchmark is, our spring LinkedIn campaigns replied at 18.8% against its 22% median. Per person invited the same campaigns got 2.3%, which is the number to plan pipeline with. The tool worked; the surprises were in the API, where editing a live campaign sent it back to draft and some calls returned 200 while doing nothing.
We ran LinkedIn outreach through HeyReach on two sender seats from March to October 2026, mostly from scripts through its API and MCP server. The question for this review: did it perform the way the vendor says, and what does a team driving it from code need to know?
Our numbers against HeyReach's benchmark
HeyReach published a benchmark in September 2026 covering about 96,000 campaigns. It defines reply rate as replies divided by conversations started, so that's the fair way to compare. On that basis our spring campaigns replied at 18.8%, a few points under its 22% median. Accept rates on our spring pool ran under its median at first and above it later in the year.
The benchmark answers "once a conversation starts, how often does the prospect answer?" For planning pipeline you also want "of everyone I invite, how many reply?" On our spring campaigns that was 2.3%. Both are true of the same data; they answer different questions, and a vendor benchmark will quote the first.
Some of the gap to the median was ours. In one vertical campaign, about four in ten of the people who replied told us we had the wrong company, which is a list problem.
Accept rates followed the calendar
The most interesting result had nothing to do with the tool. Before a trade show we sent about 300 invites to people attending. Accepts ran at 4% to 8% in the first week, then 20%, then 44% in the last few days before the event. People accept strangers when they expect to meet them. If you have an event coming, put your LinkedIn volume in the week before it.
Where the funnel leaked
Of the people who accepted in spring, roughly a quarter never got a message from the campaign, and most acceptors who did never replied. HeyReach also stores no email addresses, so following acceptors by email needed a separate finder. Write the post-accept message before launch and check it fires.
What the API did
This is the part we'd want to know before building on it.
| Behavior | What it meant for us |
|---|---|
| Editing a scheduled or live campaign | Sent it back to draft |
| Webhooks | None we could receive without hosting an endpoint, so we polled |
| Seat activation | Not possible through the API |
progressStats.totalUsers on drafts |
Reported double the real count |
excludeInOtherCampaigns |
Didn't persist when set through the API |
AddLeadsToListV2 without a profile URL |
Returned 200 and added 0 leads |
| Emoji in a profile URL | Lead rejected |
| Message steps | Accepted branch only, at least 3 hours apart |
| InMail | Needs Sales Navigator |
We ran 25 connection requests a day per seat (40 is the maximum) and 40 a day for other actions.
Check your CRM before you upload
Our spring pool went in without a CRM check, and that was our mistake: people at existing customers and open deals got cold invites. HeyReach will send to whoever you load. Run your customer, open-deal and suppression lists against the pool first.
Pricing
On November 9, 2026 Growth was $79 per sender a month for 1 to 9 senders and $59 from 10. Full plans on the HeyReach pricing page.
Per LinkedIn sender: $79/sender/mo for 1-9 senders, $59 from 10; yearly $64 or $48; 100 enrichment credits per sender
Who it fits
| You are | How it went for us |
|---|---|
| Running LinkedIn from two or more seats | Good fit; per-seat limits stack |
| Working an event or trade show | Our best LinkedIn results came the week before one |
| Editing campaigns while they run | Plan for them dropping back to draft |
| Wanting replies pushed to your systems | Host a webhook receiver or poll |
| Following acceptors by email | Bring your own email finder |
Try it in 30 days
- Clean the pool against your CRM and suppression lists.
- Run one list per campaign on one seat at 25 invites a day.
- Write the post-accept message before launch and confirm it fires.
- At day 30, report replies per conversation (to compare with the benchmark) and per person invited (to plan with).
More options: HeyReach alternatives, HeyReach vs Expandi and the LinkedIn outreach tools guide. Our cold email results from the same months are in cold email reply rates.
Questions buyers ask
What reply rate should I expect from HeyReach?
Close to its benchmark if you measure the same way: our spring 2026 campaigns got 18.8% replies per conversation against a 22% median. Per person invited it was 2.3%, the better number for pipeline planning.
What is a good LinkedIn connection acceptance rate?
HeyReach's benchmark median was about 21% in September 2026. Ours ranged from under that in spring to 25% to 30% in October, and reached 44% in the days before a trade show.
Can I edit a live HeyReach campaign?
Editing a scheduled or live campaign through the API sent it back to draft for us. Make changes before launch or plan to relaunch.
Does HeyReach have webhooks?
We found none we could receive without hosting our own endpoint, so we polled the API on a schedule.
Does HeyReach store email addresses?
No. Following acceptors by email needs a separate email finder.
How much does HeyReach cost?
Growth was $79 per sender a month for 1 to 9 senders and $59 from 10 on November 9, 2026.
Sources
Compare alternatives
Compare the part of the workflow you want to replace, including scope, billing and operating responsibility.
HeyReach alternatives →