Case Study Deskcasestudydesk.com
FintechSourced

Case Study: Scalapay cut data-issue support tickets to zero with Elementary

Scalapay Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Scalapay
Industry
Fintech
Challenge
Recurring data issues generated weekly support tickets and slow diagnosis
Headline result
How Scalapay eliminated weekly data-issue support tickets with Elementary

Key results

Zero
Weekly data-issue support tickets
Down from a few each week
Minutes
Time to diagnose data issues
Down from hours/days

The challenge

Scalapay's data team fielded a handful of support tickets each week caused by data-quality issues in its dbt pipelines. Diagnosing the root cause of a given issue could take hours or days. The team lacked a systematic way to detect and triage failures before they reached downstream consumers.

The solution

Scalapay adopted Elementary's dbt-native observability, running data-quality and anomaly tests and centralizing test-failure reporting in Elementary Cloud. Alerting and lineage helped the team catch issues earlier and trace them to their source.

Since implementing Elementary we've effectively reduced our support tickets from a few each week to zero.

ZD
Zachary Damcevski
Data Engineer, Scalapay

The results, in context

After implementing Elementary, Scalapay reduced data-issue support tickets from a few each week to zero, per its data engineer. Elementary's published story also reports time to diagnose data issues dropping from hours or days to minutes. Figures are the company's own published claims, quoted from Elementary's customer story and dated.

Products used

Elementary Elementary CloudElementary Elementary OSS (dbt package)