Skip to content

Onity_ recruitment workflow automation: what changed after switching ATS

Onity_ is a Germany-based IT recruitment firm that wanted big-agency quality with more speed, flexibility and a personal touch.

Its existing system could not keep up, so the team moved to a combined ATS + CRM. This page walks through what the firm reported changing, what each change actually fixes, and how to tell whether your own desk has the same problem.

The setup problem: one person, several roles

>Onity_ works a market where the same person can be a candidate on one search and a client on another. That single fact drives most of the requirements: a record has to hold many connections without turning into a maze, and a consultant has to see the whole relationship in one place. The team's stated needs were a system built for that model, plus automation for the routine parts of the week.

What the firm reported after the switch

>Three outcomes were reported: shorter hiring time, tidier data management, and fewer repetitive manual tasks once automation and AI were in use. The headline claim is that hiring time was cut in half. Treat that as the firm's own before-and-after figure for its own desk, not a benchmark you can assume for a different market, role mix or team size.

Search was the deciding feature

>The requirement that settled the choice was database search: Boolean and advanced search. For an IT recruiter this is the difference between a database that stores CVs and a database you can interrogate. A skill stack, a location and a seniority band can be combined in one query instead of three manual passes.

One window instead of several tools

>The team wanted ATS and CRM functions together rather than stitched across separate products. Email sequences, task management and reporting sat in the same place as candidate and client records. In the firm's account, the practical benefit was having everything in one window, and the transition felt natural rather than like learning a brand-new system. Those are the firm's reported impressions of its own rollout; they are not a promise that any other team's migration will be equally smooth, and any support or partnership framing belongs to the original publisher's own account.

Three fixes, and what each one actually solves

>Use this to separate the problems. They look similar from the outside and need different remedies.

  • Incomplete records. The old process was heavy enough that consultants left fields blank or filled them later, so the database drifted out of date. The remedy is structural: make the record the only place the update can live, with required fields and automation that writes the change at the moment it happens. If your records are complete but scattered across tools, this is not your problem.
  • Slow data entry. Consultants avoided the CRM and asked for admin help. The fix is interface design and defaults, not more rules. If your team enters data but takes too long, look here first.
  • Repeated outbound work. Status updates, client updates and compliance notices were retyped each time. The fix is a trigger-based sequence. If your team is fast at data entry but still writes the same email weekly, this is the gap.

A team can have all three at once, which is why the firm's results arrived together rather than one at a time.

Where automation and AI sat in the workflow

>Workflow automations handled recurring and multi-step tasks, including GDPR-related updates and keeping clients informed. Integrations let the team shape the dashboard and data fields around its own process rather than the reverse. On the AI side, the features the team singled out were the job description generator and smart candidate matching, both of which arrived quickly after rollout.

A worked example of one automation step

>Take a GDPR notice that has to reach a client whenever a candidate record changes status. Manually, that is: notice the change, open the client record, find the right contact, write the message, log that it was sent. As an automation it becomes: a status-change trigger, a condition that the client is subscribed to compliance updates, a templated message, and an automatic log entry on the record. The saving is not the writing time; it is the remembering. The same shape works for interview scheduling confirmations and for placement-stage client updates.

Checklist before you copy this switch

>- Can one record hold both a candidate and a client relationship without duplicate entries?

  • Does your database support Boolean and advanced search across custom fields, not just name and title?
  • Which three recurring messages could become triggers this month?
  • Who owns data completeness, and is it enforced by required fields or by habit?
  • Will migration preserve history and attachments, and who verifies the record count afterwards?
  • Which AI features will you actually use in week one, and which are nice-to-have?
  • How will you measure hiring time before and after, on the same role types?

What this case does not tell you

>The reported halving of hiring time has no published baseline, sample size or measurement method, so it cannot be used to predict your own result. The firm's satisfaction rating is its own view. Feature availability, integrations and AI capabilities change over time; check the current product documentation for what is live today rather than relying on this account.

Frequently asked questions

What did Onity_ actually change?

It replaced an outdated recruitment system with a combined ATS + CRM, then added workflow automations and AI features including a job description generator and smart candidate matching. The reported results were shorter hiring time, better organized data and fewer repetitive tasks.

Does 'cutting hiring time in half' mean I will get the same result?

No. That figure is the firm's own before-and-after comparison for its own desk. It has no published baseline or method, so it should be read as a reported outcome, not a forecast for a different team, market or role mix.

Why did Boolean search matter so much?

The firm named Boolean and advanced database search as the feature that decided the purchase. For IT recruitment, being able to combine skills, location and seniority in one query replaces several manual passes over the same database.

Is a combined ATS + CRM necessary, or can two tools work?

Two tools can work, but the firm's requirement was one window for candidate and client records, email sequences, tasks and reporting. The trade-off is integration effort and duplicate records versus a single system's constraints on customization.

What is the risk when migrating?

The main risks are incomplete history, broken attachments and records that lose their link to the other side of a relationship. Plan a verification pass after migration: compare record counts, spot-check a sample of candidate-client pairs, and confirm that automations fire on the migrated data.