Everything from SW labs
Most of what you do by hand every week follows fixed rules. A program that knows those rules is enough. I build AI in where whatever comes in looks different every time.
Whatever comes in. If it has the same shape every time, a rule is enough. If it looks different every time, AI can help read it. I figure that out for each process on its own, before I build anything.
What comes in
Fixed layout, fixed rule. No AI needed, and every invoice can be traced later.
AI suggests, a person confirms where it matters. For orders from the inbox, that looks like this:
AI reads
The email comes in, and the AI pulls out the quantity, the item and the customer and fills in the order.
Someone confirms
Someone in your business takes a look and sends it off. The typing goes away, the second look stays.
The rest follows rules
What happens next, booking, delivery note, invoice, runs on fixed rules. Nothing gets guessed after that.
Which model, and where it runs, are two questions.
The same model is often available in several places: from the maker, through Microsoft, Amazon or Google, on a server of your own, or right on the device. Which place fits depends on the data the process touches.
| From the maker | Microsoft Azure | Amazon Bedrock | Google Cloud | Ollama Cloud | Your own server | On the device | |
|---|---|---|---|---|---|---|---|
| Claude Anthropic | available, no promise on where it’s processed | available, no promise on where it’s processed | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | not available there | not available there | not available there |
| GPT OpenAI | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, no promise on where it’s processed | not available there | not available there | not available there | not available there |
| Gemini Google | available, no promise on where it’s processed | not available there | not available there | available, processed in the EU or on your own hardware | not available there | not available there | available, processed in the EU or on your own hardware |
| Mistral Mistral AI | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, no promise on where it’s processed | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware |
| Open models Llama, Qwen, Gemma, gpt‑oss | not available there | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware | available, no promise on where it’s processed | available, processed in the EU or on your own hardware | available, processed in the EU or on your own hardware |
As of October 2026, per the providers’ documentation. It changes all the time and differs from model to model. The proposal says which cell it’ll be for your process.
Where a mistake costs little, say an email lands in the wrong folder, you don’t need the second look. Where you do, we decide that together before we start, one process at a time. Which AI service runs behind it and what happens to your data along the way is spelled out in the proposal.
Usually the answer is no. That makes it simpler.