How does this fit into an SDR's existing outbound workflow?

It sits before the cold sequence, not after. The traditional SDR motion is research, sequence, hope for a reply. The watchlist motion is comment publicly first, then sequence with reference to the comment thread. Buyers who saw your comment three times that week respond at multiples of the rate of buyers receiving cold first-touch. Reply rates on sequences improve as a downstream effect.

Who actually benefits from this — junior SDRs or senior ones?

Both, differently. Junior SDRs benefit because voice-captured drafts give them comment quality they could not produce manually for 6 months of practice. Senior SDRs benefit because the watchlist focuses their existing skill on the right 5 posts per day instead of scrolling 200. The motion compresses the learning curve for juniors and the search-time for seniors.

How long until booked meetings show up?

First DMs from watchlist profiles in week 3. First booked meetings from LinkedIn-sourced conversations around day 45. By day 90, meetings per week with a LinkedIn-attributed origin become a measurable share of the SDR's pipeline. Volume varies — SDRs working high-LinkedIn-density ICPs (devtools VPs, RevOps leaders) see faster results than those targeting roles that post less.

What does this replace in the SDR's day?

The 2 hours of Sales Nav searches and CSV exports that produce lists nobody works through. The Notion doc of "people to engage with this week" that gets stale by Wednesday. The scattered LinkedIn scrolling between cold-call windows. All three collapse into one 20-minute morning cadence on the watchlist, plus 1–2 contextual DMs sent later in the day to buyers who replied.

How is this different from "social selling" training?

Training tells SDRs to be active on LinkedIn. It does not give them a system. The watchlist is the system — it tells the SDR which 5 posts to comment on today, drafts the comment in their voice, routes the reply back to them in Slack in near real time, and logs everything to HubSpot. Training without a system produces inconsistent behavior. The system produces a consistent cadence.

LinkedIn for SDRs: a feed that replaces 2 hours of prospecting

The problem you're trying to solve

SDRs spend 2 hours a day on Sales Nav, lead-list scraping, and prospecting docs — and the cold sequences built on top still get sub-2% reply rates because the buyer has never heard the SDR's name before. Your SDR opens Sales Navigator at 8:30am. They run three saved searches. They export 80 leads. They paste them into Outreach. The sequence sends. By 11am the SDR has touched 80 prospects and 0 of them have any reason to remember the touch. By 5pm one prospect has replied — "remove me from this list."

Meanwhile, every one of those 80 prospects has posted something on LinkedIn this week. Half of them have posted about a problem your product solves. None of them have seen your SDR comment on any of their content. So when the cold email arrives, it arrives from a stranger — which is why warm-first outbound consistently outperforms the cold-first sequence on the same list.

The volume motion fails not because the leads are bad but because the SDR's name carries no weight. There is no surface where the SDR builds recognition before the cold touch. Comments are that surface. Nobody has set up the system to use them.

What GTM Brigade configures on day one

On day one we give every SDR a 120-profile watchlist mapped to their ICP segment, capture their voice, route signals to Slack in near real time, and log every comment and DM to HubSpot — so the cold sequence finally lands on a name the buyer has seen before.

Per-SDR watchlist

The watchlist is composed from the SDR's ICP segment — 60 buyers, 30 amplifiers, 30 deal-stage targets if there are open opportunities. It updates daily as profiles post. The SDR sees one prioritised feed instead of running Sales Nav searches.

Voice model

The supervised voice-model setup captures the SDR's cadence, opinions, and vocabulary. Drafts come pre-written. The SDR reviews, adjusts (usually 30 seconds), sends. Five comments per day. Total time: 20–25 minutes.

Signal routing + HubSpot sync

When a watchlist person replies to the comment, posts new content, or DMs the SDR, Slack pings in near real time. Every interaction logs to HubSpot as a touchpoint on the contact through our LinkedIn-to-HubSpot sync. The cold sequence now references the comment thread when it sends — "saw your post on X last week" becomes a literal callback.

What the first 90 days look like

By day 14 the watchlist is live, by day 21 first DMs from buyers land, and by day 45 first meetings from LinkedIn-sourced conversations book.

Days 1–14: Watchlist build, voice-model setup, Slack routing, HubSpot sync. SDR drops 1.5 of the 2 hours of Sales Nav and starts the daily-5 cadence.
Days 15–45: First DMs from watchlist profiles. Connection-request acceptance passes 60% because invites follow public comment trust, not precede it. Cold-sequence reply rates climb.
Days 45–90: First booked meetings from LinkedIn-sourced conversations close. HubSpot logs them in the LinkedIn-sourced attribution lane. SDR-to-AE handoffs now include a comment thread context, not just an email reply.

What this is not a fit for

Skip this if your SDR motion is high-volume transactional, if your ICP doesn't post on LinkedIn, or if your SDRs won't commit 20 minutes a day. Three honest disqualifiers:

Your motion is high-volume cold (500+ touches per SDR per day). The watchlist is depth-over-volume. If your funnel needs raw touch count, the cadence breaks the math — though the prospecting motion overview covers hybrid setups where both can coexist.
Your buyers don't post on LinkedIn. If the directors in your ICP are not publishing, the watchlist has nothing to surface for them.
SDRs won't commit 20 minutes a day. Daily cadence is non-negotiable. Reps who batch-engage once a week miss live threads and the loop breaks.

How to know if this is the right play for you

A 30-minute walkthrough with one of our strategists is the fastest qualification path. We'll pull up your current outbound stack, sketch what the SDR-side watchlist would actually contain, and tell you within the meeting whether the cadence will lift your sequence reply rates — or whether the volume motion you have is fine for now.