Case study · Manufacturing
Cloud ERP for manufacturers
A full enterprise resource planning system, delivered as a monthly subscription and customised per company — without the codebase splitting into thirty versions of itself.
30+
Companies running it
1,200
Users
9
Modules
2
Regions
The brief
Run the whole company, not one department.
Manufacturing companies were working across spreadsheets, a warehouse tool and an accountant's system that never quite agreed with each other. The brief was one platform where a purchase order, the stock it creates, the invoice it triggers and the tax it attracts are the same record seen from four angles.
Delivered as a cloud subscription with monthly billing, so a mid-sized manufacturer could start without buying servers or a licence up front.
Modules
- Procurement
- Sales
- Invoicing
- Tax
- Inventory
- Item and partner master data
- Users, roles and permissions
- Integrated payments
- Subscription billing
The hard parts
Three problems that decide whether an ERP survives.
01 — Customisation
One codebase, thirty companies
Every manufacturer wants its own workflow. Branch the code per client and within a year you maintain thirty products. Configuration is held as data, not as forks, so a new customer is set up rather than developed.
02 — Permissions
Rights down to the single action
A warehouse clerk may book stock but not release a payment; a controller may see margins nobody else does. Permissions are per operation per module, and every screen and endpoint enforces the same matrix.
03 — Tax
Two regions, two rulebooks
The system runs in Central Europe and the MENA region. Tax rules live in a replaceable layer instead of being welded into invoicing — which is what makes moving an ERP to another country harder than writing one.
What it proves
Long-lived business systems, carried end to end.
Thirty companies and 1,200 users mean the system is lived in daily, not demonstrated occasionally. That is a different discipline from shipping a front end: data has to stay correct for years, upgrades cannot interrupt invoicing, and every change meets an audit trail.
Have a system like this to build or take over?
We reply within one business day.