Published on 24/10/2026

What does process automation cost, and when does it pay off?

"What does automation cost?" sounds like a simple question. A number without a defined workflow is worth little, however. A small script can be cheap to build and expensive to fail when exceptions, support and review are missing. A larger fixed price can make sense if integrations, approvals and ongoing operation are genuinely included.

A sound calculation separates three cost blocks: discovery, implementation and operation. It then compares those costs with a documented baseline, not a general promise.

1. Understand the workflow

Before implementation, you need to know where the case starts, which data arrives, which rules apply and who decides exceptions. This includes talking to the people who actually do the work and reviewing a small sample of real cases.

At the time of writing, the DevSeal process check includes a process map, savings estimate and implementation plan, offered from EUR 1,800 at a fixed price. This is the current entry point when drafted, not a promise that every scope is covered at that price.

2. Implement one bounded workflow

Implementation includes more than the visible automatic action. Inputs must be detected, data validated, permissions set, exceptions routed and actions logged. Testing, training and a documented handover also belong in the scope.

At the time of writing, a DevSeal automation pilot for one production workflow is EUR 6,000 to 15,000 at a fixed price, depending on scope. The agreed scope, including the number of systems, variants and approval steps, determines the actual quote. The range does not guarantee coverage of every project.

3. Include ongoing operation

Passwords change, interfaces evolve and new document variants appear. Somebody must review failures, apply safe updates and respond to outages. At the time of writing, DevSeal support for operation, adjustments and reporting starts at EUR 450 per month. The actual service depends on the agreement.

Internal time belongs in the calculation too. Employees provide samples, review outcomes and learn the new workflow. Those hours do not disappear because a supplier gives a fixed price.

An explicitly hypothetical payback calculation

A fictional business processes 300 documents each month. Before automation, each case takes 6 minutes on average. After a pilot, review and exceptions still require 1.5 minutes per case. Every volume, duration and hourly value below is an illustrative assumption, not a measured result or promise.

The assumed EUR 35 is a loaded cost per working hour: gross pay plus employer contributions and allocated overhead. It is not a DevSeal price and must be replaced with the business's applicable value.

Now assume, purely for illustration, EUR 9,000 implementation, a EUR 1,800 process check and 20 internal setup hours at EUR 35. The EUR 700 of internal time raises initial cost to EUR 11,500. With a calculated monthly contribution of EUR 337.50, the simple break-even is 11,500 / 337.50 = 34.1 months, or 35 complete months. This is a limited financial evaluation measured in valued capacity rather than cash.

The calculation deliberately includes remaining review time and ongoing support. It is still only a decision model. Holidays, ramp-up, financing, tax, price changes and alternative uses of funds are not assessed. This article is not tax or financial advice.

Capacity is not automatically cash

The 22.5 hours are released capacity first. Using them for customers, quotes or fewer overtime hours can be valuable, but it does not automatically put EUR 787.50 into the bank. Time becomes a direct cash saving only when corresponding spending actually disappears. Keep "capacity gained" and "cash saved" separate in your decision.

The model may also understate value. Fewer questions, quicker visibility and easier staff cover can matter. Assess such benefits openly, but do not invent a monetary value without evidence.

Use three scenarios, not one preferred number

Alongside the expected case, calculate a cautious and a stressed version. At half the volume, the example releases 11.25 hours. Its assumed value of EUR 393.75 does not cover EUR 450 monthly support, so there is no positive contribution and no break-even. With review doubled to 3 minutes per document, 15 hours or EUR 525 of valued capacity remain. After support, the contribution is EUR 75; 11,500 / 75 = 153.3, or 154 complete months. An additional interface change would weaken the result further. This shows whether the project works only under ideal assumptions.

Before approval, define what the fixed price includes: interface setup, failure routes, tests, documentation, training and handover. For ongoing support, ask about included support hours, the response route and the cost of additional changes. Compare quotes only at equivalent scope. A low build price without an operating plan is not directly comparable with a supported workflow.

Set a decision point after the pilot. If volume, review time or technical reliability materially misses the agreed baseline, the business can reduce scope, standardize inputs or stop before committing further cost.

Build your own calculation

For two to four weeks, record case volume, active handling time, errors and rework. Then estimate conservatively what proportion can run automatically and how much review remains. Calculate a cautious scenario and test what happens with half the volume or higher support cost.

An automation pays off when verifiable benefit exceeds full cost within a period that suits your business. To document scope, baseline and operating cost together, the DevSeal process check provides a concrete basis for the decision.