The most underused asset in a recruitment business
A consultant with ten years in a market has a few thousand connections. Somewhere in there are the hiring managers, the operations directors and the founders who make up their entire addressable market. They are first-degree connections, which means the message gets delivered and the name is familiar.
Almost nobody works it, because the export is a wall of names with no company, no title worth trusting and no way to tell a buyer from a former colleague from someone who added them at a conference in 2019.
Two things, built once
The database. Every connection screened in or out against a written definition of a prospect, with the reason. Built once, queried forever. This is the part that turns a contact list into something you can filter by industry, by seniority or by geography on the day you need it.
The weekly sweep. Ten people a week, chosen because they have been active, researched for something specific and current, with a draft note waiting. That cadence is deliberately small. It is what a person can sustain and what stays personal.
Why binary, and why the write-up matters
The screening decision is in or out, never a number. The reason is written down. That means two things: you can audit the decisions, and if a large majority of your network is coming back as a prospect, you have learned something real about your own targeting rather than generating a longer list.
What you get back
Your network in a queryable table: name, company, title, contact details where they exist, in or out, and why. Plus a weekly shortlist of ten with drafted notes, staged, waiting for you to send them.
Where this goes wrong
Enriching everyone. The single most expensive mistake available here. A network of five thousand contains a lot of students, retirees and people from a previous career. Prefilter first.
Skipping the suppression step. It runs before ranking for a reason. Rank first and you will surface someone you messaged three weeks ago, which is worse than not contacting them at all.
Automating the send. It is the one hard rule in this play. Everything upstream is automation; the message is yours.