Drafts inside Sales Nav. Lead pages, search results, saved lists.
You're already paying $99-150/mo for Sales Navigator and spending most of your sourcing day inside it. Riffly lives in the same browser tab, auto-reads each Sales Nav surface, drafts an opener in your voice, and stays out of the message-send path. No automation, no scripted connects, no bulk export. The drafting tax of switching tabs back to ChatGPT goes to zero.
Four URL families. All four work.
Every Sales Nav surface a sourcer actually uses. The lead-page popup gets the full draft flow; the search and list surfaces get a one-click batch-scan that scores 25 visible profiles against your saved job specs in parallel.
Individual lead pages
Click the icon. Riffly reads name, headline, current role, About, recent activity, Spotlights. 8-second draft.
Works on FreeAlternate lead route
Some Sales Nav accounts route to /sales/people/ instead of /sales/lead/. Same parser, same draft flow.
Works on FreeSearch builder results
Walk visible rows, extract each lead's URL + name + headline + company, batch-score against your active job specs. One click, up to 25 profiles.
Plus tierSaved lead lists
"My pipeline," "Q2 outreach," whatever you named your saved list. Same batch-scan flow as search results.
Plus tierSame wedge, richer grounding.
Sales Nav lead pages have more structured data than public LinkedIn profiles. Riffly extracts what the public profile can't see and feeds it to the prompt. Better signals in, better drafts out.
Open a Sales Nav lead
Any /sales/lead/ URL. Riffly's icon lights up in your toolbar. Click it.
Riffly reads the surface
Name, headline, current role, About, Spotlights → Skills, Experience entries, plus the recent-activity widget when present. Sales Nav's data-anonymize attributes give us stable selectors that survive their UI redesigns.
You get three drafts in your voice
Cold opener · follow-up · breakup. All grounded in the lead's actual posts, not generic compliments. Riffly's voice fingerprint applies cadence + sign-off + contraction rate from your past messages.
You copy, paste, send manually
Riffly never touches LinkedIn's message composer. You paste, edit if you want, click Send yourself. Zero automation signal for LinkedIn to detect.
Sales Nav's terms are stricter than regular LinkedIn, particularly around scraping and bulk export. Riffly does neither. Read-only DOM access on the surface you're already viewing, manual send only, no API calls to LinkedIn from our backend. Same operating model as Crystal Knows (10+ years on Sales Nav, no enforcement issues). The backend has a kill switch (RIFF_DISABLED_SURFACES env) we can flip without shipping a new extension version if LinkedIn ever signals concern.
Pasting Sales Nav profiles into ChatGPT is the long way around.
If you're already on Sales Nav, you're already inside the highest-quality recruiter UI on the internet. The friction is moving the data OUT of it (into ChatGPT, into a saved doc, into your own brain) and back in. Riffly closes that loop.
What Sales Nav users want to know.
Which Sales Navigator surfaces does Riffly work on?
Four URL families: individual lead pages (/sales/lead/<id>), the alternate lead-page route (/sales/people/<id>), search builder results (/sales/search/people), and saved lead lists (/sales/lists/people/<id>). Lead pages get the full draft popup; search and list pages get the batch-scan flow that lets Plus users score visible profiles against their job specs.
Is using Riffly on Sales Navigator against LinkedIn's terms?
Sales Nav has stricter terms than regular LinkedIn, particularly around scraping and bulk export. Riffly does neither. It reads the visible profile fields when you click the icon, drafts a message, and hands it back. You copy, paste into LinkedIn's own composer, and send manually. Same operating model as Crystal Knows (10+ years on Sales Nav, no enforcement issues). The backend has a RIFF_DISABLED_SURFACES env flag we can flip without shipping a new extension version if LinkedIn ever signals concern.
What about LinkedIn Recruiter?
Recruiter has even stricter terms, specifically forbidding candidate data export. We technically support the surface (/talent/profile/) but recommend you talk to your manager and legal team before using any third-party tool on Recruiter. Many large recruiting orgs have a blanket policy against extension use on Recruiter regardless of architecture.
How is the Sales Nav workflow different from regular LinkedIn?
Three things: (1) Sales Nav lead pages have richer structured data (job-title-history, current-company-revenue, time-in-role) that Riffly extracts and feeds to the prompt. Better grounding, better drafts. (2) The lead-list view lets Plus users batch-score 25 profiles in one click against your saved job specs (Active Profile Assist on the list surface). (3) Search-results have a similar batch flow, useful for daily saved-search workflows.
Do I need a paid plan for Sales Nav?
The drafting works on Free (3 drafts/week) and Pro ($19/mo, 200 drafts). Active Profile Assist (the batch-scan + fit-scoring) requires Plus ($39/mo) because each score triggers a separate LLM call, those costs need the higher margin to cover. If you're a high-volume Sales Nav sourcer, Plus is the right tier; the workflow is built around it.
Will Riffly slow down my Sales Nav?
No. Riffly only does work when you click the icon, there's no background polling, no profile-scraping crawler, no continuous DOM observation. Click → 8-second draft → done. Your Sales Nav stays as fast as it was.
Does the lead-list batch-scan trigger LinkedIn rate limits?
No. Riffly only reads what's already in your viewport when you click "Scan visible profiles", no scrolling, no clicking through pagination, no API calls to LinkedIn from our backend. The scoring happens server-side against the data we already pulled. You stay inside Sales Nav's normal usage envelope.
Stop alt-tabbing between Sales Nav and ChatGPT.
The drafting tax for the rest of your sourcing day is about to drop to zero. 30-day refund, no questions.