Skip to content

Basics

AI automation in SMEs: where it pays off and where it does not

By Dominik Natter · Last updated on 1 October 2026 · 2 min read

In short

AI automation pays off in high-volume processes where people read unstructured content and transfer it into a system: invoices, enquiries, emails, forms. It does not pay off when the volume is small or when errors cannot be caught by a check. What matters is human approval for uncertain cases, an audit trail and a written agreement on where the data is processed.

What language models can do reliably today

  • Read documents: invoices, orders, delivery notes, forms.
  • Classify messages: type of request, urgency, language, team responsible.
  • Match content: line items in an enquiry to items in the master data.
  • Write drafts: replies, quote texts, summaries.

Where caution is called for

Language models do not calculate reliably and do not know your prices. Anything that has to be exact belongs in your systems: amounts, terms, stock levels. The AI reads and suggests, the ERP calculates and posts.

Only cases where an error is cheap or certain to be noticed should go through unchecked. Everything else needs approval by a person.

Workflow tool or business application?

Tools such as n8n connect systems quickly and at low cost. For a manageable workflow that is the right choice. As soon as permissions, an audit trail, high volumes, error handling or a user interface for approvals are needed, the workflow becomes an application that has to be developed, tested and operated.

The difference shows in day-to-day operation: what happens when the ERP does not respond, an invoice arrives twice or the model is unsure?

Data protection in five points

  • Agree processing in a European region.
  • Rule out the use of your data for training by contract.
  • Give the model only the data the task requires.
  • Define how long logs are kept and when they are deleted.
  • Train staff and document the human approval step.

Legal framework

The GDPR applies in Liechtenstein and the EU, the revised Federal Act on Data Protection in Switzerland. Both require transparency about which data is processed and for what purpose. The EU AI Act additionally regulates the use of AI by risk level. The applications described here generally do not fall into the high-risk category. A case-by-case assessment still belongs in every discovery phase.

Typical use cases and effort

Email inbox triageCHF 12,000 to 30,0004 to 8 weeks
Creating quotes from enquiriesCHF 20,000 to 50,0006 to 12 weeks
Invoice capture with bank reconciliationCHF 25,000 to 60,0008 to 14 weeks

Frequently asked questions

How do you stop the AI from making mistakes?

By never letting it decide alone where mistakes are expensive. Every extraction is given a confidence score, uncertain cases go to a person for approval, and every decision is logged. Before go-live we measure the accuracy rate on your real data.

Where does our data go when AI is involved?

We set that out in writing for each project. The default is processing in a European region, under contracts that rule out any use of your data for training. For sensitive data, self-hosted models are an option. Hosting and database are located in the EEA, and processing is designed around the GDPR and the Swiss Federal Act on Data Protection.

Do you work with n8n or build your own software?

Both, depending on the case. n8n suits manageable workflows between existing systems, and your team can help maintain it. As soon as audit trails, permissions, high volumes or a dedicated user interface are needed, a purpose-built application is more robust. We often combine the two.

Matching services:AI automation

Let us talk about your case.

20 minutes are enough to find out whether a custom solution is worth it for you.