Demo Scenario

A morning report nobody assembles by hand

A distributor: the sales report was put together by hand every morning from the CRM, the accounting system and branch spreadsheets. We bring the sources into a warehouse and serve the report as a dashboard.

This is a demo scenario: how we would build the solution. Names and data are illustrative — it is not a specific client’s story.

01Task

Task

Management only gets the numbers by lunchtime, and every branch has its own revenue figure. One number is needed by the start of the working day.

Constraints

  • Branches keep part of their data in spreadsheets.
  • The accounting system must not be loaded during working hours.
02Solution

Solution

  1. 01

    Nightly incremental loads from accounting, the CRM every 15 minutes.

  2. 02

    Branch spreadsheets are uploaded to a template with structure checks.

  3. 03

    One revenue definition in the warehouse; the sales mart is ready by 06:00.

03Architecture

Architecture

Architecture: A morning report nobody assembles by hand
  1. CRM → ETL · schedules
  2. Accounting · 1C → ETL · schedules
  3. Branch sheets → ETL · schedules
  4. ETL · schedules → Quality checks
  5. Quality checks → Data Warehouse
  6. Data Warehouse → Sales mart
  7. Sales mart → Sales dashboard
  8. Sales dashboard
Integrations
CRM · Accounting system (1C) · Spreadsheets
Stack
PostgreSQL · Python · SQL · Docker
04What it demonstrates

What it demonstrates

Demonstrates: how a manual morning assembly is replaced by load schedules, and the argument about the “right” revenue by one metric definition.

Send the morning numbers to managers in Telegram?

Telegram notificationsBotZone