HeyReach Overview
For agencies sizing it up: how sender rotation works, what a seat buys, and what the vendor publishes about its own LinkedIn presence.
HeyReach is a cloud LinkedIn outreach tool built around running many connected accounts at once. It rotates a single campaign across multiple LinkedIn accounts it calls senders, pools every reply into one shared inbox, and bills per connected account while seats stay free. The stated audience is agencies, sales teams and growth teams.
On this page
What HeyReach is
The homepage states the pitch in one line, “10x your LinkedIn outbound. Unlimited senders, one fixed cost”, and names the buyer directly underneath: “For agencies, sales teams, and GTM experts who want to automate LinkedIn outreach, reach 1000+ leads weekly, and book more meetings.” The page title places the product in its category as a LinkedIn automation tool for agencies, sales and growth teams.
The agency orientation runs deeper than the copy. Pricing has a dedicated agency tier, a whitelabel add-on exists, and the central mechanic is running one campaign across a pool of accounts belonging to different people.
Sender rotation and the Unibox
Two mechanics carry the product, and the vendor documents both.
Sender rotation is the reason the tool exists in this form. In the help centre’s words: “The only way to reach out to more leads on LinkedIn is to scale by assigning multiple LinkedIn accounts (senders) on one outreach sequence and auto-rotating through them.” The accounting matters as much as the rotation: “the daily limits are set per LinkedIn sender, and are shared between all campaigns that the LinkedIn sender is active in.” The distribution algorithm itself is undocumented.
The Unibox is the shared inbox. “The HeyReach Unibox allows you to manage all conversations from all leads from all LinkedIn senders, centralized in one place.” Access crosses account ownership: “Even if you are not the owner of that LinkedIn account, you can still engage with the lead on your teammate’s behalf.” For an agency running client accounts, that is the operating surface.
Execution is server-side, and each connected account is isolated at the network layer. HeyReach “gives a dedicated static residential proxy (i.e. real IP address that never changes) to each of your LinkedIn accounts, and never shares that IP between two accounts.” Accounts connect with credentials plus optional two-factor, or with LinkedIn cookies, and since July 2026 that connection can be made through the API.
What it costs
The billing unit is a connected LinkedIn account. The vendor puts it plainly: “HeyReach charges only per LinkedIn senders, not per users. Feel free to onboard your whole organization on HeyReach and manage everything together, completely free of charge.”
| Plan | Monthly | Quarterly | Yearly | Senders |
|---|---|---|---|---|
| Growth, under 10 senders | $79/sender | $71/sender | $63/sender | Per sender |
| Growth, 10 or more | $59/sender | $53/sender | $47/sender | Per sender |
| Agency, micro | $999 | $899 | $799 | 25 flat |
| Agency 50 | $1,399 | $1,259 | $1,119 | 50 flat |
| Unlimited | $2,999 | $2,699 | $2,399 | Capped at 300 |
The public pricing page and the help-centre article describe the same tiers at different granularity, and the help centre is the fuller of the two. Two further plans appear without published rates, a tailor-made Custom plan and a qualification-based Early Stage Startup plan. Enrichment credits run to 1,000 on Agency and 3,000 on Unlimited.
The word Unlimited carries a documented fair-use ceiling: “Fair-user policy. The plan is capped at 300 senders, to prevent any abuse of the platform.” Whitelabelling is an Unlimited add-on at “$500 per add-on”. Add-on senders on the Growth plan are sold at the per-seat rate, and no add-on rate is published for the Agency or Unlimited tiers.
The limits it enforces
HeyReach presents the hard numbers as LinkedIn’s, and its own contribution as enforcement. The two figures it publishes are a weekly invitation budget and a daily action budget.
- Around 100 connection requests a week per account. The counter “resets every Monday at 2 a.m. Pacific Time”, and HeyReach “automatically freezes any account in your campaign that gets really close to this limit”.
- Around 200 actions a day per account, on a broad definition the vendor spells out: “Viewing a profile counts as one action. Sending a message is another action.” Accounts freeze on their own at the ceiling.
- Per-action caps are the customer’s to set. “Feel free to configure the daily limits per each of the actions, connection requests, messages, follows, etc.” No fixed per-action defaults are published.
- Campaigns share a sender’s budget proportionally. “If your LinkedIn sender has a limit of 20 connection requests per day, and is active in 3 campaigns, the limits will be shared proportionally between the 3 campaigns.”
- InMails need Sales Navigator. “LinkedIn Premium accounts and Recruiter accounts cannot send InMails through HeyReach.” Credits are “typically 50 credits per month”, open profiles cost nothing and closed profiles cost one. Above roughly 40 InMails a day the vendor refuses, saying it “could impact your account’s health”.
On the programmable side the throttle is published: 300 requests a minute across all endpoints, answered with a 429 above that.
The API, the MCP server and the CLI
HeyReach has shipped a developer surface steadily since late 2025, and it is wider than most operator dashboards in this category.
The MCP server came first. A beginner’s guide was published on 9 October 2025, which makes it the earliest documented piece. It runs on HeyReach’s own infrastructure. Each workspace gets “its own MCP Connection URL and MCP Key”, generated in the app, and clients attach to that URL over HTTP. Claude Desktop reaches it through the mcp-remote bridge, VS Code registers it as an HTTP server, and the documented client list also covers Clay, Make and n8n. The raw hostname is per-workspace and never printed publicly.
The Campaign API followed on 21 April 2026, announced in beta: “Campaign API gives you full programmatic access to LinkedIn automation. Every feature, campaigns, inbox management, lead routing, analytics, is now accessible via our API.” Six endpoints were documented at launch, covering campaign creation in draft status and updates to settings, sequence, sender accounts and schedule, plus a read of the sequence configuration. A campaign accepts 1 to 100 sender account IDs. Authentication is an X-API-KEY header against api.heyreach.io.
MCP campaign tools arrived on 12 June 2026, listing eight tools that mirror those endpoints: create a campaign, create from a template, update the sequence, settings, schedule and accounts, read the sequence, and start the campaign. The vendor does not state that the June tools are built on the April API, so the relationship is inferred from the names alone.
Two more surfaces round it out. A CLI shipped on 16 June 2026, pitched as running “LinkedIn outreach from your terminal or straight from Claude, without ever opening a browser tab”. And on 23 July 2026 account connection itself became programmatic, through credentials with optional two-factor or through cookies, with a proxy-settings endpoint alongside it.
What the vendor says about account safety
HeyReach frames safety as enforcement plus isolation. The enforcement is the automatic freeze at LinkedIn’s weekly and daily ceilings, described above. The isolation is the proxy model, one dedicated static residential IP per connected account, never shared between two accounts. Beyond those two mechanics the vendor claims “a unique algorithm that incorporates a few more technical components” and “a healthy obsession with constantly following LinkedIn updates to ensure we adhere to their rules.”
The compliance position is stated most directly by the CEO, in a post of his own: “No limits get crossed, messages, InMails, connections. No fake accounts get created. No shady shortcuts.” HeyReach publishes no ban-rate figure, no sample size and no measurement method anywhere we could find, so the safety case rests on the mechanics and the claim.
The LinkedIn takedown, in the vendor’s own words
On 25 March 2026 LinkedIn removed HeyReach’s company page and restricted several executive profiles. The vendor published this itself, twice, and both accounts are worth reading before drawing conclusions from the event.
The same-day post from CEO Nick Velkovski: “You may have noticed LinkedIn recently removed our company page along with a few of our personal profiles (CTO, CRO, CMO).” His framing was that customers were untouched. “This has zero impact on you or the product. Your automations are running exactly as before.” He also placed it in context: “LinkedIn has done this to every major tool in our space, Apollo, Seamless, Evaboot, Lemlist, LGM”, and predicted a return: “These restrictions are temporary. We’ll be back on LinkedIn eventually, just like everyone else.”
A retrospective from CMO Vukasin Vukosavljevic followed on 7 August 2026, adding detail. “LinkedIn removed the HeyReach company page and restricted the personal profiles of our CEO, CTO, CRO, and CMO.” On the process: “No notice, no communication. We just couldn’t get in anymore.” And on scope, the distinction the vendor wants drawn: “The restrictions were limited to our own LinkedIn presence. Customer accounts, campaigns, and the platform itself continued operating normally.” The lasting cost is described as marketing reach, since the company can no longer post or run LinkedIn ads.
The two posts differ on who was restricted. March names the CTO, CRO and CMO. August adds the CEO. Both remain published.
What the event does and does not show is worth stating precisely, because it gets used loosely in this category. It is an action against a vendor’s own corporate presence on LinkedIn. Neither post reports enforcement against customer accounts, and the vendor states the opposite in both.
The shape of job it fits
HeyReach is built for one job and built well around it: running LinkedIn outreach across a pool of accounts that belong to several people, with the replies landing in one place. The per-sender pricing matches that job, the free unlimited seats match it, the Unibox matches it, and the whitelabel add-on says out loud who the buyer is.
The edges follow from the same design. The unit of scale is a connected LinkedIn account, so cost tracks accounts. The Unlimited plan stops at 300 senders. Safety rests on published mechanics with no published rate behind them. And the LinkedIn channel is the whole product, which is what made the March 2026 removal of the company page a marketing problem for the vendor and not a product one.
The developer surface is genuinely unusual for an operator dashboard, and it changes who can buy it: a hosted MCP server, a campaign API, a CLI and programmatic account connection put a lot of the product within reach of a script. Where a product needs LinkedIn actions as typed calls with a published safety figure behind them, the category also holds account-based APIs such as Unipile, Linked API and GTM API. On that stack, gtm-api.com reports 20,000+ accounts at under a 1% ban rate. The dividing question is whether the buyer is running campaigns for clients or building a feature.
Frequently Asked Questions
What is HeyReach used for?
Running LinkedIn outreach across several connected LinkedIn accounts at once. A single campaign rotates through a pool of accounts the vendor calls senders, daily limits are tracked per sender and shared across the campaigns that sender is active in, and every reply lands in one shared inbox called the Unibox that teammates can answer on each other’s behalf. The stated audience is agencies, sales teams and growth teams.
How much does HeyReach cost?
Pricing is per connected LinkedIn account, and seats are free. Growth is $79 per sender per month below ten senders and $59 at ten or more. Agency tiers are flat: $999 a month for 25 senders and $1,399 for 50. Unlimited is $2,999 a month with a published fair-use cap of 300 senders. Quarterly billing is 10% off and yearly is 20% off. Whitelabelling is a $500 add-on on Unlimited.
Does HeyReach have an API and an MCP server?
Both. A hosted MCP server has been documented since 9 October 2025, with a per-workspace connection URL and key, and clients including Claude, Clay, VS Code, Make and n8n. A Campaign API launched in beta on 21 April 2026 with six endpoints covering campaign creation and updates to settings, sequence, sender accounts and schedule, authenticated with an X-API-KEY header and throttled to 300 requests a minute. A CLI shipped in June 2026 and programmatic account connection in July 2026.
What are HeyReach’s sending limits?
The vendor publishes two ceilings and presents them as LinkedIn’s own. Around 100 connection requests per account per week, on a counter that resets every Monday at 2 a.m. Pacific, and around 200 actions per account per day on a broad definition where viewing a profile counts as an action. HeyReach freezes an account automatically as it approaches either. Per-action caps below those ceilings are set by the customer, and campaigns sharing a sender divide its budget proportionally.
Did LinkedIn ban HeyReach?
LinkedIn removed HeyReach’s company page and restricted several executive profiles on 25 March 2026. HeyReach published this itself, on the day and again in a retrospective in August 2026, and both posts state that the action was limited to the company’s own LinkedIn presence: “Customer accounts, campaigns, and the platform itself continued operating normally.” The CEO’s post placed it alongside similar actions against other vendors in the category. Neither post reports enforcement against customer accounts.
Sources & Further Reading
- HeyReach, homepage (the pitch and the stated audience) · pricing · plans and pricing (the per-sender table, the fair-use cap and the whitelabel add-on)
- HeyReach, sender rotation · Unibox overview · configuring sending limits · InMails, limitations and credits
- HeyReach, is HeyReach safe to use (the weekly and daily ceilings, the auto-freeze and the dedicated residential proxy) · a quick update from Nick (25 March 2026, the CEO on the takedown and on compliance)
- HeyReach, what LinkedIn did not delete (7 August 2026, the CMO retrospective) · Campaign API (21 April 2026, the six endpoints) · API reference (auth and the 300 requests a minute throttle)
- HeyReach, beginner’s guide to the MCP (9 October 2025) · MCP with popular tools (per-workspace URL and key) · MCP campaign tools (12 June 2026) · the CLI (16 June 2026) · LinkedIn login via API (23 July 2026)
- gtm-api.com, product · pricing (our own numbers)
- Related: 15 best LinkedIn automation tools · Best LinkedIn API · LinkedIn MCP server · Scaling LinkedIn outreach · LinkedIn account restricted
LinkedIn actions as typed API calls.
Connect an account server-side, send a connection request or a message as one endpoint, and read the limits before the call goes out. On that stack, gtm-api.com reports 20,000+ accounts at under a 1% ban rate. Free plan, then from $10 per connected account at volume.
Last updated: September 2026 · Every HeyReach figure, quotation and date on this page was read off the vendor’s own site, help centre, blog and API documentation on 4 September 2026 and is linked in Sources. Vendors move pricing and claims without notice, so verify before you buy.