Nine spaces, not a list of sixty items
Around sixty technical domains sit underneath NG One. A user never sees one of them as a menu entry. The system is divided into nine business spaces instead — the way the work actually divides, rather than the way the code was written.
- 9 business spaces
- ~60 technical domains
- 270 named capabilities
- The same division you meet in the product
Why spaces rather than modules
A menu of sixty equal entries is a menu nobody reads to the end — so the work returns to whoever remembers where things are.
A system that covers the whole business contains the whole business: procurement, stock, production, the general ledger, tax records, payroll, documents and reporting. Technically that is around sixty domains. The usual answer is to put all sixty in the menu, alphabetically or in the order they were built, and leave the user to learn the map. The cost does not show in a demo; it shows six months in, when a new hire cannot find where their work happens and an old hand can — so the work piles up on the old hand.
NG One does not surface that division. The first level of navigation is nine business spaces, and each answers 'what am I doing' rather than 'which module was this written in'. The domains stay underneath, where they belong — the space groups them by the work done in it, so an accountant enters Finance and compliance instead of choosing between nine modules that each hold a piece of the tax records.
Nine is not a round number picked for a website. The product's information architecture fixes it: the first level of navigation has exactly nine ways in, and under them thirty named capabilities per space — 270 in all. The arrangement you see here is the one a user meets at sign-in; this grid is not a marketing rendering of the system, it is the system.
The nine spaces
Each space shows how many named capabilities it covers. The figure is computed from the same registry that space's page is built from — no number here is typed by hand.
My work
The personalized home screen: decisions and exceptions, tasks and approvals, an AI daily brief, and what NG One finished on its own.
30 capabilitiesSales and customers
From opportunity to cash, in one chain with nothing retyped.
30 capabilitiesProcurement and suppliers
From need to payment: purchase orders, receipts, invoices, and a landed cost that stays correct after customs arrives late.
30 capabilitiesInventory and logistics
Stock on hand, goods in motion and value on the ledger — one record, reconciled at all times.
30 capabilitiesProduction and operations
Engineering data, planning, shop floor, quality and projects in one flow — with a product cost that is not assembled after the fact.
30 capabilitiesFinance and compliance
Serbian statutory accounting, dimensions and VAT — in the core, not bolted on.
30 capabilitiesPeople and organization
Employees, working time, absences and Serbian payroll — in the core of the system, not in a separate program next to it.
30 capabilitiesDocuments and processes
One document kernel, one approval path and one decision trail — underneath every document in the system.
30 capabilitiesInsights, automation and AI
The command center for decisions — evidence behind every insight, a trail behind every automation.
30 capabilities
Thirty named capabilities per space, 270 in all, with around sixty technical domains underneath them. A capability is named the way it behaves on screen: what is not in the system is not on this list either, so the number is scope rather than ambition.
Start with the space closest to your work
We run the walkthrough on your processes rather than on demo data — your documents, your chart of accounts, your dimensions.