Skip to content
Devendra Jangiddevendra.pro
Data engineering & analyticsIndiaOngoing, running daily

Client engagement — anonymised

Scheduled analytics that catch losses nobody was looking for

A set of scheduled analytics jobs that read the operational database every day, look for patterns a person would never spot by eye, and email the right manager when something looks wrong — while there is still time to do something about it.

Daily
Checks run automatically, unattended
Days, not months
Time to spot a problem
One source
Everyone works from the same numbers
Zero manual
Effort to produce the exception reports
The situation

What was broken

  • Losses from misuse and pricing errors were only found during periodic reviews, far too late
  • Analysis meant someone exporting to a spreadsheet and working through it by hand
  • Different people produced different numbers because everyone built their own extract
  • Nobody was watching the patterns that only show up across days rather than in one transaction
RPostgreSQLSQLAutomated emailScheduled jobs
The work

What was actually done

  1. 01

    Analysis as code, not spreadsheets

    The whole analysis written as versioned scripts reading directly from the database. Same logic every run, reviewable, and no chance of somebody breaking a formula.

  2. 02

    Escalating detection windows

    The same checks run across several time windows, so a pattern that only becomes visible after several days is still caught — and flagged more urgently the longer it persists.

  3. 03

    Cleaning built into the pipeline

    Deduplication, name and code standardisation and validation run before any analysis, so results are not quietly wrong because of messy source data.

  4. 04

    Delivered to the person who can act

    Findings emailed automatically to the specific manager responsible, as a short exception list rather than a large report nobody opens.

CallWhatsAppEnquire