Does automation have to use AI?
No. I add AI only where text, meaning or variable input requires it. Exact rules are better handled by a standard integration.
I connect manual steps across email, forms, CRM, documents and task systems into a controlled automated workflow.
A working automated flow with clear control points, error notifications and the option for manual intervention.
We map the current steps and exceptions.
We separate routine work from decisions that stay with people.
I connect the tools and configure error states.
We test the flow and I hand it over with operating documentation.
The exact method depends on the product edition, licences and interfaces enabled for your account. I verify it before scope is agreed.
| System | Connection | Required |
|---|---|---|
| ABRA Flexi | REST API, read and write | API user |
| Fakturoid, iDoklad, Raynet | REST API | API key |
| POHODA | mServer — XML over HTTP | continuously running instance and appropriate licence |
| Money S3 | API module or XML import | active API module or agreed import |
| Helios (Orange, Inuvio, Green) | scheduled XML/CSV export or available API | cooperation from the Helios administrator |
| Shoptet | REST API and webhooks | available API; otherwise an add-on or XML feed |
Automation fits a workflow with known triggers, rules and outputs. I first remove unnecessary steps and document exceptions. I then connect forms, email, CRM, documents or tasks so that information moves without manual copying.
Each flow has an owner, logs, error alerts and a manual recovery path. AI can support a text or document decision inside the flow, but there is no reason to use a model where an exact rule or ordinary API is safer.
The categories can be combined, but each should solve a different part of the problem.
| Option | Use it when | Main output |
|---|---|---|
| AI audit | You need to choose a priority | Opportunity map and first step |
| AI agent | The task needs context and tool use | A controlled role with human oversight |
| Automation | The steps follow clear rules | A connected and monitored flow |
| Application | Standard software does not fit | A focused interface and data model |
| Consulting | You face one concrete decision | Independent recommendation |
| AI search visibility | The site needs stronger eligibility and content | Technical and editorial plan |
| Starting price | Included | Timing | What I need from you |
|---|---|---|---|
| A focused workflow automation starts at approximately €5,000 excluding VAT. Typical tool operation costs €15–€60 per month on your own accounts. Pricing depends on the number of steps, integrations, monitoring requirements and operational risk. | current workflow description, automated flow design, integration of your existing tools, testing, monitoring and hand-over | Timing depends on the number of systems, the quality of their APIs and the number of exceptions. I confirm the schedule after mapping the workflow. | A sample case, a list of the tools involved, the necessary access and someone who understands the workflow exceptions. |
No. I add AI only where text, meaning or variable input requires it. Exact rules are better handled by a standard integration.
I check exports, webhooks and reliable connectors first. If no safe integration exists, I design a controlled manual step or recommend another tool.
The flow records the error, alerts an owner and supports a retry or manual completion. Failure handling is part of design and testing.
Yes, when the original flow is documented and has clear boundaries. Additional steps should follow validation of the basic version in production.
Timing depends on the number of systems, the quality of their APIs and the number of exceptions. I confirm the schedule after mapping the workflow.
A focused workflow automation starts at approximately €5,000 excluding VAT. Typical tool operation costs €15–€60 per month on your own accounts. Pricing depends on the number of steps, integrations, monitoring requirements and operational risk.
A sample case, a list of the tools involved, the necessary access and someone who understands the workflow exceptions.
Automation will not fix a process without clear rules. Ambiguities and unnecessary steps need to be resolved first.