The hardest message in a job search is rarely the application. It is the message to a former colleague, months after the last project, when there is no news to share and no favour to ask yet. Most people wait until they need something, then feel the awkwardness of that timing in every sentence. The message reads like a transaction because, by then, it is one.
The answer this part of the build landed on was deliberately unglamorous. Not a CRM. Not a reminder system that scores relationships. Just a small, regular check-in: one short message, to one person, inside a slot that already existed in the week. The point was never to keep a list warm. It was to keep the habit warm, so the message never had to carry a request it was not built for.
Designing the habit
Three choices shaped this part of the build, and all three are about restraint.
First, the check-in carries nothing. No request, no hint of a request, no “keeping you in mind” language that quietly points at a future ask. The message is about them, or about something they shipped, said, or changed. If a reader could not tell whether the sender wanted anything, the check-in passed.
Second, the habit is tiny and scheduled, not large and inspired. One check-in inside the week’s networking slot, to one named person. No batching, no list-clearing, no heroic catch-up Sunday. The design assumption was simple: a habit that needs motivation will lose to a week that is already full.
Third, nothing is tracked except that it happened. No relationship scores, no last-contacted dashboard, no green-amber-red health for people. The only record is a single tick: contacted this week. Anything more turned a person into a pipeline, and the messages started to sound like it.
What worked
Referral requests changed character completely. A request sent to someone contacted twice in the past month reads as a continuation, not an opening. The reply rate was not the interesting part. The tone was: shorter answers, faster answers, and an offer to look at something specific rather than a polite “let me know how I can help.”
The habit also protected the search itself. Weeks of applications with no human reply in them are corrosive, and a single real conversation can carry a week that a portal cannot. A check-in that expects nothing in return is, paradoxically, the one most likely to produce a useful reply — a name, a hiring freeze nobody had announced, a team that is about to open a role.
And the check-ins compounded in an unexpected direction. People who made a habit of noticing former colleagues started noticing their work more carefully, and that attention showed up in the messages. Specificity became the habit’s signature, and the signature is what made the messages welcome rather than dutiful.
What broke, or nearly did
Templates nearly broke it first. A suggested opener, meant to lower the barrier, produced messages that sounded like everyone else’s suggested opener. The fix was to keep a prompt, not a script: “What did they actually ship, say, or change recently?” A prompt carries specificity. A template carries sameness, and recipients can tell.
Volume was the second trap. An early version suggested working through a whole contact list in rotation, and the result was predictable: messages sent to meet a quota, replies that felt like obligations, and a habit abandoned within a fortnight. One person a week, chosen in advance, was the ceiling that kept it honest.
The honest limit: a warm network answers faster and kinder, but it does not manufacture roles that do not exist. A check-in cannot fix a market, a hiring freeze, or a mismatch of skills. What it can do is make sure that when a role does exist, the person who knows about it hears from you before they hear from a stranger with the same CV.
Lessons for builders
Design for the moment before the moment. The referral request is decided weeks earlier, by whether contact has been ordinary and recent.
Keep the unit embarrassingly small. One message, to one named person, inside an existing slot. Habits that need a free afternoon are not habits.
Refuse to score relationships. Some things a product can make easier must not be made measurable, because the measurement changes the message.
Let a prompt carry specificity, never wording. “What did they actually ship, say, or change recently?” is a better tool than any opener.
The project behind these lessons is WUUUH, a peer community for rebuilding after a layoff, where keeping contact warm, comparing outreach that worked, and reporting replies are part of the ordinary discussion.
