The problem you're trying to solve
Sales managers can see deals in HubSpot and calls in Gong, but they cannot see what their reps are doing on LinkedIn — and they cannot tell whether LinkedIn is producing pipeline. Your weekly forecast call has the usual columns: stage, amount, close date, last activity. There is no column for LinkedIn engagement, because LinkedIn engagement happens in a UI nobody on your team logs into for tracking. When you ask reps "what are you doing about social selling?" you get vague answers. The reps who post screenshots of their post likes look productive. The reps quietly commenting on buyer posts look like they're doing nothing.
Meanwhile, the deals you're trying to forecast often started on LinkedIn. A buyer commented on the founder's post in March. Your AE replied. Three weeks later that buyer DM'd the AE. Two months later a meeting booked. None of that trail exists in HubSpot. The pipeline shows up as "inbound" with no source. This is the gap a LinkedIn-to-HubSpot sync is built to close — every comment becomes a logged touchpoint, not an invisible one.
You cannot manage what you cannot see. Right now, you cannot see LinkedIn.
What GTM Brigade configures on day one
On day one we give every rep a 120-profile watchlist mapped to their book of business, capture each rep's voice, route signals to Slack in near real time, and log every engagement back to HubSpot as a touchpoint — so the manager can see activity and attribution in standard reports.
Per-rep watchlists
Each rep gets their own watchlist — composed from their territory, named accounts, and ICP shape. The manager sees the union of all rep watchlists as a team view. New target-account additions flow through the manager. The watchlist becomes the operating layer where the manager's strategy meets the rep's daily workflow.
Daily-5 comment cadence
Reps comment 5 times per day on watchlist posts. Voice-captured drafts collapse write-time to under 3 minutes per comment. The cadence is visible to the manager as a standard HubSpot activity metric — 25–35 comments per rep per week, scored against deal stage and account fit.
HubSpot sync + attribution
Every comment, reply, and DM is tracked in your tenant against the matched HubSpot contact. Pipeline that started as a watchlist comment shows up in the LinkedIn-sourced attribution lane (in your tenant, exportable to HubSpot). The forecast call gains a column.
What the first 90 days look like
By day 14 the watchlists are live and reps are running the daily-5, by day 45 the manager has weekly activity visibility, and by day 90 LinkedIn-sourced pipeline is a forecast-call column.
- Days 1–14: Per-rep watchlist builds, voice-model setup, Slack routing, HubSpot sync. Reps start the daily comment cadence. Manager gets the activity dashboard.
- Days 15–45: The weekly Slack recap lands every Friday — per-rep comment counts, watchlist coverage, account-level engagement velocity. The 1:1 conversation gets specific.
- Days 45–90: HubSpot's LinkedIn-sourced pipeline column populates meaningfully. The CRO can see the channel's contribution. The forecast call references it.
What this is not a fit for
Skip this if you have fewer than 4 reps, if your team operates without HubSpot or Salesforce, or if your sales cycle is under 14 days. Three honest disqualifiers:
- You have fewer than 4 reps. Below that, the manager can see everything by walking around. The coordination layer is solving a problem you do not yet have.
- You don't use HubSpot or Salesforce. The attribution lane is the highest-impact piece for managers. Without bidirectional CRM sync, the pipeline column never populates.
- Your sales cycle is under 14 days. Transactional sales do not benefit from public engagement loops — buyers do not buy from comment threads on that timeline. If your sales cycle is longer but you're still working out fit-scoring, LinkedIn lead scoring is a lighter way to start.
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 will look at your current HubSpot reports, sketch what the per-rep watchlists would contain, and tell you within the meeting whether the activity-to-pipeline visibility you need is achievable — or whether your forecast process needs upstream fixes first.