Replacing 12 Spreadsheets with One Real-Time Dashboard

Key Results

The Challenge

Our client manages a fleet of 200+ vehicles delivering goods across Germany and Central Europe. Their operations ran on a patchwork of systems:

• 12 different spreadsheets tracking routes, fuel costs, driver schedules, vehicle maintenance, customer SLAs, and delivery confirmations
• 3 hours every morning spent by operations staff manually updating data from GPS systems, fuel cards, and customer emails
• Weekly management reports assembled by hand — often containing stale data by the time they were presented
• No real-time visibility — when a route went wrong, the team found out hours later via phone calls

The operations manager, Thomas, had tried off-the-shelf fleet management software. Every solution was either too complex (built for 5,000+ vehicle fleets), too rigid (couldn't match their specific workflows), or too expensive (€50,000+/year licensing).

He needed something built for their specific operations — nothing more, nothing less.

Our Approach

Month 1: Understanding the Chaos

We spent the first two weeks embedded in their operations:

• Shadowed the ops team for 3 full days to understand their actual workflows (not what was documented)
• Mapped every spreadsheet — what data it contained, who updated it, how often, and what decisions it informed
• Identified the 5 most painful manual processes
• Discovered that 60% of the spreadsheet data was duplicated across multiple files

From this research, we defined the dashboard scope:

Core modules:

1. Fleet overview — Real-time map showing all vehicle positions, status, and current routes
2. Route performance — Planned vs. actual delivery times, delay alerts, SLA tracking
3. Cost center — Fuel costs, maintenance expenses, and per-route profitability
4. Driver management — Schedules, availability, hours compliance (EU tachograph rules)
5. Customer SLA board — At-a-glance view of delivery performance per customer contract

Month 2: Core Dashboard

Two developers built the foundation while one handled integrations:

• Data pipeline — Automated imports from GPS tracking (via API), fuel card systems (CSV upload), and their existing ERP (database connection)
• Real-time updates — WebSocket connections for live vehicle positions and route status changes
• Role-based access — Dispatchers see everything, drivers see their routes, management sees KPIs
• Mobile-responsive — Dispatchers often check the dashboard on tablets in the warehouse

Month 3: Analytics + Alerts

With the data centralized, we added the intelligence layer:

• Automated alerts — Late departures, SLA breach warnings, unusual fuel consumption, maintenance due dates
• Route analytics — Historical comparison showing which routes are consistently profitable and which lose money
• Custom reports — Drag-and-drop report builder replacing the hand-assembled weekly management reports
• Export functionality — One-click PDF and CSV export for customers and compliance audits

Month 4: Polish + Training

• Performance optimization — dashboard loads in under 2 seconds even with 6 months of historical data
• Data migration — imported 18 months of historical spreadsheet data for trend analysis
• Staff training — 4 sessions covering daily workflows, report building, and alert configuration
• Documentation — operations manual for ongoing self-service

The Results

After 3 months of operation:

• Daily reporting: 3 hours → 15 minutes — data flows automatically, no manual entry
• Data accuracy: ~85% → 99.2% — automated imports eliminated copy-paste errors
• Route issue response: 2–4 hours → 30 minutes — real-time alerts catch problems immediately
• Weekly management reports: 4 hours to compile → instant — always-current dashboards replaced static reports
• Fuel cost anomalies detected: identified €2,100/month in inefficient routing within the first week

The dashboard paid for itself within 4 months through operational savings and fuel optimization alone.

Key Takeaways

1. Shadowing beats requirements documents. Two days of watching the ops team work revealed more than any spec could. We found workflows they didn't even think to mention because they'd been doing them so long they were invisible.

2. Custom doesn't mean expensive. Off-the-shelf fleet software quoted €50K+/year with features they'd never use. A custom dashboard built exactly for their needs cost a fraction and required zero workflow changes from the team.

3. The hardest part isn't the code — it's the data. Integrating GPS feeds, fuel card CSVs, and ERP data into a consistent model took more effort than building the UI. We spent 40% of development time on data normalization and pipeline reliability.

Technology Stack