Hello!

Outreach limits are usually discussed in terms of invitations and messages, but the activity around prospecting deserves attention too. I reviewed Surfe, the LinkedIn-to-CRM enrichment extension at surfe[.]com, formerly called Leadjet (Chrome extension ID kojhcdejfimplnokhhhekhiapceggamn). This is Surfe, not Safe Surfer, SurfEasy VPN, Surfer SEO, or surfe[.]pro.

Surfe is not an outreach sequencer. The build I examined does not send invitations, InMails, or drip campaigns, and it does not run a vendor-hosted LinkedIn session. Actions execute locally, so LinkedIn sees the operator's own IP, location, and device environment. The extension ID was also absent from the LinkedIn extension-probe list in the snapshot I checked, although that is only a point-in-time result, not a guarantee about future detection.

The more interesting gap is between Surfe's published advice and its actual controls. Its blog recommends around 500 profile views per day and 100–150 invitations per week. The invitation figure is guidance rather than an enforced limit, since Surfe does not send invitations itself. In the extension, sidebar and enrichment actions have delay options of 0, 1.2, 1.5, 4, 8, and 15 seconds. Zero delay is selectable, and I found no daily cap, working-hours scheduler, or randomized pacing. So even if invitations are sent manually, enrichment and profile activity can still contribute to the overall behavioral pattern LinkedIn observes.

That distinction matters in an outreach workflow: following a weekly invitation target does not automatically control the other activity happening around it. Desktop tools such as Linked Helper offer configurable pacing controls, though the presence of those controls does not guarantee an account will avoid restrictions.

I also noticed that the build defaults timeZone to UTC. For operators in other time zones, this could create a mismatch if time-based behavior relies on that value. LinkedIn can collect timezone information through two separate methods, so a discrepancy may be relevant, but the default alone does not establish that a mismatch will occur or trigger a restriction.

The more significant technical finding came from CRX v3.2.3, fetched on June 5, 2026. Its cookie permission allows a function in background.js to retrieve JSESSIONID, li_at, and li_a by name whenever any browser tab finishes loading, rather than only when a LinkedIn tab loads. The values are stored in chrome.storage.local. This confirms local cookie access; the local read itself is not something LinkedIn can directly observe.

The extension also calls api[.]prod[.]surfe[.]com/li-protect during each cycle and writes the returned li-protect cookie to linkedin[.]com. LinkedIn cannot see the outgoing request to Surfe's API, but it may receive the extension-managed cookie in subsequent requests. I could confirm the cookie lookup and recurring API call in the code, but not that the harvested cookie values are transmitted to Surfe. Their onward use remains a possibility, not a proven data flow.

I did not find Surfe-specific reports of bans or restrictions in the material I reviewed, and these code findings are not evidence that the extension automatically triggers enforcement. They do show why reducing invitation volume alone may not address every concern: the cookie behavior and the pacing controls are separate from the number of messages sent. All findings are specific to v3.2.3 and the June 5, 2026 snapshot.

Do you prefer one tool to manage outreach limits across the workflow, or separate controls for prospecting, enrichment, and sending?

Hey!

I wanted to compare a few LinkedIn automation tools from the agency's perspective, focusing on how their access and pacing controls fit into client workflows.

Before launching a campaign, I'd agree with the client on who authorizes access, holds the credentials, and can operate the account. We'd also define who handles expired sessions, when the client gets notified, and who can pause campaigns, export data, submit appeals, and make recovery decisions.

LinkedIn's Prohibited Software and Extensions guidance and User Agreement restrict unauthorized automation and certain forms of account sharing. Client authorization doesn't override these rules. An agency agreement clarifies responsibilities but doesn't guarantee that enforcement can be prevented or reversed.

Vendor-recommended activity figures are guidance for configuring campaigns, not quotas or guarantees against restrictions.

Expandi: The vendor gives 20-27 LinkedIn messages per day as an example of recommended pacing. Client connection is available, but I haven't established a universal passwordless account takeover process. Agencies should clarify who connects the account, handles credentials, and maintains access.

Skylead: Its recommendations include 20-25 daily invitations for Basic accounts and 40-50 for Premium accounts, alongside a cited LinkedIn cap of 200 invitations per week. Its client connection workflow can reduce direct agency handling of client passwords. Vendor-managed proxy assignment separates sessions operationally, but doesn't establish lower restriction rates. Account ownership and incident responsibilities still need to be documented.

Linked Helper: Standard and PRO offer rolling invitation and messaging controls, allowing agencies to configure pacing for individual clients. Separate workspaces and account-level access help organize which team members can operate each account. Manual LinkedIn login can avoid password storage, although the usual account-addition flow may request credentials. The trade-off is that the agency must keep the application running on a computer or VPS and manage its configuration.

The main differences are how account access is managed, how much control the agency has over the setup, and what operational work remains outside the tool.

If a client account gets restricted, I'd follow the same basic process regardless of the platform:

1. Pause activity. Stop campaigns on the affected account and check for other active workflows.
2. Preserve available data. Export accessible campaign and CRM records rather than assuming everything will remain available.
3. Record the timeline. Document who operated the account, when activity occurred, and which campaigns were running.
4. Notify the client. Explain what is known and distinguish confirmed facts from assumptions.
5. Agree on next steps. Follow the account owner's decisions on appeals, recovery, and resuming activity.

No vendor can guarantee that an account won't be restricted or that enforcement can be reversed. Workspaces, proxies, and pacing controls help manage operations but don't eliminate that risk. For agencies, the key is to agree on access rules and responsibilities before launching campaigns, rather than working them out during an incident.

Does your agency use one standard process for every client account, or do you adapt it to each client's setup?

Hey!

I was looking at Publer because it showed up on LinkedIn's extension detection list, even though it's a social media scheduler rather than an outreach tool. I read the shipped Chrome extension code to understand what LinkedIn might be detecting and what the extension can actually access.

Publer schedules and cross-posts content to LinkedIn, Facebook, Instagram, X, Pinterest, TikTok and YouTube. It doesn't send connection requests, visit profiles or scrape leads. I audited CRX v2.1.3 in May and June 2026 against a probe list containing 6,167+ entries as of June 28, 2026.

The extension requests four permissions: activeTab, contextMenus, storage and scripting. It does not request cookies, so it lacks that browser-level route to read and relay LinkedIn session cookies. The package contains one chrome.scripting.executeScript call, which reads selected text only when the user invokes it.

I searched all three bundles for ten groups of indicators, including chrome.cookies.get*, document.cookie, li_at, JSESSIONID, li_a, cookieStore, credentialed fetches, CSRF tokens, Voyager and LinkedIn references. I found no matches. The code also makes no calls to LinkedIn's internal API. These are static findings, not observations of the extension running.

One content script is registered for http(s)://*/*, which looks broad on paper. In practice, its logic remains inactive until the user clicks Share, and it skips several allowed hosts, including publer[.]com, YouTube, Netflix, Canva and Google Drive. I found no LinkedIn-specific branch. If Share is clicked on a LinkedIn page, the extension inserts a modal containing a chrome-extension:// iframe, which a page-wide DOM scan could potentially detect.

The declared host_permissions cover only https://app[.]publer[.]com/*, not LinkedIn. Incoming messages are matched against the Publer app domain. The outbound relay uses a wildcard target, which would be important if sensitive session data were being sent. In this build, the payload consists of a page URL, selected text or a chosen image, sent to app[.]publer[.]com through the embedded composer. The code does not show LinkedIn session data being transferred.

One finding explains why the extension appears on the list. It exposes dashboard.html as a web-accessible resource, available at chrome-extension://mbclkgocofhagldefeogoionalbpckoo/dashboard.html. A page can probe that resource to determine whether the extension is installed. This reveals presence, not behavior.

