Profound Logic Software

16/10/2026

11,400 baby boomers reach retirement age every single day. The IBM i developer community is not insulated from that number. The average RPG developer is in their mid-to-late fifties. The pipeline coming in behind them is thin.

Most organizations frame this as a risk to manage. It is also a window that's open right now and closing.

The companies that act while veteran developers are still available to validate documentation, review agent output, and encode institutional knowledge into Skills will be in a different position than the ones that wait for a departure to force the issue.
The knowledge doesn't get easier to capture after the person who holds it leaves.

Read the staffing cliff breakdown: https://hubs.la/Q04zLhJb0

15/10/2026

When private equity acquired Western Power Sports, the assumption was that IBM i would be replaced. Then someone looked at what it was actually doing.

$3 million a day in e-commerce revenue. 99.9% of sales processed online. The entire operation supported by 3.5 people.

"They wanted to replace it because they thought the 400 was old-fashioned. Then they started looking at it... and they forgot about replacing it." — Rody Cummings, Analyst, Western Power Sports

IBM i wasn't the liability in that story. It was the reason the numbers looked the way they did. Read the full case study: https://hubs.la/Q04zLkhf0

Western Power Sports proves IBM i can scale modern e-commerce. Learn how Profound AppDev enabled 99.9% self-service ordering, ~$3M/day in revenue, and a lean team, without replacing IBM i.

14/10/2026

Have you heard? COMMON NAViGATE is heading to TechXchange in Atlanta, October 26-29, and we'll be there.

Jordan Antonoff, Brian May, Roger Betacourt, and Isaac Thibault will be there all week to talk CoderFlow, IBM i futurization, and whatever's keeping your development team up at night.

700+ sessions. 100+ IBM i focused. 150+ hands-on labs. One registration gets you the IBM i community you know and a much larger technical conference alongside it.

See you in Atlanta 👉 https://hubs.la/Q04zcT1n0

13/10/2026

A finance team reconciling payments against a batch that runs at 2 AM is a team that's always half a day behind what actually happened. That gap doesn't show up as a system outage. It shows up as a standing tax on how current the business's own data is, paid quietly every day the batch window exists.

Kamik is a useful example of what closing it looks like. Their IT team built Node.js applications using Profound API that took orders from Amazon, EDI, and their Magento storefront and wrote them directly into ERP and warehouse management systems, automatically, in real time.

Three separate order sources. One path into IBM i. No overnight file drop in the middle.

The validation logic RPG was already enforcing didn't get rebuilt. It got reused, exposed as a REST endpoint any modern system could call.

That's the pattern. The business logic that already exists does the work. The integration just gives it a new entry point.
Talk to our integration team: https://hubs.la/Q04yKKF-0

12/10/2026

What if your next IBM i fix was built, tested, and waiting for your approval before you finished your morning coffee? With CoderFlow, that’s just a normal morning.

A developer describes the fix in plain language. The agent handles the compile, test, and validation loop. What comes back isn't a suggestion or a draft. It's a verified result with application screenshots showing exactly how the change behaved, and the exact lines of code that changed.

The developer looks at it. If it's right, they approve. Nothing merges without that call. That's what governance looks like inside CoderFlow.

The agent does the ex*****on work. The developer makes the final judgment. The audit trail covers everything in between.

Your IBM i is now agentic. Go with the flow. Learn more: https://hubs.la/Q04zLgXW0

09/10/2026

Traditional large-scale IBM i transformation: years of work with a single payoff at the end. Agentic Futurization: built in months with measurable ROI at each phase boundary.

That compression matters because multi-year transformation projects don't stall at the end. They stall in the middle, when priorities shift, teams turn over, and the organization loses confidence that the payoff is still coming.

Structured to deliver visible results at each milestone, before the next phase begins, is what keeps momentum alive across an initiative that spans years. See how Agentic Futurization is structured: https://hubs.la/Q04yKPtd0

08/10/2026

End of year is when most IBM i organizations look back at what the technology budget actually produced. The honest version of that conversation usually surfaces the same gap: a fair amount was spent, and the strategic position didn't change much. Interfaces were updated. Some debt was patched. The underlying constraints are still there. That's what modernization produces. It addresses the liability. It doesn't build the asset.

The organizations that come into next year in a genuinely different position are the ones that treated transformation as a strategic initiative, not a maintenance cycle. The questions they answered were different. Not "how do we update what we have?" but "how do we build a platform that grows alongside the business?"

Those two questions produce very different plans. Read the full futurization vs. modernization breakdown: https://hubs.la/Q04yKLMh0

07/10/2026

Week three in a new IT leadership role. Someone asks why the order entry program behaves that way during month-end. Everyone in the room looks at you. This is a common story for a new IT leader stepping into an IBM i environment.

The systems work. The people who know why they work that way are often no longer in the building. And the scramble to find whoever has been there long enough to remember is not a personal failing. It's a documentation problem.

80% of CIOs come from outside the organization they now lead. Most are running systems they didn't design, built by people who aren't there to explain their choices. If you're new to your seat, you're the rule. Not the exception.

Read the full guide for new IBM i leaders: https://hubs.la/Q04yKHn-0

06/10/2026

IBM i skills displaced cybersecurity as the top concern among IBM i professionals in 2026. First time that's happened since 2017. Nine years. And the thing that finally pushed security down the list wasn't a new threat. It was a staffing problem that's been building for a decade and is now impossible to ignore.

What we keep hearing from IT leaders going into Q4 planning: the backlog is real, the talent pool is thin, and the options they've tried haven't reliably moved the number.

Hiring takes months. General staffing firms place a resume with IBM i somewhere in it and call it a match. Offshore can look attractive on a rate card until the rework shows up six weeks in.

If you're heading into budget season with a capacity problem and no clean answer for it, what's the conversation you're having internally?

05/10/2026

Most integration conversations with IBM i go one direction: getting data out. The other direction gets solved with a batch job. A flat file drops overnight, and by morning the order, the inventory update, or the shipment confirmation has made it into the system that runs the business.

This works, in the sense that the data eventually arrives. A warehouse that sees last night's orders is a warehouse that may have oversold something at 9 PM.

Writing into IBM i in real time has its own constraint: the data has to be validated on the way in. RPG programs have spent decades encoding what a valid order looks like, what fields are required, what has to be checked before an inventory count moves. A raw write into a Db2 table skips all of that.

Profound API closes this by routing inbound writes through the RPG programs that already do the validation. The logic that exists gets reused, not rebuilt. Read how the inbound side works: https://hubs.la/Q04yKJ3_0