Digital Mastery, Applied Intelligence And Motility: A Framework For Modernizing The Insurance core

Insurance core modernization requires more than a mainframe exit strategy. Digital Mastery, Applied Intelligence and Motility provide a framework for understanding the application estate, applying AI where it creates value, and continuously evaluating where each workload belongs.

Five articles, three disciplines, one argument: insurance carriers don’t need an exit plan, they need to master what they run, apply intelligence where it earns its place, and keep every workload in motion toward where it belongs.

Throughout this blog series, we asked five questions about the mainframe in the age of generative AI:

• Is exit the right question?
• Is everything old really technical debt?
• Where does AI genuinely help?
• Where does intelligence belong architecturally?
• What operating model replaces the one-time migration project?

Together, the answers to these questions describe a single framework built on three disciplines: Digital Mastery, Applied Intelligence and Motility.

This final article brings them together, shows how they depend on one another and explains what it takes for an insurance executive to put them to work.

Three Disciplines, One Operating Model

Most modernization programs start with a destination: get off the platform, move to the cloud, replace the core. The framework in this series starts somewhere else. It starts with a capability a insurance carrier should build before any destination can be chosen well, adds the right use of intelligence and makes it a continuous process rather than a one-time event.

Discipline	The question it answers	What it replaces	Where the series covered it
Digital Mastery	What do we run, what does it know and what depends on it?	Treating the estate as a single block of technical debt	Articles one and two
Applied Intelligence	Where does AI genuinely earn its place, and where should it run?	Adopting AI because the market promised a magic converter	Articles three and four
Motility	Where does each workload belong today, and how do we keep answering that?	A one-time exit or migration decision	Article five

Digital Mastery: Having Command of What you Run

Digital Mastery is the discipline of knowing your estate well enough to make good decisions about it. It’s not about owning the newest technology; it’s about the command of understanding what each system does, why it exists, what depends on it and what it would cost the business to lose it.

Mastery is the foundation. Without it, every later decision — about AI, about platforms, about pricing — is made partly blind.

Applied Intelligence: AI Where it Earns its Place

The word we use deliberately is applied. Adopting AI is a purchasing decision. Applying it is an engineering and governance decision, made workload by workload, with evidence. Applied Intelligence has two halves.

First: Apply it Where the Evidence Is

In code understanding and documentation, AI is advancing quickly and already producing results. In one recent engagement, Ensono helped UK insurer Markerstudy use AI to analyze 6 million lines of legacy code and identify a savings opportunity of more than the equivalent of $13 million a year.

In IT operations, the gains are equally practical. Ensono’s internal teams have used AI to resolve incidents up to 70% faster, and the same pattern extends to anomaly detection, capacity forecasting, runbook automation and observability across hybrid stacks. In code conversion, the story is more cautious. AI can accelerate a first pass, but conversion output in a regulated business needs the same rigor as any other high-consequence decision.

Second: Apply it Where the Data Lives

For regulated systems of record, the safer default is increasingly to bring intelligence to the data rather than copy the data to wherever the AI happens to live. Policy, claims and financial transaction records carry audit, residency and latency obligations that get harder to meet with each hop off-platform.

IBM’s z17 makes the point physical: its Telum II processor puts AI acceleration on the chip itself, capable of more than 450 billion inference operations a day at roughly one-millisecond response — fast enough to score a transaction for risk or fraud in the same pass that processes it.

This also changes how AI agents should be judged. The question is no longer how many agents a carrier can stand up, but how well it can run them with visibility, governance, and the security and audit posture of the platform beneath them. Proximity to the system of record isn’t only a performance argument. It’s what makes an agent operating on regulated data governable in the first place.

Motility: Keeping Every Workload in Motion

Motility is the operating model that turns mastery and intelligence into a continuing capability. It replaces the single, one-time decision — exit or stay, migrate or don’t — with a repeatable evaluation of each workload against the variables that determine where it belongs:

• Business criticality: differentiated value or commodity function?
• Cost: what it takes to run, license and support it where it sits versus elsewhere.
• Compliance exposure: the regulatory obligations attached to the workload and its data.
• Latency: whether it needs decisioning close to the system of record.
• Data gravity: the accumulated history behind it and the cost of moving it.
• Resiliency needs: the availability, security and transactional integrity it requires.
• Modernization readiness: whether it’s legacy ready to retire or heritage that needs a careful, incremental path.