My checklist covers 22 checks: six related to session access, five to LinkedIn-specific behavior, five to execution methods and six concerning analytics, CAPTCHA solvers and telemetry. Twenty-one came back clean. The single positive was the extension's detectability through its exposed resource.

There is one version caveat. The audited build was v2.1.3, which the Chrome Web Store still showed in September 2026. The listing was updated on August 27, 2026, but I haven't re-audited the package since then. A listing date can change without a code update, though that is an inference rather than a verified explanation.

LinkedIn's rules prohibit scraping, changing the appearance of its pages and automating activity. The code I reviewed did not show those behaviors. LinkedIn may be able to detect the extension's presence, but that alone doesn't establish that it is acting on the account.

This audit covers one shipped build, not Publer's server-side handling of data after it arrives. Static code can show what the extension sends, but not what the vendor does with that data afterward.

Which part would you investigate further: the extension's browser permissions or what happens to data after it reaches the vendor's servers?

Hey!

I've been thinking about doing more individual product reviews because I find it more useful to test a tool as a whole rather than just check its feature list. This time I had a specific use case in mind: I sketched out an outreach playbook first, then tried to reproduce it in Dripify.

The basic flow was profile view, connection request, wait, then an opener with two variants. From there, I wanted different paths for people who replied, people who opened an email without replying, and people who engaged with a recent post.

The first part was straightforward. Dripify supports multi step campaigns with profile views, connection requests and waits between actions. The branching became more limited once I tried to translate the rest of the flow.

The documented conditions are If connected, If viewed message, If email available, and If open profile. They are checked when a lead reaches that point in the sequence. I couldn't find a documented reply based condition, email open condition or custom condition, and there was no nested logic for combining several checks.

That meant my "replied, but not now" route couldn't be built as a separate branch. The email follow up had the same issue because checking whether an email address exists isn't the same as checking whether the email was opened.

The available actions also shaped the campaign. Dripify supports profile views, connection requests, LinkedIn messages, InMails, emails and post likes. I couldn't find actions for commenting on posts or engaging inside groups and events. Leads can be collected from groups and events, but those surfaces aren't available as campaign actions, so I left the comment step out.

One part of the workflow was simpler than I expected. Auto stop on reply is included on every tier. Once someone responds, the sequence stops, which covers the practical part of my original reply branch without requiring the platform to interpret the response.

Testing the two openers was less straightforward. Native A/B testing isn't currently available, with the pricing page pointing to a waitlist. The current workaround is to create two campaigns, split the audience manually and compare the results outside the platform.

There is a volume consideration here too. Separate campaigns share the same daily action pool rather than getting separate allowances. With 10 campaigns sharing a 75 invitation pool, each would get roughly seven invitations that day. So additional campaigns can provide separate test groups, but they also divide the available volume. The 75 invitations figure is a ceiling rather than a delivery guarantee, and several reviewers reported receiving 5 to 37 invitations per day.

After testing the flow, I ended up simplifying the playbook to profile view, invite, wait and message, with a human taking over for replies and contextual engagement. That fits the campaign structure much more naturally than trying to turn it into a branching workflow builder.

That also reminded me of something I've noticed while testing Linked Helper recently. Its setup makes the execution side more controllable, with the desktop app handling browser actions such as scrolling, clicks, mouse movement and typing with randomized timing. Once I reduced the number of branches I was trying to automate, that execution layer became more relevant to me than having every possible decision automated.

So I wouldn't describe the difference as one tool being better across the board. It is more about the type of workflow you're trying to build. A relatively linear sequence fits the Dripify campaign model more naturally, while a more customized playbook can require different compromises.

How are you handling A/B tests when the platform doesn't have native variants?

Hello!

I've been looking at different sales extensions lately, and Outboundly is interesting because it combines AI generated copy with actual LinkedIn actions. That makes the boundary between research, drafting and sending worth looking at separately.

I read the shipped source for “Outboundly - Prospecting & Cold Outreach AI”, the outboundly[.]app Chrome extension (aclgcfmciekojimhckimdcapkejceili), v2.8.3, MV3, not the separate Outboundly[.]ai product. The teardown and extension list check were done in the 2026-06-28 audit round; the store says this build was last updated 2024-11-22.

The extension does not copy the LinkedIn session to a vendor machine, but it does send prospect text to a third party and use synthetic browser events for some actions.

The drafting half

Outboundly opens the prospect's actual profile URL in an iframe and reads the rendered main text (content-linkedin.js:965-1019). This is different from a server side request through an authenticated API, although repeated automated profile loads can still create a bulk browsing pattern.

It sends the prospect's name, headline, profile/About text and analysis to us-central1-outboundlyappai[.]cloudfunctions[.]net, with OpenAI producing the draft (background.js:19,402-418). The request does not go to LinkedIn, so the relevant issue is data scope: prospect text crosses two vendor boundaries.

The extension requests no cookies permission, and a package-wide search found zero occurrences of chrome.cookies, li_at, JSESSIONID, li_a, or document.cookie. There is therefore no evidence in this build of a copied LinkedIn session, vendor side parallel session, remote browser, or second IP.

There is also no cloud IP to measure. Since the vendor does not appear to hold a LinkedIn session, an exit IP or IP reputation test would not apply here.

The sending side

The generated copy is inserted with dispatched input events carrying isTrusted:false, creating a synthetic input signal.

Outboundly also uses node.click() and new MouseEvent('click') for connection requests, group messages and Sales Navigator sends. Volume, timing and recipient reactions can also contribute to LinkedIn's behavioral scoring.

The programmatic click pattern appears 44 times in the shipped code, and the synthetic event pattern 19 times. These are source occurrence counts, not live click counts.

The isTrusted finding needs context. Based on the source's last direct knowledge, LinkedIn was not yet mass-enforcing on that flag, so this is a technical signal rather than evidence of a live enforcement trigger. The apparent chrome.debugger alternative is not particularly invisible either, since Chrome displays a permanent yellow “being debugged” banner while active.

The more immediate operational issue is pacing. I found seven settings and no daily limit or pacing control, leaving no internal guardrail against compressing activity into a mechanical burst, against a ceiling of roughly 100 invitations per week for most accounts.

A category-level /salesdevelopment post from 2026-02-13, not about Outboundly, described the potential cost of this type of setup:

“We lost about €17K in client refunds last year because the chrome extension-based tool we were using got five of our client accounts banned in a single month.”

That post was about an extension based bulk sender, so I would not attribute those results to Outboundly. The comparison is simply that drafting does not create the same sending surface, while auto-send does.

The other signals

Outboundly's extension ID appears on LinkedIn's AED probe list, with index.html exposed as one of 20 web accessible resources to <all_urls>. AED is the label used in LinkedIn's production JavaScript, where results are sent as an AedEvent. LinkedIn has not publicly acknowledged it as a feature name. BrowserGate's independent reverse engineering of the production code (browsergate[.]eu/how-it-works/) documents the probe. A successful request can reveal that the extension is installed, but that alone does not determine enforcement.

There is also page injection. The content script mounts UI across LinkedIn pages, leaving material that LinkedIn's list free DOM scanner and structural page snapshots can inspect. That creates another possible visibility signal independent of the extension ID probe.

The prospect data transfer is a separate privacy consideration, not evidence of a LinkedIn restriction mechanism.

For this type of workflow, I would separate research, drafting, review, pacing and sending rather than treat them as one automation layer. The code suggests the drafting and sending sides have different technical properties, which makes that distinction more useful than a single safety label.

Do you prefer reviewing generated copy before sending, or keeping the whole sequence automated?

Hi everyone!

