Back to Work Case Study — Logistics / Dispatch CRM
Pre-Launch

MT Logistics Group CRM

A connected CRM, dispatch board, driver app, and customer tracking page for a UK temperature-controlled courier — leads through delivery, on one shared system instead of phone calls, email, WhatsApp, and spreadsheets.

React React Native Node.js PostgreSQL Socket.IO Stripe
0 Milestones Complete
0 Roles & Dashboards
0 Week Build

Private client project — shared here with permission.

MT Logistics Group CRM screenshot showing the dispatch dashboard with revenue, live job status, and compliance alerts
Overview

One system from lead to delivered

A courier business lives or dies on whether a job actually gets where it's going, on time, with proof it happened. MT Logistics Group CRM is being built as one connected platform covering the whole flow: a lead turns into a quote, a quote becomes a booking, a dispatcher assigns a driver and vehicle, the driver collects and delivers with proof at every stop, and the customer can watch it happen on a live tracking link — all backed by one API and one database, not a patchwork of tools that have to agree with each other.

I'm building the whole system — the web CRM for the office, the driver app for the road, the public tracking page for customers, and the API and real-time layer underneath all three.

The Challenge

Running a fleet on phone calls and spreadsheets

Before this build, the business ran entirely on phone, email, WhatsApp, and spreadsheets — leads tracked in someone's inbox, jobs assigned by phone call, proof of delivery as a photo texted to the office, and no single place to see what was actually happening across the fleet on a given day. That works at a small scale and breaks down fast as job volume grows: nothing was connected, nothing updated the customer automatically, and reporting meant someone manually reconciling numbers at the end of the month.

The Approach

Multi-drop by default, not bolted on later

The system is a pnpm/Turborepo monorepo — a React web CRM for the office, a bare React Native driver app (no Expo, for full native-module control over background location and the camera), a Node.js/Express API with Prisma and PostgreSQL, and Socket.IO pushing live updates to every screen that needs them, from the dispatch map to the customer's tracking page.

The real design decision underneath it all: every job supports one pickup and any number of drop-offs, not a single-stop assumption with multi-drop wedged in afterward. The dispatch map draws the whole route before a driver is even assigned, the driver app tracks "stop 3 of 5" with its own status and proof of delivery per stop, and a job can be partially delivered without blocking the stops that succeeded. Permissions are enforced in the API itself for five distinct roles — Super Admin, Support, Dispatcher, Driver, and Customer — not just hidden behind buttons in the UI.

What's Being Built

A Complete Dispatch Operations Platform

Leads, Quotes & Customers

A leads pipeline from website enquiry to quote to booking, with a reusable quote calculator — distance, vehicle type, and the business's own pricing formula, fuel surcharge included.

Multi-Drop Dispatch Board

A live map of unassigned jobs and drivers, with a best-match suggestion by distance and ETA, built for 1..N drop-offs on every job, not just a single destination.

Driver App & Proof of Delivery

Shift start with an odometer photo, per-stop status updates, and proof of delivery — signature, photos, and temperature logging for chilled and frozen loads — queued offline when signal drops.

Live Customer Tracking

A no-login tracking link per job, and a separate link per stop on a multi-drop job, showing live driver location, ETA, and proof of delivery once it's complete.

Payments & Compliance

Stripe-hosted payment links and bulk/consolidated invoicing, alongside a compliance tracker for driver and vehicle documents — licences, MOT, insurance — with reminders before anything expires.

Carrier Bidding Integration

A bidding-platform integration so the business can source and win loads from a haulage exchange marketplace directly inside the same dispatch system, instead of a separate standalone tool.

Built for the Real World

Real-Time, Role-Scoped, and Audited

Every status change — a job assigned, a stop delivered, a payment recorded — pushes live over Socket.IO to the dispatch board, the job page, and the customer's tracking link, instead of anyone having to refresh to find out what's happening. Every mutating action writes an activity log entry, exportable for a real audit trail, and the permission matrix is enforced in the API itself per role, not just hidden in the UI — a Driver's own app is scoped to their assigned jobs only, enforced server-side, not by trusting the client.

Current Status

Pre-launch — core system complete, final milestone underway

The CRM, multi-drop dispatch, driver app, live tracking, payments, compliance tracking, reporting, route optimisation, and the carrier bidding integration are all built and running on staging. The project is now in its pre-launch milestone: a full requirements audit against the signed scope, production-readiness hardening, and handover — before it goes live for the client's own team.

FAQ

Questions About Logistics & Dispatch Software

What's the difference between dispatch software and a generic CRM?
A generic CRM tracks leads and customers. Dispatch software adds the operational layer on top — assigning drivers and vehicles, live location, proof of delivery, and the status engine that actually moves a job from booked to delivered. For a logistics business, you usually need both working off the same data, not two separate systems that have to be kept in sync by hand.
Can a system like this handle multi-stop deliveries, not just single drop-offs?
Yes — it's built for one pickup and any number of drop-offs, not a single-stop assumption bolted on later. Every screen, from the dispatch map to the driver's job list to the customer tracking link, handles 1..N stops as the default case, with its own status, ETA, and proof of delivery per stop.
Do drivers need a separate login and app?
Yes, and that separation is deliberate. Office staff work in the web CRM; drivers get a dedicated mobile app scoped to their own assigned jobs only, with shift tracking, navigation, and proof of delivery built for a phone in a moving vehicle, not a shrunk-down version of the office screen.
How long does a custom logistics or dispatch system like this take to build?
This build is scoped as a 10-week, 5-milestone project covering the CRM, dispatch, driver app, tracking, payments, and reporting in order. A smaller first version — bookings and basic dispatch, without the driver app or reporting — can realistically ship faster if that's all a business needs to start.

Running a logistics, courier, or dispatch-heavy operation?

Tell me how your team currently tracks drivers, jobs, and deliveries — I'll tell you honestly whether a custom system is worth it for you.

Start a Project