PIPELINEGuide
AI automation: contract, ownership, and exit
Who owns the data, access credentials, and outputs in the end? The answer to this question says more about a provider than any reference list — and belongs before the signature, not after.
Before commissioning AI automation, it should be clarified in writing: data and access belong to the client, in what format and within what deadline they will be handed over upon termination, what a later change costs, and that documentation is a quoted line item and not a verbal promise.
01 — 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.
02 — Questions
Questions you should ask
- What happens if the project becomes more expensive than estimated — who bears that?
- Who owns data, access, and, if developed, the source code?
- What does operation cost in the second and third year?
- What does the documentation we receive at the end look like?
- How would you measure whether the project was successful?
- Is there a case in which you would advise us against this?
03 — Warning signs
When to be skeptical
- Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
- No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
- Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
- Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
- No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.
04 — Questions
Frequently asked questions
How reliable is it?
That depends on the use case, and we measure it before anything goes live. For classifying incoming messages, well-built systems regularly exceed ninety percent. What matters isn't the rate alone, but what happens when there's an error — that's why we always build in a confidence threshold.
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.
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.
How do we keep track of automatic decisions?
Every decision is logged: which input, which result, which confidence level. You can spot-check this anytime, just like with a human deputy.
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.
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.
05 — Next
Related pages
- AI automation — Overview
- AI automation — Integration
- AI automation — Process
- AI automation — AI disclosure
- AI automation — Measuring success
- AI automation — costs
- AI automation — DIY
- AI automation — How it works
- Process automation
- Document processing with AI
- AI knowledge base
- All guides
AI 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.