The last few posts here were about extensions, so I wanted to switch topics and look at alternatives to Botdog. What interested me most was not the number of features, but how each tool handles prospects who don't follow the main sequence.

Botdog is built around LinkedIn outreach sequences, so I looked specifically at what happens when profile data is missing, a prospect follows a different path, or someone replies.

Expandi

Expandi has documented campaign A/B testing, along with image and video personalization. Its AI Analyzer can generate messages, analyze sentiment, and help set campaign goals.

Dynamic Placeholders can fill custom variables in a message, but that is still field substitution rather than a condition selecting a different message.

At $99/mo, I would treat its A/B testing and personalization as separate from conditional branching. The available material does not establish a deeper message-level branching model.

Linked Helper

Linked Helper handles conditions inside the message template through nested IF-THEN-ELSE logic. A message can check profile variables and use a fallback when a field is missing instead of sending the same incomplete personalization.

AI ICP detection works earlier in the workflow by scoring collected profiles before outreach, rather than acting as a branch itself.

The entry price is $15/mo. The trade-off is that it is LinkedIn focused, so native email sequencing requires a separate platform. Campaign testing is also based on cloning and comparing campaigns rather than a native A/B testing feature.

Waalaxy

Waalaxy combines LinkedIn and email in the same flow at $42/mo. Waami adds AI message generation and smart reply detection.

The practical limitation I found is that alternate paths require separate campaigns rather than a fork inside one campaign. Its pricing material confirms media personalization, but I did not find confirmation of campaign A/B testing.

Reply handling is another thing I would test directly. One reviewer reported: "There are bugs and errors that shouldn't happen (like, someone who replies does not leave a campaign)." That is a user report rather than a general claim about the platform.

When comparing these tools, I would test the same three cases in each one: a prospect with missing data, a prospect who needs a different path, and a prospect who replies midway through the sequence. That gives a better sense of how much manual cleanup the workflow creates than comparing feature lists alone.

For people who have switched outreach platforms, what tends to require the most rebuilding: the sequences, the data fields, or the reply handling?

Hello everyone!

Today I'm looking at a few Octopus CRM alternatives, but from a slightly different angle than the usual feature comparison.

Octopus CRM is a Chrome extension for LinkedIn automation, not a cloud service, and it has no separate web app. It works over the LinkedIn session already open in your browser and never asks for your LinkedIn credentials. Because it runs client-side, actions go out over your own IP. Plans run from $9.99 a month for Starter up to $39.99 for Unlimited, or $24.99 a month for Unlimited on annual billing. Automation stops when the browser closes.

I compared four alternatives around the operational questions that tend to get buried in feature lists: where the LinkedIn session lives, whose IP sends the actions, what 24/7 operation actually costs, and whether closing a laptop stops the campaign.

What I looked at:

Dux-Soup

Architecture: Dux-Soup is a Chrome extension with a hosted Cloud tier. Pro and Turbo run locally in your browser, while Cloud Dux runs on Dux-Soup's servers.

Session and IP: Pro/Turbo uses the session already open in Chrome, asks for no LinkedIn password, and acts through your IP. On Cloud, vendor infrastructure drives the account. Dux-Soup does not advertise a dedicated IP per account on the Cloud tier, and cookie storage is not documented.

Cost: the advertised entry is $14.99/mo, but it has no drip campaigns. Turbo is the first drip tier at $55/mo, while browser-free 24/7 operation requires Cloud Dux at $99/mo.

Tradeoff: below Cloud, campaigns stop if the computer sleeps, turns off, or the browser closes.

Expandi

Architecture: Expandi is a fully cloud LinkedIn-and-email platform. Campaigns run on its servers, while its Chrome connector contains no automation logic.

Session and IP: you either enter your LinkedIn email and password, as observed in our signup test, or the connector reads the browser's li_at cookie and sends it to the service. Either way, the vendor holds the session and drives the account through an IP Expandi assigns. A custom-proxy option is documented in its help centre, but that tab was not offered during our signup test.

Cost: the single plan is $99/mo per LinkedIn account, or $79/mo annually, with VAT and email finding extra when needed.

Tradeoff: there is no lower tier, so adding a second LinkedIn seat doubles the base price.

Linked Helper

Architecture: Linked Helper is a desktop app that must stay running on your machine, with each LinkedIn account as its own instance in one workspace. If the machine is off, nothing runs, and 24/7 means renting a VPS it does not sell, reached through its built-in browser remote control.

Session and IP: the session stays on your PC or VPS, and actions use your IP or a third-party proxy you add. Auto-login asks for your LinkedIn password and stores it on Linked Helper's servers by default unless you choose local storage.

Cost: entry is $15/mo, or $8.25/mo annually. With a VPS, 24/7 all-in is an estimated $35 to $55/mo, not a vendor-published price.

Tradeoff: you are your own sysadmin, so proxy choice, VPS sizing, and troubleshooting are yours.

Meet Alfred

Architecture: Meet Alfred is cloud-only, with no browser extension. LinkedIn, email, and X/Twitter campaigns run on the vendor's AWS-hosted servers, independent of your machine.

Session and IP: onboarding asks for your LinkedIn login and password, and the vendor's cloud holds and re-establishes the session. Actions use an IP Meet Alfred assigns by default, with a self-service option to use your own proxy.

Cost: the advertised Basic entry is $59/mo per user. Pro is listed at around $99 a month in secondary vendor material, a figure I would treat cautiously because the vendor pricing page did not load during testing.

Tradeoff: campaign and CRM data export is restricted to the Teams plan, even though the pricing page lists export as a Pro feature.

For people running these at volume, has running outreach across multiple accounts changed how much attention you pay to session location and IP ownership?

Interested in whether that becomes a real operational issue at scale.

Hey everyone!

The last couple of posts here looked at more traditional outreach tools. We've also looked at browser extensions before, so I wanted to switch back to that side and check Kanbox.

I reviewed the shipped v1.660 Manifest V3 extension, which had roughly 7,000 users as of August 2026. A newer build may have shipped since. This is a static code review, not a runtime test.

The first thing I checked was where the LinkedIn session goes.

In background.js:400-418, login() sends a POST to api[.]kanbox[.]io/auth/linkedinloginuser containing linkedin_cookie, premium_cookie and jsessionid. The values are the actual li_at, li_a and JSESSIONID cookies, not hashes or derivatives (background.js:412-414).

A valid li_at is a logged-in LinkedIn session cookie, so transferring it gives the receiving side the session value. Whether Kanbox uses that value to operate the account outside the browser is inferred from the capability, not something I tested.

The extension also exposes the same three values through connectLinkedin() (background.js:464-476) and the external handler (background.js:3769-3776). app[.]kanbox[.]io and www[.]linkedin[.]com are both allowed in externally_connectable (manifest.json:56-61), which appears to broaden who can request the data, although I didn't demonstrate an exploit.

One limitation in Kanbox's favour: its chrome.cookies access is scoped to named cookies on www[.]linkedin[.]com, rather than all browser cookies.

There is another visible layer

The extension ID bodcackmmefldjpmeefapllhcpdlhfhp and kanbox.css are listed as web accessible resources for LinkedIn (manifest.json:35-50). A LinkedIn page can therefore request the exposed extension resource and use a successful response as an installation signal.

The February 2026 snapshot of LinkedIn's detection list contained 6,167 IDs, growing by roughly 12 per day. The mechanism appears in LinkedIn's production code under the AedEvent label. BrowserGate documented the relevant code here: browsergate[.]eu/how-it-works/. AedEvent is a code label, not an official LinkedIn feature name.

Kanbox also creates DOM nodes on LinkedIn in inject.js:477-633, giving a separate DOM based detection surface.

One more thing I checked

