Replacing spreadsheet chaos with a custom ERP

The challenge

A manufacturer with a growing order book was running its operation on disconnected spreadsheets and a legacy accounting tool. Stock counts were unreliable, purchasing was reactive, and month-end reporting meant several people reconciling numbers for days. Off-the-shelf ERPs had been evaluated twice and rejected — the licensing costs were heavy and the workflows didn’t fit how the factory actually ran.

Our approach

We started on the floor, not in the IDE: three weeks mapping how materials, orders, and approvals really moved — including the exceptions that lived in one supervisor’s head. The data model came out of that mapping, and the build followed it:

• Inventory first, because it was the loudest daily pain: barcode-driven receiving, real-time stock levels, and automatic reorder alerts.
• Purchasing and production modules next, each with a parallel-run period where the old spreadsheets stayed alive until the numbers matched for a full cycle.
• A Go-based reporting service aggregating live operational dashboards that leadership could open on their phones.
• Integration with the existing accounting system rather than replacing it — one fight at a time.

Every module shipped with training sessions and an internal champion who owned adoption for their department.

The outcome

Nine months in, five modules run the operation end to end. Month-end closing dropped from days of reconciliation to hours, stock discrepancies get caught at receiving instead of at the annual audit, and — the metric the client cares most about — the factory never stopped during the entire rollout.