SIGNAL4i — AI Intelligence for IBM i Organizations

The Execution
Signal.
Architecture Doesn't
Deploy Itself.

Vol. 3 named the stack. The IBM i MCP Server is live. Mapepire is in production. The architecture exists and is documented. So why aren't organizations running? Vol. 4 answers that. The barrier is not the technology. It is the distance between a named architecture and a deployed agent — and that distance now has a name, a cost, and a person best positioned to close it.

The execution gap is not a technology problem. It is an organizational readiness problem — and the IBM i practitioner has been living in the solution layer for thirty years without calling it that.

signal4i.ai · Vol. 4 · March 23, 2026 · Practitioner-facing · Updated as signals emerge

Signal 13

The Failure Signal

The Stack Is Ready. The Organizations Aren't.

MIT / Fortune / BCG / ManpowerGroup, 2024–2026 — Three convergent data points measuring the same gap from different angles: 95% of generative AI pilots failing, 26% of scaled experiments reaching production, 77% of organizations with no committed agentic strategy.

The readiness statistics have been consistent across multiple research organizations for two years. Their consistency is the point — this is not a temporary lag that resolves itself as organizations get more comfortable with AI. It is a structural gap that widens as AI capability advances faster than organizational readiness. BCG found that roughly three in four enterprise AI experiments that make it through internal approval still never make it to production. They stall in the translation layer between proof-of-concept and organizational deployment. Three organizations. Three methodologies. One finding: the technology arrived. The organizations did not follow.

"The platform is not the problem. Deploying without posture is."

— Signal4i · Vol. 2 · March 2026

The execution gap is real, it is measurable, and it is organizational from top to bottom.

Sources:
MIT / Fortune · mid-2025 · BCG enterprise AI research
ManpowerGroup Workforce 2026 Report

Read on Substack

Signal 14

The FDE Signal

The Market Quantified the Gap. Then Priced It.

Anthropic, 2025–2026 — Anthropic invents the Forward Deployed Engineer role because they kept watching capable organizations fail to deploy capable models. An embedded human who translates in both directions — between what AI can do and what the organization actually needs.

When a company building the most capable AI systems on earth decides it needs to put humans inside its customers' organizations just to make deployment work, that is not a product decision. That is a market signal. The FDE is the answer to a gap Anthropic kept observing: capable organizations acquiring capable models and then failing to deploy them at any meaningful scale. The gap between what the model could do and what the organization was ready to use was consistent, measurable, and not closing on its own. The market is now paying a premium for people who can speak both the language of AI architecture and the language of the business — embedded inside the organization that needs to change. That premium is a price signal. The translation layer between architecture and execution is scarce, valuable, and not going away.

"You cannot hand an organization a model and expect transformation. You need a guide who knows the terrain."

— Signal4i · signal4i.ai

The constraint does not live in the model. It lives in the organization.

Source:
Anthropic FDE role documentation · 2025–2026
Signal4i analysis

Read on Substack

Signal 15

The Scale Signal

$90 Billion. 500,000 Employees. Can't Deploy Until 2027.

WSJ / PYMNTS, March 13, 2026 — FedEx plans AI agents in more than 50% of its workflows by 2028 — but cannot begin deployment until 2027. The reason is not the AI. The reason is the organization: data consolidation not finished, hundreds of legacy systems still unreplaced.

FedEx Chief Digital and Information Officer Vishal Talwar stated the ambition plainly: every employee and every task across the globe will get adapted to AI and will improve with AI. The ambition is real. The investment is committed. And they cannot deploy until 2027. Not because the AI does not exist. Not because the vision is unclear. Because their data consolidation project is not finished. At $90 billion in annual revenue. With 500,000 employees. With a dedicated AI transformation budget that most IBM i organizations in any given sector will never approach. The IBM i organizations in every sector FedEx serves are running the same gap at a smaller scale. Same data silos. Same legacy dependencies. Same governance gaps that were never addressed because the business kept running. Smaller scale cuts both ways — what takes FedEx until 2027 can be addressed by a focused IBM i organization in phases, if they start now.

That is not a technology failure. That is a readiness failure. And it is happening at a company with more resources than every IBM i organization in this room combined.

— Signal4i · Vol. 4 · March 2026

The nature of the gap does not change with the size of the organization. Only the scale does.

Sources:
WSJ · PYMNTS · March 13, 2026
FedEx CDO Vishal Talwar public statements

Read on Substack

Signal 16

The Practitioner Signal

The IBM i Practitioner Is the Natural FDE.

Signal4i analysis, 2026 — The characteristics the market is now paying premium for are characteristics the IBM i practitioner has been building for thirty years: deep business knowledge, technical architecture fluency, organizational embedding, earned trust, and the ability to translate in both directions without losing fidelity.

What does a Forward Deployed Engineer actually need to do? Understand the business deeply enough to know what the organization is actually trying to accomplish. Know the technical architecture well enough to design what agents can realistically do. Translate between those two worlds without losing fidelity in either direction. Be embedded enough to earn the trust of the people whose knowledge needs to be encoded. Now read that description again and ask: who in the IBM i world already does this? The IBM i practitioner has been doing exactly this for thirty years. The translation layer between AI architecture and organizational deployment — the thing Anthropic invented a new job category to fill — is the thing the IBM i practitioner has been living in for decades. Karpathy: "The bottleneck was never intelligence — it was the translation layer between knowing and building." That layer is collapsing. The IBM i practitioner is now on both sides of it simultaneously.

"The bottleneck was never intelligence — it was the translation layer between knowing and building. That layer is collapsing."

— Andrej Karpathy · Former Director of AI, Tesla · OpenAI

The market is paying premium for that capability. The question is whether the practitioner names it before someone else does.

Sources:
Signal4i analysis · 2026
Andrej Karpathy · Anthropic FDE role documentation

Read on Substack

The Technology Has Arrived.
Is Your Organization Ready?

The complete Signal4i session from PowerUp 2026. The case for why the IBM i practitioner is the most valuable person in the AI economy — and exactly what to do about it. Six movements from identity to destination, built on 92 signals.

6 Movements

24 Slides

92 Signals

45 Min

Modernize → Agentify

Read the Full Session ↗

The Execution
Signal.
Architecture Doesn't
Deploy Itself.

The Stack Is Ready. The Organizations Aren't.

The Market Quantified the Gap. Then Priced It.

$90 Billion. 500,000 Employees. Can't Deploy Until 2027.

The IBM i Practitioner Is the Natural FDE.

The Technology Has Arrived.
Is Your Organization Ready?

The Architecture Signal. The Stack IBM i Has Been Waiting For.

The ExecutionSignal.Architecture Doesn'tDeploy Itself.

The Stack Is Ready. The Organizations Aren't.

The Market Quantified the Gap. Then Priced It.

$90 Billion. 500,000 Employees. Can't Deploy Until 2027.

The IBM i Practitioner Is the Natural FDE.

The Technology Has Arrived.Is Your Organization Ready?

The Architecture Signal. The Stack IBM i Has Been Waiting For.

The Execution
Signal.
Architecture Doesn't
Deploy Itself.

The Technology Has Arrived.
Is Your Organization Ready?