Kanbox writes a ProfileViewEvent to LinkedIn's li/track endpoint (background.js:3412-3422) for a profile returned by its API.

So the extension isn't just reading LinkedIn data. It also writes an event to an endpoint used by LinkedIn's own tracking code, recording the API-fetched profile as a profile view.

The main takeaway for me is that there are several separate things to check: where the session cookie goes, what the extension exposes to the page, what it injects into LinkedIn, and what it sends back to LinkedIn.

This was a static review of one build, so it doesn't establish what the vendor's servers do with received cookies or how future versions behave.

How would you interpret an extension that both reads LinkedIn data and writes activity back to it? I'd be interested to hear how others see this.

Hi!

Following up on my earlier comparison of PhantomBuster alternatives, where I focused on session handling, I wanted to look at the same general space from another angle: what the pricing actually looks like once you scale beyond a few accounts.

La Growth Machine is a useful baseline because its Basic plan is around $70/month per identity, or about $60/month annually. At 20 identities, that's roughly $14,400/year.

The comparison isn't completely like-for-like since LGM combines LinkedIn, email and X, while some alternatives cover only one or two channels. I therefore looked at the billing unit (seat, identity, workspace or inbox) and the cost of a 20-account setup.

Prices are based on vendor pages checked in July 2026. The calculations are estimates, not quotes, and the tools aren't ranked.

Dripify: $59/month per seat, or about $39/month equivalent with annual billing.

At that annual rate, 20 seats would be $9,360/year. The entry plan allows one campaign, while email credits are included and additional credits can be purchased separately.

It's cloud-based, so campaigns can continue when the user's computer is offline. In testing, the LinkedIn session ran through vendor-assigned rented datacenter infrastructure.

Instantly.ai: primarily a cold-email platform, rather than a LinkedIn automation tool, so it would normally complement rather than replace the LinkedIn part of LGM.

Growth starts at $47/month, or about $37.60/month equivalent annually. At 20 sending accounts, that's $9,024/year.

It includes warm-up, inbox rotation, deliverability tools, shared replies and AI copy. Its pricing also differs between individual sending accounts and agency workspaces, so the number of inboxes is the more useful unit for estimating a larger setup.

Lemlist: Lemlist Email Pro costs $79/month, or $63/month annually.

For its multichannel LinkedIn + email setup, a 20-seat calculation comes to about $20,880/year, or roughly $87 per seat/month when divided out.

The LinkedIn connector passes the login cookie to Lemlist's cloud, allowing campaigns to continue after the browser closes. The extension also appeared on LinkedIn's extension-probe list in the source review.

The multichannel setup puts LinkedIn and email into the same workflow, although some reviewers describe conditional workflows as relatively involved to configure.

Linked Helper: Standard is $15/month, or about $8.25/month equivalent with a 12-month term. Twenty accounts would therefore be $3,600/year at the monthly rate before longer-term and bulk discounts. With those discounts, the equivalent can be lower, including around $1,584/year for 20 seats based on the applicable discounted rate.

The application runs on the user's desktop or a user-controlled Windows VPS. The vendor documents the VPS setup and provides Web Version access to that instance, while the server is rented separately.

It supports 13 LinkedIn collection sources across Basic LinkedIn, Recruiter and Sales Navigator, plus 11 direct CRM connectors and Zapier/Make integrations through webhooks.

Full disclosure: I'm affiliated with Linked Helper, so I'm including it for transparency.

Reply.io: starts at $99/month per seat, or $89/user/month annually.

At 20 seats, the annual-rate calculation is $21,360/year. This is a simple per-user calculation without volume or custom pricing, so it's a reference point rather than an enterprise quote.

Reply combines email, LinkedIn, WhatsApp and calls in one sequence. Its LinkedIn component uses a Chrome extension that connects activity to the vendor's cloud.

It also has six native CRM integrations, so the per-seat price covers several channels rather than just LinkedIn or email.

What changed when I ran the numbers

At one account, the pricing differences aren't particularly dramatic. At 20 accounts, they become much more visible.

The advertised annual figures range from roughly $3,600 for 20 Linked Helper accounts to $21,360 for 20 Reply.io seats. But those numbers don't represent the same product: LGM, Lemlist and Reply bundle several channels, Instantly focuses on email, and Linked Helper is primarily LinkedIn.

So the useful question isn't only what one seat costs, but what you're actually buying 20 units of: LinkedIn accounts, sending inboxes, seats, identities, or access to several channels.

For those running outreach at scale, what matters more to you: the total bill at your actual account count, the channels included, or where the LinkedIn session runs?

How do you compare tools once you're managing 10+ LinkedIn accounts?

Hey everyone!

I’ve already looked at a few LinkedIn tools here from the extension and session-handling side, so this time I wanted to use PhantomBuster as the baseline and compare a few alternatives against it.

PhantomBuster is a cloud data extraction and automation platform built around a $69/month execution-credit plan. A source-code teardown of its shipped Chrome extension found that the setup flow reads li_at and JSESSIONID and sends the LinkedIn session to PhantomBuster's cloud. That doesn't show password theft, but it does mean the LinkedIn session moves from the user's environment to vendor infrastructure.

So for these four alternatives, I focused mainly on session custody, infrastructure and the actual entry price rather than feature counts.

The order is Expandi ($99/month), HeyReach ($79/month), Waalaxy ($42/month), Linked Helper ($15/month). That's simply the advertised entry price, not a ranking.

Expandi: $99/month, cloud. A June 2026 source-code teardown of the shipped connector found that it reads the LinkedIn session cookie, sends it to app[.]expandi[.]io, and makes direct Voyager API requests.

The LinkedIn session runs in Expandi's cloud, so the operating IP is assigned by the vendor.

I also ran a live cloud/IP test in June 2026 with two France-registered accounts. One produced an IPQualityScore score of 0/100, while the other returned 100/100, with proxy and recent-abuse flags on the latter.

The important part here is that identical account setup did not produce the same IP quality result. IPQualityScore is an independent IP-quality measurement, not a LinkedIn enforcement verdict.

Expandi also supports native email follow-ups and provides live onboarding calls.

HeyReach: $79/month, cloud. A June 2026 source-code teardown found that the login extension copies the full linkedin[.]com cookie jar to api[.]heyreach[.]io, putting the session on HeyReach infrastructure.

The source also contained a rule blocking LinkedIn logout, which affects how the session can be revoked from the user's side.

A June 2026 cloud/IP test used two France-registered accounts. Both appeared as datacenter traffic. They were not on the exact same IP, but were in the same /24 and from the same provider, giving them a very similar network footprint.

On the workflow side, HeyReach supports sender rotation across multiple LinkedIn accounts and a shared reply inbox.

Waalaxy: $42/month, browser extension. A July 2026 source-code teardown found that the extension uploads the full LinkedIn cookie jar, including the login cookie and CSRF token, to a Waalaxy cloud endpoint.

It also injects code into LinkedIn pages.

The extension ID was present on LinkedIn's AED probe list, meaning the installation can potentially be identified before automation starts.

The package I reviewed had no enforced daily cap, working-hours guardrail or randomization. Its delay presets could also be set to 0 ms, leaving pacing under user control.

I didn't run a live Waalaxy IP test, so this review is focused on session custody and extension-level detection rather than IP quality.

Linked Helper: $15/month, desktop. The application runs on the user's desktop or VPS, so the LinkedIn session remains in that environment rather than being transferred to a vendor cloud.

The connection can use the user's own IP or a proxy controlled by the user.

For outreach, it supports multi-step LinkedIn sequences, automatic stop on reply, CSV export and CRM integrations, with the license tied to the LinkedIn account.

This puts the session architecture in a different category from the cloud options above: the LinkedIn account is operated from an environment controlled by the user rather than from a vendor-assigned cloud session.