Each workload can land in a different place: optimized in place on the mainframe, moved to cloud or distributed infrastructure, replaced by SaaS, or consumed as mainframe-as-a-service. Since the inputs keep changing — with regulations, talent, cost and AI capability all moving — the answer for any workload can change too. A workload placed correctly in 2024 may not be placed correctly in 2027, not because anyone erred but because the estate is alive.

How the Three Disciplines Reinforce Each Other

These three disciplines aren’t a checklist. They form a loop, and each one makes the others stronger.

• Mastery tells Applied Intelligence where to look. Knowing which systems are heritage and which are legacy directs AI toward understanding what must be preserved and away from converting what should simply be retired.
• Applied Intelligence deepens Mastery. Every system AI helps document, instrument and explain becomes a system the carrier understands better, shrinking knowledge debt as a side effect.
• Mastery and Applied Intelligence make Motility possible. A placement decision is only as good as the understanding behind it and the evidence supporting it. Without both, continuous placement is guesswork repeated on a schedule.
• Motility feeds both back. Each placement decision changes the estate, creating new things to master and new places for intelligence to be applied.

Why the Commercial Model Has to Move Too

There’s a business model implication here that reaches beyond the mainframe. For decades, technology services have run on a simple equation: more work requires more people, and more people generate more revenue.

AI is breaking that equation.

A partner that merely uses AI to run the old migration model 10-20% faster will find that clients stop paying for effort long before they stop needing outcomes.

An engagement built on these three disciplines looks different. It’s not a team sized to a project; it’s a standing capability sized to the estate. It’s measured by what it delivers: decisions made well, risk reduced, cost released for modernization that matters, and knowledge preserved. That’s the practical meaning of an outcomes-based relationship in this domain.

What Insurance Executives Can do Next

None of this requires waiting for a perfect program. A sensible first set of moves is modest and concrete:

• Build an honest inventory. List the workloads that carry rating, underwriting, claims and billing logic, and sort them into legacy and heritage.
• Find the knowledge risk. Identify which heritage systems depend on a handful of retiring specialists, and start capturing what they know.
• Start applying AI where the evidence is, such as code understanding, documentation and IT operations, before conversion.
• Test the data proximity default. For AI use cases touching regulated records, evaluate running the capability on the platform before assuming the data has to move.
• Make placement a standing practice. Put the seven variables to work as a recurring review of the estate, not a one-time exercise.

This closes the loop on the five articles in our series on mainframe strategy in the age of generative AI. The thread through all of them: stop asking how to get off the platform and start building the capability to know what you run, apply intelligence where it earns its place;,and keep every workload moving toward where it belongs. 

Frequently Asked Questions

What is Digital Mastery?

Digital Mastery is command of your technology estate: understanding what each system does, why it exists, what depends on it and what knowledge it carries. In insurance, it means being able to tell legacy applications that should be retired from heritage applications that encode rating, underwriting and claims logic the business depends on.

What is Applied Intelligence, and how is it different from adopting AI?

Applied Intelligence is the deliberate use of AI where evidence shows it works and where it can run safely, workload by workload, with governance matched to the stakes. Adopting AI is a purchase; applying it is an engineering and governance discipline. In practice, it means leading with code understanding, documentation and IT operations, and bringing intelligence close to regulated data.

What is Motility?

Motility is the ongoing discipline of deciding where each workload should run, across mainframe, cloud, SaaS, distributed and mainframe-as-a-service models, based on business criticality, cost, compliance exposure, latency, data gravity, resiliency needs and modernization readiness. It replaces a one-time migration decision with a continuous evaluation.

How do the three disciplines work together?

Mastery shows where AI should be applied. Applied Intelligence improves mastery by documenting and instrumenting systems. Together they give Motility the understanding and evidence it needs to place workloads well, and each placement decision creates new things to master.

Does this mean carriers should stay on the mainframe?

No. It means the decision should be made workload by workload. Some workloads belong on the mainframe, some in the cloud, some in SaaS, and some should be retired. The framework is about making that determination well and keeping it current, not about defending any one platform.