Get the free AI Delivery Playbook
AkveoContact us

How We Refactored an Inefficient Reporting Solution

The implementation of a data warehouse, ELT process, Customer Portal, and Reports for a US-based messaging platform, reducing development time by 58%.

How We Refactored an Inefficient Reporting Solution

[ Client ]

About the Client

The client is a US-based developer of a messaging platform.

400Gb
Data Warehouse Size Managed
40%
Reduction in Design Development
58%
Reduction in Total Dev Time

[ Challenge ]

A Reporting System Built Without Engineering Discipline

The client had a reporting system for the messenger, but the previous development team implemented it without sticking to a proper engineering approach. This way:

  • Each feature was implemented irrespective of the solution as a whole. This happened due to the lack of a thorough approach towards the solution’s architecture;
  • It was impossible to locate a specific feature as a mixed bunch of tools and technologies were used on the project: a mix of both cloud/on-premise environments and languages (Python, Perl, SQL, and Bash);
  • The documentation was missing.

[ Solution ]

Building the Solution

Our team started out by analyzing the solution and improvement requests. Secondly, the team designed a new solution's architecture and suggested a set of scalable and cost-effective software tools needed to implement the required features.

Our team developed the data warehouse, ETL process, Customer Portal, and Reports from scratch. Then, we enabled direct access to data in the multi-tenant data warehouse.

Technical Details

  • The data warehouse size is 400Gb
  • ETL runs 1 time/day processing 1Gb
  • 150 tenants in a single data warehouse
  • 3000 reports being generated and emailed daily

Key Achievements

We've got a straightforward and well-documented solution ready to be scaled in regard to the current workload. The new version provides a cost-effective way for owners as the solution only charges during processing and not when idle. Our team successfully:

Analyzed the previous solution’s version

Our team analyzed the solution’s former version and documented the improvement requirements.

Prepared a solution proposal

We prepared a new solution proposal that included new architecture and the description of the mailing features. Plus, we suggested a set of software tools for the project.

Made a transition

The team implemented the project and made a smooth transition from the former solution to the new one.

[ Results ]

Impact that Matters

The team delivered a simple, well-documented solution ready to scale. The new version only charges during active processing rather than when idle, making it cost-effective.

58% faster delivery

Total development time was reduced by 58% compared to the original system, thanks to a coherent architecture and clearly defined tooling from the start.

40% faster design dev

Web app design development was reduced by 40% through reusable components and a well-structured design system applied across the Customer Portal.

Cost-efficient and scalable

The new solution is well-documented and scalable, only charging during active processing rather than when idle, giving the client meaningful infrastructure cost savings.

[ Tech Stack ]

Technologies Behind the Project

Data Warehouse

Microsoft SQL Server

Backend & ETL

Python

Infrastructure

AWS

Visuals

How We Refactored an Inefficient Reporting Solution visual 1

[ Case Studies ]

Explore More Success Stories

We have helped over 200 businesses grow their value and improve how they work through better software.

Ready to Build with AI?

Let’s discuss your goals and how AI can help you achieve them faster.

Dmitry Klim
Dmitry Klim
Head of Growth
Clutch
5900 Balcones Drive #21729, Austin, TX 78731[email protected]+1 (512) 921-9631