- Client
- Liebe Trucking, Inc.
- What we did
- Custom TMS, managed IT, documentation
- Built on
- .NET 8, React, PostgreSQL
When the software is older than half the fleet.
Liebe Trucking ran dispatch, driver pay and invoicing on a system built twenty-five years ago. It still worked, mostly. But every workaround lived in someone’s head, and every change was a risk to payroll.
We took over their IT, documented every system they owned, then built HAWKiTMS: a modern transportation management platform written around how Liebe actually moves freight. Not a template with their logo on it.
The hard part was never the code. It was switching a working business onto it without a single load, paycheck or invoice falling through the gap.
| Load | Origin | Destination | Truck | Status |
|---|---|---|---|---|
L-24817 | Cedar Rapids, IA | Joliet, IL | T-112 | Delivered |
L-24818 | Swisher, IA | Omaha, NE | T-087 | In transit |
L-24819 | Iowa City, IA | Kansas City, MO | T-140 | Dispatched |
L-24820 | Marion, IA | Rockford, IL | — | Needs a driver |
Switching a live business,
one checkpoint at a time.
Every step had a written exit criterion. If a step didn't pass, the old system kept the wheel.
Map the legacy
Every screen, report and payroll rule in the 25-year-old system, written down before a line of new code.
Build alongside
New modules went live one at a time while the old system kept running. Nothing switched off until its replacement was proven.
Parallel run
A full month on both systems, side by side, with one rule: one ticket, one invoice.
Go / no-go
A written checkpoint with the owners. Restore drill passed, backups verified, open items closed or signed off.
Go-live
Dispatch, payroll and invoicing on the new platform.
Running on software older than your newest hire?
We'll map what you have, tell you what it would take to replace it, and how to get there without a bad week.