SixValues: from fragmented BI to shared understanding.

01 · The story

A growing organisation, a more complicated reporting environment.

SixValues is a B2B organisation supporting multiple iGaming brands across markets and products. With a team of more than 300 people, it needed a way for different departments to understand performance through consistent definitions.

As the organisation grew, a data stack built primarily around Tableau accumulated layers of reporting logic. Dashboards provided visibility, but new questions and changes to existing views often depended on the data team. The problem was becoming as much about how people worked as about which tools they opened.

The transition to Gamblitude brought a dedicated data foundation, governed Metrics and self-service analytical tools together. Its purpose was to give more people a reliable starting point for exploration while reducing the preparation required for routine reporting.

02 · The story

Data was available. Access still depended on a few people.

Different stakeholders could arrive at a meeting using slightly different versions of the same KPI. Checking the definition or adjusting the dashboard created another request for the people who understood the underlying logic. As the reporting environment expanded, so did the work of maintaining it.

Before the transition, only approximately 15–20% of employees actively interacted with data tools. Questions that should have supported everyday decisions could take days to answer.

• Limited access across departments and high dependence on analysts for routine questions.
• Duplicate KPI definitions and discrepancies between the figures different teams used.
• Dashboard updates, ad-hoc reporting and KPI validation competing for the data team’s attention.
• Increasing maintenance effort across dashboards and reporting logic.

SixValues needed a common way to define performance and a practical way for non-technical colleagues to investigate it. Adding more dashboards alone would not resolve those two needs.

03 · The story

Standardise the foundation. Then broaden access.

SixValues moved away from its Tableau-based reporting model and built its analytical foundation on Gamblitude. The rollout centred on shared definitions, self-service access and AI-supported investigation, rather than treating each department’s request as another standalone report.

• A dedicated cloud data warehouse connected the analytical foundation.
• KPI definitions were migrated and standardised in a unified Metrics layer.
• Visual Dashboards and exploration tools gave teams a way to work directly with the data.
• Insight Radar supported recurring monitoring.
• AI Agent provided natural-language access to the same business definitions.

Adoption progressed from core teams to the wider organisation. Users could begin with a familiar dashboard and then ask a follow-up question without introducing another independent definition of the measure. The shared Metrics layer made those different routes part of the same analytical environment.

04 · The story

More users. Less preparation.

Employee data use rose from approximately 20% to over 70%. Time from question to answer fell by approximately 80–90%, report preparation by approximately 90%, and dashboard creation moved from several days to minutes.

Routine questions became less dependent on analysts. Non-technical teams took a more active role in exploration, while multiple redundant dashboards and layers of logic were removed. Teams aligned around KPI definitions, with fewer discrepancies between departments and stronger trust in reported figures.

These changes also affected the data team’s workload. Fewer ad-hoc reporting requests left more time for advanced analysis, modelling and strategic initiatives. The value of a common foundation extended beyond any one chart: it changed who could ask a question and how much preparation the answer required.

05 · The story

Make the first useful question easy to ask.

Moving away from a familiar BI setup can create an adoption challenge of its own. At SixValues, most users began exploring data and building views within their first days of access, with limited formal training. The visual interface and consistent definitions helped teams concentrate on their own use cases.

During onboarding, more than 60% of the targeted users engaged with the platform. They began using the environment directly, rather than simply receiving reports prepared by someone else.

• Routine requests increasingly moved from the data team to self-service exploration.
• Multiple teams began creating and sharing Dashboards and analyses.
• Users could start from established definitions rather than reconstructing the calculation for each view.

The practical change was independence: more people could examine a familiar business question without waiting for a new reporting task to be completed.

06 · The story

A different role for the data team.

The organisational change worked in two directions. Business users gained a more direct route to the information they needed, while the data team spent less of its time serving as the intermediary for every routine question.

The team shifted from preparing information on request towards enabling people to explore, validate and decide for themselves. The data team could put more attention into modelling, data quality and longer-term analytical work. Shared definitions remained part of that foundation as more departments began using it.

07 · The story

The interaction changed after the first dashboard.

At first, many users approached Gamblitude as they had approached their previous BI environment: a dashboard was the main starting point. That was familiar territory and a useful way to begin.

As confidence grew, AI Agent interactions increased from week to week. Users moved beyond consuming a prepared view towards asking their own questions, comparing breakdowns and following up on an answer. Teams that had relied on a small set of predefined dashboards began exploring more independently.

Adoption went beyond opening a tool. More people became active participants in analysis and brought their own questions to the business discussion.

08 · The story

What other teams can take from the story.

• Establish a shared meaning for important KPIs before widening their use.
• Give business users both familiar visual tools and a route for follow-up questions.
• Assess adoption through independent exploration as well as access to the platform.
• Use the reduction in routine reporting work to develop the analytical foundation further.

SixValues began with an established BI environment and a growing reporting burden. Its experience shows why a migration can be an opportunity to change definitions, access and working habits together.