Sourcing on Connecting Odds.

The mental model, before the buttons

Most sourcing tools assume the recruiter's job is to send outbound messages to strangers. That framing is what makes InMail credits the default currency of legacy platforms - the more messages you send, the more money the platform makes, and the entire product is designed to keep the message count going up. Connecting Odds is built on a different assumption. The recruiter's job is to build a network of relevant professionals and keep it warm, and messaging inside that network is the operational output of the work, not the resource that meters it. Once two members are connected, messaging is free forever.

That mental model changes every downstream decision. You are not trying to blast a thousand cold candidates a week. You are trying to add the right forty people to your network per role, keep in loose touch with the strongest hundred you have already connected with, and reach into that pool when a role opens. The tooling on Connecting Odds is designed around exactly that motion.

Step 1: Search that behaves like a recruiter's brain

Global search on Connecting Odds is a single command palette that searches people, companies, jobs and posts at once. For sourcing, the useful surface is the people tab, which supports the queries a recruiter actually runs day to day: job title, seniority, current or past company, city, country, remote availability, open-to-work status, and the free-text fields on the profile. You can compose those in plain English or with a light boolean syntax, and the results are ranked by profile completeness and recent activity so the ghost profiles fall below the active ones.

The important thing to check on your first search is that the profiles have real content. A search that returns thin profiles is not a sourcing problem, it is a data problem, and the fix is to broaden the query. Drop the exact-title match; try the two adjacent titles and the parent function. Drop the city; try the metro. Once the results look like real people, save the search and move on.

Step 2: Saved searches, because the good candidates are the returning ones

Every recruiter we watch develops the same habit within a week: they build a small set of saved searches around the roles they are actively hiring for, and they open them again every Monday. This is not a productivity trick, it is how sourcing actually works. New profiles enter the pool every day. People change titles, cities, open-to-work status, and current employer. A saved search is a standing view over the pool; a fresh run each week surfaces the people who were not there last Monday. The tool exists to keep you from re-typing the query and to sort by "new since last visit."

On Connecting Odds, saved searches ship with per-search notification settings, so you can opt into a weekly email digest for the roles you care about, or leave it silent and open the tab yourself. Most recruiters we hear from prefer the digest. It becomes their Monday reading, right after the pipeline.

Step 3: The first message, at the moment of highest leverage

When you find a candidate you want to reach, do not send the "quick intro" message. That template is what legacy platforms trained everyone to write, and every candidate reading it can smell that it is one of forty. Send a specific, three-sentence message that names the role, names the reason you thought of them, and asks one clear question. If they are open to a conversation, they will reply. If they are not, they will not, and you will not have wasted an InMail credit because there is no such thing here.

Connection-gated messaging means your first message doubles as a connection request. If the candidate accepts, you can DM freely from that point on, and the message thread lives in the same inbox as every other conversation about that role. If the candidate declines, you have your answer immediately and can move to the next name. Either outcome is faster and cheaper than the equivalent LinkedIn Recruiter cycle, and the tone of the inbox stays warm because there is no cost pressure to spam.

Step 4: Turn the reply into a call, in the same tab

The moment a candidate replies "yes, keen", the next move is a call. On Connecting Odds you have two options and neither leaves the app. If the candidate is online, click the voice or video call button in the message thread and you are on the call in one hop, no meeting ID, no dial-in, no Zoom account. If they are not, click the schedule button, drop three slots, and the platform sends a proper .ics invitation with reminders. Reschedules happen in the same interface. The whole exchange, from the first "keen" to the confirmed screen, is one thread.

The compounded value of no-hop calls is easy to miss and hard to overstate. Every context switch between tools is a place where funnel volume leaks - candidates who meant to reply and forget, invitations that get lost in a second inbox, calendar events that never make it to the recruiter's ATS. Removing those hops removes the leaks, and the net effect on a small team's pipeline is significant even if no single step feels faster.

Step 5: The pipeline, without a second ATS

Once the screen happens, you move the candidate into a pipeline stage. On Connecting Odds this is the applicant tracking system for the role, which is included in the same product as the sourcing, messaging and calls. You do not need to sync a separate tool. Stages are configurable per job, notes are attached to the candidate, and the whole team with page-admin access can see the same view. When you make the hire, the candidate archives with the offer message and the interview record intact.

For solo recruiters and five-person hiring teams, this is usually the entire product. For larger teams with a fully-configured Greenhouse or Lever pipeline, Connecting Odds is the sourcing and outreach layer and the ATS can stay where it is. Either integration pattern is fine. The important thing is that the sourcing motion does not depend on the enterprise ATS to work.

Step 6: Keep the network warm between roles

The best-paid step in sourcing is the one nobody bills for: the maintenance work you do between roles. Every two weeks, review your saved searches for interesting new profiles, connect with two or three of them without an immediate ask, and send a two-sentence message to five existing connections whose work you have been following. This is not "engagement." It is the recruiter equivalent of a chef sharpening knives on a Sunday. When your next role opens on Monday, you already have thirty warm names to consider instead of a cold blank search.

The chronological feed is genuinely useful here. Because it is not re-ranked, you see the actual updates of the professionals you have connected with - a promotion, a company move, an "open to work" toggle - in the order they happened. That signal was buried on every other network. It surfaces on this one, and it is one of the highest-value pieces of information a working recruiter can have.

The short version

Sourcing on Connecting Odds is a small set of habits: build the search, save it, message specifically, close the loop inside the same thread, and keep the network warm between roles. The product is designed to make each of those steps take one hop instead of three, and to remove the metered-messaging pressure that shapes every other sourcing tool. The result is a quieter inbox, a warmer network, and a hiring funnel that stops leaking between vendors.

Set up your recruiter workspace on Connecting Odds, or read the buyer's guide to LinkedIn Recruiter alternatives.