Modules

One company, ten ways in

Each module covers one area of work: finding customers, selling to them, serving them, delivering what was sold, buying what is needed, keeping stock, controlling budgets and cash flow, organising people, running projects and making decisions. They share one model of the company: all of them read and write the same records through the same ontology, which is why a quote in commerce already knows the open complaint in customer service and the overdue invoice in finance.

Adopted one domain at a time

Replacing everything at once is how programmes like this fail. So each module is built to run alongside the systems a company already has: import the records it needs, keep the old system connected while the two overlap, and retire it once the new record has proved itself. The next module then starts with data that is already there. Some systems stay for good: full accounting runs in a dedicated accounting program, which Finance connects to.

The same rules everywhere

Every module works the same way underneath. Agents prepare and propose; on critical steps a person decides; every action is logged. Proposals from all ten land in one approval inbox, which is the Decisions and Tasks module, and every module is extended the same way: by describing what is missing and letting an agent build it on the shared model.

Each module page says what it covers and how it works with the systems a company already runs.