Book a call
Solution — Autonomous

Automate processes — and keep building yourselves

We analyse your processes, automate the right steps and train your team so you can add more workflows yourselves. Three setup tiers from a iPaaS start to orchestration.

Many SMBs have digitalised their processes — but not automated them. Data is moved manually between systems, emails are sorted by hand, documents are checked monotonously. That is not digitalisation, that is just PDF instead of paper.

We build your workflow pipeline once, cleanly, train your team and hand it over — afterwards you extend the system with new processes yourselves, without needing a fresh consulting engagement every time. Three setup tiers, depending on volume, technical depth in the team and compliance requirements.

Important upfront: not every process is worth automating. Automation pays off where operations occur often enough, are rule-based enough and are expensive enough when done by hand — but at the same time not so complex that edge cases overwhelm the system. If you prefer full consulting accompaniment instead of self-operation, the detailed service AI process automation is the right place to start.

Three setup tiers

Which tier fits depends on the number of workflows, the complexity of the business processes and the compliance requirements of your sector.

Tier 1

Lean — quick wins with iPaaS

Tool mix

  • Cloud iPaaS like Make, Zapier or Pipedream — ready to use, no self-hosting
  • Cloud AI via API (with DPA, EU region) for classification, extraction or text generation inside the workflow
  • Existing tools are connected through built-in connectors (mail server, accounting, CRM, cloud storage)
  • Simple triggers: webhook, scheduled execution (cron), new file in cloud folder
  • Configuration as a versioned export backup, so the workflow can be migrated to n8n later if needed

Best fit

Solo entrepreneurs, small teams, individual well-scoped routines (e.g. „file an incoming invoice as a task in the tool“). Limited technical depth on the team, fast first benefit desired.

Effort & cost

Setup 1–3 days. License costs around €20–100 / month (iPaaS plan + AI API account). No self-hosting required.

Tradeoff

You depend on iPaaS vendors — when prices rise or features get cut, you are at their mercy. Pragmatic for the first one to five workflows, but at a mid-double-digit workflow count usually more expensive and fragile than self-hosting.

Tier 2

Standard — n8n self-hosted with AI

Tool mix

  • n8n self-hosted (on a German VPS or your own server), with your own domain and SSL
  • Workflows with AI nodes for classification, text generation and OCR on receipts
  • Direct integration with line-of-business software via REST API, webhook or database connection — no replication into third-party systems
  • Robustness patterns: retry logic, dead-letter queue, idempotency for critical operations
  • Monitoring with Grafana and Telegram alerts on workflow failures, audit log of all executions

Best fit

SMBs with several interconnected processes (receipts, quotes, customer requests), able to connect to their own mail server and ERP, at least one technically savvy person on the team.

Effort & cost

Setup 6–12 days. Running costs around €30–80 / month (VPS + AI API + backups). No recurring SaaS licenses.

Tradeoff

More operational responsibility: n8n updates, API renewals, backup maintenance. In exchange the workflows belong to you — migratable when tools change, no lock-in when vendors change, documentable for compliance audits.

Tier 3

Full — Camunda orchestration with n8n and self-hosted AI

Tool mix

  • Camunda 8 for complex business processes with multi-stage approvals, escalations, time service levels and BPMN 2.0 as an open standard
  • n8n for connectors and data transformation, embedded as service tasks in Camunda processes
  • Self-hosted language model (Ollama with Gemma) for data-sensitive classifications, complemented by cloud frontier only for demanding texts with a DPA
  • Optional process mining on existing system logs to make the actual process flows visible before automating them
  • Full audit trail across all steps, versioning of BPMN models, test environment for larger changes

Best fit

Regulated sectors (banks, insurers, healthcare), enterprise processes with many stakeholders, workflows with clear human-in-the-loop requirements or check steps subject to documentation duty.

Effort & cost

Setup 12–25 days. Running costs around €80–200 / month (own server + AI hardware + backups).

Tradeoff

Highest flexibility and auditability, but also highest complexity. BPMN models have to be actively maintained — otherwise shadow workflows grow alongside the official model. Only worth it when processes genuinely need orchestration for compliance or complexity reasons.

Which process patterns are particularly suitable

Six patterns where automation in SMBs typically pays off quickly — across sectors, because the operations are structured similarly:

Receipt capture & inbound classification

Incoming invoices, delivery notes, bank statements get classified via OCR and AI, fields extracted, plausibility checked, handed over to the accounting system. The clerk only reviews exceptions instead of every document.

Quotes & sales routine

Classify request by email, build a template quote from material and price database, insert standard clauses from your own library, present to sales for review. Time saving on standard requests, human control before sending.

Route inbound communication

Classify emails (complaint / inquiry / order / spam), route to the responsible person or appropriate system, generate auto-reply suggestion. Reduces manual sorting, speeds up response times.

Onboarding & master data maintenance

New customer or employee is created — AI pre-fills standard fields, asks for missing data in a structured way, the workflow creates accounts in CRM, time tracking and accounting. Consistent master data without 30 manual steps.