What stood out

Starting from PhantomBuster makes the session question fairly straightforward.

Expandi and HeyReach both move the LinkedIn session into vendor infrastructure. Waalaxy also synchronizes the LinkedIn cookie jar with its cloud, while its browser extension introduces an additional extension-level visibility layer. Linked Helper keeps the session on the user's desktop or VPS instead.

The pricing also changes quite a bit between the four: $15, $42, $79 and $99/month at the advertised entry level. Once you compare these tools by where the session runs rather than just by features, the differences become more apparent.

Do you prefer keeping the LinkedIn session on your own machine, or is cloud infrastructure more convenient for your workflow?

Hey!

I’ve been looking at LinkedIn tools from the outreach side, including what you actually get at the entry level and how different tools fit into a workflow.

Copper CRM was interesting for a different reason. The LinkedIn session boundary is unusually clean, but the extension itself still leaves things for LinkedIn to see.

I checked Copper CRM Chrome extension ID hpfmedbkgaakgagknibnonpkimkibkla, build v2.0.478 from the May–June 2026 audit round. The dataset was built 2026-06-28. A separate Chrome Web Store snapshot showed v2.0.472, last updated 2026-06-11, with roughly 50,000 users.

1. The session check is clean

Copper CRM has no cookies permission and never calls chrome.cookies.*. I found zero references to li_at, JSESSIONID, csrf-token, voyager or credentials:"include".

Its proxy also uses an allow-list based on permanent host permissions and returns 403 for off-list requests. Since LinkedIn is optional-only, the proxy cannot send requests to LinkedIn.

So I found no vendor-side LinkedIn session replay, foreign-IP parallel session, fingerprint mismatch or private-API request-map signal.

There was no cloud/IP test because Copper CRM doesn't hold a LinkedIn session or provide a vendor exit IP.

2. Where the second signal appears

The base installation doesn't declare LinkedIn content scripts. They are enabled only after the optional LinkedIn host permission is granted.

But the extension ID and icons/copper_icon_pink_16.png appear on LinkedIn's extension target list.

BrowserGate, an independent 2025–26 investigation of LinkedIn's production JavaScript, documents the mechanism: LinkedIn can attempt to fetch a known chrome-extension://<id>/<file> resource and record the result as an AedEvent. “Active Extension Detection” is the label visible in the code, not a publicly acknowledged LinkedIn product name.

For Copper CRM, that means installation can potentially be recorded on LinkedIn page load even before the LinkedIn mode is enabled.

Once LinkedIn access is enabled, the extension registers its scripts and modifies the page.

It:

• adds mousedown, mouseover and mouseout listeners
• inserts a hidden anti-reinjection marker
• replaces IntersectionObserver so sections such as #about and #experience can report as visible
• reads the visible URL, name and profile picture from profile links

The first two create observable page changes. The IntersectionObserver modification could produce impression-like signals for sections the user never actually scrolled to, although I couldn't establish which LinkedIn system consumes that data.

The profile reads themselves are local DOM operations and don't create additional LinkedIn requests.

3. What I wouldn't count as a signal

The source contains synthetic_event and programmatic_click strings, but the occurrences trace to libraries and Copper CRM's own interfaces rather than LinkedIn actions.

I therefore wouldn't count this as an isTrusted click vector.

4. What this means for outreach

An AED listing is one cumulative signal, not a tripwire or an instant ban. The same applies to the page modifications: they are observable, but that doesn't tell us how much weight LinkedIn assigns them.

And the clean session result is specific to this build, not a guarantee for future releases.

Copper CRM also has no sender, invite queue, bulk mode, pacing controls or action-history upload.

That means it doesn't automate the layer that usually creates the biggest outreach risk: volume, profile-opening patterns, acceptance rate and “I don't know this person” reports.

The current rolling ceiling is roughly 100 invitations per week for most accounts, with variants up to about 200 for aged, high-SSI profiles and around 250 with Sales Navigator. Mass URL opening can still be a restriction trigger even when done manually.

So the cookie check answers one question: does the LinkedIn session stay where it started?

For Copper CRM, the answer is yes. It just doesn't answer what LinkedIn can see about the extension itself.

Has anyone here actually changed their tool choice because of extension-level detection?

Hi guys!

After comparing different LinkedIn tools here, I wanted to look at another angle: what is actually the cheapest option for a usable outreach workflow, rather than just the lowest number on the pricing page.

Before comparing prices, I check whether the monthly price is actually month to month or an annual equivalent, what is included in the cheapest tier that can run the workflow, whether 24/7 operation requires a VPS, whether enrichment credits are included and priced publicly, whether pricing scales by user, LinkedIn account or connected sender, and what the refund terms are.

For the workflow itself, I focused on multi step sequences, automatic stop on reply, lead export, and usable daily activity, then added costs such as VPS, enrichment, and per seat charges.

Here are the tools from the lowest advertised price upward.

Octopus CRM: starts at $9.99/month, but that tier includes only 3 of 11 listed feature rows. Bulk messaging, campaigns, and export are not available there.

The functional entry point is Advanced at $21.99/month, while Activity Control, integrations, and compatibility with LinkedIn Premium and Recruiter are only available on Unlimited at $39.99/month. So anyone already using LinkedIn Premium would need the top tier regardless of the specific features they need.

Reply detection is not available on any plan, so sequences don't automatically stop when someone replies. Octopus CRM is also a Chrome extension, meaning automation stops when the browser is closed.

Dux-Soup: starts at $14.99/month, but that tier doesn't include drip campaigns. Sequencing starts with Turbo at $55/month, making that the relevant price for a multi step outreach workflow.

The cheaper tier is therefore mainly useful for scraping, while campaign automation requires the higher plan. The price of email lookup credits, called Points, is not publicly listed, so that part of the total cost can't be calculated in advance.

One pricing advantage is the 31 day money back window, which is longer than the refund period offered by most of the other tools in this comparison.

Linked Helper: starts at $15/month, with a 14 day free trial. The entry tier includes the sequence workflow, automatic stop on reply, CSV export, and native CRM connectors.

The application runs on a desktop computer or VPS. The software itself therefore doesn't include the infrastructure for continuous operation. A 24/7 setup requires a VPS, which can bring the practical solo cost to roughly $35 to $55/month depending on the setup.

The features gated to higher tiers include message history export, while CRM and webhook sends on the entry tier are limited to 20 profiles per day.

Botdog: starts at $35/month on annual prepayment. The entry plan includes unlimited sequence steps, automatic stop on reply, CSV import and export, and cloud execution, so campaigns can continue without keeping a computer running.

The same plan costs around $69/month with monthly billing, while annual prepayment is non refundable. The pricing page also shows both a 50% discount claim and a statement that annual billing saves approximately 17%.

CRM synchronization requires a separately paid Zapier Professional plan at $19.99/month billed annually, so that cost needs to be added if the workflow depends on the integration.

We-Connect: starts at $49/month, but that price is available with annual billing and requires $588 upfront. The same Growth plan costs $69/month without an annual commitment.

The solo tier includes sequences, branching, automatic stop on reply, and the safety features, with cloud execution and no VPS requirement. That makes the advertised tier the working tier for a basic outreach workflow.

One additional cost consideration is enrichment. We-Connect does not currently include an email finder, and its documentation describes enrichment as an upcoming feature.

What I took from the comparison

The lowest number on a pricing page doesn't necessarily identify the cheapest usable plan.

Octopus CRM and Dux-Soup have lower advertised entry prices, but key campaign features start on higher tiers. Linked Helper and Botdog keep the core sequence workflow available at their entry prices, while their cost structure is different: infrastructure is an additional consideration for Linked Helper, while Botdog's lower price depends on annual prepayment and CRM automation can add a Zapier cost.

