Load Management System

This is Scamp Technologies' fuel logistics load board, where dispatchers plan a load, assign it, and reconcile it in one workflow.

I led the React client, including the lifecycle UI, ingest from legacy TMS/ERP systems, and a validate-then-commit ledger. Three design partners ran those views in pilot and converted to paid contracts.

Three design partners were already running the board, so I couldn't park the product to rebuild the model.

The write path was the constraint. The document model couldn't take an amendment or an extra stop without rewriting history, so I put a validate-then-commit ledger in front of it. The first production page was about 15 seconds too slow for the real payload. I reshaped the payload, linked entities, and batched the reads in parallel so those same views would hold up on a real board.

Each load writes like a ledger. Changes get validated before they commit, so an amendment or an extra stop doesn't rewrite the past.

I mapped legacy dispatch and inventory into one load model instead of reconciling in sheets, and fixed the promise contract so rejections propagate to callers. I also reshaped the payload, linked entities, and batched reads in parallel so the main page would hold up on a real board.

You should be able to amend a load without lying about history, and a partner should be able to run it without a spreadsheet.

Those are the views that shipped, and they're the ones that turned the pilots into contracts.