XERP

The problem in context

A general business system gives you two decades of accounting, stock and sales logic on the first day. What it does not give you is a product. Its screens are built to cover every industry, which means they fit none of them closely, and the vocabulary a distributor or a clinic actually uses sits three menus deep behind terms nobody in the building says out loud.

The second problem is heavier. A service designed for separate businesses needs an isolation boundary that does not depend on every permission rule being perfect. In business software, one isolation failure could expose one business’s ledger to another.

Who it is for

A finance manager closing a month. A storekeeper receiving a delivery at the door. A salesperson who needs a price approved before the customer changes their mind. An owner who wants one number without asking three people for it. They are not the same person and they do not want the same screen, but they are all looking at the same underlying figures — which is exactly why those figures have to be single and undisputed.

The separation decision

There were cheaper ways to keep companies apart than the one we took. Every cheap way puts the guarantee in the hands of a rule that somebody has to remember to write, and remember to write correctly, for as long as the product exists. We put the boundary lower down instead, so one company’s records are simply unable to appear in another company’s report, whatever anyone forgets.

That decision changes the engineering work. Cross-business operations are no longer cheap; provisioning a business becomes a tested software workflow; and routine changes have to be applied reliably to each database. We accepted that cost because the alternative is a guarantee that depends on vigilance.

What it demanded

The discipline is in what we refuse to do. No screen may step around the permission checks for convenience, because one such shortcut undoes the whole model. And no area is half-replaced: a rebuilt area covers every list, form and action it used to, or it is not begun — leaving people to hop between an old interface and a new one is worse than either alone.