Your Best RPG Developer Retires Next Year. Does Anyone Know What Their Code Actually Does?
Most IBM i organizations don’t have a documentation problem so much as an undocumented-decisions problem. When the developer who wrote a program leaves, whatever they knew about it leaves too. Here’s why that gap is more urgent than most IT leaders realize, and what it actually takes to close it.
One Platform, Any Agent: How CoderFlow Keeps IBM i Teams Out of AI Vendor Lock-In
Autonomous coding agents that work in parallel, run against your repositories, and hand back reviewable code, all under your team’s existing controls. Parallel Agents Reviewable Diffs Governed Access Your Repositories Platform Overview CoderFlow runs AI coding agents inside isolated containers, against your own repositories, and returns their work as changes you review and approve. Submit […]
From One Screen to a Thousand: Futurizing an Entire Application Portfolio
Most futurization conversations start, and often stay, at the scale of a single application. But the real test isn’t whether Futurization works on one flagship program. It’s whether it holds up across an entire portfolio of hundreds, or thousands, of interconnected RPG programs built up over decades.
Futurizing Store Operations and Maintenance with Profound AppDev
A vertically integrated food retail and dairy company moved beyond legacy green screens to real-time store insights and mobile-enabled maintenance, using Profound AppDev’s Genie and Atrium to futurize without disrupting existing IBM i systems.
Why the Right AI Model for Your RPG Codebase Isn’t Always the Same One
Most AI coding tools ask you to trust one model with everything. For decades of RPG and COBOL logic, that trade-off deserves more scrutiny than it usually gets.
Why Most IBM i Shops Haven’t Started With AI Yet (And What the First Step Actually Looks Like)
IBM i leaders are more worried about falling behind on AI than ever before, but worry has not translated into action. Here is what is actually causing the freeze, and a first step that does not require betting the farm.
A Leading Textile Services Provider Futurizes Mission-Critical Operations with Profound AppDev
Case Study Highlights Industry: Textile Rental and Laundry Services Client: Major UK Textile Services Provider Operations: 16 plants across the United Kingdom Technology Legacy: IBM i platform with RPG applications Core Challenge: 6-month deadline to replace failed third-party system Technology Approach: Rapid IBM i futurization using Profound AppDev Key Results: Met critical deadline, zero operational disruption, successful rollout to all […]
The IBM i Transformation Decision: A Framework for Choosing the Right Path
The IBM i transformation decision is a business architecture choice, not a software selection. This framework gives IT leaders five questions to answer about their own situation so they can identify the right path, futurization, hybrid, or migration, before any vendor hands them a recommendation.
Your Toughest Futurization Problem Is the People, Not the Platform
A futurization effort can clear every technical hurdle and still stall, because the people who run the business on the same screens every day are afraid of what’s coming. The platform problem is largely solved. The adoption problem is the one your vendor can’t solve for you. Here’s how Agentic Futurization is structured to lower that fear, and the leadership playbook for bringing your team along.
International Equipment Rental Company Futurizes Equipment Management with Profound Logic
A major equipment rental company with 1,250+ locations partnered with Profound Logic to replace fixed-terminal data entry with mobile barcode scanning — futurizing their IBM i operations with Profound AppDev and achieving a 70% efficiency gain.
What Your Green Screens Signal to the Market
Most IBM i organizations frame green screens as an internal problem. An interface issue. Something to get around to eventually. But when your competitors have moved and you haven’t, that calculus changes. The risk isn’t just internal friction. It’s market position.
CoderFlow on IBM i: What Real Development Tasks Actually Look Like
Descriptions of agentic coding are easy to find. What is harder to find is a straight answer to a simple question: what does it actually look like when you hand a task to an agent in a real IBM i environment? This post walks through three examples.
AI Digital Labor on IBM i: Scaling Delivery Without Scaling Headcount
The question IT leaders are asking is no longer whether AI can write code. It’s whether AI can take on the sustained delivery work that enterprise teams need done without expanding payroll. On IBM i, the answer is already being demonstrated in production.
IT Builds It. IT Controls It. The Case for Agent-Driven Business Automation on IBM i.
Every IBM i shop has business processes that run on human effort today: repetitive, documented workflows that someone executes manually because no one has gotten around to automating them. CoderFlow gives IT the ability to set up AI agents that handle those workflows autonomously, with full governance and control staying exactly where it belongs.
Agentic Display Files: The UI Breakthrough IBM i Teams Have Been Waiting For
What if an AI agent could design a complete, responsive web screen from a plain-English description of what it should do? With Agentic Display Files in Profound UI, that’s exactly what becomes possible and it changes what IBM i futurization looks like.