One shared record
A freight platform where shipper, forwarder, carrier and consignee work from the same shipment, from the first quote to payment.
01 · Context
Five versions of one shipment
A single load usually lives in an email, a PDF, a tracking portal, a paper signature and a retyped invoice. Each company keeps its own copy, and the copies drift apart.
02 · Challenge
Agreement between companies, not inside one
Most software is built for one organisation. Freight needs several independent companies to rely on the same facts without handing control of them to any single party.
03 · Thinking
Model the shipment, not the paperwork
Quotes, orders, tracking, documents and invoices are treated as stages of one record rather than as separate tools. Every later step reads from what was already agreed.
04 · Engineering
One platform, end to end
I led the build from architecture to production: quotations and orders, live tracking, document approvals, invoicing, backhaul matching and carbon accounting, on the web and on Android.
05 · Result
TrustedTrucks, in production
The platform runs today as TrustedTrucks. Each company connects once and works with every partner on the network, instead of maintaining an integration per partner.
06 · What I learned
The record is the product
Features come and go. What customers actually rely on is that everyone sees the same thing at the same moment. Protect that and the rest follows.
Film
One record
One shipment, one version of the truth. A thirty-second explanation of the idea behind this work.
Details are described at the level of problem and approach. Implementation specifics stay with the company.
Next case · 02Evidence, anchored