There’s a conversation that rarely makes it into IT planning cycles, even though it probably should.
It’s not about uptime. It’s not about compliance. It’s not even about the developer retirement problem, which gets plenty of attention on its own. It’s about what your technology signals to the people outside your organization who see it: the customers who interact with your systems, the candidates who evaluate your company, the partners who assess your operational maturity before committing to a relationship.
Most IBM i organizations treat green screens as an internal challenge. A user experience gap. Something to address in a future budget cycle. But as more industries reach a tipping point where the majority of competitors have futurized their customer-facing and partner-facing applications, the risk calculus changes. Staying on 5250 interfaces is no longer just an internal friction problem. It becomes a market positioning problem.
That is the conversation this post is intended to start.
The Industry Tipping Point
Technology adoption curves tend to follow predictable patterns. Early movers take the risk and absorb the cost of going first. A middle cohort follows when the path is clearer, and the business case is obvious. And then there is a moment, often gradual and then suddenly visible, when the organizations that have not moved find themselves in the minority.
For IBM i shops, that moment is approaching in most industries, and in some it has already passed.
An annual IBM i Marketplace Survey is the closest thing the platform has to a community-wide temperature check, and the numbers it has been producing on application transformation tell a clear directional story. In the 2025 survey, application modernization ranked third among IBM i shops’ top IT concerns, cited by 57% of respondents. By the 2026 survey, it had climbed to 62%. IBM i skills concern moved in the same direction over the same period, from 60% to 69%. Both are heading one way, year over year.
The organizations driving those numbers are not asking abstract questions. They are asking because their boards are asking, their customers are asking, or their recruiting teams are asking. The external pressure is real, and it is coming from several directions at once.
What Customers See
The relationship between technology presentation and customer trust is easy to underestimate until it affects revenue.
For organizations where customers interact directly with IBM i-backed systems, whether through portals, self-service tools, or front-office workflows, the interface they encounter reflects the organization’s operational sophistication. A 5250-era interaction model, or even a cosmetically-wrapped green screen that still behaves like one, communicates something specific, that this organization has not invested in the experience of working with them.
In industries where switching costs are low, that signal matters. In industries where switching costs are high but vendor evaluation happens periodically, it matters at renewal. In any industry where a competitor has invested in genuinely modern application interfaces and yours has not, the comparison will be made by someone, even if it is never said aloud.
Employee expectations now mirror their personal lives. If they can easily book travel and shop online with minimal friction, they expect the same intuitive experience from company technology. That dynamic extends to the customer relationship as well. The people evaluating your systems and portals come to those interactions with a reference point shaped by consumer software. When the gap between that reference point and your interface is wide, it registers.
What Candidates See
The hiring dimension of this problem is well understood within IBM i circles, but it is usually framed narrowly, organizations struggle to find experienced RPG developers because the pipeline is thin. That is accurate, and it is a serious operational problem.
But there is a second hiring problem that receives less attention. It affects not just the technical staff who will work directly in the development environment, but every category of employee who will use the applications your IBM i systems power.
When candidates evaluate job offers, they evaluate the work environment. That includes the software they will spend their days inside. More than half of office workers say negative experiences with workplace technology impact their mood and morale, according to research. That figure does not come from IBM i shops specifically; it reflects the broader expectation employees now bring to the workplace.
Organizations that have moved to modern, browser-based interfaces built on their existing IBM i infrastructure can speak to candidates honestly about the tools they will use. Organizations that have not must either manage expectations carefully or watch candidates who have options choose employers whose work environments look like the rest of their digital life.
A seamless digital experience is now a top office perk, cited by 49% of workers. That framing would have seemed strange a decade ago. Today it is a recruiting reality.
What Partners See
The partner and vendor dimension of this risk is perhaps the least discussed and the most consequential in certain industries.
When organizations that run on IBM i engage with supply chain partners, distributors, system integrators, or technology vendors, those relationships increasingly involve data exchange, portal access, and collaborative workflows. Modern partners have built their integration expectations around current web standards. When your side of the interaction is constrained by 5250 interface logic, the friction shows up in integration timelines, workarounds, and occasional outright limitations on what the partnership can accomplish.
More broadly, operational maturity signals matter in B2B relationships in ways that are difficult to quantify but easy to observe. Organizations presenting modern, browser-based access to shared workflows send a signal about their investment posture and their trajectory. Organizations presenting terminals or terminal emulators send a different signal.
This does not mean every partner will penalize you for it. It does mean that in competitive situations where two vendors are otherwise equivalent, the one that appears to be moving forward will tend to be viewed more favorably.
The Compounding Effect
These three audiences, customers, candidates, and partners, do not experience your technology in isolation. The signal they receive compounds.
A company that struggles to attract younger technical talent because of its interface environment will also tend to be slower to futurize, because the people who would drive that work are harder to recruit. A company that presents an outdated interface to customers is also likely presenting an outdated interface to partners, which creates friction in both directions. The competitive gap does not stay static. It widens.
Organizations using digital experience data consistently are seeing 24% higher end-user satisfaction and 26% more productivity compared to those that treat experience as an afterthought. Those productivity gains compound over time. An organization that acts now captures years of operational improvement. An organization that waits gives up not just the future improvement but the accumulated lead its competitors are building.
The Futurization Argument
This is where the distinction between rewriting and futurizing becomes strategically important.
The reason so many IBM i organizations have deferred this problem is that the apparent solution seemed disproportionate to the risk. If the choice is between “accept the competitive disadvantage of green screens” and “replace decades of mission-critical RPG logic,” many organizations will choose the first option. They are correct that a complete rewrite is a high-risk undertaking with a history of overruns and introduced defects.
But that is not actually the choice.
Profound AppDev is an integrated development suite that enables IBM i organizations to futurize their application interfaces without touching the business logic underneath them. The RPG programs that run your inventory, your pricing, your order processing: those stay exactly where they are. What changes is the layer between those programs and the people who interact with them.
Profound AppDev brings together five purpose-built tools that cover the full range of IBM i futurization:
- Profound UI replaces 5250 display files with Rich Display Files that render as native web pages in any browser.
- Agentic Display Files (available with CoderFlow) let AI agents generate screens directly in HTML, CSS, and JavaScript, removing the widget ceiling and dramatically accelerating interface development without touching the RPG underneath.
- Genie web-enables existing green screens immediately, without code changes, as a practical first step while deeper futurization proceeds.
- Profound.js enables teams to build new application capabilities in Node.js that call RPG programs directly and access Db2 data natively.
- Atrium unifies all applications, legacy and futurized alike, through a single consistent web-based portal so users navigate seamlessly regardless of where a given program sits in the futurization timeline.
- Profound AI lets organizations build and deploy AI assistants directly within their applications, connecting to leading LLMs from providers like OpenAI and Google, drawing on live business data for real-time intelligence, and integrating with IBM i through MCP, all without extensive coding or AI expertise.
The coexistence architecture that underpins Profound AppDev is what makes this practical for organizations that cannot afford a big-bang transformation. Futurization happens one program at a time. The highest-traffic, highest-visibility applications go first. Business continuity is maintained throughout. The risk profile is fundamentally different from a rewrite, and so is the timeline.
The CTO's Calculation
For CTOs and IT directors reading this, the question is probably already forming: At what point does deferred futurization cost more than the investment required to address it?
The honest answer is that many organizations have already passed that point without recognizing it.
The competitive signal that green screens send is not loudly announced by the market. It shows up as recruiting friction that gets attributed to other causes. It shows up as customer portal feedback that gets treated as a UX wish list. It shows up as partner relationships that are slightly more complicated than they should be. The costs are real but distributed, which makes them easy to rationalize as manageable.
The organizations that act while the window is open, while experienced developers are still available to guide the transition, will be in a fundamentally different position than those who wait until the internal capacity to execute has thinned further.
The competitive risk of staying on green screens is not a future scenario. It is an active condition for any organization whose industry peers have moved and whose customer, candidate, and partner audiences are now forming impressions on the basis of that comparison.
The technology to address it exists. The path is incremental, not disruptive. The business case for moving is clearer than it has ever been.
Starting the Conversation
If your organization is ready to take a clear-eyed look at where your IBM i applications stand relative to the expectations of the people who interact with them, Profound AppDev provides the foundation for that conversation.
The place to start is not a full transformation plan. It is an honest assessment of which applications are most visible to customers and partners, which interfaces generate the most friction for users, and what a phased futurization path would look like for your specific environment.
Ready to explore what that looks like? Reach out to our team at Futurization@ProfoundLogic.com or visit profoundlogic.com/profound-appdev.