Reports & reminders

Maintenance dates, follow-ups, contract renewals, KPI reports — as scheduled workflows with clear recipients. What happens on a cycle belongs in a workflow, not a calendar.

Compliance and audit obligations

Log data protection requests automatically, track deletion deadlines, collect audit trails of AI outputs. With a clear workflow compliance becomes reproducible — and not dependent on the discipline of individual employees.

What we teach

So you can add further processes yourselves after the pilot month, six areas of competence in workshop and accompaniment:

Process inventory

Which operations in the business are repeatable, rule-based and high-volume enough to justify automation — and which are better left manual. What an honest frequency and effort balance looks like.

Workflow design

How a workflow is planned before it is built: trigger, steps, error paths, idempotency, escalation. The model on paper saves hours of debugging later.

Using AI sensibly

When a deterministic rule node is enough and where a language model adds real value. Which tasks AI handles well (classification, extraction, standard correspondence) and which it does not (complex reasoning, legal judgement).

Robustness & monitoring

Retry, dead-letter queue, idempotency, alerting — the invisible disciplines that separate a stable workflow from a burning pipeline.

Compliance & audit trail

What GDPR says about automated decisions, where Art. 22 applies, how an audit log has to look so it is still readable in two years.

Workflow maintenance

Versioning, test environment, change log — workflows are code. Whoever runs them without discipline lives with invisible risks.

What gets automated

Six families of routine steps that workflows take over in operation — and that together make up most of manual office work:

Inbound classification

Emails, receipts, requests are automatically sorted into categories and handed to the appropriate processing.

Data extraction via OCR and AI

Structured fields are pulled from PDFs, emails and forms, plausibility-checked and written to target systems.

Cron and webhook triggers

Time-driven routines (daily, weekly, monthly) and event-driven workflows (new file, incoming payment, webhook from third-party system) run without human kick-off.

Cross-platform data sync

Master data and status updates flow between ERP, CRM, accounting and line-of-business software, without manual Excel lists anywhere.

Error handling & escalation

Workflow errors are logged, retried, parked in a dead-letter queue on persistent failure and escalated to the responsible person — instead of dying quietly.

Audit and compliance reports

Who triggered what when, which data flowed where, which AI classification was accepted or corrected — automatically logged and exportable on demand.

What stays MANUAL on purpose

Automation without human control is legally delicate and operationally risky in most SMB scenarios. These six points belong in human hands:

Process decision

Which processes get automated at all — that is a business decision with cost-benefit weighing, not a technical question. Workflow engines decide nothing, they only execute.

Approval of automated decisions

AI classifies, humans decide — for every operation with consequences (booking, contract conclusion, customer communication) it must be clear who approves. Full automation without human control is legally delicate and operationally risky in most SMB scenarios.

Maintenance of process models

BPMN diagrams, workflow templates, prompt libraries — they will silently age over time if no one maintains them actively. That maintenance is human discipline, not a workflow step.

Handling edge cases

When an operation falls outside the standard — new supplier, unusual contract constellation, legal exception — humans decide, not workflows.

Disaster recovery drills

Run a backup restore quarterly, test failover, document what did not work. Does not happen without human discipline.

Strategic workflow roadmap

Which workflows arrive next quarter, which get reworked, which are retired — that is an ongoing business process, not autopilot.

How the handover into self-operation works

From first workshop to self-operation typically 8–14 weeks — depending on tier, number of initial workflows and integration depth:

1

Process inventory

Which operations are repeatable, high-volume and time-intensive? Frequency, processing time, error rate, interfaces — a list with cost-benefit estimate as the foundation.

2

Pick a setup tier

Lean, Standard or Full — based on volume, existing technical know-how and the compliance requirements of your sector. Reasoned recommendation, you decide.

3

Workflow design

For the selected processes, define triggers, steps, error paths, AI insertion points and escalations as a clear model — on paper, before anything is built.

4

Build & integrate

Tools set up (n8n, Camunda as needed), integrations configured, AI prompts tuned to your domain, robustness patterns (retry, DLQ, idempotency) built in.

5

Pilot in parallel operation

First workflow runs in parallel with the manual process. Results are compared, edge cases documented, prompts and rules refined — only when quality is stable is full automation switched on.

6

Training & handover

2-day hands-on workshop with workflow owners: read, adjust and debug workflow logic. Maintain AI prompts. Interpret audit logs. Practise versioning.

7

Accompanied pilot month

First 4–6 weeks with weekly sparring sessions: integrate new edge cases, evaluate workflow performance, prioritise next candidates.

8

Self-operation with extension roadmap

From then on you maintain the workflows yourselves and add further processes step by step. Optional: quarterly refreshers and joint review of the workflow landscape.

Effort and investment depend on setup tier, number of initial workflows and the level of accompaniment — concrete numbers come after the inventory workshop, in the context of our pricing overview.

Ready for the next step?

Free intro call, no strings attached. In 30 minutes you'll know whether and how AI can help your business.

Book a callBAFA funding