What ATS Do You Need for a 20, 50 or 100-Person Team?

The question “what ATS do I need?” has a different answer depending on where you are. A 20-person company with 8 annual hires needs something very different from a 100-person company managing 50+ hires across 6 departments. The wrong match in either direction is costly: underbuying means you hit the ceiling again in six months; overbuying means you are paying for enterprise features your team will never use and maintaining a system that requires more administration than it saves. This guide gives you an honest breakdown by stage — including where each tier ends and what the next one actually requires.

Teams of 1–20 People: Do You Need an ATS at All?

The honest answer at this size is: it depends, and a vendor who tells you otherwise is selling you something.

At 1–10 employees making fewer than 8 hires per year with a single decision-maker, a well-structured spreadsheet handles the territory. The coordination overhead of hiring at this scale is low enough that a general-purpose tool genuinely does the job. There is no meaningful ROI on ATS infrastructure when one person is managing two roles at a time and making all decisions independently. Spending time and money on a platform you do not need yet is not a sign of good planning — it is over-engineering a solved problem.

The threshold at 10–20 employees is determined by two factors: concurrent roles and collaboration. If you regularly have three or more open roles running simultaneously, or if more than one person is giving structured feedback on candidates, you have crossed the line where spreadsheet coordination starts to create real errors. The specific failure modes are predictable: follow-ups fall through the gaps, feedback arrives in separate inboxes and never gets properly compared, and the hiring manager’s version of the pipeline diverges from the recruiter’s version.

The ATS you need at this size is deliberately simple. What matters: a visual pipeline with five or six stages, multi-board job posting so you are not logging into each platform separately, basic collaboration for two to four users with shared candidate visibility, and email templates for the most common communication points. What you do not need yet: enterprise governance, approval hierarchies, workforce analytics, or a dedicated IT person to run it. If a demo introduces any of those things as selling points, that is an enterprise product mis-sold to an SMB.

Teams of 20–50 People: The Core ATS Stage

This is the size range where an ATS delivers its most obvious ROI. The transition is usually gradual rather than sudden — a company that has been growing notices, around 20–25 employees, that hiring has become a coordination problem rather than just an execution problem. Multiple departments are hiring simultaneously. Each role has a different hiring manager, different interview panel, and different requirements. The same candidate may be right for two different roles. Nobody has a complete picture of what is happening across the full pipeline.

The features that matter at this stage:

• Kanban pipeline with full team visibility: Every stakeholder can see every candidate’s status across every open role in real time, without asking anyone. This is the core fix for the coordination problem.
• Structured scorecards: Each interviewer records numerical ratings and notes immediately after the interview, before discussing the candidate with anyone else. At this size, you are dealing with multiple hiring managers who each have strong opinions. Without a structured collection mechanism, the hiring decision reflects whoever spoke last rather than the collective informed view of the interview panel.
• Calendar integration: Scheduling an interview should not require a separate email thread for every candidate. Native Google Calendar or Outlook integration that shows interviewers’ availability and books directly eliminates the back-and-forth that adds days to your time-to-hire.
• Multi-job-board posting: One form, one click, all your boards. Applications from all sources arrive in a single inbox. Source tracking shows you which boards are actually producing hires, not just applications.
• Candidate communication templates: Consistent, professional communication at every stage. Acknowledgement of application, invitation to interview, next steps after each round, and rejection notice — all templated, all sent without requiring someone to draft from scratch each time.

The HR module starts to make genuine sense at 30+ employees. Below 30, most HR functions are handled person-to-person and the overhead of implementing structured tooling often exceeds the coordination problems it solves. At 30–50 employees, leave management and onboarding become real administrative burdens: tracking who is on leave across a team of 35 people in a shared spreadsheet introduces errors that have operational consequences, and onboarding a new hire without a structured checklist means the experience varies significantly depending on who is managing it that week.

Teams of 50–100 People: Platform, Not Just Pipeline

At 50 employees, an ATS alone stops being enough. The hiring pipeline is still critical, but the HR operations around it have grown to the point where a standalone ATS creates a significant integration problem: a candidate who gets hired has to be re-entered manually into your HR system. Leave requests arrive by email and are tracked in a spreadsheet by someone who also has seventeen other things to do. Performance reviews happen inconsistently because there is no system to surface when they are due and no structured format to collect feedback.

