The problem no balance sheet shows
Every small manufacturer operates with a hidden liability: the institutional knowledge locked inside the heads of its founders, engineers, and machinists. When a lead engineer sets a machining parameter, when the founder decides to bulk-buy raw material before a price hike, when a veteran machinist adjusts a tooling strategy — that decision gets made, executed, and forgotten. Never written down. Never explained. And the next time the same situation arises, the company pays the same learning cost all over again.
For a 50-person job shop producing engineered components across diverse geometries, materials, and customer requirements, this isn't academic. It's cash. A missed delivery because no one recorded that EN8 warps without stress relief. A quality rejection because no record existed of a CNC fixture drifting 0.05mm every three setups. An order accepted at a margin that makes the machine run but loses the company money. These happen every week — and they accumulate silently into the gap between a company that grows and one that simply stays busy.
Eight modules. One company brain.
Rather than waiting for an ERP rollout that would take months and six figures, the answer was an 8-module Excel workbook engineered to function as a lightweight decision intelligence system — something every team member could open, read, and contribute to from day one.
The Part Master established a single source of truth for every manufactured component: part number, material spec, drawing revision, CAD reference, and weight. The Geometry module captured tolerances, surface finish requirements, and machining complexity scores — giving the company an objective basis for quoting and capacity decisions rather than gut feel. The Work Order Tracker gave live visibility into every active job: machine, operator, stage, and schedule status. Overdue orders flagged red automatically; on-track jobs turned green. The foreman and the founder saw the same picture at the same time, for the first time.
The Sales Pipeline linked every order to delivery date, margin, and production status — calculating days-to-delivery in real time and escalating at-risk orders before they became problems. The Purchase Log did something most companies never do: it captured not just what was bought and from whom, but why. Every entry recorded the decision maker, the rationale, and the outcome. Purchasing history became a learning record, not just a cost record.
The Decision Engine — where gut feel becomes a system
The heart of the workbook was the Decision Engine. It formalised the decisions the company needed to make repeatedly — reorder triggers, tooling change thresholds, delivery risk assessments, make-versus-buy evaluations — and attached to each one its key ratio, the threshold that triggered action, the recommended response, the responsible owner, and two predicted outcomes: the good path and the risk path. Eight parameters monitored across all domains: Stock-to-Demand Ratio, Tool Life Ratio, Delivery Buffer, Dimensional Reject Rate, Overhead Absorption Rate, In-house vs Market Cost, Gross Margin %, and Fixture Drift Rate.
Instead of a founder making a gut call and a junior engineer making a different one on the same situation next quarter, the company had a documented framework that improved with every entry. The Knowledge Log completed the picture — capturing in plain language every significant decision or lesson learned, from minimum margin policy to the discovery that climb milling on a specific alloy eliminates chatter. Each entry records who decided, why, what parameters were involved, and the outcome.
"Manufacturing companies don't fail because they can't make things. They fail because they can't consistently make the right decisions — about what to buy, when to buy it, how to make it, who to sell it to, and at what price."
— Decision Intelligence System Abstract · P. S. GhatoraDecision intelligence isn't a luxury reserved for companies with enterprise software budgets. It's a discipline — and it starts with the simple act of writing down why a decision was made. For a 50-person manufacturer with no ERP, this workbook delivered immediate operational value by filling the gap every system leaves open: between data and decision, between history and action, between what one person knows and what the whole organisation can use.
