Skip to main content

What is Off-Platform Hire, and Why It Matters

Understand what an off-platform hire is, how it costs search firms revenue, and how Recruiterflow's automatic detection protects your fees.

Written by Amogh Balikai

Your firm did the work. You sourced the candidate, screened them, and submitted them to the client. The client rejected them. Months later, you find out the client hired that same person directly, without paying you a fee.

This is an off-platform hire. And it happens more than most search firms want to admit.

Most firms protect themselves contractually: their client agreements include a clause stating that if a client hires a candidate the firm submitted, within a defined window (typically 6 to 12 months), the client owes a fee, regardless of whether the firm was involved in the final hire.

The problem has always been enforcement. You only catch it if you happen to notice. Until now.

Off-Platform Hire detection in Recruiterflow monitors your submitted candidates and flags when someone you sourced and submitted, and who was subsequently rejected, appears to have been hired by the same client outside your process. When this happens, a tag appears directly on the relevant Job Candidate Activity (JCA) page so your team can investigate and act.

What you can do with this

  • Spot potential contract breaches early before the detection window in your agreement expires.

  • Build an evidence trail: the tag logs the event on the detected hire.

  • Protect your firm's revenue: recover fees you're contractually owed.

Did this answer your question?