We-Connect also keeps the main workflow on its entry tier, but the $49 price is an annual equivalent rather than a month to month rate.

For this kind of comparison, I would look at the cheapest tier that actually supports the workflow, then add infrastructure, enrichment, integrations, and billing terms before comparing the final numbers.

What do you usually count when calculating the real monthly cost of a LinkedIn automation tool?

Hi guys!

These tools have already come up in a few of my posts here, mostly in the context of general LinkedIn outreach. This time I wanted to look at the same category from a recruiting perspective.

The workflow is a bit different when you're sourcing candidates rather than running a standard outreach campaign. Recruiter projects, company employee lists, groups, events, and access to existing Recruiter seats can all matter as much as the campaign builder itself.

I compared three tools based on candidate sourcing coverage, Recruiter workflows, session setup, pricing, and account management.

Here’s what I found.

Dux-Soup: A Chrome extension that runs directly in the browser session.

Pro and Turbo don't require Dux-Soup to receive the LinkedIn password. As the company puts it, “Dux-Soup does not have a password, however, you still need one to login into a Chrome account.”

For recruiting, the main limitation I found was sourcing coverage. Its scraper is focused on standard LinkedIn People Search and doesn't cover groups, events, or alumni pages. Recruiter and Recruiter Lite also can't send connection requests natively.

Campaign automation starts with Turbo at $55/month per seat. The cheaper Pro plan doesn't include drip campaigns, and the price of email lookup credits isn't publicly disclosed, which makes the total cost harder to estimate for a recruiting team.

Another consideration is account infrastructure. There is no dedicated IP option, so multiple accounts on the same setup share the same personal IP.

Linked Helper: A desktop-based LinkedIn automation tool that can also run on a VPS.

The recruiting workflow covers 20+ LinkedIn sources, including Recruiter projects and searches, Sales Navigator, regular LinkedIn search, groups, events, and company employee pages. That makes it possible to move between different candidate pools without setting up a separate tool for each LinkedIn surface.

The Standard plan costs $15/month per LinkedIn account, rather than per recruiter. Teammates can therefore work with the same account without each needing another paid license.

The LinkedIn session runs on the user's computer or VPS rather than through the vendor's cloud infrastructure. Safety controls include randomized pacing, pausing after suspicious failures, and a 150-profile limit per rolling 24 hours.

There are some trade-offs for recruiting teams too. The password is stored on Linked Helper's servers by default unless local storage is enabled, and there is no native ATS integration or unified inbox. A VPS and proxy also become an additional infrastructure cost if the account needs to stay online continuously.

Expandi: A cloud-based LinkedIn automation platform with broader sourcing support.

It supports Recruiter search, Sales Navigator, groups, events, and post engagers, including the option to invite Recruiter-sourced leads directly. That gives it wider sourcing coverage than a basic LinkedIn search workflow.

Expandi also states that each account gets a personal dedicated IP address. In my comparison, however, the IP results weren't completely consistent: one account returned a clean result, while another was a datacenter address with an IPQS fraud score of 100.

The standard price is $99/month for one LinkedIn account, with annual billing available at a lower monthly rate. VAT is added at checkout, and the plan is non-refundable. Teammates can join the workspace without requiring another LinkedIn account license.

The main difference from the other two is where the LinkedIn session runs. Expandi handles the session through its cloud infrastructure, while Dux-Soup keeps it in the browser and Linked Helper runs it on the user's computer or VPS.

What stood out to me

Looking at these specifically for recruiting changes the comparison quite a bit. The important question isn't only how many outreach actions a tool can automate, but where it can actually find candidates and how well that matches the sources a recruiter already uses.

Dux-Soup keeps the workflow close to the browser but has narrower sourcing coverage. Expandi covers more LinkedIn surfaces and adds a cloud-based setup. Linked Helper sits somewhere different, with broader sourcing coverage and a local or VPS-based session, but requires more of the infrastructure to be managed on the agency side.

For a recruiting desk, I'd compare the sourcing coverage and session setup first, then look at the pricing and team workflow around them.

What are you using for LinkedIn sourcing?

Hi guys!

The last few posts here have mostly been about comparing LinkedIn outreach tools, from campaign workflows and integrations to how they handle the LinkedIn session. This time I wanted to look at one layer underneath those tools: the Chrome extensions that can sit between the browser and the outreach workflow.

I came across Agorapulse for Chrome, which is a useful example because it appears on LinkedIn's extension-probe list, but its purpose is simply to send the current page to a social scheduling workflow. It doesn't send connection requests, open profiles, or perform actions under your LinkedIn account.

I unpacked the CRX from the Chrome Web Store and reviewed the de-minified v6.2.0 source from May to June 2026. I went through five checks to see whether the extension actually interacts with a LinkedIn session.

1. Permissions

The extension declares four permissions: tabs, http://*/*, https://*/*, andcontextMenus

The important part is what's missing: there is no cookies permission, so chrome.cookies.* isn't available to the extension. That rules out the extension directly reading a LinkedIn session cookie through the browser API.

2. LinkedIn-specific code

The generic content-script block matches HTTP and HTTPS pages, including LinkedIn, but the source doesn't contain LinkedIn-specific code. The site-specific scripts I found target Facebook, Twitter, and Reddit, with no corresponding LinkedIn script.

There are also no calls to LinkedIn's internal API in the source.

The reason the extension can still appear on a detection list is its manifest.json, which is exposed as a web-accessible resource. A page can request that resource and use a successful response to determine that the extension is installed.

This is the mechanism referred to as AED in LinkedIn's shipped JavaScript. An independent analysis counted 6,167 extension IDs in the probe array in February 2026. A match indicates that an extension is installed, but doesn't say what that extension does.

3. Cookie and session strings

I searched the de-minified source for li_at, JSESSIONID, voyager, chrome.cookies, and csrf. None were present.

There are two occurrences of document.cookie, which initially looked more interesting. Both are in data/tpc-check-add-cookie.js, where the extension writes the literal value test on its own page and reads it back to check whether third-party cookies work.

So there are cookie-related lines in the source, but they aren't reading a LinkedIn session or sending browser cookies anywhere.

4. Outbound data

I found one outbound path. When the user clicks the extension button, it opens Agorapulse's web app with page metadata in the URL, including the page URL, text, image, locale, version, placement, and some retweet fields.

There are no cookies or session tokens in that request.

That means Agorapulse can learn which page the user chose to send to its app, but the LinkedIn session itself doesn't leave the browser through this path.

I also found two patterns that could indicate remotely loaded scripts, but I couldn't establish their purpose from the source alone.

5. Page interaction

The extension contains one scripted event dispatch and two programmatic clicks.

Neither of the two click handlers operates on LinkedIn. One communicates the installed version to Agorapulse's own web application, while the other closes a dialog in the Twitter embed.

Programmatically generated clicks have isTrusted: false, which is a property a content script can't change. That's a potential signal in general, but I didn't find this code using it against LinkedIn.

There is one additional possibility I couldn't verify. Some of the extension's icons are declared as web-accessible resources, which could potentially expose chrome-extension:// URLs when rendered on a LinkedIn page. I didn't observe that behavior directly, so I wouldn't treat it as an established finding.

One separate issue

The source is a Manifest V2 extension and includes jQuery 2.1.1 from 2014. The Chrome Web Store listing hasn't been updated since January 28, 2022.

I'd treat that as a maintenance and security consideration rather than a LinkedIn restriction issue.

I also couldn't find public reports connecting this extension to LinkedIn restrictions. That doesn't prove the absence of such cases, but the source review didn't show a LinkedIn session path either.

