This is the real journey of building Amir Ventures — from a fleet run on phone calls and paper notes to a production platform used every day by 30+ drivers and 4 dispatchers. Everything below is true. Nothing confidential is named.
We keep the operator confidential and we don't quote numbers we can't stand behind. What follows is the story of the work — the starting point, the problems, the build, the testing, the go-live, and what changed — described as it happened.
How a working transportation company went from managing dispatch in their heads to running it on a single live system.
Jobs came in by phone and went out by text. A dispatcher held the whole board in their head, scribbled addresses on paper, and called drivers one by one to see who could take the next run. There was no map, no record of who was where, and no way to look back at what had actually happened on a given day. It worked — until it didn't.
Drivers called in constantly — "where's my next one?" — because they couldn't see a queue. Jobs slipped through when a text got buried. Nobody knew which driver was closest to a pickup because there was no GPS. Commission was tallied by hand at the end of the week, which meant arguments and mistakes. And when something went wrong, there was no trail to check — just memory against memory.
The build started where the pain was: a driver app that turns any phone into a live dispatch terminal, and a dispatcher command center to run the whole board from one screen. Underneath sat a serverless cloud backend to keep both sides in sync in real time. Nothing was designed in a vacuum — every screen was put in front of the people who'd actually use it, and reshaped by what dispatchers and drivers said after using it for real.
A dispatch tool is only as good as its worst moment — a driver in a tunnel, a rush hour with everyone busy, a phone that dies mid-trip. So the platform was hardened against exactly those cases while the old process still ran alongside it. Jobs and completions were made to survive dead zones and sync on reconnect. Busy-driver routing was tested against real rush-hour load. And a full audit trail was added so any edge case could be traced after the fact.
The platform moved into daily production with the fleet: 30+ active drivers on the driver app and 4 dispatchers running the command center, backed by a signed licensing agreement. It stopped being a project and became the way the company operates — through morning airport runs, evening rushes, and everything in between.
The honest way to describe the outcome: the operation is organized now. Dispatch happens in one place instead of across texts, calls, and paper. Every vehicle is visible on a live map. Commission calculates and verifies itself instead of being reconstructed by hand. Fewer jobs fall through the cracks, because every job is tracked start to finish. And when a question comes up about what happened, there's a record to check. We're not going to quote you a percentage we can't defend — but the difference between "it's in someone's head" and "it's in the system" is the whole point.
“The dispatcher used to be the system. Now the dispatcher runs the system — and the system remembers everything.”
— On what changed after go-liveThe same operation, before the platform and after — described only in terms we can stand behind.
No fabricated metrics. Just the concrete ways the operation runs differently now.
Dispatch, scheduling, messaging, and money live in one system instead of being spread across texts, calls, and paper. The board is a screen anyone can look at — not a memory only one person holds.
Every vehicle is on a live, geofenced map. Dispatchers can see who's available, who's on a trip, and who's closest to a pickup — instead of guessing or dialing around.
Rates are stamped per trip, math runs itself weekly with correct cash-vs-card handling, and uploaded payment proof is read by OCR — so dispatchers review the exceptions, not the whole ledger.
Because every job is tracked from creation to completion — and survives dead zones on the way — trips stop slipping through the scroll. What's dispatched gets accounted for.
Two-way chat with text, voice notes, photos, and files sits inside the same app the job lives in — so a conversation about a trip is attached to the trip, not scattered across phones.
Reports, earnings, trip logs, a client database built from real trips, and a full audit trail all come from the same data. One place to answer "what happened" — and to plan what's next.
“We didn't set out to replace the dispatcher's judgment. We set out to give it a memory, a map, and a record — so nothing depends on one busy person remembering everything.”
— The design principle behind the buildThis story started with a real company that ran on group texts and paper notes. Yours can start with a live walkthrough — or you can try the apps yourself, right now, with sample data.