Reporting with List & Label Cross Platform at kessoft

Company: kessoft
Industry: software development
Area of application: web applications, back-end systems, and SaaS applications
Product: List & Label Cross Platform
Website: https://www.kessoft.com/

Initial Situation

We are a software provider focused on the development of customized software solutions for companies. Our portfolio ranges from browser-based applications and app development to back-end systems as well as cloud- and infrastructure-related solutions. Our development team works with a strong cloud focus. Applications are built automatically via GitLab pipelines and operated in a Docker cluster. Technologically, we primarily rely on .NET-based back-end systems as well as web applications built with React and Angular, complemented by desktop development with WPF and WinForms.

Reporting and KPI dashboard of the AUREM platform – optimized for desktop and mobile use.

Reporting Before List & Label Cross Platform

Before using List & Label Cross Platform, we relied on a separate Windows client application for report creation. This application was launched from within the web applications and was solely responsible for generating reports.

This approach resulted in significant organizational and technical overhead. In particular, deployment, maintenance, and version management of the additional client component increasingly no longer aligned with our architecture.

The Trigger for Change

The key trigger for searching for a new reporting solution was the growing complexity caused by the separate Windows client application. Operating, maintaining, and deploying this additional component became increasingly time-consuming.

In addition, we operate a SaaS product in which many users no longer want or are allowed to install desktop applications. A reporting approach that strictly depends on a local Windows client was therefore no longer sustainable in the long term.

Evaluation and Decision

As part of our evaluation, we considered Telerik Reporting in addition to List & Label. The decisive factor in choosing List & Label Cross Platform was, in particular, the designer, which impressed us in terms of functionality, usability, and flexibility and best met our requirements for complex reports.

Implementation and Early Adopter Experience

We deliberately started as an early adopter with List & Label Cross Platform. As expected, typical initial topics arose.

In some areas, the documentation could initially have been more detailed; additional practical examples in particular would have made getting started easier. However, we were able to address this feedback directly: within just a few days, the documentation was specifically expanded and supplemented with exactly the points that proved relevant in practice.

As a result, our specific user feedback directly contributed to the further development of both the product and the documentation.

We currently still see a functional limitation in the area of direct printing, which is particularly important in production environments.

Measurable Benefits

Compared to our previous architecture, we achieved significant performance improvements with List & Label Cross Platform.

Previously, the process from triggering the print command in the web application to launching the separate client application and rendering the report sometimes took up to 8 seconds. Today, this time is approximately 1 second.

This acceleration is immediately noticeable to end users and measurably contributes to higher user satisfaction.

Detailed view of the dashboard with revenue, order, and KPI overviews.

Support and Collaboration

Our experience with combit support has been consistently very positive.

Communication was fast, direct, and on equal footing. We particularly appreciate that combit works very closely with customer feedback and provides practical support—especially a decisive factor during the early adopter phase.

Roadmap

In the future, we plan to gradually replace List & Label Classic with List & Label Cross Platform. A prerequisite for this is that all required functions are fully available, including for more complex reports, so that the transition can take place without functional limitations.

Conclusion