The total cost of an ATS has two components. The first is the subscription fee — visible, predictable, and what most budget conversations focus on. The second is the operational overhead cost: the time your recruiters spend on workarounds, the candidates lost to a poor application experience, the slower time-to-hire caused by a system that creates friction at every step. The second component is often larger than the first, and it's almost always invisible.

The following eight signs are the patterns that consistently appear when the second cost is growing. Each one is observable without any special analysis — they show up in your team's daily behaviour, your candidate metrics, and your renewal conversations. If you recognise three or more of these patterns, the conversation worth having is not whether your ATS is costing you, but how much.

It's worth acknowledging: most HR teams rationalise each individual sign when it first appears. The spreadsheet is "just temporary." The email feedback is "just the way this hiring manager works." The renewal increase is "just market conditions." What changes when you see all of them together is that the pattern becomes undeniable — your ATS is the system you work around, not the one you work in.

Sign 1: Your recruiters have spreadsheets running alongside the ATS

This is the clearest signal of all, and it's almost always present in teams where the ATS isn't working well. It shows up as: a Google Sheet tracking which candidates are at which stage because the ATS pipeline view is too slow or too limited. A separate spreadsheet tracking interview schedules because the ATS calendar integration doesn't sync reliably. A shared doc listing open roles and their status because the ATS job list doesn't give the hiring manager a usable overview.

The spreadsheet is not the problem — it's the symptom. The actual signal is that your team has stopped trusting the ATS to be the source of truth. When that happens, two things follow: the ATS data degrades (updates happen in the spreadsheet but not always in the system), and the time savings that justified the ATS subscription evaporate, because your team is now maintaining two systems instead of one.

What to do about it: identify specifically which function the spreadsheet is replacing. That function is either configured incorrectly in your ATS, limited by platform capability, or not supported at all. If it's a configuration issue, fix it. If it's a capability gap, assess whether it's a dealbreaker or a workaround you can live with. If it's consistently present across multiple functions, it's a platform signal.

Sign 2: Candidates are dropping out of your application process

Candidate drop-off in application forms is often attributed to labour market conditions or role attractiveness — and sometimes those are the right explanations. But a broken or friction-heavy application process creates drop-off that is entirely within your control to fix, and an ATS that generates that friction is costing you qualified candidates.

The signals: applications that start but don't complete (your ATS should track form start vs. submission rate), mobile application completion rates significantly lower than desktop (most ATS application forms are built for desktop and perform poorly on mobile), and candidate feedback mentioning the application process as a pain point. If your time-to-apply is more than 10 minutes, you're losing candidates who are evaluating multiple opportunities simultaneously and will abandon a difficult form in favour of a smoother one.

What to do about it: test your own application form on a mobile device. Time it. Note every field that requires manual input that could be pre-populated from a CV upload. Note every required field that isn't actually necessary for a first-stage screening decision. If the form would frustrate you as a candidate, it is frustrating your candidates — and some of them are walking away from your pipeline.

Sign 3: Hiring managers use email instead of the ATS to give feedback

Hiring manager feedback workflow is where ATS adoption breaks down most commonly. If your hiring managers are emailing recruiters their interview feedback rather than entering it in the ATS, the reason is almost always one of three things: the ATS feedback interface is too complex for occasional users, the mobile experience is poor, or they were never properly onboarded to the feedback workflow.

The cost of email-based feedback is compounding. The feedback isn't centralised, so the recruiter has to collect it, summarise it, and re-enter it manually. The candidate record in the ATS doesn't have the full picture, so a DSAR response would be incomplete. The next recruiter to review this candidate's history can't see the full evaluation context. And the analytics for why candidates were rejected are inaccurate, making pipeline analysis less useful.

What to do about it: determine whether this is a usability problem (the ATS feedback interface is genuinely too complex for part-time users) or an onboarding problem (hiring managers were never shown how to submit feedback). Usability problems require either ATS configuration changes or platform evaluation. Onboarding problems are fixable with a 15-minute walkthrough and a reference card.

Sign 4: Your renewal came in higher than last year with no new features

ATS renewal pricing has become an active problem for mid-market companies in 2025-2026. The pattern is familiar: a reasonable first-year price, a 10–15% second-year increase with vague justification, and a 20–40% third-year increase framed as "enterprise tier" pricing that you didn't sign up for. Meanwhile, the product roadmap has delivered improvements that benefit enterprise customers but not mid-market users.

The critical question at renewal time is not "is this a fair price increase?" but "is the total value we're getting from this platform worth the new price, compared to available alternatives?" Those are different questions. Your ATS vendor's account team is paid to get you to sign the renewal; they are not incentivised to help you evaluate whether a different platform would serve you better at a lower price. That evaluation is your responsibility.

What to do about it: start a competitive evaluation 6 months before renewal, not 6 weeks. The 6-month window gives you time to complete an actual evaluation (demos, reference checks, pricing negotiation) rather than a rushed comparison that results in signing a renewal by default because you ran out of time to migrate.

Sign 5: You're paying for integrations you set up with Zapier because the native ones don't work

Zapier integrations are a signal worth paying attention to. They indicate that a native integration your ATS promised (or that you need) doesn't work reliably enough for your team to trust it. Zapier connects things that don't connect natively — and paying for a Zapier subscription on top of your ATS subscription to compensate for the ATS's integration gaps is a direct cost that belongs in your total cost of ownership calculation.

Beyond the direct cost, Zapier-based integrations are more fragile than native integrations: they break when either connected platform updates its API, require manual maintenance when workflows change, and create data flow delays that native integrations avoid. If you're running hiring workflows through Zapier because your ATS doesn't handle them natively, that's both a cost and a reliability risk.

