The Journey
Super K Express does not have a founding story that begins with a vision board and a venture round. It begins with a grandfather who knew Georgia's industrial corridors better than most people know their own neighborhoods, a father who turned regional relationships into a real fleet, and a third generation that inherited both the trucks and the obligation to keep getting better. By the time the current ownership took over day-to-day operations, Super K had grown into a 50-to-100-truck operation running simultaneous local and long-haul lanes out of Union — a genuinely unusual operating model that most TMS vendors never bothered to design for.
The complexity that comes with running both local and OTR under one roof is hard to overstate. Local drivers — the ones doing yard-to-yard shuttle runs, turning four to twelve loads a day, punching out and going home — need dispatch to be fast, paperwork to be instant, and pay to be calculated on a stop-count basis. Long-haul OTR drivers need multi-stop dispatch sheets, accurate ETA tracking, BOL capture at each stop, and settlement statements that account for fuel advances, layovers, and per-diem. The same dispatch board has to serve both realities at once.
Compounding the operational complexity was a rate book problem that had quietly metastasized over decades. Super K had accumulated more than forty active customer accounts, and almost every one had a different rate structure negotiated over years of relationship-building. Some customers paid per mile with distance-based tiers. Others paid a flat per-load rate. A handful had weight-based tables with minimums. Nearly all of them had fuel surcharge riders that referenced DOE fuel index tables and reset on a different day of the week. The institutional knowledge required to bill any given load correctly lived inside the heads of two or three people in the office — and it was becoming a fragile single point of failure.
The operation was running on spreadsheets and memory. Not because management lacked ambition — but because no system they had evaluated was willing to get into the details with them. Legacy TMS vendors wanted to simplify the rate structure. Generic freight software assumed a uniform pay-per-mile model. The tools that offered EDI capability required enterprise contracts that assumed a 500-truck fleet. Super K kept waiting for a platform that could handle what they actually did, not a sanitized version of it.
