How to Build a Business Case for an ATS to Your Manager

To build a business case for an ATS, write one page that states the problem with your current hiring process in measured terms, the option you propose, the full cost, the benefits you can defend, the risks, and a small time-limited pilot with clear success measures. Your manager should be able to say yes to the pilot in one meeting.

What a manager actually needs from you

Managers rarely say no to a better way of hiring. They say no, or not now, when a request is vague, expensive-sounding or risky. A good business case reduces all three. It is short, so it gets read. It uses your own numbers, so it feels grounded. And it asks for something small and reversible first, so that saying yes is cheap. Think about what your manager is worried about: budget, workload, another tool nobody uses, data protection, and looking bad if it fails. Write for those worries. You do not need a slide deck or a vendor brochure. You need a one-page document, a worked cost sheet and a pilot plan. This guide gives the structure, the objections you will hear and how to answer them honestly, and a pilot proposal you can adapt. For background on the tools involved see /applicant-tracking-system and /recruitment-software, and for the numbers see our ROI walkthrough (see the blog post on how to calculate it), which explains how to supply your own inputs. Always check any vendor's current pricing and features yourself before you quote them.

Start with the problem, in measured terms

Open with the problem, not the product. A manager will approve a solution only if the problem is real and costly. Gather a few facts from the last three to six months. How many roles did you fill? How long did each take from approval to offer? How many hours did you or the team spend on screening, scheduling and paperwork? How many candidates did you lose or forget to reply to? Where do records live today, such as inboxes, spreadsheets and chat threads? Were there any near-misses, such as a missed offer deadline or a hiring decision nobody could explain? Collect what you can and label guesses as guesses. Even rough numbers like twelve roles last half-year and about five hours of admin per role are better than adjectives. If you do not have any data, say so, and make collecting it part of the pilot. A sentence such as we cannot currently see how long each stage takes is itself a finding. Avoid blaming people. Frame it as a process with no single place to see what is happening.

The one-page structure

Keep the whole case to one page, with detail in an appendix if needed. Use these headings in this order and keep each to a few lines.

Put the ask first in your email and last on the page. State the decision in one sentence, for example: approve a four-week pilot on two live roles with a maximum spend, and a review meeting on a named date. Writing the ask this clearly makes it easy to agree to.

Show the options, including doing nothing

A business case that compares only the tool you like with nothing looks one-sided. Show a fair spread of options, including cheaper ones. The honest comparison also protects you if the pilot shows a simpler option is enough.

Do not state a competitor's price or feature as a fact in this table. Prices and features change, so write check current pricing and features and add the date you looked. A manager will respect a case that admits the cheap option may be right at low volume. It makes your recommendation more believable when volume justifies the paid tool.

Costs and benefits you can defend

Count the full cost over twelve months: subscription for the plan you would really use, the number of seats, extras, the hours of setup and training, and the weeks you will run old and new processes together. Then list benefits in order of how defensible they are. Most defensible: recruiter and manager hours saved on screening, scheduling and paperwork, which you can time-log in the pilot. Next: shorter gaps between stages, such as the days a CV waits unread, and fewer lost candidates. Next: consistency, because every interviewer uses the same scorecard and the reason for each decision is recorded. Least defensible: avoided bad hires, which should be presented as possible upside, not as a promised saving. Use your own numbers and label every example figure as an example. If you want a formula, our guide to the ROI of recruitment software in the blog explains the calculation line by line. Show a low and high case, not one hopeful number. If the case works on the conservative version, say so plainly. If it does not, say that the pilot is the way to find out.

Objections you will hear, and honest answers

Expect these objections and prepare short answers. Use the table in your meeting.

Answer calmly and do not oversell. Where an objection is partly right, agree. The goal is not to win an argument but to design a pilot that addresses the concern.

A pilot proposal you can copy

