Home StreamsSales One Lead, End to End: The Complete Sales Navigator + Dynamics 365 Play

One Lead, End to End: The Complete Sales Navigator + Dynamics 365 Play

by Mo Faheem
Two relay runners passing the baton during a race on a track

Over the past month this blog has built a Sales Navigator + Dynamics 365 integration one piece at a time: wiring, sync settings, embedded forms, match-rate repair, Smart Links, the Advanced Plus intelligence layer, governance, even the off-boarding runbook. Each post stood alone. This one doesn’t. It’s the relay race, following a single imaginary lead from “we’ve never heard of her” to “closed conversation on the Dynamics timeline,” with each leg handing the baton to the piece of the machine we already built. Consider it the series’ table of contents, told as a story.

Leg 1. She surfaces in a saved search

A Sales Navigator lead search with a Changed jobs filter and the save search toggle enabled
Where every good lead enters: a precise, saved search with alerts on. Ours is a Changed-jobs search. The week she takes the VP role, she arrives in the alert digest without anyone searching for her.

Nobody found this lead. The system did. In Stop Casting Nets we built stacked-filter searches and saved them with alerts. Monday morning, the alert delivers: a new VP of Operations at one of our fit accounts, three weeks into the job. The exact window when new leaders form their vendor shortlists. She goes into the segment’s lead list with one click.

Leg 2. The account context is already waiting

The account page row showing Common searches for all employees and decision makers plus persona chips
On her account’s page, the personas we defined slice the company to our buyer profile instantly, and Account IQ has already read the filings.

Before writing a word to her, two minutes on the account page (the Advanced Plus tour): Account IQ summarizes how her company makes money, the Relationship Explorer shows a past colleague two doors from her team, a warm path instead of a cold open, and she and her likely committee go onto the Relationship Map. Auto-save, configured back in What Actually Syncs?, is meanwhile pulling the account’s CRM records into view with badges.

Leg 3. First touch, with receipts

A Smart Link detail page showing Modify and Copy link buttons and the viewer analytics panel
The InMail carries a Smart Link, not an attachment, so Tuesday night, when she reads the two-pager for four minutes and forwards it to someone we’ve never met, we know.

The intro message references the warm path and something true about her company (Account IQ earned its keep), and the content rides a Smart Link. The unfamiliar viewer in the analytics is her ops director, a name for the Relationship Map and the next introduction. Because InMail logging is on, deliberately, per the governance post, the outreach is already on the CRM timeline without anyone typing a note.

Leg 4. She becomes a record, and the record becomes a workspace

The embedded Sales Navigator widget showing a matched LinkedIn profile on a Dynamics 365 contact form
She replies. She’s real. She’s pipeline. Create contact from Sales Navigator (write-back settings decide how), and on the Dynamics form the embedded widget renders her live profile, matched, because our match hygiene is in order.

From here the two systems stop being two systems. The contact record carries her live LinkedIn profile beside the timeline. The timeline carries the InMails, the Smart Link views, the calls. The nightly Match Data Report confirms she’s matched, so validation will flag it if she changes jobs mid-deal. The champion-left-quietly scenario that kills deals in the dark. And if our rep changes jobs mid-deal, the off-boarding runbook means her successor inherits a timeline, not a rumor.

The play, on one page

  • Discover: stacked filters → saved search → alerts. The funnel refills itself.
  • Understand: Account IQ + personas + Relationship Explorer before the first message, not after the first meeting.
  • Engage: warm path, InMail, Smart Link. Every touch leaves a receipt.
  • Operationalize: contact created by policy, widget on the form, activities on the timeline, match rate watched nightly.
  • Endure: governance agreed in daylight, off-boarding that preserves the story.

Wrapping Up, and where the series goes next

None of the legs is heroic on its own: a search, a briefing, a link, a toggle. The compounding is the product. Each piece hands its output to the next until a stranger in a Monday alert becomes a documented, transferable, team-visible customer relationship. That was always the promise of wiring LinkedIn into Dynamics. It just takes the whole relay to see it. The series isn’t quite done, data validation is still ripening in my trial, and sequences deserve their own walkthrough, but if you’ve built along since Two Systems, One Conversation, you now run the same play I set out to document. Pass the baton cleanly, and the race runs itself.

Related Articles

Leave a Comment