At 5:30am, the operations manager was already at her desk. Not because the work required her brain at that hour — because the work required her presence. Jobs needed to be manually assigned. Drivers needed to be texted. Compliance forms needed to be checked. By 9am she’d done three hours of work that, in her words, “a decent spreadsheet could do.”

She was being conservative. It took us four weeks to automate it.

The Problem

Forty hours a week of coordination work that lived in someone’s head and a shared inbox. Job assignments done manually by matching driver availability (tracked in a whiteboard) against daily job lists (emailed in PDFs). Compliance paperwork chased by phone. Status updates relayed by SMS.

When the operations manager was sick, the whole system wobbled. When she went on leave, they hired a temp.

What We Built

An operations platform that handles the coordination layer automatically:

How It Works Now

The operations manager starts her day at 8am. She opens the dashboard. Everything assigned for the day is already confirmed. She deals with two exceptions — one driver swap, one late job request — and moves on to actually running the business.

The compliance folder at the end of each month generates itself. The auditor gets a link instead of a box of paper.

The Numbers

Independence Architecture

The platform runs on the operator’s own cloud infrastructure. Driver apps connect to their own database. All integrations use API keys owned by the business — Google Maps, their TMS provider, their compliance authority portal. ABISA built it; they run it.

Maintenance documentation and admin guides are stored in the operator’s internal systems. A junior staff member can manage day-to-day operations and add new drivers, job types, and routes without ABISA involvement.

Leave a Reply

Your email address will not be published. Required fields are marked *