AI agents vs hiring: what a 200-person company should automate first

In a growing company, a new capacity request may combine higher demand with coordination work nobody has measured yet. Separate them before choosing a response.

Someone asks for a report. Three people spend two days compiling it from four different systems. The report is useful for about three days. Then someone asks for it again. Nobody questions why it exists. Nobody asks what decision it supports. It just runs, like a ritual.

Before hiring or buying an agent, establish which work serves a real decision and which exists because a process is poorly connected. Necessary control work should not be removed just because it is repetitive.

The hiring reflex is understandable. A manager notices that their team is drowning in manual reconciliation, reporting, and routing approvals. The team complains. The manager asks HR for another headcount. HR says the budget is tight but maybe one more person. The company hires someone with a generic title like Operations Coordinator. Six months later, that person is drowning too.

The problem was never headcount. The problem was that three separate workflows were silently consuming twenty hours a week across four people, and nobody had mapped them because they were too small to justify a project and too embedded to question.

Separate staffing needs from workflow defects

Organizations behave this way after growing beyond one person's field of view. Informal processes become the real processes. Undocumented spreadsheets become the system of record. Only the people doing the work can still see it.

Decide which workflows deserve an agent, which need a person, and which should disappear entirely.

The companies that get this right start with an inventory of what people actually do on a Tuesday morning. The org chart and the SOP usually tell a cleaner story.

Screen each candidate workflow: volume, handoffs, context sources, consequence of failure and the kind of intervention needed. Then check data access and who will own the operation.

The answer is rarely obvious. The workflow that looks like the biggest time sink is often the one with the most undocumented exceptions. The one that seems minor turns out to be a bottleneck that blocks twelve other processes. The thing everyone complains about is usually a symptom of something else.

Here are the three patterns that show up most often in companies of this size, and what tends to work for each.

Reporting. Extraction and assembly may be good automation candidates. Financial and compliance reports still carry material risk, even as drafts. Validate the sources, reconciliation rules and review capacity; select the first workflow by value, risk, access and ownership.

Reconciliation. Invoices against purchase orders. Inventory counts against system records. Timesheets against project budgets. Two systems contain overlapping information and a person checks whether they match. Pattern matching at this scale exhausts people. A controlled system can read both sources, flag discrepancies, and present them for human judgment.

Routing approvals. Purchase requests. Expense reports. Contract revisions. Something moves from A to B to C while each person checks, approves, or sends it back. Routing creates the delay. Predictable cases can follow deterministic rules while exceptions go to a person.

Leave workflows involving company direction under human judgment until leadership agrees on what a good answer looks like. If a client approval takes three weeks because nobody owns the decision, an agent will only accelerate a bad process.

An agent is useful only when its task and failure boundaries match the operation. A market adoption statistic cannot select the workflow for you.

A process problem automated is just a faster process problem.

This is why the first question in any engagement is never which tool should we use. It is what work are we actually doing, why are we doing it, and what would happen if we stopped?

The hiring decision and the automation decision are the same decision viewed from different angles. Both are responses to a capacity gap. The question is whether that gap comes from too much work or from work that should not exist in its current form.

Hiring into a poorly understood process can preserve avoidable work. Involve the people doing it in the redesign; they often know which checks protect the business.

If you automate a process that should not exist, you waste money on tooling and integration for something that produces no value. The agent works perfectly. The output goes to nowhere. The cost is lower than a person, but it is still a cost.

The sequence matters. Map first. Question second. Decide third. Build fourth.

There is a cost question underneath all of this, and it deserves a direct answer.

Use the actual loaded cost for the role and geography: salary, employer costs, recruitment, onboarding and management. A single European salary band would hide too much variation.

A system intervention for the same scope of work requires someone who understands the workflows, the systems, and the exceptions. It is not a plug-and-play purchase. It begins by deciding whether the case needs a War Map or a bounded Feasibility Sprint, then agreeing scope, evidence, timing, and risk controls for the actual operation.

A person brings judgment, relationships and adaptable capacity. A system brings a defined operating scope that must be tested and maintained. Compare total cost, quality, resilience and responsibility for the same work.

The question to ask before you post a job requisition or sign an agent vendor contract is the same one that matters for any operational decision: what work are we actually doing, and what would happen if we did it differently?

Not hypothetically. Specifically. Which workflow. Which volume. Which handoffs. Which person currently owns it. Which system contains the context. Which decision requires human judgment. Which step is just waiting.

The companies that answer these questions before they hire or automate are the ones that see results. The ones that skip them are the ones that end up with a new employee doing old waste, or a new agent doing old waste faster.

A third option comes first: understand the work.