Automation

How Long Until an Automation Pays for Itself

Petru Constantin
••6 min read
#ROI#payback#automation cost#SMB#calculation#Romania

Divide the total cost by the real monthly saving and you get the number of months. Total cost includes the build, the subscriptions and your people's time. The real saving is hours saved multiplied by the true hourly cost, which is a different number from the gross salary. Under twelve months is almost always worth it.

Everyone sells automations with the promise that they "pay for themselves". Rarely does anyone show you the arithmetic, because honest arithmetic rules out some of the projects.

Below is the formula we use, followed by a worked example built from numbers we chose to show the method. They are not data from a client and they are not a result we promise you. They are numbers put into the formula so you can see how it moves.

The formula

Months to payback = total cost ÷ net monthly saving. Total cost is the build price plus the subscriptions plus your people's hours during implementation. Net monthly saving is the value of the hours saved plus the avoided mistakes you can quantify, minus the monthly maintenance.

Three numbers, and each of them is usually wrong from the start.

Total cost: what everyone forgets

The build price. With us it is fixed and published: an end-to-end workflow costs between 700 and 1,500 EUR, a production agent starts at 3,500 EUR, and the AI Diagnostic costs 490 EUR and is deducted in full from a build started within thirty days. Prices are final, with no VAT added.

The subscriptions. Platforms, model API keys, hosting. Sometimes zero, sometimes a few tens of euros a month. They go into the calculation; being small is no reason to ignore them.

Your people's time. The part forgotten in almost every calculation. Someone in the company has to explain the process, give access to the systems, test the result and answer questions. These are real hours, paid by you.

Maintenance. A supplier system changes, a format gets modified, a new case shows up. With us the retainer starts at 490 EUR a month and is optional. If you do not take it, the cost does not disappear, it just moves to someone in your company.

The monthly saving: where the numbers get inflated

This is where most payback calculations that look too good get made.

Hours saved, measured rather than estimated. Ask the person who does the work, not their manager. Time it for a week. The gap between estimate and measurement is usually large, in both directions.

The real hourly cost. Neither the net salary nor the gross. The employer's total cost divided by the hours actually worked.

Saved hours are not money in the bank. This is the main trap. If you release two hours a week from a person you pay anyway, you have not saved a cent. You have freed capacity. It turns into money only if those hours produce something else you can sell, if you postpone a hire you were going to make, or if you stop paying for overtime.

Avoided mistakes, only the ones you can prove. A double payment, a late payment penalty, a wrong order. If you can show how many there were last year and what they cost, they go into the calculation. If not, do not invent a number to make the result work.

See in 1 minute if it can be automated gives you a first read before you start the calculation.

Worked example, with numbers we chose

The numbers below are an illustrative example. We picked them to show the mechanics of the formula; they do not describe a client or a guaranteed result. Replace them with yours.

The assumed situation: one person spends 5 hours a week processing incoming documents. Assumed total hourly cost for the employer: 15 EUR. The automation removes 4 of the 5 hours, and the remaining hour goes to checking exceptions.

Assumed total cost:

  • Build: 1,200 EUR
  • Subscriptions: 25 EUR a month
  • Team time during implementation: 10 hours × 15 EUR = 150 EUR
  • Initial total: 1,350 EUR

Assumed monthly saving:

  • 4 hours a week × 4.33 weeks = 17.3 hours a month
  • 17.3 × 15 EUR = 260 EUR
  • Minus subscriptions: 260 − 25 = 235 EUR a month

Result: 1,350 ÷ 235 = about 5.7 months.

Now the part that changes the conclusion. Those 17 hours a month become money only if the person does something else of value in their place. If the salary stays the same and the hours go to something unimportant, you bought comfort and accuracy, not savings. Comfort and accuracy can be worth 1,350 EUR, but then the decision is made for the right reason.

Change a single number and see how sensitive the result is: at 2 hours saved a week instead of 4, the same figures give almost thirteen months instead of six.

Which threshold to use

Under 12 months: almost always worth it, assuming the process stays stable.

Between 12 and 24 months: it depends on stability. If the process changes every year, the automation does not pay for itself in time.

Over 24 months: you usually picked the wrong process. The right answer is to choose another process, and negotiating the price will not fix it. How to make that choice is in what to automate first in a 10-person company.

Frequently asked questions

How do I calculate how long an automation takes to pay for itself?

Divide the total cost by the monthly saving. Total cost means the build price plus the monthly subscriptions plus your people's time during implementation. Monthly saving means the hours saved multiplied by the real hourly cost of the person who did the work, plus only the mistakes you can honestly quantify.

What is a reasonable payback period?

Under twelve months is almost always worth it. Between twelve and twenty-four months it depends on how stable the process is: if it changes every year, the automation does not pay for itself in time. Over twenty-four months, you are usually automating the wrong process, and the right answer is to pick another one.

Do saved hours automatically mean saved money?

No, and this is the most common mistake. If you save two hours a week for an employee you pay anyway, you have not saved money, you have freed capacity. It becomes a real saving only if those hours produce something else of value, if you postpone a hire, or if you stop paying for overtime.

Next step

To do the calculation with your own numbers, you need a real price, not a range.

Book a Technical Diagnostic (EUR 490). We look at your processes, provide exact figures, and calculate ROI together. If payback doesn't happen in under 12 months, we tell you straight.

Want AI agents and automations your business can actually run on?

We ship production AI in fixed two-week sprints, then secure them. Book a 30-minute call to scope yours.

Book a Call

Before you book, you can see what we build, how a sprint works, how our pricing works, what we have already built, or write to us directly.

Weekly AI Agents, Automation & Security Digest

How we build AI agents and automations with Claude Code, plus practical AI security, integrations, and platform notes, delivered weekly.

No spam. Unsubscribe anytime.