Leon's Approach to AI: Medium- and Long-Term Strategic Position

Strategic Position

Leon's use of AI is not a new strategic direction. It is an extension of the principles that have guided the platform since its inception:

• Using technology to increase operational efficiency.
• Making premium capabilities, previously accessible only at high price points, available to a broad base of operators.
• Reducing the complexity of advanced functionality so it is usable without specialist technical knowledge.
• Maximizing the degree to which the platform can be customized to an operator's specific requirements.

AI is applied to these existing goals rather than treated as a separate initiative. This has two practical implications for operators evaluating Leon over a multi-year horizon: customization built with AI assistance remains fully under the operator's control, and the platform's investment in AI is directed at extending capability, not at replacing the operator's ability to configure and verify how the system behaves.

Customer-Facing Applications

AI is applied to customer-facing functionality along two tracks: reducing the technical barrier to customization, and preparing Leon to operate within multi-system, agent-coordinated workflows.

Reducing the technical barrier for customization

The first track uses AI within features that let operators adapt Leon to their own operational requirements. Current examples include roster validation rules and complex flight pricing calculations. In both cases, AI generates the underlying rule logic.

The distinction that matters: AI does not generate output presented directly to the end customer, and it does not make operational decisions on its own. It functions as a generator of deterministic, testable rules — output that is fully inspectable and verifiable regardless of how it was produced, and that always sits behind an explicit, auditable rule rather than an opaque AI judgment. Each operator maintains its own distinct configuration. The practical effect is that configuring these features no longer requires a developer; it requires domain knowledge of the business logic involved.

The same model applies to the AI Assistants built into the Document Manager and Report Wizard: capabilities that previously required programming knowledge are now accessible to users with domain expertise but no coding background. The platform's underlying determinism is unchanged — what changes is who can build within it.

For operators, this means that AI-assisted customization is not a black box: every rule it produces can be reviewed, tested, and modified independently of the tool that generated it.

Positioning Leon for agentic, multi-system workflows

The second track addresses how Leon fits into workflows that span multiple systems. Most operational workflows are not confined to a single platform. Leon is frequently the central system in these workflows, but it remains one component among several. As operators move toward automating end-to-end processes, they are increasingly coordinating them
using AI agents.

This is a current, not hypothetical, requirement. AI systems have matured to a point where they support workflows that are both extensive in scope and predictable in behavior. Major providers now offer established ecosystems of skills, connectors, plugins, and hooks that measurably reduce the time required for well-defined tasks — several years after the initial wave of generative AI tools, this category has reached a stage where it produces quantifiable operational value rather than experimental results.

Leon's current integration model was designed for direct, point-to-point data exchange between systems. That model is not structured to support agents composing actions across systems dynamically, and it is not sufficient on its own to make Leon a functional participant in agent-driven workflows.

This is the rationale for developing Leon's MCP server and an accompanying marketplace of AI skills: to give operators the technical means to incorporate Leon into automated, agent-coordinated processes as that mode of operation becomes standard, rather than requiring them to work around it. Over the coming quarters, this will translate into an expanding set of skills and connectors available directly to operators, extending the same MCP foundation.

Internal Use as Supporting Context

Internally, AI also supports the team responsible for operating and maintaining Leon — in particular, extending the context and capacity available to support external integrators and to keep technical documentation current as the platform evolves. This is mentioned here only as context: it reflects the same operating principles described above, applied internally
rather than in the product.

Summary

Leon's AI strategy is consistent with its historical approach to technology adoption: apply new capabilities to established goals — efficiency, accessibility, simplification, and customization — rather than treating AI as an end in itself. Investment in agent-compatible infrastructure (the MCP server and skills marketplace) is intended to ensure the platform remains a viable, technically current foundation for operators building automated, multi-system operations over the medium and long term.

Not yet a member of Leon community? Contact our Sales team to find out more or jump straight into the 30-day free trial.