The platform everyone depended on, and nobody could touch
Sýn, Iceland's telco and media group, had accumulated three overlapping warehouses, roughly 1,200 stored procedures holding business logic, half a dozen ETL tools and three BI platforms. Each was justified when it arrived; none was ever retired.
It produced the reports it had to. It also produced 188 incidents a year, and conflicting numbers depending on which warehouse you asked. The data specialists spent their time on reconciliation, fixes and incident response, while the analysis the business actually wanted kept being deferred.
The programme turned on a single reversal: free the people from fixing data, and let them work with it. A Databricks lakehouse gave the foundation. What makes it different is what went in from the first day.
First, one version of everything
Solid foundations come before any AI. Every business source — advertising sales, billing and usage, CRM, the national registry, ERP and planning — now lands in one governed lakehouse with full lineage in Unity Catalog.
Nine business areas keep curated gold workspaces, modelled together with the business owners, alongside certified semantic models where each KPI is defined once — conformed dimensions, row-level security and Git versioning.
That last part carries more weight than it looks. Everything that consumes the platform — a dashboard, an analyst or an AI system — reads the same certified figures, and sees only what it is allowed to see.
AI-native, not AI-added
Most implementations bolt a chatbot on at the end. Sýn's platform was designed with AI inside it, all of it running on Claude models, working both as the operator of the platform and as the interface to the business. Through the Databricks MCP and the Power BI MCP, Claude gets direct, governed access to the lakehouse and the certified semantic models — the data, the KPI definitions and the permission structure together.
The platform runs itself
Self-healing, humans in the loop
Agents watch the pipelines, the data-quality checks and the incident queue, and act on what they find — with human approval required before anything merges.
Engineering, guardrailed
Idea to production, faster and safer
AI writes a substantial share of the platform code inside safety guardrails. Custom skills encode Sýn's own standards, so AI-assisted changes follow the disciplined path rather than around it.
The business asks directly
Plain language, certified answers
Nobody needs to understand the semantic layer. People describe the work they are doing and ask where the data helps; Claude, holding the full business context through the MCPs, answers.
Beyond analysis
A base for AI automation
Turning governed surfaces into tools via MCP makes automation a property of the platform rather than a series of separate projects.
Security by design
The data stays home
Everything runs inside Sýn's secured environment, AI included. The models work where the data already lives.
Master data management — for €40 a month
Master data — product catalogues, reference dimensions, the values everything else joins against — sits in an awkward middle ground: too governed to edit directly, too operational for a ticket queue. At Sýn, updating a dimension meant spreadsheets, emails and engineering time.
So we built a governed write-back loop, driven from chat. Business users read and change master data conversationally in Claude Desktop, without raw lakehouse write access and without stepping around governance. Identity is checked at the door, privilege is minimal throughout, and nothing reaches the lakehouse on a model's say-so — only on a human's confirmation.
A custom skill parses uploads — xlsx, csv, pdf — maps values to the dimension schema and shows a confirmation table. An MCP server on Azure Container Apps exposes read and write over a stateless HTTP endpoint, with Entra ID validating every token through OAuth 2.1, Conditional Access and MFA, and Managed Identity connecting to storage and Databricks without stored secrets. Confirmed changes land as parquet in a dedicated master-data store — an immutable record — and Delta Live Tables validate, enrich and promote them through bronze, silver and gold to the golden record.
Because Databricks, Entra and the networking were already Sýn's, the net-new cost is a container app and a storage account: about €40 a month. The first dimension, the product catalogue, went from kick-off to production in six to eight weeks, and the pattern extends to any other dimension.
“Master data used to mean tickets and spreadsheets. Now our product catalog is updated in a conversation — and every change still lands governed, validated and fully audited. It's the first AI tool we trust with writes.”
Half the run-rate, and the team back on analysis
Consolidating the tools into one governed platform ends the arguments about whose number is right. The people who used to keep pipelines alive now sit with the business teams, contributing to the platform directly rather than adding to a backlog.
Folding legacy licences, parallel pilots and ageing infrastructure onto the lakehouse roughly halves the platform's run-rate — while adding the scalability, governance and AI capability that were not available before. Support through the Databricks partnership part-funded the programme, which lowered the up-front investment before the savings began.
Team
- —Filip Strunjak
- —Ihor Protsiv
- —Andriy Zhubryd
Key objectives
Replace three overlapping warehouses, six ETL toolchains and three BI platforms with one governed lakehouse.
Free the data specialists from reconciliation and incident response, and put them back on analysis.
Build AI in from the start — running the platform, guarding the engineering, and answering the business directly.
Services
- —Data platform architecture
- —Data engineering
- —Semantic modelling & BI
- —AI & MCP integration
- —Master data management
Technology
Numbers
~50%
Lower platform run-rate after consolidation
9
Business-area gold workspaces, owned by the business
6→1
ETL toolchains consolidated into one lakehouse
2–3
People freed from firefighting per phase
≈€40
Net-new run cost per month for master data
6–8
Weeks from kick-off to production



