Framing this as a replacement decision usually produces a bad answer. The realistic outcome for most SMEs is that automation absorbs the repetitive share of a role — the triage, the copying between systems, the first response — and the person keeps the part that needs a person.
Compare against a measured baseline, not an impression
Before either decision, measure the current process: how many cases per week, how long each takes, where it waits, and how often it goes wrong. Without that baseline you cannot tell whether a hire or a workflow helped, and you have no basis for the second decision. Most teams discover the volume is either much smaller than assumed — in which case neither option is urgent — or concentrated in one step that is cheap to automate.
Automation has an operating cost too
A workflow is not a one-time purchase. It needs monitoring, occasional tuning as the surrounding tools change, and an owner who handles what it escalates. That cost is real but flat, which is precisely why it compares well against headcount as volume grows — and poorly against it when volume is small.
A conservative break-even example
Use measured figures rather than treating this illustration as a forecast. Suppose a team handles 450 cases a month at eight minutes each: that is 60 hours of current handling time. If a pilot safely removes 55% of handling time after human review and exceptions, it releases 33 hours. At an assumed fully loaded labour cost of €28 an hour, the capacity value is €924 per month. Subtract an assumed €350 monthly platform and operating cost, leaving €574 in monthly net capacity value. A €4,000 implementation would therefore take about seven months to recover on this model (€4,000 ÷ €574).
This is capacity value, not an automatic payroll saving: it becomes cash savings only if the business actually avoids or reduces cost. Include QA, exception handling, maintenance and any extra task, API or model usage in the operating figure. Replace every input with a representative baseline and a scoped quote before making a hiring decision.
If you want the arithmetic rather than the argument, the ROI methodology guide sets out how to model both sides with assumptions you can defend.