PIPELINEGuide
AI automation: ongoing costs and operations
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, AI automation typically requires a few hours of maintenance per quarter, plus hosting, licenses and usage-based third-party fees. The most frequently forgotten item is not the money but the responsibility: systems become outdated because nobody is designated, not because maintenance is demanding.
01 — Operation
What ongoing operation means
After settling in, the effort is low but not zero. For AI automation, this is typically a few hours per quarter: additions when something changes in your offering, a look at 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
Does our data end up in a language model's training?
No. We exclusively use access where training with customer data is contractually excluded, and we process in the EU. For particularly sensitive data, we use models that run on your own infrastructure.
What does the EU AI Act say about this?
Most business use cases fall into the low-risk category and primarily trigger transparency obligations. Where customers interact directly with the system or AI-generated content is published, we label it. For applications in HR, we look more closely — stricter rules apply there.
How does this differ from a chatbot?
A chatbot answers questions in dialogue. AI automation runs in the background without conversation — it reads, categorizes and pre-decides while someone else is focused on the actual work.
What if the documents or formats change?
As long as the content meaning stays the same, the system handles it well — unlike rigid, field-based recognition. Fundamentally new document types need brief adjustment, not a rebuild.
Do we need large amounts of data for this?
No. Unlike traditional machine learning, a few dozen good examples are enough for most use cases, because the language model already brings language competence.
Can we start small?
That's the only sensible approach. One use case, eight weeks, measurable outcome. What comes next, you decide based on what you've seen.
What's the difference from regular automation?
Regular automation follows fixed rules: if field A is filled, do B. AI automation comes into play where there are no fixed fields — free text, images, changing document formats. The right answer is usually both together, not one or the other.
05 — Next
Related pages
- AI automation — Overview
- AI automation — common mistakes
- AI automation — DIY
- AI automation — Contract and ownership
- AI automation — data protection
- AI automation — Alternatives
- AI automation — AI disclosure
- AI automation — Small businesses
- Process automation
- Document processing with AI
- AI knowledge base
- All guides
AI automation by region
Next step
Send us a few sentences about your project.
We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.