ATS prices include roughly $6,000 yearly for smaller teams, a $12,240 median for 200 employees, and $63,000-$144,000 and up for larger organizations.
Key takeaways
- Use the figures as budget starting points.
- Separate customer-reported ranges from the negotiated median.
- Compare total costs, including renewal terms.
- Test your own hiring workflows before signing.
Once you sign, you are tied to a contract, a set of integrations, and a team that has to learn new habits. Before you sit through a demo, it helps to know what other teams of your size typically pay.
This post gives three price points, one for each rough size of buyer: a small team, a median-sized company, and a large organization. The figures come from a single published roundup, and that matters. They combine a customer-reported range with a median negotiated contract. Treat them as a starting point for your budget, not as a quote from any vendor.
We will cover where the numbers come from, what each price point does and does not tell you, how to measure whether a system is paying off, and the questions to ask before you sign.
Where the numbers come from
The prices in this post come from Lever's guide, 15 best applicant tracking systems in 2026. Its method is worth reading before you rely on any figure. The authors looked at each platform's published capabilities and aggregated user reviews from G2 and Capterra, as of August 2026. Where vendors don't publish list prices, they used customer-reported pricing instead.
That method has two consequences. First, some vendors do not publish list prices, so for them the numbers are what customers reported, not what a pricing page lists. Second, the data is a snapshot. Keep in mind that a published figure and a signed contract can differ, and the difference often depends on which features you bundle.
A related Lever article on its vendor assessment tells readers to compare the 15 best applicant tracking systems for your talent team. Use a list like that to build a shortlist of three or four, then use the price points here to decide which vendors deserve a demo.
Price point one: small teams, about $6,000 a year
Lever's roundup puts the customer-reported range for smaller teams at roughly $6,000 a year. Use that figure as a budget starting point for a smaller team.
Whether a plan at that level covers what you need depends on the vendor. Ask every vendor to put in writing what its base plan includes. Useful items to check are the number of user seats, the number of open jobs you can run at once, applicant record limits, reporting, and which integrations come with the plan rather than as add-ons.
Fit matters more than price at this size. The guide makes the point directly: the right ATS for a growing in-house team isn't the right ATS for a staffing agency or a 10-person startup. A staffing firm often manages several client accounts and needs pipelines that reflect that. A small in-house team may need a simple setup that one person can run without a dedicated administrator. Price alone won't tell you which one you need.
Usability is the other factor to test at this size. Reviewers, according to the same guide, describe the interface as intuitive and easy to use for team members with varying technical skills (G2, August 2026). That is a useful signal for a team where recruiters also handle scheduling, sourcing, and admin. It is still a summary of reviews, so confirm it in a trial with your own staff.
At this size, be careful about paying for capacity you will not use for a year. Ask whether the plan can be adjusted down as well as up, and whether a seat or job limit can be raised in the middle of the contract without a long re-quote. A plan that fits today's team, with a clear path to the next tier, is often a better buy than one sized for the team you hope to have.
A closer look at staffing firms
Small staffing teams deserve a closer look, because a common ATS setup assumes one employer hiring for its own roles. A staffing firm may work several client accounts at once, submit applicants to each client, and report on fills and placements by account. Those workflows can look very different from an in-house process, so test them directly rather than assuming they are included.
When you talk to vendors, describe your real flow. Ask them to show how an applicant moves from one client's requisition to a submission, how you see which client an applicant belongs to, and how a recruiter reviews work across accounts. If the answer depends on a workaround, count the time that workaround takes each week. Those hours are part of the cost, even though they do not appear on the invoice.
Ask about data ownership too. Applicant records often pass between your firm and clients, so confirm who controls the data, what clients can see, and how records are removed when a placement is complete or an applicant asks. A short written answer from each vendor is worth more than a long sales deck on this point.
Price point two: the median, about $12,240 a year
If your company is about 200 employees, this is the most direct comparison. Lever's guide cites data from Vendr, 2025, which puts the median negotiated contract for a 200-employee company at about $12,240 a year. Note the scope. This median covers companies of about 200 employees. It is not a median across all businesses, and it is not a list price.
The word negotiated matters. The figure reflects what companies agreed to after negotiation, so a vendor's first quote is a starting point, not a final price. Your own number could land above or below the median depending on contract length, the features you need, and how the negotiation goes.
That is about twice the small-team figure, so the jump is real and worth explaining to your finance team before you start a demo cycle.
When you compare quotes at this level, put them on the same basis. Ask each vendor for a first-year total that includes implementation, training, data migration, and any integration fees. Then ask what the renewal price will be, since a first-year number does not show what it costs to keep the system after that.
Read the contract for the terms that change cost over time: the length of the commitment, how users or open jobs are counted, any usage limits, and the notice you must give to change or end the agreement. These details rarely come up on a sales call, but they decide how much room you have later.
Integrations deserve the same care. The guide cites 400+ integrations across HRIS, sourcing, background checks, and productivity tools, which is a useful sign of breadth. A count only helps if it includes the tools you already use. Make a short list of must-have connections, such as your HR system, job boards, background check provider, and calendar or email tool, and confirm each one by name. Ask whether each integration is included in your plan or billed separately.
At a company of about 200 employees, hiring managers can be the hardest users to win over. Ask whether they can review applicants, leave feedback, and approve offers without extended training. Ask the vendor to show a hiring manager's view, not just the recruiter's. A system that managers avoid leaves recruiters re-entering notes elsewhere, which erodes whatever the license saved.
Price point three: large organizations, $63,000 to $144,000 and up
For larger organizations, the guide's customer-reported range runs from $63,000 to $144,000 a year, with the top figure marked as "and up." The spread is wide. A range that broad suggests the other factors matter a great deal, such as the scope of the rollout, the number of users, and the systems each buyer must connect.
At this scale the ATS is often one part of a larger stack. It usually has to work with an HR system, sourcing tools, background screening, and the reports that leadership reads. Each connection adds setup work and cost, and each one is a place where the project can stall. Plan for an integration review early, with the people who own those systems in the room.
Larger buyers also need a clearer decision process. Recruiting, IT, procurement, and legal often each have a stake in the contract. Settle early who owns the budget, who approves user access, and where applicant data will be stored and who can see it. Those answers shape the contract, and they are much harder to change after you sign.
Large organizations also tend to run a security and privacy review before signing. Ask early what documents the vendor can provide, how long that review usually takes, and who on your side must approve it. A review that starts after the business case is approved can delay a purchase considerably.
Ask for a trial that uses your own requisitions and workflows, not a demo built on sample data. Also measure the team's time, not only the license fee. A system that is cheap to license but takes months to configure can cost more over a year than a pricier system your team adopts quickly. The same logic applies at every size, but the stakes are higher here.
Ask for references from customers that look like your organization in size and structure, and ask them what they would change. A reference who has been through a renewal can tell you more about the real cost than any sales page.
How to read the three figures together
The table below puts the three figures side by side.
| Buyer | Figure from the guide | Question to answer first |
|---|---|---|
| Smaller teams | roughly $6,000/yr | Does the plan include what we need? |
| 200-employee company | Median negotiated contract: about $12,240/yr | What is the first-year total and renewal? |
| Larger organizations | $63,000–$144,000+/yr | Which integrations and approvals must be in place before we sign? |
None of these figures comes with a formula linking headcount to price, so do not try to work out a headcount-based rate from these numbers. The 200-employee median also sits between the other two figures. If your company falls between these sizes, ask each vendor where it places you and why.
Use these figures to sanity-check a budget before you talk to vendors. If a quote for a team your size lands far outside the range, ask why. Sometimes the difference is a real need, such as a required integration or a compliance feature. Sometimes it is a packaging choice you can change. Either way, a quote you can explain is worth more than one you accepted because it looked reasonable.
Measure whether the system pays off
Price is only half of the decision. You also need evidence that the system improves hiring. Indeed's guide to recruitment yield ratios puts it simply: "They can help employers understand how efficient and effective their recruitment funnel is." A yield ratio compares how many applicants move from one stage of hiring to the next, such as from applicants to phone screens, or from interviews to offers.
Before you sign, write down your current yield for a few recent roles. During the trial, measure the same stages using the data the new system holds. Compare the two sets of numbers. If the system does not move your numbers, or if the data is too messy to trust, the extra cost is hard to justify. A small team can do this in a spreadsheet, and a large one should agree on the definitions first so that every recruiter counts the same way.
Illustrative example: compare stage counts
Suppose 20 applicants reach interviews and 10 receive offers before the trial. During an illustrative trial, 20 reach interviews and 10 receive offers again. The stage counts are unchanged. Check scheduling time and reporting quality too before deciding whether the system justifies its cost.
Run a trial that tells you something
A trial is only useful if it is set up to test what matters. Choose two or three open roles that cover different levels or types of work, so you see how the system handles more than one pattern. Decide before you start what success looks like, such as fewer days spent on scheduling, a clearer view of each stage, or fewer applicants lost between steps.
Involve the people who will use the system every day. That means recruiters who will enter applicants and hiring managers who will review them. Give each of them a short list of tasks, such as posting a role, moving an applicant forward, leaving feedback, and pulling a report. Note where they get stuck. The sticking points will matter more after you sign than any feature on a comparison chart. Use an interview scorecard and hiring decision debrief to test feedback and decision records.
Keep the trial short and time-boxed. Set an end date, and ask for help only through the channel the vendor would offer after you sign. If support is slow during the trial, treat that as a sign of what you may get later.
Today, write down your must-have workflows and choose a real role to use in the trial.
Questions to ask before you sign
What is the first-year total, including setup, training, data migration, and integration fees?
The first-year total should combine the license and those additional costs.
What does the base plan include, and which features are add-ons?
Ask for a written breakdown separating included features from add-ons.
How many user seats and open jobs does the quote cover, and what does an increase cost?
The quote should state both capacity limits and expansion costs.
Which of our must-have integrations are built in, and which are billed separately?
Confirm each required connection and its cost by name.
What will the renewal price be, and how is it set?
Check the renewal price and how the contract allows it to change.
How do we export applicant data and records if we leave?
Ask the vendor to demonstrate an export during the trial.
What reporting is included, and can we export funnel data to measure yield?
Test the reports and exports against the hiring stages you measure.
What support hours and response times are written into the contract?
Use the written terms to assess support coverage.
Can we run a trial with real requisitions and our own team?
Request a trial using your team's actual hiring tasks.
Who will own our account after the sale, and who do we call when something breaks?
Get a named account contact and a support route before signing.
Match the tool to your team
The price points here are a map, not a verdict. Smaller teams, median-sized companies, and large organizations each have different needs, and the cheapest or most expensive option is not automatically the right one. Start with how you hire: how many roles you fill at once, whether you work for clients, which tools must connect, and who will use the system every day.