VoxSim: Simulating Society to Understand the Impact of Policy Before It Lands
Apr 20, 2026 · 6 min read
In January 2024, a Turkish distribution company approached us with a problem that sounded simple on the surface: they needed to stop managing their courier operations in WhatsApp groups and spreadsheets. By February, we had delivered a working system. What we didn't expect was how clearly those eight weeks would define an entire product line.
The Problem Was Chaos, Not Technology
Tayfa Dağıtım operated a fleet of couriers handling daily deliveries across multiple routes. Their process involved morning briefings on WhatsApp, manually updated Excel sheets tracking which driver was where, and phone calls when something went wrong. When a delivery failed or a customer complained, tracing what happened took hours.
They didn't need something magical. They needed assignments to reach drivers instantly, drivers to confirm pickups and deliveries from their phones, and management to see the current state of all routes without calling anyone.
What We Built
The system had two primary layers. The backend and web management panel were built in Laravel — a RESTful API serving both the web interface and the mobile application, with a management panel giving dispatchers full visibility into active orders, courier positions, and delivery status. The panel was multi-tenant from the start, designed to support multiple courier businesses under a single installation rather than one deployment per client.
The mobile application for couriers was built in Flutter. A Flutter app compiles to native Android and iOS from a single codebase, which mattered for a courier operation where drivers use whatever Android phone they own. The app handled job assignment notifications, pickup and delivery confirmation with photo capture, and real-time location reporting back to the dispatch panel.
Two features shaped the operational experience more than any others. Smart pool management replaced manual assignment: orders entered a pool based on zone and priority, and the system allocated them to available couriers automatically, accounting for current load and proximity. Live order tracking gave dispatchers a real-time map of all active couriers and orders without any polling — status updates pushed from the mobile app to the panel the moment they happened.
We built it in eight weeks. By the end of February, the client had eliminated the WhatsApp coordination entirely.
The Moment We Saw the Pattern
During the project, something became clear: every courier and distribution business has essentially the same operational structure. Orders come in. Drivers pick them up. Someone needs to see where everything is. Exceptions need handling. Customers want tracking links.
The specific client had unique quirks — multi-zone pricing, restaurant partnerships, specific reporting needs — but the underlying model was universal. We had built, without intending to, the first version of what would become Delivio.
From Custom Project to SaaS Product
After delivering the Tayfa Dağıtım system, we spent the following months generalizing it. The multi-tenant architecture that was already in place made the transition straightforward — the system already knew how to host multiple courier operations. Restaurant management became a dedicated module. The mobile app was refined to handle onboarding for new couriers without dispatcher intervention. White-label customer tracking pages were added.
Delivio today is a full courier and food delivery management platform: restaurant and vendor management, courier tracking, order management, payment integration, and reporting. The Laravel API and Flutter mobile app that powered Tayfa Dağıtım are still the core of the product — just significantly expanded.
This is exactly why we build vertical SaaS. The Tayfa Dağıtım engagement wasn't consulting — it was research under production conditions. Every feature in Delivio has a reason that traces back to a real dispatch problem we watched someone struggle with.