Workflow ERP optimization
Built a lightweight Airtable ERP that reduced operational time by 40%.
Resultados
The problem
The operation needed better control over inventory, production planning, and costs, but the real workflow lived in disconnected manual steps. That made the team slower than it needed to be, and it made planning depend too much on memory and informal coordination.
System shape
| Surface | What it handled | Why it mattered |
|---|---|---|
| Inventory | Stock, materials, and product state | Let the team see what existed before planning production. |
| Production | Planning, status, and coordination | Turned repeated manual steps into a visible workflow. |
| Costs | Inputs, cost control, and planning signals | Made pricing and production decisions less guess-based. |
| Dashboards | Operational visibility | Helped the team inspect the system without digging through raw records. |
Approach
The goal was not to force a small operation into a heavy ERP. It was to build the smallest system that made the operational model visible and reliable.
- Model the work first. Inventory, production, and cost control became structured records instead of scattered notes.
- Make the decisions visible. Dashboards exposed the current state of the operation without requiring raw table inspection.
- Keep it practical. Airtable was the right level of system for the client: fast to change, easy to operate, and structured enough to reduce mistakes.
Outcome
The project reduced operational time by 40% and gave the client a clearer view of inventory, production, and cost decisions. It is a good example of the kind of software I like building: not oversized, not theatrical, just enough system to make the business easier to run.
Repository
The public writeup and project artifacts live at Workflow-ERP-Optimization.