About
Two people.
One craft.
“Time is rarely lost where you assume it is. So we measure before we cut.”
— The NLS principle
01 — Founders
Who sits at the
table with you.
N
Co-founder
Noel Payano Diaz
The initiator
The idea started with Noel. In the summer of 2025 he set out to learn what AI-driven processes can actually do for a business; in December 2025 that became NLS. After his commercial apprenticeship (Kaufmann EFZ), he now works as a Digitalization & AI Developer, including on the Odoo ERP system. He is the one who moves first: a question becomes a conversation, a conversation becomes a prototype, a prototype becomes a system.
Co-founder
Urim Krasniqi
The architect
In the autumn of 2025 Noel showed him what he had been building, and Urim joined as co-founder soon after. After his apprenticeship in ICT support, he now works as a System Engineer, in second-level support and device management with Microsoft Intune. He sees every day where IT gets stuck inside a working business. So where Noel acts, Urim weighs: which problems AI can solve, which it cannot, and how a system must behave before it earns a place inside a client's business.
One moves. One weighs. The work happens in between.
02 — Origin
Small,
on purpose.
NLS began with an observation you can make in almost any company: there is one process everybody agrees takes too long, and nobody with the time to change it. Meanwhile the AI industry sells platforms meant to do everything, and therefore none of it properly.
From Uster in the canton of Zürich, we design, build and operate every system ourselves. Nothing is outsourced, nothing handed to a freelancer you never meet. Whoever built the system also answers the phone when it jams.
There are two of us. That isn't a phase we're passing through — it's a decision: every engagement is led by one of the founders, from the first conversation through to daily operation.
03 — Standards
What you can
hold us to.
Not values — three commitments you can check we kept.
I
The number comes before the build
Effort, monthly cost and duration are fixed in writing before anything is built. If something is added along the way, we ask first — not on the final invoice.
II
Acceptance, not delivery
What the system must be able to do, we agree before the build. If it doesn't meet those criteria it isn't finished — regardless of how many hours are already in it.
III
You can leave at any time
Configuration, data and documentation are yours and are handed over on request. No minimum term on operation, no format you can't get out of.
04 — Begin
A small studio.
An uncompromising standard.
We stay deliberately small. That limits how many engagements we can carry at once — and guarantees that each one is led by a founder.
Arrange a conversation
→
