The part of the loop nobody automated.
A decade of supply chain software solved visibility. Closing the loop afterwards is still manual work. nudu automates that part.
The starting point
Diagnosis is already solved across most operations. The systems detect the exception and display it on a dashboard. The work that follows the alert still happens outside those systems, in supplier calls and parallel spreadsheets that repeat a question already asked the month before.
That work appears on no org chart and it does not scale. Adding coordinators multiplies the volume. Adding visibility software multiplies the signals without resolving them. The only way out is a system that takes the case and closes it with the answer on record.
nudu occupies that place and no other. It does not plan and it does not replace the systems already in operation. It turns a signal into a resolved, recorded action, and it stops where the decisions that require human judgment begin.
Design criteria
The four implementation principles.
-
Scope narrowed by design
nudu closes the loop on an exception, and it does so in any domain of the chain, from procurement to distribution. Adding planning or forecasting would require replacing the systems the operation already runs, and nudu would stop being a layer.
-
Every client, a directory of rules
A client is defined in a directory of rules. When a new case requires opening the core of the engine, the problem is in the design and it is corrected there.
-
Silence by default
The product intervenes only on exception. Constant notification trains an operations team to ignore it, and the system loses its purpose.
-
Evidence on every case
Every case keeps the information it was decided on. A wrong judgment stays visible and is corrected, and the case is escalated to human supervision when it requires it.
The team
A small team, with direct responsibility for the product and its implementation.
-
Tomas
CEO
Leading the vision of the business and the relationship with the operations teams involved in the development of nudu.
-
Joaquin
CTO
Architect of the engine and the interface, and lead of the technical work.
-
Facundo
COO
Directing day to day operation and the brand identity of nudu.
-
Olivia
CPO
Product and market. Defining what nudu builds and in what order.
-
Imanol
Founding engineer
Ensuring the quality of every flow and opening contact with new operations.
A real case, from signal to record.
The conversation starts from a specific exception in the operation and runs the full loop, from the signal through to the recorded action.