Guide
Process automation: ongoing costs and operation
The project price is only part of the calculation. What actually arises in effort and costs after going live — and which item is most often forgotten.
After going live, process automation typically requires a few hours of maintenance per quarter, plus hosting, licenses, and usage-based third-party fees. The most commonly forgotten item isn't the money, but the responsibility: systems become outdated because no one is assigned, not because maintenance is complex.
01 — Operation
What ongoing operation means
After the settling-in period, the effort is low, but not zero. For process automation, that's typically a few hours per quarter: additions when something in the offering changes, a check of the logs, occasional corrections.
More important than the scope is the responsibility. Systems don't become outdated because maintenance is demanding, but because no one is assigned. One person with a recurring calendar appointment solves this problem completely.
What additionally arises on an ongoing basis depends on the setup — hosting, licenses and third-party usage-based fees belong in the same calculation as the implementation. We show this separately in the quote instead of hiding it in the project price.
02 — Factors
What drives the price
- Scope and number of integrations. Every additional system that needs to participate costs effort — regardless of how simple the core is.
- State of your starting point. Clean data, existing content and documented processes significantly reduce effort. Chaos is the most expensive cost factor.
- How much new material needs to be created. What you can contribute doesn't need to be invented by anyone. This is the biggest lever you have in your own hands.
- Requirements for design and customization. A solid standard system costs a fraction of a custom solution — and is sufficient more often than vendors admit.
- Operating model. One-time project costs or ongoing support: calculated over three years, this often gives a different picture than the quote comparison.
03 — Contract
What needs to be clarified in writing
- Ownership of data and access. They belong to the client. If a provider won't clearly confirm this, that's the most important information from the conversation.
- Handover upon termination. In what format, within what timeframe, at what cost.
- No minimum term without consideration. Lock-in is justifiable if something is delivered in return — otherwise not.
- What a later change costs. The total cost isn't determined by the project price, but by the hourly rate in year three.
- Documentation as a deliverable. Not as a promise, but as a line item in the proposal.
04 — Questions
Frequently asked questions
Are there subsidies for this?
For digitalization projects in Austria, there are several funding programs, such as KMU.DIGITAL or the aws digitalization funding (kmudigital.at, aws.at). Whether and to what extent this currently fits your situation, we check together — important: The application must be approved before the contract is awarded. Plan lead time for this.
How quickly does it pay off?
For the processes we typically start with, payback is between four and ten months. We calculate that before the quote, not after.
Do we have to buy new software for this?
Usually not. Most of it runs on the systems you already have, plus an automation layer. We only suggest new software if there's a real gap.
How do we know what's worth automating?
Rule of thumb: A process is worth it if it occurs at least weekly, has clear rules and is manual work today. In the current-state analysis, we calculate every candidate — frequency times duration times cost — and you decide based on numbers.
Do we lose control over our processes?
On the contrary: An automated process is fully documented and logged for the first time. You see every run. Before, only the person who always did it knew.
What if our processes change?
Then the workflows are adjusted. We build them so that the variable parts — text blocks, recipients, thresholds — are in a table that you maintain yourself, without needing us.
What happens to the people who used to do this?
In practice, a position rarely disappears — the part of the work that nobody liked disappears. The time goes into things there was never time for before.
05 — Next
Related pages
- Process automation — Overview
- Process automation — Duration
- Process automation — contract and ownership
- Process automation — Where to start
- Process automation — data protection
- Process Automation — Common Mistakes
- Process automation — Measuring success
- Process Automation — Implementation
- AI automation
- CRM integration
- Automate Quote Creation
- All guides
Process automation by region
Next step
Let's talk briefly about whether this makes sense for you.
A twenty-minute conversation is usually enough to clarify whether a project makes sense. If not, we'll say so — that's cheaper for both sides than an offer nobody needs.