Most digitization case studies get published at the launch party, full of promise and short on follow-through. This digitization results case study is the opposite: twelve months after go-live, with the wins, the disappointments, and the one module we quietly abandoned, all laid out honestly for a family-run manufacturing business I have worked with in Indonesia.
The business makes packaged food products, sells through distributors and direct retail, and had run on a mix of paper order forms, WhatsApp confirmations, and a single shared spreadsheet for a decade before we started. A year ago, we rebuilt their order intake, production costing, and inventory tracking into one connected system. This is what actually happened, not what the sales pitch promised.
The starting point
Before digitization, the business had three structural problems that every family manufacturer I have worked with shares in some form:
- Order errors from manual re-entry. Orders came in by phone or WhatsApp, got written on paper, then re-typed into a spreadsheet by a different person. Every handoff introduced a chance for a wrong quantity or wrong SKU.
- Costing that lagged reality. Raw material costs changed weekly, but the costing spreadsheet got updated monthly, so pricing decisions were made on stale numbers.
- No single source of truth for stock. Three people kept their own inventory counts, and reconciling them at month-end routinely took two full days.
The wins, with numbers
Twelve months in, the measurable improvements held up:
| Metric | Before | After 12 months |
|---|---|---|
| Order entry errors (wrong SKU/qty) | ~1 in 15 orders | ~1 in 90 orders |
| Time to update product costing | Monthly | Real-time, on material price change |
| Month-end inventory reconciliation | 2 days | 3 hours |
| Order-to-invoice turnaround | 2-3 days | Same day |
The order error reduction was the most immediately felt win, because every error used to mean a phone call, a correction, and often a discount to keep the customer happy. Cutting that by roughly six times paid for a meaningful chunk of the project cost within the first six months, just in avoided rework and goodwill discounts.
Real-time costing turned out to be the quiet high-value win nobody predicted at the start. The owner could now see, the same day a supplier raised raw material prices, exactly which products were becoming unprofitable at current pricing. That visibility changed two pricing decisions within the first quarter that would previously have gone unnoticed for weeks.
The disappointments
Being honest about what did not work matters more than repeating the wins.
One module got abandoned. We had built a production scheduling feature meant to auto-suggest daily production runs based on order backlog and material availability. Nobody used it. The production floor supervisor kept using his own paper-based method, not out of stubbornness, but because the auto-suggestion did not account for machine maintenance windows we had failed to model properly. Rather than force adoption of a broken tool, we shelved it. It is a documented lesson, not a hidden failure: the module solved the problem we specified, not the problem that actually existed on the floor.
Adoption dipped hard when the champion went on leave. The office manager who drove adoption took a month of maternity leave in month seven, and system usage measurably dropped, staff reverted to WhatsApp confirmations for a subset of orders because the temporary backup staff were not confident in the new system yet. It recovered once she returned, but it exposed a real fragility: the system's success was more dependent on one person's championing than the business had realized. We have since built a lighter onboarding guide specifically so a temporary replacement can operate the core flows without hand-holding.
The unplanned benefit: financing got easier
This was not in the original business case. Nine months in, the owner applied for a working capital loan to expand a product line, and the bank's due diligence process moved noticeably faster because the business could produce clean, consistent inventory and sales records on demand instead of reconstructing them from scattered spreadsheets. The loan officer specifically commented that the data quality reduced the verification work on their end. Clean digital records turned out to be collateral of a different kind, and it is a benefit worth mentioning to any family business owner weighing whether digitization is worth the disruption.
What I would do differently
If I were starting this project again, I would spend more time on the production floor before building the scheduling module, rather than specifying it from conversations with the office manager alone. The gap between what management thinks happens on the floor and what actually happens there is the single most common cause of an abandoned feature in every digital transformation project I have run. I would also build a backup champion role into the plan from day one, not as an afterthought after adoption wobbled.
Practical takeaway
A year-one scorecard should have both columns: what worked, with numbers, and what did not, named honestly. This family manufacturer cut order errors by roughly six times, moved costing from monthly to real-time, and gained an unplanned edge with lenders, while also losing a scheduling module to poor floor-level fit and discovering their adoption was more fragile than expected around a single champion. That is a realistic outcome, and realistic outcomes are the ones worth building a second year on.