UI / UX Design
Dashboard Redesign
The admin panel dashboard suffered from low reliability and poor adoption.
Although it was intended to be the main source of truth, in practice it failed to fulfill that role.
This led to operational dependency, increased internal costs, and a fragmented client experience.
At the same time, the product was undergoing a broader admin panel rebranding, aimed at elevating perceived value, modernizing the experience, and supporting long-term scalability.
Year :
2024
Industry :
Tech
Client :
Alloyal
Project Duration :
2 Years
Problem
The initial analysis revealed five critical areas:
Data inconsistency
• Calculation errors and mismatched metrics
• Loss of trust in the dashboard
Loss of trust in the dashboard
• Low client adoption
• The main persona (B2B client) avoided using the dashboard
Preference for indirect channels to access data
• Operational overload
• High volume of requests directed to Customer Success
Constant dependency for data interpretation and extraction
• Use of external tools
• CS team relied on Looker for reliable reporting
High volume of support tickets
• Frequent requests for data correction and validation
• Increased operational cost and noise
Dashboard Original version
Goal
Reposition the dashboard as:
• A single source of truth
• A self-service tool for clients
• A way to reduce operational load for CS
• A strategic product within the admin ecosystem
Additionally:
• Elevate product perception through rebranding
• Establish a scalable foundation with a Design System
Approach
1 - Data validation with real stakeholders
• Direct alignment with:
• Customer Success team
• Active clients
• Cross-checking:
• Displayed data vs. operational data (Looker and other sources)
Outcome: Clear identification of inconsistencies and redefinition of calculation logic
2 - Dashboard information architecture redesign
• Organized by product domains:
• Subscriptions
• Points management
• Cashback
• Clear separation between:
• Strategic KPIs
• Operational data
• Progressive disclosure (overview → details)
3 - Expanded data coverage
Before: limited and non-actionable insights
After: dedicated dashboards per domain
• Subscriptions
• Recurring revenue, churn, active base
• Points
• Accrual, expiration, balance
• Cashback
• Transaction volume, returns, usage
4 - Focus on client autonomy
• Reduced dependency on Customer Success
• Introduced:
• CSV data export
• Clear and comparable visualizations
• Intuitive data structure
5 - Visual evolution, consistency, and rebranding
• The project was part of a broader admin panel rebranding initiative, aimed at repositioning the product as a more modern, reliable, and scalable solution.
• Creation of a dedicated Design System
• A structural foundation to support the new visual and strategic positioning
• Ensures consistency within a white-label environment, allowing customization without losing coherence
• Standardization of:
• Components
• Charts
• Typography
• States (error, empty, loading)
• Interface evolution:
• Reduced visual inconsistencies from the previous version
• Increased perception of quality and reliability
• Alignment with modern SaaS standards
Outcome: The Design System evolved from a UI asset into a strategic pillar of the rebranding, enabling consistency, scalability, and a more mature product experience.
Solution
A redesigned dashboard experience based on three pillars:
Reliability
• Data validated with CS and clients
• Consistent and reviewed calculation logic
Clarity
• Strong visual hierarchy
• Progressive and contextual data reading
Autonomy
• Data export capabilities
• Reduced reliance on CS
• Centralized information within the product
Results
For Clients
• Easier data interpretation and analysis
• Reduced need for support
• Increased trust in the platform
For internal teams
• Significant reduction in dashboard-related tickets
• Reduced reliance on external tools (Looker)
• Lower operational load for Customer Success
For the product
• Dashboard repositioned as a strategic feature
• Improved perception of modernity in the admin panel
• Strong foundation for future scalability
Feedback
• “We significantly reduced the number of tickets related to data inconsistencies.” • “Clients are asking fewer questions about basic metrics — conversations are now more strategic.” • “We no longer need to rely on Looker for most client requests, which saves time and reduces context switching.”
CS Team
• “This is the first time the dashboard is being used as a product feature, not just a support tool.” • “The Design System helped us move faster and maintain consistency across new dashboard modules.” • “We now have a scalable foundation to expand analytics across other products.”
Product Team
Key Learnings
Reliable data matters more than visuals
Without validating with real users (CS + clients), dashboards fail.
Dashboards are not just visualizations — they are decision-making tools
Centralizing data reduces operational costs and increases product value
A Design System is not just UI — it’s product infrastructure.
UI / UX Design
Dashboard Redesign
The admin panel dashboard suffered from low reliability and poor adoption.
Although it was intended to be the main source of truth, in practice it failed to fulfill that role.
This led to operational dependency, increased internal costs, and a fragmented client experience.
At the same time, the product was undergoing a broader admin panel rebranding, aimed at elevating perceived value, modernizing the experience, and supporting long-term scalability.
Year :
2024
Industry :
Tech
Client :
Alloyal
Project Duration :
2 Years
Problem
The initial analysis revealed five critical areas:
Data inconsistency
• Calculation errors and mismatched metrics
• Loss of trust in the dashboard
Loss of trust in the dashboard
• Low client adoption
• The main persona (B2B client) avoided using the dashboard
Preference for indirect channels to access data
• Operational overload
• High volume of requests directed to Customer Success
Constant dependency for data interpretation and extraction
• Use of external tools
• CS team relied on Looker for reliable reporting
High volume of support tickets
• Frequent requests for data correction and validation
• Increased operational cost and noise
Dashboard Original version
Goal
Reposition the dashboard as:
• A single source of truth
• A self-service tool for clients
• A way to reduce operational load for CS
• A strategic product within the admin ecosystem
Additionally:
• Elevate product perception through rebranding
• Establish a scalable foundation with a Design System
Approach
1 - Data validation with real stakeholders
• Direct alignment with:
• Customer Success team
• Active clients
• Cross-checking:
• Displayed data vs. operational data (Looker and other sources)
Outcome: Clear identification of inconsistencies and redefinition of calculation logic
2 - Dashboard information architecture redesign
• Organized by product domains:
• Subscriptions
• Points management
• Cashback
• Clear separation between:
• Strategic KPIs
• Operational data
• Progressive disclosure (overview → details)
3 - Expanded data coverage
Before: limited and non-actionable insights
After: dedicated dashboards per domain
• Subscriptions
• Recurring revenue, churn, active base
• Points
• Accrual, expiration, balance
• Cashback
• Transaction volume, returns, usage
4 - Focus on client autonomy
• Reduced dependency on Customer Success
• Introduced:
• CSV data export
• Clear and comparable visualizations
• Intuitive data structure
5 - Visual evolution, consistency, and rebranding
• The project was part of a broader admin panel rebranding initiative, aimed at repositioning the product as a more modern, reliable, and scalable solution.
• Creation of a dedicated Design System
• A structural foundation to support the new visual and strategic positioning
• Ensures consistency within a white-label environment, allowing customization without losing coherence
• Standardization of:
• Components
• Charts
• Typography
• States (error, empty, loading)
• Interface evolution:
• Reduced visual inconsistencies from the previous version
• Increased perception of quality and reliability
• Alignment with modern SaaS standards
Outcome: The Design System evolved from a UI asset into a strategic pillar of the rebranding, enabling consistency, scalability, and a more mature product experience.
Solution
A redesigned dashboard experience based on three pillars:
Reliability
• Data validated with CS and clients
• Consistent and reviewed calculation logic
Clarity
• Strong visual hierarchy
• Progressive and contextual data reading
Autonomy
• Data export capabilities
• Reduced reliance on CS
• Centralized information within the product
Results
For Clients
• Easier data interpretation and analysis
• Reduced need for support
• Increased trust in the platform
For internal teams
• Significant reduction in dashboard-related tickets
• Reduced reliance on external tools (Looker)
• Lower operational load for Customer Success
For the product
• Dashboard repositioned as a strategic feature
• Improved perception of modernity in the admin panel
• Strong foundation for future scalability
Feedback
• “We significantly reduced the number of tickets related to data inconsistencies.” • “Clients are asking fewer questions about basic metrics — conversations are now more strategic.” • “We no longer need to rely on Looker for most client requests, which saves time and reduces context switching.”
CS Team
• “This is the first time the dashboard is being used as a product feature, not just a support tool.” • “The Design System helped us move faster and maintain consistency across new dashboard modules.” • “We now have a scalable foundation to expand analytics across other products.”
Product Team
Key Learnings
Reliable data matters more than visuals
Without validating with real users (CS + clients), dashboards fail.
Dashboards are not just visualizations — they are decision-making tools
Centralizing data reduces operational costs and increases product value
A Design System is not just UI — it’s product infrastructure.
UI / UX Design
Dashboard Redesign
The admin panel dashboard suffered from low reliability and poor adoption.
Although it was intended to be the main source of truth, in practice it failed to fulfill that role.
This led to operational dependency, increased internal costs, and a fragmented client experience.
At the same time, the product was undergoing a broader admin panel rebranding, aimed at elevating perceived value, modernizing the experience, and supporting long-term scalability.
Year :
2024
Industry :
Tech
Client :
Alloyal
Project Duration :
2 Years
Problem
The initial analysis revealed five critical areas:
Data inconsistency
• Calculation errors and mismatched metrics
• Loss of trust in the dashboard
Loss of trust in the dashboard
• Low client adoption
• The main persona (B2B client) avoided using the dashboard
Preference for indirect channels to access data
• Operational overload
• High volume of requests directed to Customer Success
Constant dependency for data interpretation and extraction
• Use of external tools
• CS team relied on Looker for reliable reporting
High volume of support tickets
• Frequent requests for data correction and validation
• Increased operational cost and noise
Dashboard Original version
Goal
Reposition the dashboard as:
• A single source of truth
• A self-service tool for clients
• A way to reduce operational load for CS
• A strategic product within the admin ecosystem
Additionally:
• Elevate product perception through rebranding
• Establish a scalable foundation with a Design System
Approach
1 - Data validation with real stakeholders
• Direct alignment with:
• Customer Success team
• Active clients
• Cross-checking:
• Displayed data vs. operational data (Looker and other sources)
Outcome: Clear identification of inconsistencies and redefinition of calculation logic
2 - Dashboard information architecture redesign
• Organized by product domains:
• Subscriptions
• Points management
• Cashback
• Clear separation between:
• Strategic KPIs
• Operational data
• Progressive disclosure (overview → details)
3 - Expanded data coverage
Before: limited and non-actionable insights
After: dedicated dashboards per domain
• Subscriptions
• Recurring revenue, churn, active base
• Points
• Accrual, expiration, balance
• Cashback
• Transaction volume, returns, usage
4 - Focus on client autonomy
• Reduced dependency on Customer Success
• Introduced:
• CSV data export
• Clear and comparable visualizations
• Intuitive data structure
5 - Visual evolution, consistency, and rebranding
• The project was part of a broader admin panel rebranding initiative, aimed at repositioning the product as a more modern, reliable, and scalable solution.
• Creation of a dedicated Design System
• A structural foundation to support the new visual and strategic positioning
• Ensures consistency within a white-label environment, allowing customization without losing coherence
• Standardization of:
• Components
• Charts
• Typography
• States (error, empty, loading)
• Interface evolution:
• Reduced visual inconsistencies from the previous version
• Increased perception of quality and reliability
• Alignment with modern SaaS standards
Outcome: The Design System evolved from a UI asset into a strategic pillar of the rebranding, enabling consistency, scalability, and a more mature product experience.
Solution
A redesigned dashboard experience based on three pillars:
Reliability
• Data validated with CS and clients
• Consistent and reviewed calculation logic
Clarity
• Strong visual hierarchy
• Progressive and contextual data reading
Autonomy
• Data export capabilities
• Reduced reliance on CS
• Centralized information within the product
Results
For Clients
• Easier data interpretation and analysis
• Reduced need for support
• Increased trust in the platform
For internal teams
• Significant reduction in dashboard-related tickets
• Reduced reliance on external tools (Looker)
• Lower operational load for Customer Success
For the product
• Dashboard repositioned as a strategic feature
• Improved perception of modernity in the admin panel
• Strong foundation for future scalability
Feedback
• “We significantly reduced the number of tickets related to data inconsistencies.” • “Clients are asking fewer questions about basic metrics — conversations are now more strategic.” • “We no longer need to rely on Looker for most client requests, which saves time and reduces context switching.”
CS Team
• “This is the first time the dashboard is being used as a product feature, not just a support tool.” • “The Design System helped us move faster and maintain consistency across new dashboard modules.” • “We now have a scalable foundation to expand analytics across other products.”
Product Team
Key Learnings
Reliable data matters more than visuals
Without validating with real users (CS + clients), dashboards fail.
Dashboards are not just visualizations — they are decision-making tools
Centralizing data reduces operational costs and increases product value
A Design System is not just UI — it’s product infrastructure.