Outbound sourcing has a recording problem. The work happens in a browser — profiles, search results, messages — and the system of record is somewhere else. So it gets written down in a spreadsheet, or not at all.
Everything that follows from that gap is predictable: duplicate outreach, no idea which searches produced hires, and no way to answer whether sourcing is worth the time it consumes.
What the gap costs
- Duplicate contact. Two recruiters message the same person for two roles in the same week. Or the same person is approached who applied and was rejected three months ago — which is worse, and visible to the candidate.
- Lost context. Someone sourced for a role that closed is worth revisiting for the next similar one. If they were never captured, that pool does not exist.
- No measurement. Profiles viewed, contacted, replied, screened, hired — the outbound funnel has its own conversion rates, and without capture none of them can be computed.
- No compliance record. Data collected about someone who did not apply still creates obligations, including telling them you hold it. A spreadsheet does not carry a retention policy.
What a capture extension does
The mechanic is simple: add a candidate to a pipeline from the profile you are looking at, without switching tabs, and have the record land in the same system as inbound applications.
The features that matter:
- Capture without leaving the page, into a chosen role or pool.
- Duplicate detection at capture time — the highest-value feature. Being told at the moment of capture that this person applied in March, or that a colleague contacted them last week, prevents the error rather than recording it.
- Source tagging automatically, so outbound candidates are separable in channel analysis.
- Outreach logged against the record, so sequence and response are visible to everyone.
The compliance part people skip
Sourcing collects personal data about people who did not apply to you. That has consequences that inbound applications do not:
- You have to tell them. Where data is collected from a source other than the individual, there is an obligation to inform them within a reasonable period. In practice, the first outreach message is the natural place — a line stating what you hold and where it came from.
- Retention applies. A sourced candidate who never responded is still a record with a retention period. See retention.
- Capture only what you need. Professional history relevant to the role. Not personal posts, photographs, or anything unrelated.
This is the strongest practical argument for capturing into the ATS rather than a spreadsheet: retention, access control and deletion apply automatically. A spreadsheet on someone laptop has none of them and is invisible to a privacy review until it is not.
Measuring outbound
Once capture is in place, four numbers become available:
- Response rate — contacted to replied. The clearest signal of whether your targeting and message are working.
- Reply to screen — interested to actually suitable.
- Sourced to hire — the end-to-end conversion, comparable against inbound channels.
- Recruiter hours per sourced hire — the real cost, and the number that decides whether outbound beats paid channels for a given role.
Outbound typically converts far better per contact than inbound and costs far more recruiter time per hire. Both halves are needed to make a sensible decision, and neither is available without capture.
For the extension and how captured candidates flow into pipelines, see the browser extension and sourcing.