Is there an ATS for companies that only hire occasionally?
Yes. Occasional hirers should pick usage-based pricing or a cheap warm tier, minutes-not-weeks setup, and GDPR tooling that runs between hiring rounds.
On this page
Yes. Teams that hire in bursts should look for usage-based pricing or a cheap flat tier they can keep warm, setup measured in minutes rather than weeks, and GDPR tooling that looks after candidate data through the quiet months. What does not fit is the industry default: an annual per-seat contract sized for continuous hiring. The right system costs little while idle and is ready the morning a resignation letter lands.
Why does occasional hiring break normal ATS pricing?
Most ATS pricing assumes recruiting is a year-round activity. Per-seat subscriptions charge twelve months a year whether you filled two roles or twenty, and annual contracts lock that in before you know what the year holds. A company that hires three or four times a year might use the system intensively for eight or ten weeks in total. On a standard contract, that means paying for roughly ten idle months to cover two busy ones.
That mismatch is why many occasional hirers never buy at all and run hiring from inboxes and spreadsheets, then rediscover mid-vacancy why that hurts: lost candidates, no overview, and a GDPR posture held together by good intentions.
The root problem is the billing unit. Seats measure how many people have logins, not how much hiring happens. Enterprise suites like Greenhouse or Lever are openly built for the continuous case: quote-based pricing, annual terms, onboarding projects. None of that is wrong, it is simply sized for a different customer than a team with one vacancy per quarter.
Which pricing models fit burst hiring?
Four models match cost to bursts better than annual per-seat does:
| Model | How you pay | Fit for occasional hiring |
|---|---|---|
| Usage-based | Per unit of work: candidates processed, credits, actions | Strong. Cost follows the burst, idle months cost little |
| Per active job or period | Only while a vacancy or month is live | Good, if reactivation is instant and data survives the pause |
| Free floor with paid bursts | A free tier carries the quiet state; you pay when busy | Viable in theory; check what the caps exclude |
| Low flat tier | A cheap monthly plan kept warm year-round | Good when it sits below your “not worth thinking about” line |
Per-job pricing deserves a caveat. Tools like Recruitee price by job slots, which looks tailor-made for a team with one role at a time, but a burst of three simultaneous vacancies triples the bill at your busiest moment. Free floors carry the mirror risk: the caps often exclude exactly the automation, multiposting and compliance tooling you need mid-burst. The full arithmetic on these mechanics is in usage-based pricing vs per-seat ATS.
Recruitifly’s answer to the burst problem is a low flat tier plus metered work. The Freelancer tier costs EUR 70 per month (EUR 58 billed annually) for one seat, unlimited jobs, and 150 Actions of automated work, an Action being one task like parsing a CV or having the Fly assistant draft outreach that you approve. When a burst outruns the allowance, packs cost EUR 30 for 250 Actions and never expire, so capacity bought for this round is still there next spring. Current numbers are always on the pricing page.
Is it worth keeping an ATS between hiring rounds?
Cancelling everything between rounds feels thrifty, but a warm system keeps earning in three quiet ways.
- The talent pool compounds. The strong runner-up from your last round is the cheapest, fastest candidate for your next one, provided you kept their data with consent. Teams that delete everything start every vacancy from zero.
- Compliance does not pause. Retention windows expire and deletion requests arrive whether or not you are hiring. A system that enforces retention rules automatically is most valuable in exactly the months nobody is logged in.
- History stays searchable. Who applied before, what you offered, why a candidate declined: that institutional memory survives manager changes and saves the next hiring manager from repeating last year’s mistakes.
The alternative, cancelling and exporting everything to spreadsheets, quietly converts an organized GDPR posture into an unmanaged one. Personal data in a forgotten xlsx has no retention clock, no access control, and no deletion workflow.
How do you stay GDPR-clean between hiring rounds?
Under GDPR you may keep candidate data only with a legal basis and a defined retention period, and quiet months are where sloppy habits get expensive. A practical between-rounds routine:
- Close out the round. Delete or anonymize rejected candidates you have no basis to keep. Dutch guidance, for example, expects application data gone within weeks of a process ending unless the candidate agreed to longer.
- Ask for talent-pool consent explicitly. “May we keep your details for future roles?” is a separate question from the application itself, and the answer needs a timestamp.
- Let retention rules run. Set the windows once and let the system delete on schedule, rather than relying on someone remembering in a month when nobody opens the tool.
- Stay reachable for rights requests. Access and deletion requests are still due within a month, even if your last hire was in March.
How long each category of data may be kept, and the consent mechanics behind it, are covered in how long to keep CVs and candidate data.
Why setup speed should decide your shortlist
Occasional hiring rarely starts on a planned date. It starts when a resignation letter lands or a new contract is signed, and the vacancy needed to be live yesterday. That makes time-to-live a harder requirement than any feature on the comparison sheet: a six-week implementation project is useless to you.
Fast, in practice, means self-serve signup with no implementation fee, CV import without a consultant, posting to job boards on day one, and a trial you can run on the live role you actually need to fill. Recruitifly is built to that spec: a 7-day trial, no setup fee, one-click posting to hundreds of boards, and the Fly assistant proposing the routine work from the first morning, with every change confirmed by you.
Whatever you choose, run the one test that matters: from creating an account, how many hours until your real vacancy is live and the first CV is parsed? If the answer is measured in days, that tool is sized for someone else’s hiring rhythm.
Recruitifly is in private beta at the moment. If your team hires a few times a year and resents paying like it hires every week, talk to us and bring your last hiring round: we will work out what it would have cost, idle months included.
Frequently asked questions
Can I pause my ATS subscription when not hiring?
Some vendors let you pause or drop to a cheap storage tier; most annual contracts do not. Ask three questions before signing: can you downgrade between rounds, what happens to candidate data while paused, and is reactivation instant. Monthly billing makes all of this easier. Remember that GDPR obligations, like honouring deletion requests on time, continue while the subscription is paused.
What is a pay-as-you-go ATS?
A system where the bill follows usage instead of seats or calendar time: you pay per candidate processed, per active job, or per unit of automated work. Recruitifly uses a low flat tier plus metered Actions, and extra packs (EUR 30 for 250) never expire, so capacity bought in one burst is still there for the next. Pure pay-per-job models exist too, but a multi-role burst can spike them.
Should I delete candidate data between hiring rounds?
Delete or anonymize what you have no legal basis to keep, and keep the rest deliberately. Rejected candidates who never agreed to stay on file should be removed within your stated retention window; Dutch guidance expects weeks, not years. Candidates who explicitly opted into your talent pool can stay for a defined period. An ATS with retention automation turns this from a chore into a policy.
How fast can I restart hiring after a break?
With a warm system, the same day: reopen a job, repost it, and start from your talent pool instead of a blank page. If you cancelled and exported everything to spreadsheets, expect days of re-importing and consent checking before you can responsibly contact anyone. That difference, repeated every future round, is the strongest argument for a cheap warm tier over full cancellation.
Recruitifly Editorial
Editorial
Related reading
Adding LLM screening to your ATS without creating duplicate records
Layer LLM screening over your ATS without splitting your candidate data: one source of truth, stable ID sync, scores written back as fields, not copies.
Sourcing with adjacent job titles and skills
Searching one job title misses most of the market. A worked SRE example plus a repeatable method for mapping adjacent titles and skills for any role.
AI Act candidate disclosure: notice template
What to tell applicants when automated screening is used, under the EU AI Act and GDPR Articles 13, 14 and 22, plus a copy-paste disclosure notice template.
Want to see how this looks on your own data?
No hard promises. Just a straight conversation about exports, stages, and your current stack.
Contact us