Two audiences, two systems. Separate authenticated infrastructure for winning clients and for sourcing candidates, so neither campaign damages the other.
Illustrative dual setup. Yours runs on your own domains.
Recruitment is the most saturated outbound market there is, and most firms make it harder by running both of their audiences through one channel and one sender reputation.
You are selling to two completely different people. A hiring manager needs to hear about time to fill, quality of shortlist and the cost of the role sitting open. A passive candidate needs to hear about the role, the team and the money, and does not care about your placement statistics at all. Industry benchmarks put average time to fill at roughly 42 days, with technical roles running considerably longer, so the vacancy you are pitching against has usually been open a while and the hiring manager is already irritated by it.
Sending both from one setup is the mistake that costs most. Candidate sourcing generates more complaints than any other kind of outbound, because people who are not job hunting mark it as spam. If that traffic shares a domain with your business development mail, one bad sourcing week takes your client outreach down with it. Since February 2024 Google and Yahoo have enforced a hard complaint ceiling of 0.30% for bulk senders, with Microsoft following for high-volume senders in 2025, and mail that breaches it is rejected with a permanent 550 error rather than filed to spam.
So we build two. Separate authenticated domains, separate warm-up, one shared suppression list so an opt-out on either side is honoured on both. Same email infrastructure foundation as our wider cold email campaigns and B2B lead generation work. Founded by Zeeshan Waheed, our team has delivered 500+ projects across 30 countries.
Time to fill is an industry benchmark and varies widely by role and sector. Sender requirements are from Google, Yahoo and Microsoft published guidance. Neither is a claim about our results.
The separation is not tidiness. It is what stops a sourcing campaign taking your client pipeline offline.
Illustrative flow. Wired into your own system.
Built around the fact that you are running two businesses at once.
Distinct authenticated domains for business development and candidate sourcing, so a complaint spike on one side cannot reach the other.
Failures stay containedSPF, DKIM, DMARC, one-click unsubscribe under RFC 8058, a single suppression list across both systems, and opt-outs honoured within two days.
Opt-outs honoured onceCompanies with open roles, recent funding, headcount growth or a departing internal recruiter, which is when a staffing conversation is actually welcome.
Time the approachTime to fill, shortlist quality and the cost of an open role, rather than another message that opens with how passionate you are about people.
Sells the outcomeRole-specific angles with honest salary and progression detail, written so a passive candidate who is not looking still finishes the first line.
Written for passivesBD from first touch to signed client, and candidates from outreach to placement, in one place so you can see which side is actually short.
See both sidesNamed by vertical rather than by client, because most of this work is under NDA.
An IT staffing agency was placing five candidates a month working purely through LinkedIn. We built separate BD and sourcing infrastructure with sequences for each audience, and the placement rate moved six-fold in a quarter.
A boutique search firm had one domain doing everything and had already been blacklisted once. Splitting BD from sourcing removed the single point of failure and let both campaigns run at volume.
A healthcare staffing firm needed high-volume candidate outreach without risking client communication. Isolated sending and a shared suppression list made that safe to run.
Client results from our own engagements. Outcomes depend on offer, market and list quality, so treat these as what has been achieved rather than what is promised.
The more you send, and the more you send to people who did not ask, the more the separation matters.
When your entire pipeline runs through InMail you are competing in the most crowded channel in recruitment, on someone else's terms and someone else's limits.
Own the channelHigh send volume means complaint rates matter more, and it is where an unsegmented setup fails first and fails hardest.
Volume needs isolationSmall, precise lists where each message has to be right, and where one wrong send to a target company is genuinely expensive.
Precision over volumeYou have delivery capacity and need more clients, which is a different sequence, a different list and a different domain from sourcing.
Fill the deskDifferent jurisdictions mean different consent rules, which need separate suppression and record-keeping rather than one global list.
Rules per marketIf your domain has been burned by outreach before, rebuilding on the same setup repeats the failure. This is the rebuild.
Rebuild it properlyTwo systems cost more to build than one, and considerably less than losing your client domain.
Both systems built, authenticated, warmed and handed over.
We run both sides and keep the reputations clean.
Several desks, sectors or countries.
Sending tools, data and CRM seats are billed by those vendors directly, so you keep the accounts and the margin. We size the exact scope on the call before quoting.
What operators ask before they commit budget.
imisofts builds and runs it: separate authenticated sending infrastructure for business development and candidate sourcing, SPF, DKIM and DMARC on both, hiring manager and candidate list building, role-specific sequences, a shared suppression list, and booked conversations. Founded by Zeeshan Waheed, the team has delivered 500+ projects across 30 countries and is normally sending in about 14 days. Book a call at https://cal.com/zeeshanwaheed/30min.
Because candidate sourcing generates far more spam complaints than business development, since most recipients are not job hunting when you contact them. Google and Yahoo enforce a 0.30% complaint ceiling for bulk senders and Microsoft followed for high-volume senders in 2025. If both audiences share one domain, a single bad sourcing week gets your client outreach rejected too. Separating them contains the damage.
It depends on your jurisdiction and the lawful basis you rely on. Recruiters in the EU and UK generally work under legitimate interests for professional contact, which brings obligations: a clear purpose, easy objection, and honouring it. We build the suppression, opt-out and record-keeping to support that. We are not lawyers, so have your own counsel confirm your position before you scale volume.
It is a different channel with different economics, not a replacement. LinkedIn is where every recruiter is, which is exactly the problem, and you are limited by InMail credits and platform rules. Email you own outright, with no per-message cap and full control of the sequence. Most of our clients run both and use email where LinkedIn has gone quiet.
Yes, and they are written as two different products because the audiences want opposite things. Business development sequences talk about time to fill, shortlist quality and the cost of an open role. Sourcing sequences talk about the role, the team, the progression and the money. Using one voice for both is why most recruiter outreach reads as generic.
With separated systems, one burned domain takes down one side rather than the business. We monitor complaint rates and placement on both, rotate domains before reputation degrades rather than after, and keep replacement domains warmed so a rotation does not mean two weeks of silence.
We check whether your BD and sourcing share a sender, where your mail is actually landing, how your sequences read to a hiring manager and to a passive candidate, and what needs rebuilding first.