Skip to content
CogniYukti

Analytics

Volume is easy to buy. Hires are not.

A source that floods your pipeline and converts at two percent is costing you more than the subscription — it is costing you the recruiter hours spent dispositioning it.

Suite E

Seven cards on where the pipeline goes.

Stage-to-stage conversion, so the leak has a location rather than a feeling. Time to hire and time to fill, which are different numbers and get confused And source performance measured in hires, not applications — because applications per source flatters whichever channel is noisiest, and the noisy channel is rarely the one that fills the role.

One client · one quarterworst step marked
  • Sourced412
  • Submitted96−77%
  • Client responded44−54%
  • Interviewed31−30%
  • Offered9−71%
  • Joined7−22%
Half of what you submitted never got an answer. That is not a recruitment problem and no amount of extra sourcing fixes it.
Illustrative
  • Per role, per client, per quarter

    Aggregates that hide a single bad client are not insight.

  • Source is captured at arrival

    By every sourcing route — the careers page, email intake, the extension, a Resdex import — with the original reference stamped on the record, so nobody has to tag anything for the question to be answerable.

  • Cost per source is not in yet

    What each channel costs is not captured, so the ratio you actually want — spend against hires — is a calculation you still do outside. Cost per hire does exist on the vendor side, from fees actually billed.

Before you cut a source

Including what this cannot tell you yet.

Can you tell us our cost per hire by source?

Not yet. What each channel costs is not captured, so the spend side of that ratio is missing and we are not going to invent it. Hires per source is real; cost per hire from fees actually billed exists on the vendor side.

Why measure hires per source rather than applications?

Because applications per source flatters whichever channel is noisiest, and the noisy channel is rarely the one that fills the role. A source that floods your pipeline is costing you recruiter hours before it costs you a subscription.

Does someone have to tag where a candidate came from?

No. Source is stamped at arrival by every route — the careers page, email intake, the extension, a database import — with the original reference on the record.

Can we see the funnel for one client only?

Yes, and you should. An aggregate that hides a single unresponsive client is not insight, it is an average.

Which step usually leaks most?

In agency work, the one after you submit — the client's first response. That is not a recruitment problem and no amount of extra sourcing fixes it, which is why it is worth seeing as its own number.

Book a demo

Find the leak in a real funnel.

Bring a role that went quiet and we will show you which stage it died in.