Why we didn't bundle payroll into an ATS
The easiest way to raise the average deal size is to sell one more module. It's also how a small team ends up paying for four tools to get the one they wanted.
A common pattern in HR software: a company starts as an ATS, then adds payroll, then time-off tracking, then performance reviews, until "applicant tracking" is one tab in a much bigger, much more expensive product. For a company that actually needs all of that, the bundle is convenient. For a company that just needs to track candidates for a role or two, it's a tax.
The math that gets skipped
When hiring is bundled into a broader HR suite, the pricing is usually built around the whole suite, not the hiring module alone. A team that only wants an ATS ends up either paying for modules it doesn't use, or getting a hiring feature set that's noticeably thinner than a dedicated tool, because it was never the product's main focus.
It also means switching later is harder. Untangling your candidate data from a system that also holds your payroll records is a bigger project than exporting a spreadsheet.
What "hiring only" actually buys you
- A price that reflects what you're actually using, not a suite average.
- A product roadmap that's entirely about hiring, not split across four departments' feature requests.
- An easier exit if you ever do need a bigger HR system — your candidate data isn't entangled with anything else.
If you already run payroll and benefits through another system, hiring being its own thing isn't a gap — it's the point. Plug it in next to what you already use instead of replacing it.