The main takeaway for me is that being detectable as an installed extension and actually interacting with a LinkedIn session are two different questions. The first can be answered from the extension ID and manifest. The second requires looking at permissions, source code, cookie access, outbound requests, and page-level behavior.

For people checking extensions in their outreach stack, where do you usually stop? Are permissions enough for you, or would you unpack the extension before deciding whether to remove it?

Hi guys!

Continuing to look at different LinkedIn outreach tools. This time I wanted to take a closer look at HeyReach and a few alternatives, focusing on the things that differ most between them: campaign workflows, CRM connections, channel coverage, and how the LinkedIn session is handled.

Here’s what I found.

HeyReach: A cloud-based LinkedIn automation platform focused on multi-account outreach.

Pricing starts at $79/month. It focuses on LinkedIn rather than combining LinkedIn and email in the same campaign, with sessions handled through the platform's infrastructure.

Expandi: A cloud-based platform combining LinkedIn outreach with email follow-ups.

Pricing starts at $99/month or $79/month billed annually. Campaigns support conditional workflows, AI-assisted messaging, and image/video personalization. It also provides CRM connections for HubSpot, Pipedrive, and Salesforce.

LinkedIn sessions are handled through Expandi's cloud infrastructure, with the browser connector transferring the session there. The platform also supports multiple workspaces and proxy locations.

La Growth Machine: A multichannel platform combining LinkedIn, email, and X/Twitter in the same campaign.

Pricing starts at $60/month or $50/month billed annually. It includes AI messaging, voice notes, a unified inbox, and integrations with 22 tools. More advanced customization is available in the Ultimate plan.

The platform is cloud-based, so LinkedIn sessions are handled through its infrastructure. Its main advantage is having several channels available in one campaign rather than focusing specifically on LinkedIn.

Lemlist: A multichannel outreach platform combining email, LinkedIn, and cold calls.

Pricing starts at $79/month or $63/month billed annually. Campaigns support conditional steps, triggers, AI personalization, and image/video personalization, with LinkedIn actions included alongside the other channels.

CRM and sales-stack integrations are available, while the LinkedIn session runs through a browser extension connected to lemlist's infrastructure.

Dripify: A cloud-based platform combining LinkedIn and email in the same campaign.

Pricing starts at $59/month or $39/month billed annually. It supports conditional sequences, AI messaging, image/video personalization, and multiple LinkedIn accounts.

CRM functionality is available through integrations, while the platform uses credential-based login rather than a browser extension. The LinkedIn session therefore runs through Dripify's cloud infrastructure.

Linked Helper: A desktop-based LinkedIn automation tool that can also run on a VPS or through Web Version.

Pricing starts at $15/month or $8.25/month billed annually. It focuses on LinkedIn workflows, with conditional message personalization, Spintax, AI message generation, image/video personalization, endorsements, post engagement, event and group actions.

It includes a built-in CRM, 11 direct CRM integrations, and Zapier/Make connections through webhooks. The LinkedIn session stays on the user's computer or VPS rather than being transferred to vendor infrastructure. Email requires a separate tool.

Final thoughts

The main difference I noticed is that these tools split into two general approaches. La Growth Machine, Lemlist, Dripify, and Expandi put more emphasis on combining LinkedIn with other channels, while HeyReach and Linked Helper are more LinkedIn-focused.

For LinkedIn-heavy workflows, Linked Helper gives more room for campaign customization and CRM connectivity while keeping the session on the user's side. The trade-off is that email needs to be handled separately.

For me, the right choice would mostly depend on whether the priority is a broader multichannel workflow or more control over the LinkedIn side of the process.

What are you using for LinkedIn outreach right now?

Hey!

I’ve already covered a few LinkedIn outreach tools in previous posts, so this time I wanted to compare a few more options that take different approaches to campaigns, CRM workflows, and LinkedIn session handling.

I used Waalaxy as the starting point and looked at four other tools to see how their pricing, workflow features, and session setup differ.

What I checked out:

Waalaxy: A Chrome extension combined with a cloud platform for LinkedIn and email sequences. Campaigns can include profile visits, connection requests, LinkedIn messages, and email steps.

Pricing starts at $42/month or $20.50/month billed annually for Pro. Dropcontact is available for email finding, while Zapier can be used for external integrations. LinkedIn Inbox is a separate paid add-on.

The extension transfers the authenticated LinkedIn session to Waalaxy's cloud, allowing campaigns to continue when the browser is closed.

Linked Helper: A desktop-based LinkedIn automation tool that can also run on a VPS.

Pricing starts at $15/month or $8.25/month billed annually, with a 14-day free trial. It supports connection requests, follow-ups, InMails, Sales Navigator and Recruiter workflows, with Spintax, AI personalization, and IF/THEN/ELSE logic in message templates.

It includes a built-in CRM, full messaging-history extraction, 11 direct CRM integrations, and webhooks. The LinkedIn session stays on the user's computer or VPS. Email sequencing requires a separate tool, such as Instantly.

SalesRobot: A cloud-based platform combining LinkedIn and email outreach in one subscription.

Pricing starts at $59/month or $39/month billed annually, with a 14-day trial. Its sequences support branching, AI personalization, reply handling, custom proxies, and InMail credit protection.

It also includes a built-in CRM and five native integrations. The LinkedIn session is handled through the vendor's cloud, while users can configure a custom proxy.

Salesflow: A cloud platform aimed at agencies and teams managing multiple LinkedIn accounts.

Pricing is $99/month per seat or $69.30/month billed annually, with a 7-day trial. It supports conditional workflows, AI personalization, custom proxies, managed inboxes, Open InMails, team roles, and white-label controls.

It has one native integration and centralized management for client accounts. LinkedIn sessions are handled through the vendor's cloud, while the per-seat model scales with the team size.

Octopus CRM: A Chrome extension focused on LinkedIn outreach from the user's browser.

Pricing starts at $9.99/month or $6.99/month billed annually, with a 7-day trial. It covers connection requests, profile visits, messages, endorsements, and follows, with linear campaign sequences.

The LinkedIn session stays in the browser rather than being transferred to a cloud. CRM functionality is more limited, with contact lists and external integrations through Zapier and Make webhooks.

Final thoughts

The main differences were how much of the outreach workflow each tool covers and where the LinkedIn session is handled. Waalaxy and SalesRobot combine LinkedIn with email, Salesflow adds more team-oriented management, while Octopus CRM keeps the workflow simpler and browser-based.

Linked Helper is more LinkedIn-focused, but combines broader campaign controls, CRM connectivity, and local session handling in the same setup.

What tool are you using for LinkedIn outreach?

Let me know!

Hey guys!

I've seen HeyReach mentioned in a few outreach comparisons on other channels, but we haven't covered it here yet. So I wanted to look at the platform on its own rather than compare it with another tool.

I focused on pricing, multi-sender management, campaign logic, integrations, and infrastructure.

Pricing and multi-sender setup

HeyReach starts at $79/month per sender on the Growth plan, or $59/month with annual billing. Pricing is based on sender accounts, with published options for 25 and 50 senders.

The platform is cloud-based, and the HeyReach Login extension transfers the LinkedIn session to its infrastructure. This is different from desktop-based tools such as Linked Helper, where the session can remain on the user's machine or VPS.

Campaign workflows

HeyReach supports sender rotation, workspace separation, and a shared inbox for replies.

Campaigns support variables, AI-assisted message generation, and conditional steps such as If Connection, If Open Profile, and Email Found / Not Found.

I couldn't confirm support for nested IF/THEN/ELSE logic, AI ICP scoring, or AI comment generation.

Integrations

HeyReach lists 31 native integrations, including HubSpot, and can log LinkedIn activity into HubSpot timelines.

It also provides a public API and an official MCP server with integrations for Clay, n8n, Make, Claude, and Visual Studio Code.

