Sixty profiles read, nine messages drafted for you

What does a companion do that a sourcing tool does not?

It works across all of them.

LinkedIn Recruiter has the freshest data at the source, and Gem, SeekOut and hireEZ own sequencing, talent pools and contact-finding, as of this writing. The seams between them land on whoever sits in the middle.

A companion takes the seams. It reads LinkedIn through the session you are already signed into, checks each keeper against your ATS, looks up contact details and stages the writes. It runs on macOS and Windows, which is how it gets to be signed in as you.

Sixty profiles read, fourteen shortlisted, three already in play

A backend-engineer search, started in the ten minutes before a meeting. The companion reads 60 profiles against your rubric, shortlists 14, checks all 14 against Greenhouse and drops three already in process. It finds work emails for 9 of the remaining 11 through Hunter and Lusha, then stages 11 prospect records and 9 drafted messages.

You read, edit two drafts, reject one profile the rubric got wrong, approve the rest. The other two hours did not happen.

Which writes stop for approval?

Greenhouse, Ashby, Lever, Workable and Teamtailor are native integrations, so "add these eleven as prospects with a source tag" runs as written. Creating a candidate is a write, and writes pause, so you see the record first.

Hunter and Lusha are native too, so contact-finding happens mid-pass. The full sweep is in how to automate candidate sourcing.

Write the rubric once, apply it sixty times

Twenty minutes writing down what "right kind of company" means pays for every pass after it.

A companion applies the same test to profile 60 as to profile 1. Outreach stays yours to approve one message at a time.

Frequently asked questions