What hidden costs come with recruiting software?

At the boundaries of the core product. Implementation and configuration are frequently quoted separately from the subscription, sometimes as a fixed onboarding package and sometimes as professional services days. Data migration from an existing system is another, particularly where historical records need field mapping or cleanup. Integrations are a third: a connection to your HRIS, payroll, background check provider or assessment tool may be included, charged per connector, or require services work. Then there are capability gates, where features such as single sign-on, custom reporting, API access or advanced permissions sit in a higher tier than the one you were quoted. None of these is dishonest, and all of them are avoidable surprises if you ask the question directly during evaluation instead of after.

Anything tied to a driver you expect to increase. If pricing is per recruiter seat, adding coordinators or agency partners raises it. If it is per employee, company growth raises it independently of hiring activity. If it is bundled by job slots or application volume, a busy quarter can trigger overage. Storage for video interviews and attachments can carry a limit. Support tiers sometimes escalate as your usage grows. Ask the vendor to state plainly which of these apply and what the rate is beyond the bundle, then model a realistic busy year rather than an average one. The useful question is not what does it cost, it is what makes it cost more, and a straightforward answer to that question is itself a signal about the vendor. Reviewing how recruiting software is priced first makes the conversation shorter.

Time, mostly. Configuration during rollout, data cleanup before migration, training sessions for recruiters and hiring managers, the productivity dip while people learn, and ongoing administration once live. There is also the cost of running two systems during transition, since a notice period on your existing contract often overlaps with the new subscription. Where an integration requires engineering work, that is internal cost even if no vendor invoices for it. None of this appears in a quote, and together it frequently exceeds the first-year licence fee for a mid-sized deployment. Estimate it during implementation planning rather than discovering it in the middle of a rollout, and put the estimate in the business case so nobody feels misled later.

Ask one direct question in writing: please list everything that is not included in this quote but that a customer of our size and profile commonly needs. Good vendors answer it usefully because it prevents a difficult conversation later. Then verify the answer through references, asking specifically what they had to pay for that they assumed was included. Finally, take the quote apart line by line and ask what each unit means and what happens when it is exceeded. Request that the answers appear in the order form rather than in an email. The pattern that should concern you is not the existence of additional charges, which is normal, but reluctance to enumerate them when asked plainly.