The Work Your Team Does That Isn't Really Their Job

Article spoiler:most companies have never calculated what their repetitive tasks actually cost - in real euros, per person, per year. Th…We care about our clients, so we made a short takeaway from this article. Press to quickly get the point.

most companies have never calculated what their repetitive tasks actually cost - in real euros, per person, per year. The math in this article is simple and uncomfortable. And the counterintuitive part: automation doesn't shrink teams. We consistently see the opposite - companies that automate routine work end up handling more volume with the same people, not fewer people with the same workload.

Take a small editorial team. Reporters, an editor, a photographer. Each person was hired for a specific kind of work - writing, editing, visual storytelling. That's what generates value. That's what clients pay for.

Now look at what actually fills the day.

The editor spends roughly two hours every morning on tasks that have nothing to do with editing: formatting articles into the CMS, resizing and uploading photos, copying metadata from one system to another, sending the same status update to the same three people. Not because they're inefficient. Because someone has to do it and there's no other system.

Two hours a day. Five days a week. That's 10 hours a week not spent editing.

Multiply that across four weeks: 40 hours a month. A full working week, every month, spent on work that a well-configured workflow could handle without anyone's attention.

Now put a number on it. In Spain, an editorial coordinator earns roughly EUR 14-16 per hour (INE, 2024 labor statistics). At EUR 15/hour, those 40 hours cost EUR 600 per month. Per person. Annually: EUR 7,200.

If three people on that team follow similar patterns, and they usually do because this kind of accumulation is invisible and happens everywhere, you're looking at over EUR 21,000 a year absorbed into tasks that produce no editorial output.

That money doesn't disappear visibly. It's folded into salaries and accepted as the normal cost of running a team. Nobody questions it because nobody has added it up.

What "saving time" actually means for a growing business

The instinctive fear around automation is that it replaces people. In practice, that's almost never the outcome, and it's not the outcome worth pursuing.

The editor who gets two hours back doesn't get made redundant. They edit more. They review content that was being skipped because there wasn't time. They catch problems earlier. Output quality improves without adding headcount.

What changes is the ceiling.

A team of three that was processing 40 pieces a week can now process 60. Not because they're working harder, because the bottleneck wasn't skill or effort, it was repetition. Remove the repetition, and the same team handles significantly more volume.

For a business trying to grow, this is the real argument. Not cost reduction. Capacity without proportional cost increase.

If you hired a fourth person to close that gap instead, you'd pay another EUR 1,800-2,200 a month once you include salary and employer social security contributions. Automating those specific workflows typically costs a fraction of that as a one-time setup, and runs continuously, without sick days or onboarding.

The three people you already have stop being a ceiling and start being a foundation.

Why some automation creates faster errors, not fewer

Automation works well on tasks that are repetitive, rule-based, and don't require judgment. Routing a file to the correct folder based on its name: yes. Generating a weekly summary report from data that already exists in your systems: yes. Sending a confirmation email when a form is submitted: yes. Deciding whether a piece of writing is good: no.

That distinction matters because poorly targeted automation creates its own costs. We've seen processes automated at a point where human judgment was actually needed, and the result was faster errors at higher volume. That's worse than the original problem.

The right model keeps people in the loop for decisions and removes them from the conveyor belt. The editor still decides what gets published. They just don't spend their mornings uploading JPEGs one by one.

This is also why full automation, removing people entirely, is rarely the right goal. The goal is freeing people for work that actually requires them. Done correctly, this usually means the business can handle more with the same team rather than the same amount with fewer people.

The calculation to run before committing to anything

Before implementing anything, do this one exercise: pick the single most time-consuming repetitive task your team performs. Time it honestly across one week. Then:

Hours per week x hourly rate x 52 = annual cost of that one process

For most small teams, this number comes out between EUR 5,000 and EUR 15,000 for a single workflow. Where it lands depends on the hourly rate involved and how many hours the task actually consumes, the formula is the same either way. Automating that workflow properly typically costs EUR 1,500-5,000 depending on complexity.

Payback period: 3-12 months. After that, the savings compound.

The increased capacity, the ability to take on more clients, more volume, more work without proportional hiring, doesn't appear in that calculation at all. It's the reason companies don't undo these changes once they've made them.

---

If you want to run this calculation for your own team before committing to anything, that's exactly what the first phase of our process audit covers. We map where time actually goes, identify which processes are realistic automation candidates, and produce an honest technical estimate of complexity and priority before any implementation begins. Get in touch.