Ighama began as a family-owned forklift manufacturer producing a few dozen units per month for local warehouses. Demand grew beyond the local region. Plants were added across the country. Regional distribution centers were established. Hundreds of dealer relationships were built. Each layer of expansion added complexity that the existing systems, spreadsheets and disconnected ERPs, could not absorb.

The inventory problem was visible at both extremes simultaneously. High-demand dealers ran out of forklifts and maintenance parts while other locations sat on excess stock. Plants and dealers tracked independently, with no signal connecting a stockout at one location to available inventory at another. The transfer that would have prevented the stockout did not happen because nobody had the data to see that it was needed until after the customer was already frustrated.

Shipping costs climbed as the reactive response to stockouts became emergency freight. Dealers compensated by building safety stock that tied up capital unnecessarily. Plants overproduced low-margin models against projections that nobody could validate, while high-demand models went short. Management at headquarters had no clear picture of which plants were performing, where the bottlenecks were, or what the actual margin looked like across the full network.

Financial consolidation was a quarterly manual exercise. Revenue, costs, and margins were scattered across plant and dealer reports that each used their own formats and timing. By the time the consolidated P&L was assembled, it reflected what happened two months ago, not what was happening now. In 2026, making strategic decisions from a P&L that old is not managing a business. It is reading its history.

FireFlight addressed Ighama's challenges by building a unified, data-driven platform connecting every plant, regional warehouse, and dealer location into one operational record. Every sale, production completion, inventory transfer, and financial event feeds a real-time event pipeline that keeps all levels of the organization current simultaneously. Configuration was structured across three phases, with core inventory and financial engines live in the first 30 to 60 days.

Every transaction in the Ighama network generates an event that FireFlight captures and propagates immediately to every level with a stake in that event. A dealer sale does not sit in a queue waiting to be reconciled at month-end. It triggers a chain of automatic updates that keeps inventory, financial records, and demand signals current across the full network within the same session.

The network's operating posture shifted from reactive to data-driven. Inventory moves that had been triggered by stockout emergencies were replaced by transfer optimizer recommendations acting on demand signals before the shortage reached the dealer. The emergency freight line item that had been a predictable quarterly cost began to decline as the transfers that prevented those emergencies happened earlier and at lower cost.

Headquarters saw a P&L that reflected the current state of the network rather than last month's manually assembled report. The ability to drill from a consolidated HQ number down to a specific dealer's margin in a single session changed what questions management could ask and how quickly they could act on the answers.

At the scale of multiple plants and hundreds of dealer locations, the inventory imbalance problem and the emergency freight problem are the same problem seen from two different positions in the network. Excess stock at low-demand locations and stockouts at high-demand locations are both symptoms of inventory moving reactively rather than proactively. The transfer optimizer addresses the symptom. The unified inventory picture with real-time event capture is what makes proactive movement possible in the first place.

Deployments for multi-location manufacturing and distribution networks covering unified inventory, financial roll-ups, transfer optimization, and production scenario planning are structured in phases, with core engines live in the first 30 to 60 days and full network visibility complete within months, not years.