Automation and AI implementation
Once it is clear what to build and why, the hardest part remains: building it so that it keeps working after the contractor leaves. I work in iterations, show the first results within weeks, and leave the code and the access on your side.
When it makes sense
The most common reason companies fear an implementation isn't the price but dependence on the contractor. A system you can't take over is a running cost, not an investment.
- The last implementation works, but nobody except the contractor knows how to change it.
- Your data sits in several systems that don't talk to each other.
- The team does by hand something that repeats dozens of times a day.
- A project has dragged on for months and there is still nothing anyone can use.
What you get
A working system, in stages
I deliver in iterations. After each one you get something that really works, instead of waiting for one big launch at the end.
Code, accounts and access on your side
The system is built on your accounts, and the source code and documentation are yours. You can move them to another contractor without asking my permission.
Documentation and handover
A description of the architecture and instructions for whoever maintains it. The handover is part of the implementation, not an extra service.
Integration with what you already have
I connect your existing systems (ERP, CRM, spreadsheets, e-mail, databases) instead of talking you into replacing everything.
Optional support after launch
An ongoing maintenance contract, if you want one. If not, the system still works and is documented.
How it goes
Free intro call
30 min
We go through the problem and the scope. If the case is complex, I suggest an audit first rather than quote in the dark.
Proposal
2 working days
You get the scope, the timeline and the price. No hidden items and no billing by the hour.
Contract
2–5 days
Negotiation and signing. The terms of our work are set out in the Terms of Cooperation.
Implementation in iterations
Depends on the scope
I work in stages and show progress as I go. The first working parts usually arrive within 2–3 weeks.
Handover and support
After launch
Documentation, training for your team and, if you want it, an ongoing maintenance contract.
What it costs
from €1,500 net
I price the whole scope, not an hourly rate. The price depends on the number of integrations and the complexity of the process. I give it after the intro call or after an audit.
All prices are net of VAT. VAT is charged under EU rules, and a company in another EU country is invoiced under the reverse charge.
A 30-minute call on Google Meet. The calendar opens in a new tab, and the nearest free slots are usually within a few working days.
Common questions
How much does an automation implementation cost?
From €1,500 net. A simple connection between two systems usually sits at the lower end, and a staged implementation with AI costs correspondingly more. I price the scope, not the hours, so you know the price before we start.
How long does an implementation take?
From a few weeks for a single automation to a few months for a staged implementation. I work in iterations, so you usually see the first working parts after 2–3 weeks, not at the very end.
Who owns the code once the implementation is finished?
You do. I build the system on your accounts and licences, the source code and documentation pass to you, and the handover is part of the implementation. You can move the whole thing to another contractor without me.
Which tools do you work with?
I choose them for the problem, not the other way round: low-code and no-code platforms where they are enough, and conventional code (Python, .NET, SQL) where it is needed. If you already have a stack, I usually extend it rather than add another tool.
What if something stops working after launch?
Complaints and liability are governed by the contract. Separately, you can buy ongoing support with priority handling, or maintain the system yourself, because the documentation and access are on your side.
Will you take over an implementation someone else started?
Yes, as long as it can be taken over. Sometimes it is cheaper to rebuild a part than to maintain someone else's shortcut. I start by reviewing what exists and tell you plainly what I recommend.
Let's talk about your case
A free intro call, 30 minutes. If I can't help, I will say so straight away.
A 30-minute call on Google Meet. The calendar opens in a new tab, and the nearest free slots are usually within a few working days.