When we started building FactoraERP, I thought we were building software for factories. What we were really building was a way for a plant to remember what it did, accurately, without anyone having to rebuild the story at the end of the week.
Here are five lessons that shaped the product, and that I think apply to anyone running or building for a production floor.
1. Start from the lot, not the ledger.
Most business software starts from accounts. A factory starts from material. A delivery arrives, it's checked, it's stored, it's issued, it's transformed, it's tested, it's shipped. If the lot number isn't the spine of the system, everything else is reconstruction. So in FactoraERP, batch-level traceability from intake to dispatch came first, and finance, costing and sales hang off it, not the other way round.
2. The record has to be written where the work happens.
A record that gets typed in later is a memory, not a record. People on the floor won't walk to an office to log a reading, and the signal isn't always there when they need it. That's why mobile capture works offline and syncs when the connection returns. If capture is hard, the data will be late, and late data is guesswork with a timestamp.
3. A named person beats an anonymous alert.
Alerts that go to "everyone" go to no one. We made acknowledgements named: when a QC checkpoint fails or a condition goes out of range, a specific person acknowledges it, and that acknowledgement stays in the audit trail. Accountability isn't about blame. It's about knowing who saw it, and when.
4. Costing is only as true as the stock movements underneath it.
Every factory wants to know its real cost per batch. But you can't cost a batch from an estimate. If materials, production runs and stock movements are recorded in the same system as they happen, the cost of a batch comes from what actually happened. If they live in three spreadsheets, the cost is an opinion.
5. One system beats many integrations.
It's tempting to stitch together a production tool, an inventory tool, an accounting package and a payroll app. Every seam between them is a place where the truth can drift. FactoraERP puts production, inventory and costing, finance, procurement, sales, payroll and multi-site operations in one system, so a question like "show me this lot" has one answer, with a full audit trail behind it. And when sensors join the picture through FactoraIoT, the conditions a batch went through stay with that batch's record instead of sitting in a separate dashboard.
What I'd tell another founder building for industry
Don't build features. Build the record. The features are just the different ways people need to write into it and read from it. If the record is honest, complete and available at the moment someone needs it, whether a production lead, a finance team, a buyer or an auditor, the software is doing its job.
That's the idea behind FactoraERP: the manufacturing operating system. If your plant still keeps part of its story outside the system, I'd like to hear which part, and why.
Learn more at factoraerp.com (pricing on request).
For builders
The same ideas show up outside factories. A system whose "source of truth" is reconstructed every Friday is a ledger without a lot number. An alert that pages a shared inbox is an anonymous alert. A cost model fed from three spreadsheets is an opinion. Prefer one record written where the work happens, with a named person on every exception.
Learn more at factoraerp.com (pricing on request).
Originally published at isaacmuthui.com/insights.
Top comments (0)