For sales pods & agency pods

Your pod runs as one unit. Your tool should too.

Most LinkedIn outreach tools were built for one operator running one inbox. A pod is eight, ten, fifteen senders moving on a shared list — and per-seat pricing, separate inboxes, and per-sender reporting punish you for every one of them. LinkedReach is built the other way around.

Acme Outreach Pod · 8 senders

Today
Sends today
187
Replies today
34
Qualified replies
11
Meetings booked
4
Per-sender sends today (8 accounts)
The pricing problem

Per-seat tools charge you for the people who don't even send.

Most LinkedIn outreach tools price per "user" on the dashboard. A pod has more users than senders. The math gets ugly fast.

An 8-sender pod, 1 manager, 1 RevOps analyst Per-seat tool ($99/seat) LinkedReach (per active sender)
Senders billed 10 (every login is a seat) 8 (only the active LinkedIn senders)
Monthly bill $990 / mo $632 / mo
Annual gap $4,296 / year saved
Manager and analyst access Billed as full users Free · unlimited operator seats
When the pod doubles to 16 senders $1,782 / mo (still pays for 18 seats) $1,264 / mo · $6,216 / year saved
The honest version

Pricing should track the unit that drives the cost of serving you. A LinkedIn sender needs a residential proxy, an AI personalisation budget, and browser-pool capacity. A manager looking at dashboards needs none of that. Charging per seat in a pod is asking the agency or the in-house team to pay a tax for adding the human who supervises the work. We don't.

What changes when your tool is built for pods

Six things a pod hits every week. Six things LinkedReach actually solves.

Cross-sender collisions

Two SDRs hit the same account. The lead notices.

The legacy version: every sender runs its own list. Same target lands in two queues. Two pod members message the same lead from different angles within a week. The prospect screenshots both and posts about it.

LinkedReach: the target list is pod-scoped. A lead added to one sequence is locked to one sender across the whole pod — with a 90-day cooldown on the account before another sender can touch it. Collisions never happen because the system won't let them.

Pod-level reporting

The manager wants pod numbers, not nine sender CSVs.

The legacy version: dashboards roll up to the user. The manager exports nine CSVs, opens a Google Sheet, builds a pivot table at 11pm Sunday to know what the pod actually shipped this week.

LinkedReach: the pod is a first-class entity. Pod-level dashboards roll up acceptance, reply, and meeting-booked rates across every sender by default. Drill into an individual when you need to coach. Roll back up when you don't.

Onboarding new pod members

A new SDR joins. Day one they should be contributing, not warming up alone.

The legacy version: buy a license, wait for IT, set up the new account from scratch, run a 2-week warm-up curve in isolation. The pod's pipeline takes a hit while the rookie ramps.

LinkedReach: add the sender to the pod, drop them on the existing target list, and the safe-cap warm-up runs automatically inside the same sequence the pod is already running. Day one the new sender is contributing — at 5 connection requests, ramping +3 a week, inside the limits the workers enforce.

Shared signal on warnings

One sender gets warned. The whole pod is exposed.

The legacy version: sender 04 catches a soft warning and slows down. Senders 01 to 09 keep firing at full speed because the tool has no concept that they're related. Twenty-four hours later, three more accounts are restricted.

LinkedReach: a warning on one sender broadcasts a 24-hour cooldown across the pod. Pacing tightens 3× on every other sender for a day. The pod manager gets pinged the moment the first warning fires — not when the third account is already locked.

Reply routing

A reply lands. Whose queue does it belong in?

The legacy version: every sender owns its own inbox. A reply addressed to one SDR sits in their personal LinkedIn until they log in. The closer who should handle it never sees it. The hot lead goes cold.

LinkedReach: one unified pod inbox. Replies are auto-routed to the pod member who owns the account or the closer queue, with full thread context, intent label, and warmth score attached. Hot leads land in front of the right human in seconds, not hours.

One AI brain across the pod

The pod's voice should compound, not split nine ways.

The legacy version: if the tool has AI at all, every sender gets its own model state. Sender 03's tone, sender 07's tone, sender 09's tone — nine different voices that each have to be tuned in isolation.

LinkedReach: Agent Mode learns from every reply the entire pod handles. The model gets better at your ICP, your objections, and your booking patterns the more the pod uses it — not just one inbox at a time.

Account assignment

Pods own a territory. The tool should respect it.

The legacy version: account ownership lives in a Google Sheet. Two pods both think they own a logo. The senior AE finds out at the QBR.

LinkedReach: the manager assigns target accounts to specific pod senders inside the dashboard. The system enforces the boundary — sender 02 cannot touch a lead that belongs to sender 05's account list, full stop. Territory hygiene without the spreadsheet.

Free operator seats

The manager and the analyst log in for nothing.

The legacy version: every login is billable. The manager pays full freight to look at dashboards. The RevOps analyst pays full freight to pull reports. The pricing model treats supervision and analysis as the same line item as outbound sending.

LinkedReach: unlimited operator seats at no charge on every plan. Pay only for the LinkedIn senders that are actively running outreach. A 10-person pod with 3 supervisors pays for the 7 senders, not the 10 humans.

How a pod runs LinkedReach

One pod, one operator console, one accountability surface.

Five steps from "we have a list" to "the pod is shipping."

Step 01

Manager assigns accounts

Drop in the territory list. Allocate target accounts to specific pod senders. The system enforces the boundaries.

Step 02

Senders run sequences

Each sender works its assigned list inside daily safe-caps. New members auto-warm at 5/day inside the pod's existing sequences.

Step 03

Replies land in one inbox

The unified pod inbox surfaces every reply across every sender, routed to the right pod member with intent labels.

Step 04

Agent Mode handles the easy ones

Auto-classify intent, draft contextual replies, propose calendar slots. Approve-each-reply or fully autonomous — pod's choice.

Step 05

Manager rolls up the pod

Pod-level dashboards. Acceptance, reply, meeting-booked rates by sender, by sequence, by week. No CSVs, no pivot tables.

Who runs LinkedReach as a pod

Two shapes of pod, one tool.

Sales pod

The in-house go-to-market unit

An SDR pod under a manager, with an AE and a RevOps analyst rolling up. You own a segment or a vertical and you need three things the per-seat tool doesn't give you: shared coverage of the account list, a unified reply queue, and pod-level reporting that the VP can read in 30 seconds. The manager's seat costs you nothing here. Neither does the analyst's.

Agency pod

The lead-gen team running one client

A pod of 5 to 20 LinkedIn senders working a single client's outbound. The agency principal logs in to monitor, the account manager logs in to QA messages, the closer logs in to handle replies — and only the senders are billable. Multi-client agencies stack pods one per client, with workspace isolation and white-label per brand.

Stop paying per seat for a pod that runs as one unit.

14-day free trial. No credit card. Add your senders, invite your manager and analyst at no extra cost, and see what pod-built pricing actually looks like on your bill.