What I build

Software for logistics and transport

Dispatch board

Jobs and loads assigned to drivers on one board, with status updates instead of check-in calls.

Driver web app

Drivers see their jobs, update status and capture proof of delivery from their phone browser.

Customer tracking portal

Customers see where their delivery is and download documents without calling you.

Document capture

Bills of lading, delivery notes and fuel receipts photographed and turned into data.

Quotes and invoicing

Quotes, completed jobs and invoices connected, so nothing delivered goes unbilled.

Operations reporting

On-time rates, costs per job and customer profitability in one dashboard.

AI, right now

Where AI genuinely helps

Small logistics and trucking companies often run dispatch, tracking, customer updates and proof of delivery across separate tools and phone calls. 2026 guides show the shift toward real-time dispatch, OCR for documents like bills of lading, and AI that handles the routine updates.

I haven’t built for a logistics company yet, so I won’t pretend otherwise. What I bring is the same building blocks I’ve shipped for real clients, shown below.

  • Paperwork into data

    OCR and AI read delivery notes, bills of lading and receipts, so nobody retypes them.

  • Route and schedule suggestions

    Suggested job order and driver assignment, adjusted as jobs change; dispatchers decide.

  • Customer updates without calls

    Automatic delivery updates and answers to "where is my order?" from live job data.

  • Exceptions flagged early

    Late jobs, missing proof of delivery and unbilled work highlighted every morning.

Similar work

Data, security and access

  • Customers only see their own shipments and documents.
  • Driver and customer personal data limited to what each role needs.
  • Every status change and document is time-stamped for disputes.
  • Built to work with the tools you have, through APIs or exports.

How a project runs

  1. Call

    A 30-minute call about what you need, who it is for, and what success looks like.

  2. Scope

    A written scope: features, architecture, timeline, price range and risks.

  3. Build

    Working increments you can click through, not a big reveal at the end.

  4. Ship

    Live on your domain and hosting, with a handover so you know how it runs.

More in how I work, or see internal tools.

Questions

Common questions

Why not a standard TMS or dispatch tool?

If one fits, use it. Custom tools make sense when your operation doesn't match the standard flow, or when you need to connect dispatch, documents and invoicing that currently live in separate tools.

Do drivers need to install an app?

No. The driver tool runs in the phone's browser, so there's nothing to install or update.

Can you read our paper delivery documents?

Yes. Photographed or scanned documents go through OCR and AI extraction, then staff check the result. I built the same kind of scan-to-data pipeline for 7Centre.

How much does it cost?

A focused first version is a fixed-price project, scoped and priced after a 30-minute call (MVPs start from $3,000). Ongoing work can run on a monthly retainer.

Chasing drivers and retyping paperwork?

A 30-minute call is enough to tell whether it fits, what the first version should include, and how long it takes.

Book a 30-minute call