How does LinkedIn lead scoring actually work?

Every LinkedIn interaction emits a signal — comment, reaction, profile view, DM, mention, watchlist post, tag-in. GTM Brigade scores each signal against a 0–100 ICP-fit model that weights signals by intent strength (a 3-sentence comment from a VP is worth more than a like from an intern). Scores update per-interaction and decay 2 points per week of inactivity. Contacts crossing 70 route to Slack with full context and a draft warm-DM in near real time.

Who is this designed for?

B2B sales and RevOps teams of 4–25 reps who need to surface warm contacts faster than weekly reporting allows. Most common fit is companies running HubSpot with an active LinkedIn motion. It also fits ABM teams trying to identify which buying-committee contacts have started showing engagement. It doesn't fit teams without a CRM, teams with sub-14-day sales cycles where lead scoring is moot, or teams without a defined ICP.

How long does deployment take?

Scoring is live on day 1 (model loaded, threshold defaults applied). Watchlist + voice model deployment take the rest of the 14-day window. By day 7 the first scores are flowing. By day 14 threshold alerts are firing to Slack with draft DMs. By day 30 the team is calibrated on their thresholds and false-positive rates have dropped below 10%.

What does this replace?

Replaces manual lead-scoring spreadsheets, lead-scoring fields in HubSpot that were built on form-fill events only, and the Zapier/Make chains your RevOps team built to ferry LinkedIn signals into the CRM. Some teams also retire their intent-data tool's LinkedIn signal layer (keeping the firmographic and search-intent layers). Engineering and ops hours saved usually pay for the seat cost in the first 60 days.

How is this different from HubSpot's native lead scoring?

HubSpot's native lead scoring runs on properties HubSpot already has — form fills, email opens, website visits. It cannot score LinkedIn engagement because that data isn't in HubSpot natively. GTM Brigade captures the LinkedIn signals first, scores them, and writes both the score and the underlying events to HubSpot. You can then feed our score into HubSpot's native scoring as one input among many. The two layers compose; they don't replace each other.

LinkedIn lead scoring: in near real time from comment to CRM

The problem you're trying to solve

Your lead scoring model is blind to 80% of buyer intent. Your HubSpot scoring fires on form fills, email opens, demo-page visits, and pricing-page views. Those events happen at the bottom of the funnel — by the time someone fills a form, they've often already decided. The earlier signals — a VP commenting on your founder's post, a buyer reacting to a competitor's announcement, a director DMing a peer about your category — all happen on LinkedIn and never reach your CRM.

The pattern: your top SDR somehow knows which 10 contacts to prioritize this week. When you ask how, the answer is "I scrolled LinkedIn at 8am and noticed a few of them were active". You cannot scale that. The other SDRs aren't scrolling, or are scrolling the wrong feed, or don't know which signals matter.

You don't have a lead-scoring problem. You have a "the highest-intent buyer signals never arrive in your scoring system" problem. Adding more weight to form-fill events won't fix it. You need a different signal source — exactly what the RevOps workflow treats as a data-ingestion gap rather than a scoring gap.

What GTM Brigade configures on day one

The day-one configuration is a 7-signal LinkedIn scoring engine, ICP-fit weighting calibrated to your tenant, and end-to-end signal-to-CRM latency in near real time. This is lead scoring built for the channel where buyers actually leave breadcrumbs.

The signal set we score

Comment on a team post: base 8 points × ICP weight (3-sentence-plus content scored higher than a 5-word "great post")
Reaction on a team post: base 2 points × ICP weight
Profile view of a rep: base 4 points × ICP weight (when LinkedIn exposes it via Sales Nav linkage)
DM sent to a rep: base 15 points × ICP weight
Mention or tag-in: base 10 points × ICP weight
Watchlist post (their own original post): base 1 point × ICP weight × recency
Comment on competitor's post: base 5 points × ICP weight (signals category active interest)

Decay rule: -2 points per week of zero interaction to keep the surfaced list current.

The ICP weight

Calibrated in week one from your ICP definition. A VP of RevOps at a 200–2000 employee SaaS company in our example tenant gets ICP weight 1.5×. A junior employee at a non-target industry gets 0.2×. The same comment is worth 7.5× more from the right person.

Threshold and routing

Default threshold for the "warm contact" alert is score ≥ 70. When a contact crosses the threshold, our LinkedIn-to-HubSpot sync writes the event in the same transaction:

Score written to HubSpot custom property linkedin_icp_score (latency: in near real time)
Slack alert fires to the contact's owner (or to a configured channel) with: who they are, what triggered the score, HubSpot stage, deal value, recent engagement history, and a draft warm-DM in the rep's voice model.
HubSpot timeline event written with subtype score_threshold_crossed.

The rep edits the draft DM in under 60 seconds and ships. The score is the routing trigger; the voice model is the response.

Calibration

Week one (Calibrate phase) is where we tune the model. False-positive rate typically drops from ~25% on day 7 to under 10% by day 21 as your team flags incorrectly-scored contacts and we adjust ICP shape weights.

What the first 90 days look like

By day 14 the scoring loop is firing, by day 30 the team trusts it, and by day 90 it's the primary surfacing mechanism for warm contacts.

Days 1–14: Scoring engine live, HubSpot properties + Slack routing wired, watchlist built, voice models captured.
Days 15–30: First wave of threshold-crossing contacts surface. Calibration drops false-positive rate below 10%. Reps' meeting count climbs as warm contacts get worked within hours instead of days.
Days 30–90: HubSpot reports show score-threshold-crossed → meeting-booked → opportunity lineage. Most teams retire their manual lead-scoring spreadsheets by day 60.

What this is not a fit for

Skip this if you don't use HubSpot, your sales cycle is sub-14 days, or your ICP isn't defined yet. Honest disqualifiers:

Not on HubSpot. Scoring writes to HubSpot natively. Salesforce support is roadmapped, not live as of May 2026.
Sub-14-day sales cycle. Lead scoring optimizes for surfacing warm leads ahead of time. If you book demos in the same week as first touch, scoring isn't your bottleneck — the SDR workflow is closer to the right starting point for high-velocity motions.
No defined ICP. The model weights are calibrated to ICP shape. Without one, the model surfaces noise.

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 look at your current lead-scoring model, simulate what the LinkedIn signal layer would have surfaced last quarter, and tell you in the meeting whether this materially changes your SDR efficiency — or whether your existing scoring is already capturing what you need.