What clients
ask first.

It turns on four quantities: the complexity of the process, the number of connected systems, the processing volume and the level of support. As orientation, a simple automation starts at around CHF 840 a month and a standard workflow sits between CHF 1,700 and 5,000. The binding figure comes out of the analysis — before that it would be a guess. All the indicative ranges and what drives them.

First conversation 60 minutes, analysis one to two weeks, prototype two to four weeks. A simple process can therefore be in production around six weeks after we first speak. Cross-functional projects with deep integrations take longer — we say so in the analysis, not afterwards.

Nothing, neither of them. You describe the process that costs you the most time; we build a demo from it and show it to you in an hour, with nothing to sign afterwards. We do it because our work explains itself better against your own process than in a brochure.

Not on operation. Analysis and prototype are fixed prices with a scope agreed in advance; ongoing operation is billed monthly and can be cancelled monthly. If the system isn't carrying its weight, you stop.

On our word alone, you shouldn't. That is why the engagement is built so you don't have to believe us: effort, monthly cost and duration are fixed in writing before anything is built. What the system must be able to do is agreed beforehand as acceptance criteria. Operation is cancellable monthly, and configuration, data and documentation are yours and can be handed over.

The advantage of two people: a founder runs your project, not a rotating junior. The disadvantage: we can't carry unlimited engagements at once — and we say so before the contract rather than after.

None we could show you. NLS is young. We won't put up client logos that don't exist or savings figures we haven't measured. What we offer instead is the free demo: you see how we think and work against your own process before any money moves. We think that is more honest than a wall of logos.

For the prototype, the acceptance criteria agreed before the build apply. If it doesn't meet them it isn't finished — regardless of how many hours are already in it. In ongoing operation, the monthly cancellation applies. And we build processes so the previous route keeps working: one switch halts the system without halting your business.

Client systems run in Swiss data centres. Your data is never resold and never used to train anyone else's models; each client gets separate models.

One distinction, because it often gets blurred: this website runs on Cloudflare. The contact form we handle ourselves; only the notification to us goes via Mailjet in France. The website assistant runs entirely in your browser and sends nothing to us or to anyone else. All of it is set out openly in our privacy policy.

Currently as a simple partnership under Art. 530 ff. of the Swiss Code of Obligations, run by Noel Payano Diaz and Urim Krasniqi. A GmbH is in preparation; we'll publish the UID as soon as it is issued. The rest is in the imprint.

No. We build onto what already runs at your place — that is the point of a system cut to fit. Modern systems with a documented interface connect quickly; with a decades-old installation and no API, the connection becomes a project of its own. Which of those applies to you, we establish in the analysis, before anyone promises anything.

Yes, and it usually makes things easier. We work on one bounded process, not on your whole IT landscape. Your IT gets documentation and access; if they want to take operation over later, that is exactly what it is built for.

Often not. Plenty of processes are solved faster and more cheaply by a decent template, a rule or an interface than by a language model. If the analysis shows that, we write it down — you then pay for the analysis and for no project. We would rather give an honest no than build a system nobody needs.

German and English — conversations, documentation and support. The systems themselves can answer in further languages; which ones make sense depends on your users.