Choosing an ATS for a small team: what matters

Start from your week, not a feature list

Every comparison of an ATS for a small business or a small team is organized the same way, as a grid of features with ticks in it, and the grid is close to useless. Enterprise systems tick everything. They tick everything because they were built for a company with a recruiting operations team, and the ticks describe capabilities that require someone to configure and maintain them. For a small team of two to ten recruiters, most of the ticked boxes are work you will not do.

A better method takes an afternoon. Write down what your last three hires actually cost you in hours, step by step, honestly. Posting the job. Reading applications. Typing candidate details into somewhere. Getting availability. Rescheduling. Chasing a hiring manager for feedback. Writing rejections.

Almost every small team that does this finds the same shape: reading and typing near the top, and scheduling somewhere close to the top or at it. One measure of how much of that is administrative rather than judgment comes from candidate.fyi, which puts admin-related scheduling at 46% of coordinator time. Whatever your own split turns out to be, the point of the exercise is that it gives you three or four questions with weights, instead of a grid where everything counts the same.

The seven questions below are the ones that separate tools for small teams from tools that merely have a small plan.

Q1. Does scheduling live inside it?

Ask for a demo of the exact moment a candidate goes from "we would like to meet you" to a confirmed time in a calendar. Watch what happens on screen.

Most systems, at that moment, hand you back to email. You leave the tool, write an availability request, wait a day, cross-reference the reply against your calendar in another tab, and come back. The system stored the candidate beautifully and did nothing about the expensive part.

What you want instead is that the candidate gets a link, sees only slots that are genuinely free, picks one, and the interview appears in your calendar with a video link on it, without them creating an account. If that whole sequence happens without you leaving the tool, the tool is doing the work. If any part of it involves you typing times into an email, it is not.

Q2. Does it read the CV for you?

The second largest cost in a small team's week is turning documents into records. A CV arrives as a PDF, and someone types the name, the email, the current title and the company into a form.

A system worth paying for reads the PDF and fills that in: contact details, links to a LinkedIn or GitHub profile, the current title and company, a skills list, and a summary a recruiter can read in ten seconds before a call. Ask to see it run on a messy CV, not the demo one, ideally on a real file from your own pipeline.

Then ask the more important question: what does it do when a recruiter has already typed something. The correct answer is that it fills blanks and never overwrites a human entry, which is how Bestpeople handles it. A system that silently replaces the title you learned in a phone call with whatever the PDF said is creating work rather than removing it, and you will only discover it after you have stopped checking.

Q3. Where do applications come from?

An empty ATS is a filing cabinet. Ask how candidates get into it in the first place.

The honest answer for most small companies is three routes: a careers page, direct sourcing, and forwarded referrals. Of those, the careers page is the one a tool can genuinely solve for you, and the one most small companies never build because the person who would build it is busy shipping the product. The three structures that work at this size are set out in careers page examples.

So ask whether a careers page is included and whether applications from it land in the pipeline with the CV already read, or whether it emails you and you upload the attachment yourself. Bestpeople includes one at bestpeople.ai/careers/your-company, generated from your website, description and logo, with applications landing in the talent pool enriched. Whatever the vendor, the test is the same: does the page feed the system, or does it feed your inbox.

Q4. How many jobs, how many recruiters, and what does that cost?

Pricing is where tools built for large companies reveal themselves. Two patterns cost small teams the most.

The first is per-seat billing. It sounds fair and it produces a bad outcome: a five-person team decides that only two of them need logins, so the other three work from forwarded emails, and the shared pipeline that was the point of buying the system quietly stops being shared.

The second is a plan whose limit is the number of active jobs. This one is legitimate, because it is the dimension that actually tracks the size of the problem, but you have to check the number against your real pipeline. Count how many roles you have open simultaneously in a busy month, not on average.

For reference, Bestpeople is one plan at 100 euros a month, or 80 euros a month billed yearly, which is 960 euros a year. It covers five jobs and unlimited recruiters, with no setup fee and no contract, and there is a fourteen-day trial that does not ask for a card. Compare that shape to whatever else you are looking at: what does adding a colleague cost, and what happens when you open a sixth role.

The three questions people forget

These come up after the purchase rather than before it, which is why they belong on the list.

Can candidates use it without an account?

Every account you require a candidate to create is a step where some of them stop. Ask specifically what a candidate has to do in order to apply, to book an interview, and to move one. The answer should be nothing beyond opening a link. A password reset email sent to a candidate who is trying to reschedule with you is a self-inflicted no-show.

Google Calendar and Meet: native or bolted on?

There is a real difference between a system that reads your actual calendar to decide what is free and one that keeps its own schedule and pushes events into your calendar afterwards. The second kind will offer a candidate a slot you are already busy in, and you will find out when they book it.

Ask how many sign-ins the setup takes, and whether the calendar check and the video room are independent. In Bestpeople, one Google sign-in gives both, and either works without the other, so you can sync the calendar and still run phone interviews. Ask what happens when a colleague books over an interview slot after the link has been sent.

Can you leave?

Ask every vendor, including the ones you like: if we stop paying in two years, what do we get out, in what format, and how long does it take. Candidate records, CVs, notes and stage history are your data about your applicants, and you may have legal obligations about them that outlast the subscription.

Ask for the format and the deadline in writing before you sign: candidate records as a spreadsheet plus the original CV files, delivered within a few business days. If the answer is a support ticket rather than a button, price that in.

What only matters at 500 hires a year

A few things dominate enterprise comparisons and should not affect your decision at all right now.

Deep approval workflows, requisition routing and multi-level permission schemes exist because a large company has to control who can open a job. In a team of five, the control is that you all talk to each other.

Interview scorecards and structured evaluation frameworks are genuinely good practice at volume, where you need consistency across dozens of interviewers you cannot supervise. At your size they mostly generate forms nobody fills in.

Diversity dashboards, sourcing analytics and CRM-style nurture campaigns all need a volume of candidates you do not have yet, and until you do they display noise.

None of these are bad ideas. They are answers to problems created by scale, and buying them early means paying for configuration work in exchange for nothing. Buy for the week you have.

Two small things do matter more than their size suggests, because you will do them constantly: how fast you can move a candidate between stages, and how fast you can send a decision. Keep a rejection email after interview template to hand, and check in the demo that sending one takes seconds rather than a page of clicks.