Choosing an ATS often feels like an obvious decision: "we need one."

In practice, many companies buy an ATS to solve an organization problem and end up adding another tool to a messy system. Or worse: they pay for years for features they don't use.

A good ATS can organize, accelerate, and create visibility. One chosen poorly just formalizes the chaos.

That's why, before comparing tools, you have to start with the uncomfortable part:

1) First: do you actually need an ATS?

This isn't a philosophical question. It's a business question.

Three variables help you decide:

  • Company size: managing 10 reqs a year isn't the same as 200.
  • Projected volume (12–24 months): the decision isn't justified by today's volume, but by what you'll handle soon.
  • Expected ROI: an ATS should improve (at least) one of these dimensions: speed, quality, cost, traceability, or experience.

If you can't explain what concrete improvement you expect, the ATS will most likely become an expensive repository.

2) How to justify budget (when it does make sense)

If you already suspect you need an ATS, these reasons usually help unlock budget:

Candidate database ownership

Building your own database reduces dependence on third parties: LinkedIn, agencies, external databases. The company stops "starting from zero" on every req.

Careers site + inbound generation

A good careers site, plus email marketing and a minimal content strategy, can increase applications and lower cost per hire.

Process automation

For both Talent and Hiring Managers. Even the most basic ATS includes automations: reminders, templates, statuses, tasks. More advanced ones add deeper functionality, including async interviews and AI agents.

3) You're in a good moment: "legacy + AI" vs "AI native"

Today the market offers two major paths:

  • Traditional ATS platforms incorporating AI.
  • AI-native solutions with more modern architecture and AI features better integrated from the design up.

The first usually bring robustness, coverage, and operational maturity. The second usually bring better experience, faster innovation, and better fit with new workflows.

Neither is "better" by definition. It depends on context.

And that context comes down to one question:

4) The question that defines everything: what's your budget?

This isn't just about cost. It's about strategy.

Because the set of features worth prioritizing changes depending on how you recruit:

  • Are you more inbound or outbound (cold sourcing)?
  • Do you have a candidate database to import?
  • Are you hiring volume or hard-to-fill profiles?
  • Is your biggest spend today LinkedIn Recruiter?
  • Is your bottleneck screening, interviews, coordination, or decision?

Useful data point: LinkedIn Recruiter isn't an ATS, but it does cover two decisive aspects: candidate database + sourcing capability, at a high cost. In many organizations, the stack ends up revolving around LinkedIn and the ATS is used only to "track."

That can be avoided, but first you have to see it.

5) Feature ≠ value (quick example)

A feature can be incredible in one context and counterproductive in another.

Example: AI Interviewer

  • For high-volume or mid-level profiles, it can save time and standardize screening.
  • For a highly in-demand senior role that isn't actively looking, an interview with an agent can increase friction and lower conversion. There, human touch and a well-run process usually matter more.
The tool isn't the system. It's a component.

6) Feature checklist to evaluate (with judgment)

There's no universal list, but these variables often define the success or failure of an implementation:

AI Interviewer

Useful for volume. Evaluate friction for senior profiles.

AI Matching

Everyone wants it to work perfectly. It's still evolving. If this feature is key for you, test it before buying:

  • Upload 50–100 real (or anonymized) profiles from complex roles.
  • Compare ranking vs. human judgment.

I've run this test with a widely used tool and it couldn't reliably distinguish a BI Analyst from a Data Scientist. If matching fails at the basics, don't discover that after you've bought it.

Chrome extension to import profiles from LinkedIn

Saves real time. For outbound teams, it's usually indispensable.

Email marketing

Not just to "send emails." To reactivate your database, nurture candidates, and improve conversion.

Careers site

More important than it seems: how flexible is customization? Does it integrate with your brand? Does it convert?

Pro tip: if it has LinkedIn "Basic Jobs" integration, jobs from this portal get republished on LinkedIn, generating a very high volume of applicants. LinkedIn cancels this functionality if your company is in staffing.

Database ownership

Can you export candidates? Or are you locked in? This defines your ability to migrate or combine tools in the future.

Internal talent "marketplace"

Some platforms sell access to candidate databases. It can help, but understand quality, segmentation, and limitations clearly.

Integrations

Calendar, email, Slack/Teams, assessments, background checks, HRIS. Every missing manual integration becomes friction. You need to account for your tool stack and map where your main stakeholders will interact.

Support

Do they support you in your language? Is your English level sufficient? Especially during onboarding and initial customization, support defines success.

Analytics

What metrics do you want to track? Does the ATS offer them natively, or will you depend on BI? Does it allow clear definitions by source, stage, and time?

7) A final note

These are some aspects. There are many more: permissions, compliance, multi-country, workflows by unit, referral modules, etc.

The choice is never "final." It's a combination of: context + budget + strategy + adoption capacity.

The most practical recommendation I can leave you is this:

Don't buy an ATS to "have an ATS." Buy it to solve a concrete part of the system. And measure that improvement from day 1.