Overview
Sales Navigator is where LinkedIn's own sellers prospect. But to prioritize leads, reps had to toggle between Sales Navigator, Merlin, and their CRM, stitching signals together by hand, deal after deal. We brought LinkedIn's first-party data directly into Sales Navigator's Lead Search as native filters, letting reps prospect from one platform. It shipped to LinkedIn's internal sales teams as the first pillar of the company's "Customer Zero" Sales Navigator vision.
The problem
Prospecting is mission-critical: SD reps spend ~60% of their time on it. But the internal workflow was fragmented: the first-party signals reps relied on to prioritize leads lived in Merlin, not Sales Navigator, so reps constantly switched tools and stitched the picture together by hand.
"By the time I've jumped between Merlin, Sales Nav, and the CRM to figure out who's worth contacting, half my prospecting time is gone."
Recurring theme from rep research (paraphrased)- A productivity tax: tool-switching cost reps 4 to 8 hours per week, roughly $3.6M a year in lost productivity.
- The signals lived elsewhere: 55% of Merlin searches relied on just four data signals that Sales Navigator didn't have.
- An adoption gap: some sales teams sat at just 44% weekly active use vs. 75% for others, despite 99%+ license activation.
Process
The tempting move was to rebuild all of Merlin's filters inside Sales Navigator. We framed the work differently: find the few signals that actually drive prospecting, and bring those in first.
Research & framing
Partnering with PM and data science, we dug into Merlin's Prospect Finder usage data to turn an anecdotal question, "which signals matter?", into a quantified one. The data was decisive: a small handful of signals accounted for the majority of real prospecting searches.
Explorations
With the signal set narrowed, the work turned to fit and trust: which signals to ship first, how the new filters should sit alongside Sales Navigator's existing Lead Search, and, hardest of all, making the underlying data accurate enough that reps would believe what it returned.
Key decision
We shipped the highest-value P0 signals as native filters: active & previous subscriptions, recent job posters, and company page admins, and invested just as heavily in making that data accurate and properly governed. The rest of Merlin's signals were phased deliberately rather than ported wholesale.
Solution
The result brought LinkedIn's first-party data into the prospecting flow as native search filters. Three ideas carried the work:
The right signals, not all of them
Rather than port every Merlin filter, we used usage data to find the handful that drove most prospecting, and brought those in first.
First-party filters, native in Lead Search
Active & previous subscriptions, recent job posters, and company page admins, right where reps already search, with no tool-switching.
Data reps can trust
Surfacing the signals was only half the job. They had to be right. We worked diligently with engineering on data accuracy and with legal on governance, so every internal user gets the insight and trusts it's correct.
Impact
Shipped to 100% of internal sales teams (Feb 2026). Eight weeks after launch:
Reflection
Two lessons stuck. First, restraint: the obvious path was to recreate all of Merlin inside Sales Navigator, but the data showed a small set of signals carried most of the value, so we shipped those first and proved it on our own teams as "Customer Zero." Second, trust: adoption hinged on the data being right, which took diligent work with engineering on accuracy and with legal on governance, so every internal user believes what the filters return.
This was Pillar 1 of three. Within eight weeks, weekly active use among sellers climbed from 54% to 85%, and the same playbook now extends into deeper CRM integration and multi-channel outreach.