Why we built Rafaelo as a layer first, and an ATS second
Asking a team to replace their ATS is asking them to change how they work. We chose the harder path instead.
The first version of Rafaelo was a full applicant tracking system. Candidates, stages, pipelines, reports. It was complete, and almost nobody switched to it. The reason was obvious in hindsight: an ATS is the system of record for hiring, and replacing a system of record is a project, not a purchase.
The layer insight
Recruiters did not dislike their ATS. They disliked the work around it: writing the post, publishing it in six places, chasing calendars, retyping notes. That work lives in browser tabs, spreadsheets and inboxes, not inside the ATS. So we moved the agent there, and made the ATS the place where results are written back.
- Two-way sync: jobs, candidates, stages and notes stay identical in both systems
- No migration: your ATS stays the source of truth
- One day to value: connect, add calendars, pick your brand voice
Then the ATS came back
Something unexpected happened. Teams who started with the layer kept asking: if the agent already does most of the work, why do I still pay for a separate system? A year later, a growing share of customers move to Rafaelo ATS, because the data is already clean, structured and theirs.
Start as a layer, finish as the system. That is the order that respects how teams actually change.
It is also the order that makes the product better. A layer has to be excellent at integration. An ATS has to be excellent at structure. Building both, in that sequence, forced us to be good at each.