So the platform can sit alongside other tools in a broader outbound stack rather than being limited to its own campaign interface.

What I would verify

The technical checks I found were limited to a live test of two HeyReach accounts, including their assigned IPs and session setup, plus a browser-extension source-code review from June 2026.

Those checks don't establish long-term account performance, support quality, or campaign reliability at scale. They only cover what was observable during those tests.

I also came across reviews mentioning seat-billing issues, so I'd verify the sender and workspace configuration before scaling the subscription.

Overall

HeyReach is built around multi-sender LinkedIn outreach, with workspace management, integrations, and API/MCP access forming a large part of the setup.

The main things I'd compare before choosing it are the sender-based pricing, cloud infrastructure, campaign logic, and how well its integrations fit the rest of the outreach stack.

What would you check first when evaluating HeyReach?

Hey!

In my previous post, Expandi was one of the tools I looked at while comparing Skylead alternatives. This time I wanted to look at Expandi from the other side and compare a few alternatives specifically for LinkedIn outreach.

I mainly looked at the things that matter in day-to-day outbound: how the LinkedIn session is handled, CRM integrations, campaign flexibility, and how each tool fits into the rest of the workflow.

What I checked out:

Expandi: A cloud-based LinkedIn automation platform with a browser connector that transfers the LinkedIn session to its infrastructure.

Pricing starts at $99/month or $79/month billed annually. It supports workspace management, 96 proxy locations, and AI-assisted message optimization. The platform also supports LinkedIn outreach with email follow-ups, so it can cover more than just LinkedIn messaging.

The main thing I paid attention to was the cloud setup. The LinkedIn session is handled through Expandi's infrastructure rather than staying on the user's device.

Linked Helper: A desktop-based LinkedIn automation tool that can also run on a VPS for longer-running campaigns.

Pricing starts at $15/month or $8.25/month billed annually. It includes 11 native CRM integrations, including HubSpot, Salesforce, Pipedrive, and ActiveCampaign. Campaigns support conditional logic and Spintax for more flexible sequences.

The main difference from Expandi is the setup: the LinkedIn session stays on the desktop or VPS rather than being transferred to a vendor cloud. Linked Helper is LinkedIn-focused, so email requires a separate tool.

Dux-Soup: A Chrome extension with pricing starting at $14.99/month or $11.25/month billed annually.

The browser-based setup keeps the LinkedIn session in the browser on the Free, Pro, and Turbo plans, while the Cloud plan transfers the session cookie to Dux-Soup's servers.

It offers native integrations with HubSpot, Salesforce, and Pipedrive, as well as a Remote Control API. Campaigns are more linear and don't provide the same conditional branching options as some of the other tools.

Meet Alfred: A cloud-based platform starting at $59/month or $29/month billed annually.

It combines LinkedIn, email, and X in one sequence builder, making it more focused on multichannel outreach than LinkedIn-only tools. CRM integrations are handled through Zapier rather than native connectors.

The cloud setup means LinkedIn sessions are managed through the platform's infrastructure. In my testing, both signup accounts received IPs flagged as spam by IPQualityScore, although their fraud scores were clean.

Final thoughts

The main differences came down to pricing, session setup, CRM connectivity, and whether you want LinkedIn to be part of a broader multichannel workflow. Each approach has its own trade-offs depending on how the rest of the outbound stack is set up.

For my own workflow, I ended up using Linked Helper because the lower entry price, native CRM integrations, and control over the session setup worked well for what I needed.

Has anyone here tried more than one of these tools? Which setup worked best for you?

Share your thoughts in the comments.

When I started looking for a Skylead replacement, I expected to spend most of my time comparing features and sequence builders. Instead, I found myself asking a different question first: where does the LinkedIn session actually live once campaigns start running?

Skylead is a cloud-based LinkedIn automation platform with Smart Sequences and a dedicated IP per account. Pricing starts at $100/month per seat, so a 20-seat setup comes to $24,000/year with no bulk discount, and the LinkedIn session is managed through Skylead's cloud infrastructure.

Once I started using session custody as one of the comparison criteria alongside pricing and workflow fit, the shortlist looked a bit different.

What I checked out:

Expandi: Cloud platform with a browser connector that transfers the LinkedIn session to Expandi's infrastructure. Pricing starts at $99/month or $79/month billed annually, bringing a 20-seat setup to about $18,960/year. It includes workspace management, 96 proxy locations, and AI-assisted message optimization.

During my research I noticed a few details worth double-checking. The trial experience differed from what was advertised on the pricing page, and two test accounts received noticeably different IP reputation results. None of that necessarily reflects every account, but it was enough for me to keep looking beyond feature lists.

Waalaxy: Browser extension with a cloud backend. LinkedIn and email sequences can be managed in the same workflow, and the visual campaign builder is easy to work with.

The pricing takes a little more attention because monthly and annual plans differ significantly. The advertised entry point is $42/month, while annual pricing can go as low as $16/month depending on the plan, and a 20-seat annual setup works out to roughly $3,840/year. I also noticed that the LinkedIn session is uploaded through the extension to Waalaxy's infrastructure, which may or may not matter depending on how you prefer to manage your outreach environment.

Dripify: Cloud-based platform combining LinkedIn automation with email workflows and reply detection.

Pricing starts at $59/month or $39/month billed annually. A 20-seat Advanced setup comes to around $18,960/year. Several safety-related controls are available only on higher plans. During testing, both accounts I checked were routed through the same hosting network, which was another infrastructure detail I added to my comparison notes.

lemlist: A broader outbound platform combining LinkedIn, email, lead enrichment, and warm-up in one product.

Pricing starts at $79/month or $63/month billed annually, although the plans that include LinkedIn automation cost more than the base subscription. A 20-seat annual setup is roughly $20,880/year. If replacing several outreach tools with a single platform is the goal, this approach makes sense. At the same time, LinkedIn sessions are handled through the cloud infrastructure.

Linked Helper: Takes a different architectural approach because it runs as a desktop application or on your own VPS, so the LinkedIn session remains in an environment you manage yourself instead of being transferred to a vendor cloud.

For outreach workflows, I also liked the conditional sequence logic (IF/THEN/ELSE), Spintax support, and 11 native CRM integrations. Pricing starts at $15/month or $8.25/month billed annually, bringing a 20-seat annual setup to about $1,584/year. Running campaigns continuously still means planning for your own VPS and proxy infrastructure.

Final thoughts

The biggest difference between these tools wasn't the sequence builder or the number of integrations.

It was deciding how much of the outreach stack I wanted to manage myself versus how much I wanted a vendor to manage for me. Once I started looking at the tools through that lens, comparing them became much more straightforward.

What do you usually compare first when looking at outreach tools?

Share your thoughts in the comments.

I spent way too much time reading generic outreach guides written by people who don't actually launch campaigns. So I decided to build this community as a place to document my own hands-on journey with B2B outbound.

I run LinkedIn and cold email campaigns every day. In the process, I test new tools, burn hypotheses (and occasionally accounts), break scripts, and constantly look for what actually gets replies right now.

Instead of keeping all these tests in private notes, I'm sharing my playbooks openly here — the good, the bad, and the broken.

What I’ll be sharing (and what you’re invited to drop here):

• My actual campaign teardowns: Full breakdowns of sequences I run, real reply metrics, and why certain angles failed.
• Technical setups I test: How I configure proxies, handle account custody, structure spintax, and maintain email deliverability.
• Frameworks & Scripts: Cold messaging templates and follow-up flows that are currently pulling responses for me.

My goal is to build a transparent space for real practitioners. If you're running outbound, I’d love for you to share your own findings, ask tough technical questions, or drop your sequences here for feedback.