How we build
Separate systems, one standard.
Every product we build is its own system, with its own customers, its own data and its own set of books. They are not one platform in different colours. What they share is the standard they are built to, and that standard is the reason an accountant can trust any of them.
First, the honest part
Nothing is shared between the products
No shared database, no shared ledger, no shared instance. A school running one system and a salon group running another have nothing in common at runtime, and neither can affect the other. That is deliberate: they are different businesses with different regulators and different working days, and a layer that tried to serve all of them would serve none of them well.
What carries across is the set of rules each system is built to. Those rules are below, and they are the same in every product regardless of sector.
The standard
What is true of every system we build
Each of these is a rule about how the software has to behave. Not a feature list, but a floor that a system has to meet before it goes anywhere near a customer's money.
Separate by tenant
Each school, group or company gets its own workspace, its own users and its own books. No two customers share a set of records.
Double-entry throughout
A fee invoice, a salon bill, a production issue: every module posts a balanced entry as it happens, rather than reporting alongside the books.
Many places, one view
Campuses, branches or companies each keep their own accounts and stock, and roll up without anyone re-keying a figure.
Audit trail
Who posted what, when, and what it looked like before. Every financial action, in every system.
Rights per user
What someone can see, post and approve is set per person, not handed out with a shared login.
Reports you can build
A report builder and Excel and PDF export in each system, so a figure nobody anticipated does not need us to produce it.
Some capabilities are just as real and are not on this list, because they are not true everywhere. Weighted-average costing and bill of materials matter to a manufacturer and a salon and mean nothing to a school, so they are described on the pages of the products that have them rather than claimed for all of them.
Per system
The detail is on each product's own page
Every product page shows where a figure in that system comes from: the places the work happens, the posting rule in between, that system's own accounts, and the reports read back out of them. Under it sits one real transaction, posted line by line.
See it on your own accounts
Bring your own chart of accounts
A demo runs on your accounts and your branches, not a sample company. If you keep the books for a business, come with the report your current setup cannot produce and we will show you where each line lands.