Outreach Guard

Chrome extension for LinkedIn recruiting teams

Never approach the same candidate twice.

Outreach Guard turns a profile yellow on every teammate's screen the moment someone messages that candidate on LinkedIn or LinkedIn Recruiter. The extension detects the send by itself, so there is nothing to log, tag, or paste into a shared sheet.

Start now See how it works

talent search / shortlist OG
SL Sofia L. Product Designer · Porto
MR Marta R. Senior Backend Engineer · Lisbon ✓ Contacted by Anna on 12/09
JD John D. Data Engineer · Remote
PN Priya N. Engineering Manager · Madrid
TK Tomas K. QA Lead · Braga
Illustration of the extension. Names and dates are fictional.
  • Runs on LinkedIn profile pages and search lists
  • Marks reach every PC on the licence
  • Profile link, sender, date. Nothing else

The cost of a duplicate

A second approach is not a second chance.

  1. 01

    The candidate gets two different pitches for the same role in the same week, then stops replying to both.

  2. 02

    You pay for the InMail twice and get the same answer once. On a team of six that is a budget line nobody can explain.

  3. 03

    The recruiter who wrote first finds out on the follow up call, in front of the client.

How it works

Three steps, none of them yours.

01

The mark is already there

Anna messaged Marta R. on 12 September. Since then the name carries a yellow marker on every screen in the company, and the who and the when sit one hover away.

Anna's PC
talent search / backend OG
SL Sofia L. Product Designer · Porto
MR Marta R. Senior Backend Engineer · Lisbon ✓ Contacted by Anna on 12/09
JD John D. Data Engineer · Remote
02

Sending is the trigger

Rui writes to John D. and hits send. The extension reads the send in the page and writes the mark before the thread even opens. No button to remember, no CRM field to fill, nothing that depends on a recruiter being in the mood for process.

Rui's PC
talent search / backend OG
SL Sofia L. Product Designer
MR Marta R. Backend Engineer
JD John D. Data Engineer
To John D. Send Mark written
03

Everyone else already knows

Marco opens the same search from another office a few seconds later. John D. is yellow on his screen too. The record belongs to the company, not to the machine that created it.

Marco's PC, another office
talent search / data OG
AV Ana V. Analytics Engineer · Lisbon
JD John D. Data Engineer · Remote ✓ Contacted by Rui on 16/09 Synced
TK Tomas K. QA Lead · Braga

Why teams keep it

Built for the part of the process nobody follows.

It works on the recruiters who would never log anything

Adoption is what kills shared trackers. Here there is nothing to adopt. The extension watches the send and writes the record, so the recruiter who ignores every process still feeds the same database as the one who loves it.

Yellow reads faster than a list

The signal sits on the name, inside the list you are already scanning. No second tab, no search box, no cross check before you write.

Priced per PC

You pay for the machines you install on. Add a seat when someone joins, drop one when a contract ends, from the billing portal.

Nothing to migrate

No CRM integration, no API keys, no import. Install, paste the licence key, carry on working the way you already do.

Expiry

Old outreach should not block new outreach.

A candidate you approached eighteen months ago is a fresh candidate today. Every mark carries a clock, 180 days by default, and expires on its own across the whole team. Set the window per company, from 30 days to whatever your market needs.

  1. Day 0 Marta R. Anna sends. The mark appears on every PC.
  2. Day 90 Marta R. Still marked. Still nobody writes to her twice.
  3. Day 180 Marta R. The clock runs out. The mark clears itself everywhere.
  4. Day 181 Marta R. Open again. A new message starts a new 180 days.

What we store

The record is three fields long.

What leaves the browser

  • A one-way fingerprint of the profile link, hashed on your machine. The link itself never leaves the browser
  • Which teammate sent the message
  • The date and time of the send

2e5097…a4896  |  rui  |  2026-09-16 10:42

What never does

  • Candidate names, headlines or profile content
  • Message text, subject lines or attachments
  • CVs, exports, or anything the page renders around the profile
  • Any record belonging to another company on the platform

Each company reads only its own marks. The extension sends the hashed fingerprint, the licence key and the device id, and stops there. The hash cannot be reversed, so even our own database never knows who your candidates are.

Get started

Set it up before your next campaign.

Create your account Already have a licence? Log in

  1. 01 Sign up and choose how many PCs you need.
  2. 02 Install the extension on each PC, paste the licence key.
  3. 03 Work as usual. The marks take care of themselves.

Independent product, not affiliated with or endorsed by LinkedIn. LinkedIn is a trademark of LinkedIn Corporation.