Seven Systems, Zero Answers: The Manufacturing Data Trap

A friend of mine runs a fabrication business — good size, well run, the kind of operation that’s survived thirty years because he knows it cold. I was in his office a while back when his son, who’d just joined, asked him a simple question: “Pa, how much are we actually making on the Mehta order right now?” My friend opened his accounts software. Then he opened a spreadsheet his production supervisor maintains. Then he pulled up his phone to check something on a WhatsApp group. Then he called his store manager. Twenty minutes later, three people involved, he had an answer he wasn’t fully sure of. His son looked at him and said, “We have all this software and you still had to phone someone?”

That’s the trap. And it’s worth understanding exactly what it is, because it’s the single most common reason a well-run manufacturing business still leaves its owner flying half-blind.

You didn’t buy too little software. You bought too much.

Here’s the strange thing about the mid-sized manufacturer’s data problem: it isn’t caused by a lack of systems. It’s caused by having several, none of which talk to each other.

Walk through a typical setup. Your accounts and inventory live in one system — Tally, most likely, the backbone of the business. You probably bought an ERP at some point, on the promise it would unify everything; in reality it’s half-implemented, used properly by two departments and ignored by the rest. Production is tracked in a spreadsheet that one reliable person maintains by hand, because nobody trusts the ERP’s shop-floor numbers. Quality keeps its own register. Sales lives partly in someone’s head and partly in a CRM that’s three months out of date. And the real, fast, important conversations — the vendor who’ll be late, the customer who’s annoyed — happen on WhatsApp, where they scroll away and are gone.

Every one of these works. Each does its own job reasonably well. The trap isn’t that any single system is bad. The trap is the gaps between them — the spaces where no system is responsible, where information from one island would mean everything if only it could meet the information from another. Your accounts system knows the Mehta order’s costs. Your production sheet knows its delays. Your CRM knows when you last spoke to Mehta. The answer to “how are we doing on this customer” lives in all three at once — and in no place you can actually look.

So you’ve spent good money on software and you still, like my friend, have to phone someone to find out how you’re doing. More systems didn’t give you more answers. They gave you more islands.

“So I should just buy a better, bigger system?”

This is where most owners’ minds go next, and it’s the wrong turn. The instinct is: my systems don’t talk, so I’ll buy one big system that does everything, rip out the rest, and finally have one source of truth.

I understand the appeal. I’d gently warn you against it, for two reasons.

First, you’ve likely already tried a version of it — that’s what the ERP was supposed to be. And you’ve learned, expensively, how these things actually go in a real mid-sized business: the implementation drags, the shop floor resists, the spreadsheet survives in the corner because people trust it more, and eighteen months later you have a powerful system that two departments use properly and everyone else routes around. Not because the software was bad, but because ripping out the working guts of a running business and replacing them wholesale is brutally hard, and the business has to keep shipping product the whole time.

Second, and more important: a big operational system is built to run parts of your business — to process the order, manage the stock, post the entry. That’s its job, and a good ERP does it well. But running the business and seeing the whole business are two different needs. Even a perfectly implemented operational system is built for the person doing the task, not for you, the owner, asking “how is all of it doing, right now, together?” You’d have replaced five islands with one very large, very expensive island — better than five, certainly, but still not the thing that walks up to you each morning and says “here is your whole business, and here is what needs you today.”

The thing you actually need sits above your systems, not instead of them

So here’s the shift in thinking that matters. You don’t need to replace what you have. You need something that sits above what you have — that reaches into Tally and the ERP and the production sheet and the customer history, takes what each one knows, and assembles it into a single honest picture for you. Not another place where work gets done. A place where everything that’s already happening gets seen, together, by you.

This is a different category from your operational systems, and the distinction is the whole point. Your ERP and your accounts software are where the business runs. What I’m describing is where the business becomes visible — to the one person who has to answer for all of it. The two aren’t rivals. The operational systems keep doing exactly what they do; this simply reads across all of them and answers the question none of them can answer alone. Keep your engine. You’re just finally getting a dashboard that shows you the whole car instead of one dial at a time.

And because it reads across everything at once, it can do what no single island ever could: connect the costs in accounts to the delays in production to the silence in the customer history, and tell you that the Mehta order is slipping on margin and the customer’s gone quiet and nobody’s called him in six weeks — in one view, the moment you walk in, without you phoning anyone.

Why this matters more in our world than in the West

There’s a reason this particular trap bites mid-sized manufacturers especially hard. The reality of how our businesses are actually run — Tally as the backbone, a part-used ERP, the trusted spreadsheet, the decisive WhatsApp group — is genuinely fragmented in a way the textbooks don’t describe. A great deal of real operational truth lives in places no formal system will ever capture. Any honest answer to the visibility problem has to start from that reality — the mix you actually have, the messiness included — rather than pretending you run on one clean system you don’t. The fragmentation isn’t a flaw to be ashamed of. It’s just the ground truth of a real, working, mid-sized manufacturing business. The answer isn’t to deny it. It’s to finally see across it.

The simple test

If you want to know whether you’re caught in this trap, here’s the test. Ask yourself the question my friend’s son asked: how are we actually doing on our most important customer, right now? If the honest answer involves opening more than one system, or asking more than one person, or any phrase that begins with “let me just check with…” — then you don’t have a software shortage. You have a connection shortage. The pieces are all there, in your seven systems. They’ve just never been introduced to each other, and handed to you, in one place, in time to matter.

Walking in knowing doesn’t mean buying an eighth system. It means finally connecting the seven you’ve already got.

Part of Manufacturing Week. Read the overview — The Factory Runs in Real Time. Why Doesn’t Your Information? — or see why timing is everything in Your Month-End Close Is a Post-Mortem.