Active sourcing for small teams: reaching out actively without a recruiting department

In the talent shortage, posting an ad and waiting no longer suffices for many roles. The best people are rarely actively job hunting - they have a job and look only when something exciting passes by. Active sourcing means approaching exactly these people actively instead of hoping they stumble across your ad. That sounds like a task for large recruiting departments, but it's doable for a small team - if you go at it focused rather than broad.

The fallacy of small teams is treating active sourcing as a volume game: send a hundred messages and hope for one reply. That doesn't work and burns your reputation. For a small team, active sourcing is a precision game: identify ten very well-matched people and approach each one personally and convincingly.

Before opening any platform, answer one question: who exactly are you looking for? Not 'a developer' but 'someone with three to five years of backend experience in our language, ideally from a similarly sized company within 50 kilometres'. The sharper the profile, the faster you find real matches and the more personally you can reach out. A vague target group leads to vague messages, and vague messages get ignored.

Derive two or three hard filters from the requirements profile to search by on the platform, and a few soft signals to watch for when reading profiles. The hard filters make the list small, the soft signals make the outreach accurate.

There's no universally best sourcing platform - it depends on the role. For many professional and leadership roles in the DACH region, the large business networks are the first stop, because people are professionally discoverable there. For very technical roles, it's often worth looking into specialist communities, repositories or forums where the target group shows its work. For trades and local roles, regional channels and referrals can deliver more than any network.

Don't underestimate referrals: the shortest path to a good person often runs through someone who already knows them. Actively ask your team whom they know for the role - a warm introduction via a mutual acquaintance beats any cold outreach.

The first message decides everything. A generic mass message ('We're looking for talent like you!') is immediately recognised as spam and deleted. A good first outreach shows in the first two sentences that you really read the profile: refer concretely to a project, an experience or a skill of the person. Briefly explain why this person and why now. And be honest that it's an outreach, not a guarantee.

Keep the message short, name the role and a real reason why it might be exciting, and make the next step small - a brief conversation, not a full application process. No one answers a first message that immediately demands a CV and cover letter. You're courting, not demanding.

The most common mistake in small-team active sourcing is that contacts get lost in a spreadsheet or the mail inbox. Whoever has actively reached out to someone should bring the contact into the pipeline immediately as a candidate - with its own source 'active sourcing' - so you can honestly see at the end of the quarter whether the effort paid off. Without clean tracking, you never know whether sourcing really brings you hires or just busywork.

In KI BMS you create a sourced candidate manually in the pipeline, record the source and run the conversation in the same tool as your incoming applications - with the same notes, scorecards and audit log. That way actively approached and incoming candidates don't blur together, and your source-quality analysis stays honest. You see in black and white what active sourcing really contributed compared with your other channels.