Build a referral pipeline before you need it: the 12-month playbook

The fastest way to get referred isn’t to message more people during a search. It’s to know the right people before the search starts. A referral from someone who’s watched your work for a year is a different object than a cold ask: they can vouch for you honestly, so the recruiter screen treats it differently. The catch is timing. You have to build the relationship before you need it. Here’s the 12-month version, plus what to do this week if you’re starting from zero.

This is part of our referral playbook. If you need a referral this week instead, start with how to ask for a referral on LinkedIn.

Why the long game wins

When you ask a stranger for a referral cold, you’re asking them to vouch for someone they don’t know. Even with a perfect message, the internal note they write is thin: “Candidate reached out, seems competent, JD looks like a match.” A recruiter can read between those lines. It’s a polite endorsement, not a real one.

Now compare the version where you’ve been in conversation for eight months. The referrer can write: “I’ve known this person’s work for most of a year. They consistently have sharp takes on observability, and the team needs exactly that background. Strong yes.” That note moves you to a different pile. The work to build the relationship is what makes the second note possible.

The mechanism shows up in the data, too. Applicant-tracking vendor Ashby, analyzing its own customers’ funnel data, found that referred candidates advance through interview stages at a markedly higher rate than people who apply cold (see its referrals report). It’s a durable pattern, not a new one: SHRM, reporting on annual sources-of-hire data, has noted for years that employee referrals stay among employers’ top sources of hire and convert from interview to offer at unusually high rates (see SHRM’s coverage). The other half of the case is timing. A lot of the best roles get filled before they’re ever posted, through people who already know someone worth tapping. A pipeline is just a way to be that someone at more companies when the search starts.

The 12-month plan

None of this takes much time per week. It takes consistency. Here’s how the year breaks down, phase by phase.

Months 1–3: map the network you want

Pick 30 companies you might want to work at in the next two or three years. For each, find three to five people whose work you respect. Engineers if you’re an engineer, PMs if you’re a PM, founders if you’re aiming at small companies. The list doesn’t need to be perfect. You refine it as you go.

Where to find these people:

• Conference speakers and meetup organizers in your field
• Authors of technical blog posts that actually changed how you work
• Maintainers of open-source tools you use every day
• People whose comments you keep nodding along to on LinkedIn or X

Months 1–12: engage publicly with substance

Comment on their public writing. Not “great post!” — substantive engagement. Disagree where you actually disagree. Add an example from your own work. Push their idea one step further than they did. Two or three real comments a month per person is more than enough. Quality beats volume here every time.

This isn’t a performance. You’re engaging with people whose work you already find interesting, in a way that happens to be visible to them. The relationship forms because you have something to offer, not because you’re running a play. If you can’t find anything genuine to say about someone’s work, they don’t belong on your list.

Months 3–6: reach out for a non-job reason

Once you’ve been visible in someone’s comments for a couple of months, move to a direct message. The rule: it’s about anything except a job. A specific technical question. A pushback on a post they wrote. An offer to share a tool or write-up that’s relevant to what they’re working on. You’re building a real professional relationship, and you give first.

Some of these go nowhere, and that’s fine. Some turn into ongoing conversations. The ones that stick are the foundation of the pipeline. The ones that don’t cost you a few minutes.

Months 6–12: maintain the conversation

For the people who engaged back, send them something every two or three months. A relevant article. A follow-up question. An update on something you’re building that connects to a topic they care about. Don’t overdo it. One ping a quarter per person is plenty. The goal is to stay loosely in mind, not to occupy their inbox.

This is also where a tracker earns its keep. Across 15 relationships, you will not remember who you last spoke to or what about. A simple board of who you’re in touch with, what they’re working on, and when you last reached out turns “I should ping people sometime” into an actual cadence.

Month 12+: the ask is easy

Now a role opens at one of your target companies. The message you send looks like this:

Hi [Name] — finally starting a real search. [Company] is at the top of my list, and the [role] role on your team looks like a strong fit. You know my work already from our back-and-forth on [topic]. Would you be open to flagging my application internally?

Notice how short that is. It can be short because the year of context is doing the persuading. You don’t need to prove you’re competent or explain who you are. They already know. For the mechanics of the ask itself once you’re here, see how to ask for a referral on LinkedIn.

Why the warm ask converts so much better

The whole point of the pipeline is to change which conversation you’re having when you ask. A cold ask and a warm ask are not the same request with different odds. They’re different requests. Here’s how they differ at each step:

