Skip to main content
TRITECH Software

Case study · Cloud Platform

ArchData Analytics

ArchData ran a fleet of 300+ vehicles across the Philippines and relied on monthly spreadsheets stitched together by hand. Every question about performance required asking three different people. They wanted one platform that answered those questions instantly.

Client
ArchData
Industry
Data & Analytics
Year
2024
Duration
5 months
Team
4 engineers, 1 data engineer, 1 designer
archdata.build / productionLive
ArchData Analytics interface preview

Results — in the client's own numbers

less time spent producing monthly reports
72%
fuel cost reduction through anomaly alerts
9%
disconnected systems consolidated into one view
5

01The Problem

What wasn't working

A mid-market logistics company had data scattered across five systems and no way to answer basic questions about fleet performance.

02The Challenge

Where it started

The five source systems had no shared identifiers: the same vehicle appeared as different codes in the fuel system, the ERP, and the dispatch tool. Cleaning and joining this data was the entire problem — the dashboard was the easy part.

03Research & Planning

Finding the real problem

We sat with the finance and operations teams and listed the 40 questions they asked most often about the fleet. These became the metric definitions. We then audited each source system to map fields, formats, and refresh cadences.

04Design

Designing for the people who use it

We used a KPI-first layout: every dashboard opens with the few numbers that matter, then lets users drill into detail. Color coding follows a strict convention (green = good, amber = watch, red = action) so the dashboards read correctly at a glance.

05Architecture

The technical blueprint

Nightly batches load raw data into ClickHouse for fast aggregations, and dbt models transform it into a clean metrics layer. The Next.js front end queries pre-aggregated tables so dashboards stay fast even over slow office connections. An alerting service watches fuel and utilization patterns and notifies managers via email and chat.

06Development

Building in shippable increments

We started with the finance dashboard because cost questions were the highest priority, then added operations and executive views. Data validation checks ran against the client's existing monthly reports to prove correctness before each module went live.

07Final Solution

What shipped

A cloud analytics platform that ingests, models, and visualizes operational data in one place — with role-based dashboards.

ArchData now answers fleet questions in seconds instead of weeks. The monthly reporting process that consumed three people-days is now a scheduled task. The data team, previously stuck reconciling spreadsheets, now spends its time investigating the anomalies the platform surfaces.

08Key Features

What the product does

  • Automated ingestion from fleet, ERP, and fuel systems
  • Data warehouse modeled with dbt for consistent metrics
  • Executive, operations, and finance dashboard suites
  • Drill-down from company-level KPI to individual vehicle
  • Scheduled report delivery via email
  • Anomaly alerts on fuel and utilization patterns

09Technology

The stack

  • Next.js
  • TypeScript
  • PostgreSQL
  • ClickHouse
  • Python
  • dbt
  • AWS

10Screenshots

The interfaces in production

Select any screenshot to view it up close. Use the arrow keys to move between them.

  • 01A single overview of cost, utilization, and fleet health.
  • 02Operations view with drill-downs to vehicle and route level.
  • 03Cost analysis with variance against budget and prior periods.

Our monthly reports used to take days and were always slightly wrong. Now they take minutes and match the numbers on the ground.

Joseph Tan

Head of Operations, ArchData

11Related work

More projects like this

View all work
  • Nexa CRM preview
    Web Application

    Enterprise Services · 2025

    Nexa CRM

    A 400-agent service organization tracked customers across spreadsheets and email, with no single view of a relationship.

    shorter average resolution time
    32%
    from kickoff to first usable release
    14 days
    faster new-agent onboarding
    3.5×
  • LedgerFlow preview
    SaaS

    Financial Technology · 2025

    LedgerFlow

    A fintech startup needed a subscription billing platform that could handle complex pricing — without building billing from scratch in-house.

    merchants onboarded in the first year
    2,300+
    scheduled invoice accuracy
    99.9%
    reduction in failed payment revenue loss
    38%