Part of Process automation.

AI automation
for everyday work.

Your process has clear steps.
The information does not
always fit a form.

We use AI at that point in the process. It interprets the message, document or image. Your business rules then decide what happens next, with a person involved where the task needs their judgement.

A customer explains a request in their own words. A supplier sends a document in a new layout. Before the process can continue, someone has to work out what the information means.

01 / Where it helps

Where does AI help
an automated process?

Use AI where the next step depends on understanding meaning or recognising a pattern. If the information is already structured and the rules are clear, ordinary automation can handle it.

01

Understand an open-ended request

A customer asks to change an order in their own words. AI identifies the requested change. The workflow finds the order, checks what is allowed, makes the change and confirms it.

Missing or conflicting details go to a person.

02

Work with changing documents

Suppliers send order confirmations in different layouts. AI finds the products, quantities and delivery dates. The workflow matches them to the purchase order and updates expected deliveries.

Price or quantity changes follow your review rules.

03

Recognise a visual issue

AI checks inspection photos for signs your team has defined, such as a missing label. The workflow sends possible issues for review and records the final result against the job.

People confirm findings. We test with your own images.

These are examples of possible projects. We agree the tools, access and checks with you before building.

02 / How it could work

From a delivery question
to a useful answer.

A customer emails to ask where their order is. AI helps the workflow understand the question, even when the wording changes. The answer comes from your order and delivery systems.

  1. 01

    Receive

    Save the customer’s email and keep the original message.

  2. 02

    Interpret

    AI identifies a delivery question and picks out any order reference in the message.

  3. 03

    Check

    Match the customer to the right order, then get its delivery status and tracking link.

  4. 04

    Respond

    Send the verified delivery update when the request meets your rules. Other requests go to a colleague.

  5. 05

    Record

    Save the response against the customer’s order so the team can see how the enquiry was handled.

What if the message or order is unclear?

If the customer cannot be matched, the request has several meanings or delivery information conflicts, a colleague gets the original message and the facts found so far. The workflow does not invent a delivery date to finish the reply.

AI helps understand the question. Your systems supply the order facts, and your rules decide what can happen next.

03 / Planning the first version

What needs interpretation?
What needs a person?

We look at the point where the process needs to understand something, then decide what can continue automatically and what needs a person. The checks should match the consequences of getting it wrong.

Examples to test with your team
SituationWhat should happen
Different wording, same requestRecognise the intent and follow the agreed process.
Information in a new layoutFind the needed details and check them against the original.
Missing facts or several possible meaningsAsk for clarification or pass the task to a person.
A request outside your rulesKeep it for review rather than making a new policy decision.
Structured information with clear rulesUse ordinary automation if AI adds no useful interpretation.
05 / How we work together

Test the interpretation.
Then connect the next step.

We agree what the first version should do, how to check it and who will look after it. Then we work through it with your team.

  1. 01

    Find the step that needs interpretation.

    We follow the process with your team and identify what someone has to understand before the next step can happen. We check whether ordinary rules are enough.

  2. 02

    Test examples from your work.

    We try the typical requests, unusual wording and difficult cases together. We check both the interpretation and the time your team still spends reviewing it.

  3. 03

    Connect the checks.

    We add the rules and approvals needed before a result can move to another tool or affect a customer.

  4. 04

    Keep checking after launch.

    We agree who reviews quality, handles problems and tests changes to the AI or the instructions it follows.

06 / Access and upkeep

Know where the answer
came from.

Know where data goes.

We agree which documents the AI can use, where they are processed, how long they are kept and the provider’s terms for using them.

Keep important decisions with people.

We agree who reviews unclear results. Accounting decisions, contracts and decisions about people need the appropriate person involved.

Test changes first.

A new AI model or a change to its instructions can change the result. We test it against the agreed examples before using it in live work.

Look at the mistakes too.

We track missing details, wrong categories and corrections, so your team can see when the setup needs attention.

07 / Questions before you start

AI automation questions.

What does a first project cost?

First projects start from CHF 4,800. We test the interpretation step on examples from your work before agreeing the full build. The proposal covers scope, timing, AI usage and the checking your team will still need to do. A workflow means one complete business task, or a connected set of tasks, automated from start to finish. It may take several n8n workflows, other tools or pieces of code to deliver that result.

When does AI help more than ordinary rules?

When someone needs to interpret changing language, documents or images. If the information is already structured and the rules are clear, ordinary automation may be simpler and cheaper.

Can it read our formats and languages?

We find out by testing examples from your work. We agree the formats and languages to support and what happens with anything outside them.

How do you check mistakes?

We test a shared set of examples and look separately at wrong categories, missing values and invented details. We also measure how much checking your team still needs to do.

What will a person still review?

We agree that around the consequences of a mistake. A draft summary can need different checks from an accounting change or a message to a customer.

What if the AI is unsure or stops working?

The original is kept. The task can wait, retry safely or go to a person, depending on what we have agreed. Missing information should not be filled in with a guess.

Where is our data processed?

We check the actual AI provider, connected tools and contract, including storage and any use for training.

What happens after a pilot?

We review whether it meets the agreed checks and is worth using. Before launch, we agree connections, approvals, support and who watches the quality of real results.

Which step needs someone
to make sense of the information?

Walk us through one process and the messages, documents or images it receives. We’ll look at where AI could help it move forward.

Book a first call