Join the waitlist
← Blog · August 25, 2026 · 6 min read

Why You Shouldn't Pay to Store Your Candidates

ATS pricing has a dirty assumption baked in: that you hire all the time. Most companies don't. So they cancel the subscription between hires — and throw away their most valuable recruiting asset every time they do.

The occasional-hirer's dilemma

If you run a small or mid-sized company, your hiring probably looks like this: an intense burst — two or three roles, dozens of conversations, hundreds of applicants — then months of nothing. Maybe a year of nothing.

Now look at how applicant tracking systems charge: per month, per seat, whether you're hiring or not. Faced with paying every month for software you'll seriously use six weeks a year, you do the rational thing:

All three paths destroy the same thing: your talent pool's memory.

Your past candidates are your cheapest pipeline

The people you interviewed last year are the warmest leads you will ever have. You've already screened them. You know their salary expectations, their notice periods, what they're good at, why the timing didn't work. Industry benchmarks consistently put cost-per-hire in the thousands of euros — and the single biggest driver is starting cold every time.

A candidate who was "great, but we went with someone else" in 2024 is often exactly who you need in 2026. But that only works if:

That requires the database to survive the gaps between hiring. Which requires storage between hiring to cost you nothing — because otherwise, you'll cancel, and it won't.

Why "free database" actually makes sense (for the vendor too)

This isn't charity economics. A resting candidate database is genuinely cheap to operate: storage costs approach zero, and a company that isn't hiring generates almost no compute load. The expensive parts of an ATS are the active-hiring features — sourcing campaigns, AI screening, pipeline automation, integrations pushing thousands of events.

So the honest pricing model matches cost to value: keeping your data should be free; actively hiring is what you pay for. The vendor wins because when you do start hiring, upgrading is one click — your data is already there, structured and current. No migration project, no re-import, no "we'll get back to the new ATS after this hire" (you won't).

What a free tier must include to be useful

A free tier that's just a locked read-only archive misses the point. Between hiring pushes, real things still happen:

So the baseline is: full database, working inbox, search, add candidates — free, indefinitely. Campaigns, pipelines, screening automation: paid, when you're actually hiring.

The compounding effect

Here's what changes when storage is free and permanent: your database stops resetting to zero. Every hiring push adds a layer — more candidates, more context, more conversations. Two years in, you're not starting searches from job boards; you're starting from a few hundred people who already know your company. Add an AI agent that can actually work that pool — re-ranking it against a new role, drafting re-engagement messages, flagging who's likely open to a move — and the asset works for you continuously, even while you sleep between hires.

Companies that keep their recruiting memory compound. Companies that reset every time pay full price — in money and in weeks-to-hire — for every single hire, forever.

This is the model ATSBrain is built on

ATSBrain's free tier is exactly the baseline described above: your full candidate database, conversation history, inbox and search — free while you're not hiring, for agencies and companies alike. Paid tiers switch on when hiring does. It's the product one of us wished existed while hiring only occasionally — so we're building it.

Stop renting your own candidate database

Join the waitlist and get founding-user pricing when ATSBrain launches.

Join the waitlist