The features that become genuinely necessary at this stage:

• Reporting and analytics: Time-to-hire per role and per department, pipeline conversion rates by stage, source-of-hire ROI so you know which channels to invest in. At 50 employees, your leadership team will start asking for hiring data. If your answer is “let me compile that from several spreadsheets,” that is a gap in your operational infrastructure.
• Performance review workflows: A structured, recurring process for 360° or manager-led reviews. Without tooling, reviews happen when someone remembers to schedule them — which means they happen inconsistently across departments and become a source of employee dissatisfaction rather than a development mechanism.
• Leave management with proper balance tracking: Request submission, manager approval, balance calculation, and integration with payroll or HR records. At 50+ employees, manual leave tracking creates payroll errors and compliance exposure.
• Onboarding checklists: New hire experiences that are consistent regardless of who is running the onboarding. IT access, equipment requests, policy acknowledgements, first-week check-ins — all tracked against a standard template so nothing falls through the gaps.
• GDPR compliance documentation: Candidate data consent, data retention policies, and the ability to action deletion requests. At this size, compliance is an operational requirement rather than a box-ticking exercise.

The unified platform advantage is most visible at this stage. A candidate who accepts an offer should flow directly into the HR module without anyone re-entering their name, contact details, start date, and role. The hiring record becomes the employee record. Onboarding tasks are triggered automatically. This transition — from candidate to employee — is where the data re-entry cost of running separate ATS and HR systems becomes measurable.

Teams of 100–200 People: Reporting Becomes Critical

At 100 employees, the thing that breaks without tooling is visibility. No single person has a complete picture of the hiring situation across the organisation. Different departments are at different stages of their annual hiring plans. Some roles have been open for three months; others are newly approved. Leadership wants to know where the company stands against its headcount plan, and the answer requires aggregating data from multiple sources that are maintained by different people.

The capabilities that become essential at this size go beyond the pipeline itself:

• Real-time analytics dashboards: Live visibility into where each department’s pipeline stands, open role count, time-to-fill trends, and hiring pace against plan. This is not a reporting feature used once a quarter — it is the operational information that hiring managers and HR leadership need to make decisions about resource allocation and process adjustments week to week.
• Budget tracking per role: Compensation benchmarks, approved salary ranges, and actual offers made. At 100+ employees, uncontrolled salary variance across similar roles becomes a retention and equity problem as well as a budget problem.
• Compliance audit trails: A documented record of every hiring decision, candidate communication, and data handling action. At this scale, employment law compliance is not optional risk management — it is a genuine operational requirement that requires structured tooling rather than individual good intentions.
• Employment contract storage and statutory leave compliance: Contracts linked to employee records, leave entitlements calculated correctly by employment type and jurisdiction, and the ability to produce documentation on request for any employee.

The management overhead of running a 100-person organisation without integrated HR tooling is significant. Decisions that should be data-driven become opinion-driven because the data does not exist in a usable form. This is the stage where companies that have been growing on manual processes tend to hit a wall simultaneously on multiple fronts.

200+ Employees: When to Look Beyond Treegarden

This section is here because honesty is more useful than sales optimism. Treegarden is designed and built for growing teams, not large enterprises. The platform covers the full hiring and HR lifecycle for companies from their first ATS purchase through to around 200 employees with active hiring across multiple departments.

At 200+ employees with multi-entity legal structures, deep ERP or payroll system integration requirements, complex enterprise governance with multiple approval layers, or workforce planning at a scale that requires dedicated HRIS expertise to administer — you will likely outgrow what a platform built for SMBs can provide. The feature depth, integration breadth, and compliance coverage of enterprise HRIS systems like Workday or SAP SuccessFactors exist because they are required at that scale. Treegarden is not a Workday replacement.

The honest caveat: some companies at 200+ employees, particularly those whose complexity is primarily around hiring volume and operational HR rather than enterprise governance, find that a well-configured SMB platform provides a better experience than a legacy enterprise system that is technically capable but practically painful to use. Treegarden users at the upper end of the size range tend to be companies that have experienced enterprise HRIS implementations and actively prefer the simplicity trade-off. But that is a specific context, not a general recommendation. If you are at 200 employees and evaluating options, the fit assessment will tell you honestly whether you fall into that category.

Feature Checklist by Company Size

Frequently Asked Questions