Starting from zero: what to do this week

If you have no network and a search is six months out, you’re in the ideal spot. Don’t overengineer it. Three short sessions get you moving.

Hour 1: build the list

Write down ten companies you’d want to work at in the next two or three years. For each, find one person whose public work you actually respect. Follow them.

Hour 2: read and engage once

Read three recent posts from each person. Where one actually resonates, leave a substantive comment. Not on all ten. On the two or three where you have something real to say.

Hour 3 (week two or three): be useful

Find one way to help without expecting anything back. Send someone a link to a related write-up. Share their work in your own network. Open a small pull request on a public repo they maintain. Then set the cadence: one substantive comment a week, rotating across the ten. That’s the whole engine.

What kills the pipeline

• Transactional energy.If your engagement reads as “networking,” people pull back. If it reads as genuine interest, they lean in.
• Vague flattery.“Love your work!” builds nothing. “I disagreed with your point on X because Y” builds a relationship.
• Pinging only when you need something. If your last five messages were all asks, the relationship was never a relationship.
• Copy-paste comments. If your comment could apply to 50 posts, it applies to none. Specificity is the entire signal.

The thread running through all four: this only works when the interest is real. For the longer version of staying on the right side of that line, see networking without being pushy.

The ROI is mostly free time

The honest pitch for doing this is that it barely costs anything. Most of the “work” is reading you’d do anyway, plus a few comments and a quarterly message. Call it an hour or two a week of incremental effort. In exchange, when you start a search, a handful of your target companies already have someone inside who knows your work and will flag your application without you having to sell yourself first.

The exact multiple depends on the role and the relationship, so don’t anchor on a number. The shape is what holds. A warm ask converts a lot more often than a cold one, and the gap compounds: more flagged applications mean more interviews, which mean more offers, which mean a stronger hand when you negotiate. Why employees say yes at all is worth understanding too, including the referral bonus they often earn. We covered it in why employees say yes.

Doing this without it becoming a second job

Tracking 15 relationships across 30 companies by memory doesn’t work. You forget who you spoke to, miss the quarterly ping, and by the time a search starts you’ve lost the thread on half the list. That’s the part Rolewynhandles: it keeps a contact board across your target companies, so when you do activate a search, the people you’ve been engaging with surface as priority outreach instead of getting lost.

It also drafts the eventual ask in your voice from your resume and the job description, and reminds you when a relationship has gone quiet. You still write the human parts and press send. The tool just removes the busywork between you and the people you already know. More on the contact discovery itself on the referrals page.

The deeper principle

Networking that works is professional curiosity practiced consistently in public. You don’t have to be performative. You don’t have to attend events. You have to actually engage with work you find interesting, by people you find interesting, in a way that’s visible to them. The career benefits follow on their own. The pipeline is just the residue of a year spent paying attention to the right people. Start now, while you don’t need it. That’s the only time it’s easy to build.

Want the harder-mode version — asking people you have no relationship with at all? Read how to ask a stranger for a referral and how to get referred at Series-B startups.

Frequently asked questions

How long does it take to build a referral pipeline?

Plan for six to twelve months of light, consistent engagement before you need anything. A relationship that's a few weeks old still reads as a cold ask. The point of starting early is that by the time a role opens, the person already knows your work and can vouch for you honestly.

How many people should I keep in the pipeline?

Aim for 10 to 15 active relationships across roughly 30 target companies. That's enough that a few will be at hiring companies whenever you start a search, and few enough that you can engage with each one for real instead of running a script.

What if I'm starting from zero and have no network?

Everyone starts cold. Pick ten companies you'd want to work at in two or three years, find one person at each whose public work you respect, and leave one substantive comment a week across the list. The relationships emerge from genuine engagement, not from a head start.

How do I network without it feeling transactional?

Engage with work you actually find interesting, and don't ask for anything until you've given something first. If your last five messages to someone were all favors, it isn't a relationship. Share a relevant article, answer a question, or send a useful resource with no ask attached.

When and how do I finally ask for the referral?

When a real role opens at a company where you've built a relationship. Keep the ask short: name the role, remind them you've been in touch, and ask one specific thing, like flagging your application to the hiring manager. The months of prior context do the persuading, so the message itself can be brief.

Is it worth building a pipeline if I'm not job hunting right now?

That's the best time to build it. Most people who change jobs aren't actively searching when the opportunity finds them, and a warm relationship is what surfaces those opportunities. Building the pipeline while you're employed means you negotiate from strength, not desperation.