Sign 6: Your time-to-hire has been increasing, not decreasing

A well-implemented ATS should compress time-to-hire over time as your processes mature and the tool handles more coordination automatically. If your time-to-hire has been trending upward over the past year or two — without a corresponding change in role complexity, hiring volume, or market conditions — the ATS deserves investigation as a contributing factor.

Time-to-hire increases attributable to ATS friction typically appear as delays in specific stages: applications sitting in an unreviewed queue longer than they should because the ATS review interface is inefficient, interview scheduling taking multiple days of back-and-forth because the calendar integration is unreliable, offer approvals taking longer than expected because the approval routing in the ATS isn't trusted and people are doing it by email instead.

What to do about it: pull your time-to-hire data broken down by pipeline stage. Where is the time accumulating? If the delays are concentrated at specific stages, investigate whether the ATS supports that stage well or creates friction at it.

Sign 7: Your team dreads ATS training for new hires

When a new recruiter joins your team, what does the ATS onboarding look like? If the answer involves a multi-day training process, a manual with screenshots, and a follow-up session for "advanced features" — that's not onboarding complexity, that's a signal about interface quality. A well-designed ATS should require a half-day of onboarding for a recruiter who has used any ATS before. If it takes longer, the complexity is in the product, not in the user.

The practical cost: recruiter ramp time. A new recruiter who spends 2 weeks becoming functional in the ATS before they're running their own pipelines is a delay that compounds across every hire you make in the first quarter. A recruiter who can be productive in their first week is a meaningful productivity gain — and the difference between those two scenarios is often entirely determined by the ATS they're working in.

Sign 8: You've had to create workarounds for every new job type you post

Hiring workflows differ between job types: a sales role and a software engineering role have different screening criteria, different interview processes, and different approval structures. A mature ATS should support job-type-specific workflows without requiring significant manual adjustment each time you post for a new type of role.

If every new job type you post requires a workaround — a custom Zapier flow, a manual stage addition, a change to your general pipeline that affects all other jobs, or a conversation with vendor support — that is a flexibility limitation that will grow more costly as your hiring needs diversify. Companies are often willing to tolerate this early in their ATS adoption, but it compounds: the more job types you hire for, the more workarounds accumulate, and the more the ATS starts to feel like a constraint rather than a tool.

How to calculate your ATS's real cost

The total cost of your ATS includes more line items than the subscription invoice. For a complete picture, calculate each of the following:

Direct costs:

  • Annual subscription fee (including all tiers you've been upsold into)
  • Implementation and onboarding fees paid to vendor or implementation partner
  • Zapier or middleware subscription costs
  • Additional integration licensing fees
  • Training costs for new hires

Indirect time costs (calculate per year):

  • Recruiter hours per week maintaining parallel spreadsheets × recruiter FTE count × 52 weeks × average hourly recruiter cost
  • Hours per hire spent on manual coordination that should be automated (email scheduling, feedback collection, offer routing) × annual hire count × average hourly cost
  • IT or admin hours spent on ATS maintenance and workaround management

Time-to-hire cost:

  • Calculate your average time-to-hire in days, and estimate the revenue impact of each additional day a role is open (a rough estimate is daily revenue per role per open day, which varies widely by role level and business impact)
  • If your ATS is adding 5–10 days to average time-to-hire through friction, that is a quantifiable cost

For most mid-market companies running this calculation seriously, the indirect costs exceed the subscription fee. The subscription fee is what you pay; the indirect costs are what your ATS costs. They're not the same number.

What to do if you recognise these signs

Recognising these patterns doesn't require an immediate migration decision. It requires an honest cost assessment: calculate the actual annual cost of your current ATS, including subscription fees, integration costs (Zapier, other tools), recruiter time on workarounds (hours per week × recruiter count × hourly cost × 52 weeks), and an estimate of time-to-hire impact.

Then compare that total against the all-in cost of a better alternative: subscription fee, migration cost (typically 1–2 months of your current subscription amortised over the contract term), and the productivity gain from eliminating workarounds.

The decision follows from that comparison, not from the subscription invoice alone.

We make the switch straightforward

Treegarden's team helps with data migration from any ATS. Transparent pricing from $299/mo. No surprise costs mid-migration.

See pricing and migration support →

Frequently asked questions

How do I know if my ATS is slowing down hiring?

The clearest indicators are time-to-hire trends and recruiter workaround behaviour. If time-to-hire has increased over 12–18 months without corresponding changes in role complexity, and your recruiters are maintaining parallel spreadsheets or using email for functions the ATS should handle, those are strong signals. Pull your time-to-hire data broken down by pipeline stage to identify where delays are accumulating.

What's the average time-to-hire?

SHRM benchmarks put the average time-to-fill at approximately 36 days across industries, with technology roles running 45–60 days for senior hires and high-volume roles much shorter. The more meaningful benchmark is your own trend over time: a well-implemented ATS should be compressing your time-to-hire as processes mature, not allowing it to drift upward.

How do I calculate my ATS ROI?

Compare recruiter time savings (hours per hire on automatable tasks × hourly cost × annual hire count) and time-to-hire improvements against the platform cost plus workaround costs (Zapier, additional tools, recruiter hours on manual work). If the workaround costs exceed the platform cost, you have a negative ROI situation worth addressing.

When is it worth switching ATS providers?

When the total cost of staying — subscription plus workaround time cost plus time-to-hire impact — exceeds the total cost of switching — subscription differential plus migration cost amortised over the contract term. A migration that costs the equivalent of 2 months of current subscription pays for itself quickly if it eliminates 3+ hours of weekly recruiter workarounds and reduces time-to-hire by 5+ days.

Related Reading