Logistics CRM Case Study | brdz.net
Case study

A logistics CRM: orders, drivers and documents in one place

Logistics / freight forwarding

Confidential 4–6 weeks for the first working version TypeScript Next.js PostgreSQL Telegram Bot API

Challenge

A freight company ran on a customer chat, a table of loads, a second table of drivers, and a folder of scanned CMRs and invoices. A dispatcher who was out for a day took half the picture with them. Answering "where is my cargo?" meant calling the driver.

Solution

We built a private web CRM around the one thing the company actually sells: a shipment. Every order is a card with the client, route, cargo, price, assigned driver and vehicle, status and every document attached to it. Dispatchers see a board of today's loads; drivers get a simple page or Telegram bot to confirm pickup and delivery; accountants see closed orders ready to invoice. Roles decide who sees prices and margins.

Client statuses are sent automatically at key moments, so nobody has to ask.

Results

One source of truth for every load. Handover between dispatchers no longer depends on memory, documents are found in a click, and invoicing starts from closed orders instead of from a hunt through chats. The client sees the status without calling.

Orders, drivers, documents in one card Roles for dispatch, drivers, accounting Automatic client status updates