Nalu AI

A decision platform for demand forecasting that is configured per customer instead of hard-wiring industry logic. Design and engine are my work. It is not an offering, and there are no numbers for it yet.

What Nalu does differently

The entry point is not a dashboard but a list of decisions that are due, sorted by expected damage. Every entry names event, probability, impact, deadline, recommendation and cross-check. Classic reports remain, but as evidence to look up, not as the home screen.

A statement about the future has four parts instead of one: expectation, range, probability and hit rate. The last one is the uncomfortable one. It says how often the announced range actually held recently. Where accuracy is lacking, Nalu refuses the firm number and says why.

Where it comes from

Nalu is the generalisation of the platform work in project A. What is hard-wired there, cutting patterns, site logic, industry terms, is configuration in Nalu. Every customer would get their own instance on their own infrastructure; no data leaves their premises.

The name is Hawaiian and means wave. Data follows the same patterns as the sea: seasonality, trend, noise. Spotting the next wave and being ready for it, that is the idea.

Status

In the making, alongside my main job. The drafts below show the interface with sample data, no real customers and no real numbers. What comes of it will appear on this page once it is measured. Before that I claim nothing.

Six views, drawn

The interface as it would look for a fictional beverage wholesaler. Every view answers a question a classic dashboard does not ask. All values are sample data.

Today: The entry point is not a wall of metrics but the list of decisions that are due. Each names reason, drivers, recommendation and how good the model was here recently.
Forecast cockpit: What is coming, as a range rather than a single number. On the right, the breakdown of where the increase comes from.
Scenario: Options are calculated against each other and valued in euros. The rejected variant stays visible.
Forecast accuracy: Nalu discloses how often the announced ranges held recently. The page sits under Decide, not under Settings.
Purchasing: The service level is the dial. The question shifts from "how much do I order" to "how much risk can I afford".
Risks: Sorted by expected damage, not by urgency. That puts the right thing on top.