Enterprise data teams face a classic dilemma: textbooks say every table must be cleaned and modeled before it can be queried. IFS Copperleaf has nearly 30 source systems and tens of thousands of tables; if they followed this process in sequence, modeling would never finish. Misagh Jebeli, the Enterprise Data Architect, recalls that they initially did exactly that, but soon realized that path was unworkable.
They made a counterintuitive decision: maintain full modeling only for high-risk areas such as finance and the marketing-to-sales funnel, while letting AI answer questions directly on raw data for everything else, with business teams teaching AI to understand the meaning of that data. Jebeli summarized this as a 180-degree turn—letting AI work on raw data and letting the business tell it what the data means. He described it as a huge gamble, but one that made the project succeed.
This gamble succeeded thanks to the shared business context layer provided by Genie Ontology. Skills sit atop the Ontology, allowing business teams to directly correct AI understanding during conversations: excluding partner accounts, converting amounts to euros, setting renewal start dates—all without needing engineers to change code. Lisa Richter pointed out that when AI gives wrong answers, correcting it is easier than abandoning it, so those who never wanted to join data governance committees started doing governance proactively.
However, allowing business users to write logic directly and change numbers seen across the entire company was a cultural shock for technical teams. Richter admitted that five years ago she would have shut this down herself—no tickets, no sprints, no release cycles, yet business users were changing definitions right in conversations. She eventually accepted this reality: a small team could never know what every number meant across the whole company; the owners of the definitions are the ones who do. So instead of putting up gates, they put up guardrails: every definition has a named owner, and the AI Council reviews them before promotion to the entire company.
Another layer of the governance architecture is access control via Unity Catalog. Richter emphasized that AI cannot change access rules—no Skill, prompt, or AI tool can allow someone to see data they are not already permitted to view. Sensitive information remains within governed environments, accessible only to those whose roles require it.
IONA launched company-wide in July 2026, subsequently achieving a 70% activation rate and a 68% 30-day repeat usage rate. Four months after launch, the human capacity released by IONA covered its operating costs. The marketing team reduced pipeline analysis, which previously required weeks of manual integration, to seconds; financial currency conversion rules, defined once, are now automatically applied to all revenue answers; customer service managers can obtain a complete story of client contract terms, open tickets, and product versions an hour before a renewal call.
The boundaries that must be preserved are: all figures above are self-reported by IFS Copperleaf and have not yet been independently verified. Jebeli and Richter describe an implementation path suitable for multi-system environments with inconsistent definitions, but whether it can be migrated depends on whether the organization is willing to hand over semantic definition rights from the data team to the business team, and whether there are sufficient governance mechanisms to prevent the spread of incorrect definitions. Their own advice is: model high-risk areas first, let the business teach AI the rest—the order itself may be more critical than specific tool choices.