Figures as reported by the team and the operators. Client names and module details are withheld until documented and cleared for publication.
The problem
Factories and trading companies ran their day on separate records and procedures — stock in one place, invoices in another, production and purchasing on paper or in spreadsheets. The owner could not see the operation as one picture, and every month-end was a reconciliation exercise.
What the team built
A desktop ERP, developed and owned by our team, deployed at factories and companies working in several sectors. It connects the operations a business actually runs:
- Purchasing, stock and warehouses — receipts, issues, balances and valuation
- Sales and invoicing, customer and supplier accounts
- Production and cost tracking for manufacturing clients
- Reports the owner reads, not exports the accountant rebuilds
What this case proves
That our team can build business systems that are used for real and keep working for a very long time — and that we know industrial and commercial environments from the inside: the warehouse, the shop floor, the import file, the month-end.
What this page does not show
No client names, no screenshots and no module-by-module description until each has been documented and the client has approved publication. We do not publish user counts or transaction volumes we have not measured. References can be arranged on request once the client has agreed.
Stack
- VB.NET / C#
- Windows desktop
- SQL Server
- Reporting