Executive Summary
Key Takeaway (with a straight face): While QAD and Infor parade their cloud-native AI agents and “agentic” champions, many legacy customers are stuck managing a horror show of six incompatible user interfaces, offshore Progress 4GL lifelines, and warehouse systems that look like they were designed by a nostalgic mainframe from the Reagan era.
What This Follow-Up Covers:
- The absurd reality of running not two, not three, but six different ERP front-ends simultaneously
- How scarce Indian 4GL talent has become the manufacturing equivalent of unicorn wranglers
- Why your $400M global operation needs 35 IT people just to keep the green screens blinking
- The delicious irony of vendors touting “seamless modernization” while customers alt-tab through the 90s, 2000s, and whatever the Web UI is pretending to be
Who Should Read This: Anyone who has ever cried at a CHUI error message, any CIO secretly calculating how many more years they can delay the inevitable cloud reckoning, and everyone who enjoys watching vendors sell the future while customers live in the past.
Introduction: The Cloud Looks Great from the Vendor Keynote
In our previous analysis, “Go Cloud or Bust,” we soberly dissected how QAD and Infor are herding legacy manufacturers toward their subscription clouds with the gentle urgency of a shepherd wielding a cattle prod. As of early 2026, QAD’s Adaptive ERP is now proudly “agentic,” Infor has unleashed AI agents faster than marketing can invent buzzwords, and both companies are offering “fixed-fee” migrations that somehow still cost more than a small house.
Bravo.
Meanwhile, back on planet Earth—specifically in the fluorescent-lit IT cubicles of mid-sized manufacturers—the reality is far more entertaining. The promised land of a single, modern Web UI remains a distant mirage. Instead, many organizations are operating what can only be described as Frankenstein’s ERP: a stitched-together abomination of modern browser tabs, multiple 2000s-era .NET thick clients, and a character-based (CHUI) warehouse addon that looks and feels like it was coded during the Clinton administration—because it probably was.
This follow-up pulls back the curtain on the internal IT circus that vendor roadmaps conveniently ignore. We’ll do it with the respect these systems deserve: none whatsoever.
The Six-Headed Monster: A Guided Tour of UI Hell
Picture this: It’s 2026. QAD just announced that their new AI agent can predict supply chain disruptions before they happen. Fantastic!
Now zoom into a typical $400M manufacturer with plants in the US, Mexico, UK, and India. Their users are doing this daily dance:
- Open the modern Web UI for basic order entry (limited features, naturally).
- Switch to .NET Client #1 for financials (because the web version still can’t do that one report).
- Fire up .NET Client #2 (the asset management special edition—acquired in 2008, never fully integrated).
- Launch .NET Client #3 for advanced production scheduling (another acquisition, another era).
- And finally, for the grand finale: boot the CHUI warehouse addon in a terminal emulator to print labels, scan receipts, and pray the session doesn’t drop mid-shift.
Six different interfaces. Six different ways to hate your job.
The CHUI system deserves its own spotlight. Built on Progress OpenEdge 4GL—a language so niche it’s practically an endangered species—this green-screen relic handles the most mission-critical tasks: label printing, RF scanning, shipping, and receiving finished goods. One crash and the entire production line grinds to a halt. It’s the ERP equivalent of keeping your factory running on a single 40-year-old steam valve while the vendor brags about their new electric turbine.
And the best part? The code is only editable through a haphazard .NET-wrapped IDE that crashes more often than a Windows ME machine. Modern development? Please. This is archaeology.
The Offshore 4GL Wizard: Manufacturing’s Most Precious Resource
Need a bug fixed in the CHUI label routine? Better hope your retainer with that one guy in India is still active. Progress 4GL expertise is rarer than a quiet day in a warehouse, and it’s all concentrated halfway around the world.
A critical production receipt fails at 2 PM Colorado time? That’s 1:30 AM in India. Good luck. By the time the wizard awakens, you’ve lost a shift, inventory is wrong, and someone is manually printing labels on a desktop printer like it’s 1999.
These developers aren’t just skilled—they’re mythical. Companies guard their contact details like nuclear codes. Lose one to attrition, and you’re suddenly shopping in a talent market that makes finding a honest politician look easy.
Staffing: Or How to Employ 35 People Just to Keep the Lights On
For a $400M global manufacturer running this Frankenstein portfolio, the “bare minimum” IT organization looks like this:
| Role Category | Headcount | Unofficial Job Description |
|---|---|---|
| Leadership & Governance | 3–4 | Professional apologizers to the business for why nothing works seamlessly |
| Functional Support | 8–10 | Translators who speak six UI dialects and one ancient 4GL incantation |
| Technical Maintenance | 6–8 + contractors | Includes 2–3 offshore wizards who can actually edit the sacred 4GL scrolls |
| Infrastructure & Endpoints | 5–7 | Keepers of terminal emulators, legacy printer queues, and prayers for Wi-Fi |
| Service Desk | 6–8 | First responders to “Why does this only work in the old client?” |
| Total | 28–35 + mythical beings | Congratulations, you’ve built a museum staff for a live production system |
This isn’t an IT department. It’s a support group for technological trauma.
The Delicious Irony: Vendors Party, Customers Pay
While QAD unveils “agentic champions” that proactively optimize manufacturing, and Infor’s AI agents presumably write poetry about supply chains, actual manufacturers are:
- Spending six figures annually on contractors just to keep CHUI alive
- Training new hires on interfaces that belong in the Smithsonian
- Watching talented cloud engineers flee for jobs that don’t involve debugging WinForms from 2003
The vendors’ message is clear: “Move to our beautiful, unified cloud and leave this mess behind!”
The customer’s reality: “Sure, just as soon as you port our 500,000 lines of custom 4GL code, replicate all the exclusive .NET features, and guarantee zero downtime during warehouse cutover.”
Spoiler: That day never comes without a seven-figure consulting bill.
Conclusion: Embrace the Absurdity (or Finally Escape It)
Let’s be honest: maintaining this Frankenstein ERP is performance art. It’s a testament to human ingenuity that these systems still run at all.
But the joke is wearing thin. Every day spent alt-tabbing through the 90s is a day not spent on actual digital transformation. The cloud vendors aren’t wrong that modernization has benefits—they’re just conveniently ignoring how their past acquisition sprees and deliberate feature gaps created this monster in the first place.
So, dear manufacturer: you have three real options.
-
Keep calm and carry on—hire more wizards, stock more Red Bull for 3 AM calls, and perfect your “it’s a feature, not a bug” smile.
-
Bite the bullet—pay the ransom for cloud migration, rewrite everything, and pray the new AI agents are worth it.
-
Rebel—use this inflection point to evaluate alternatives that don’t treat customers like ATM machines with loyalty issues.
Whatever you choose, just remember: in the grand comedy of enterprise software, you’re not the villain.
You’re the punchline.
Until you decide to write a new joke.
References & Further Reading
- The collective tears of manufacturing IT departments worldwide
- QAD’s glossy brochures about “agentic” futures
- Infor’s press releases that definitely weren’t written by AI
- Progress OpenEdge documentation (now with extra nostalgia)
- Anonymous quotes from people who have seen CHUI error messages in their nightmares
This piece is based on real patterns observed in legacy QAD/Infor deployments. Any resemblance to your actual ERP system is purely coincidental… probably.