A pilot turns a large decision into a small one. Adapt this word-for-word template. Proposal: run a four-week pilot of [tool name] on two live roles, [role one] and [role two]. Owner: [name]. Participants: [hiring managers and interviewers]. Maximum spend: [amount, from the vendor's current pricing]. Scope: we will use the tool for applications, screening, interviews, feedback and decisions on these two roles only, and keep the spreadsheet as a backup. Data: no data is loaded beyond the two roles; we will check storage, retention and deletion terms in writing before starting. Success measures, agreed in advance: hours we spend on screening and admin per role compared with our time log; days between stages; whether every interviewer submits feedback on time; whether hiring managers say they would use it again; whether the ranking on ten known CVs matches our own. Review: a 30-minute meeting on [date], where we decide to stop, extend or buy. Exit: we export all data and cancel at no further cost. Ask: approve the pilot and the spend cap. Putting the exit and the review date in the proposal tells your manager you are not asking for a blank cheque.

A worked example with example numbers

The numbers below are examples only. A 50-person company filled 10 roles in the last 12 months. The recruiter logged about 8 admin hours per role on screening, scheduling and paperwork. Example loaded cost per hour: 40. The proposed pilot covers 2 roles over 4 weeks with an example spend cap of 120 and about 6 hours of setup time, also valued at 40 per hour, so the total pilot cost is 360.

The pilot may not pay for itself in four weeks, and the case should say so. What it buys is evidence: real hours, real stage dates and real adoption, which turn a guess into a decision. If the measured saving holds across a full year of ten roles, the example arithmetic would be much more favourable, but only the pilot can tell you. Present this as an illustration, not a forecast.

How to run the meeting and follow up

Send the one-page case a day before, so nobody reads it for the first time in the room. Open the meeting by stating the ask in one sentence, then spend most of the time on questions. Bring the cost sheet and your time log, but do not read them aloud. If your manager raises an objection you did not expect, write it down and promise a written answer within a few days instead of improvising. Agree three things before leaving: whether the pilot is approved, the spend cap and the review date. Send a short written summary the same day with the decision, the owner and the dates. If the answer is not yet, ask what would change it, such as a budget cycle, a volume threshold or a result from a free tracker, and write that condition into your notes. Then do what you said. Collect the pilot data as planned, report on the review date even if the results are mixed, and be open about what did not work. Managers approve the next request more readily when the last pilot was reported honestly.

Where Rezumz fits

Rezumz is a hiring workspace for small and mid-size hiring teams, and it can be the tool in a pilot like the one above. It scores each CV against the must-haves you set and shows the CV lines it relied on, collects applications on a link, schedules interviews, gathers scorecard feedback from each interviewer through a personal link, records the team decision with a reason and handles offer letters with approval and a simple typed-name signature. Hiring managers can review a shortlist on a view-only page and vote. People make every decision, and nothing is rejected for you. It is not a job board and has no one-click multiposting. It is not a deep HRIS or payroll system, so large enterprises with those needs should look elsewhere. It connects through webhooks and a read-only API rather than ready-made links. The free plan includes 2 free candidate analyses, enough to test a few CVs; paid plans are $29 a month, $199 a year, or a limited $499 lifetime, and Team is $79 a month or $699 a year for up to 10 teammates, aimed at 4 or more recruiters. See /pricing, /compare and the live demo at /demo.

Common mistakes and when not to ask

Common mistakes: leading with features instead of the problem, asking for a large annual commitment first, hiding the cost of setup time, promising savings you cannot measure, ignoring data protection, skipping the hiring managers, and having no exit plan. Another is presenting a vendor's marketing numbers as your own evidence. When should you not ask at all? If you hire only once or twice a year and the process works, a request will cost goodwill for little gain. A tidy spreadsheet and a written scorecard might be the better first step, and /interview-feedback-form and /job-description-template give you free structure. If your manager has just frozen all spending, collect your time log now and ask next quarter. And if the real problem is a lack of clear roles or decision rights, fix that first, because a tool will only make the confusion visible.