A short list worked weekly beats a long list worked when it is quiet
Every recruiter has a version of this list: the hundred accounts and people who would change the desk if they became clients. Nearly everyone works it the same way, in bursts, when a deal falls through and the pipeline looks thin. Business development done only in the gaps produces exactly the feast and famine it was meant to cure.
The fix is not more effort. It is a fixed list, a fixed day and a small number. Ten a week, every week, gets round a hundred names several times a year without anybody hearing from you twice in a quarter.
What makes that sustainable is that the slow parts are done before you sit down: checking who has moved, finding something current worth saying, writing the first draft. What is left for you is judgement and the send.
The list itself can come from anywhere. One good source is your own network: turn a LinkedIn connections export into a scored prospect database builds and screens the pool. This play assumes the hundred are chosen and is only about the weekly rhythm.
What you get back
Every week, ten rows from your list. Each carries what changed since the last refresh, a research note with its source, and either a connection note inside the character limit or a warm message for someone already in your network. All of it is marked as staged in your own table. You also get a line on who was held back and why, so you can see the suppression working.
Variations worth knowing
Build the hundred first. If you have the criteria but not the names, the list can be built with one people search per segment, de-duplicated on profile URL, and checked against your existing connections so that nobody you already know receives a cold invitation.
Segments with different weight. The score uses the priority you give each segment, so say in your notes which ones matter most.
A one-off list. For a campaign list, not a standing one, see write one sourced opening line per person on a list you have already built.
Where this goes wrong
Ranking before suppressing. The order is the point. Rank first and the most recently contacted people float to the top.
Not marking rows as sent. Suppression only knows what the table tells it. Send a note without dating the row and the same person is back next week.
A profile address that belongs to someone else. Handles get abandoned and reassigned. The refresh can return a stranger's details without any error, which is why the returned name is checked against yours.
A hundred that is really four hundred. A loose list turns the sweep into a feed of whoever changed job this week.
Automating the send. It is the one hard rule here. Everything before the message is automation. The message is yours.
