Vehicle papers in one place, and no missed renewals.
01What needed changing
A fleet’s insurance, roadworthiness, licences and permits each expire on their own schedule, and the failure is finding out after a vehicle is stopped. Reading documents automatically helps, but a confidently wrong expiry date is worse than none.
02Decisions we made
What we chose, and why.
01
Make verification a state of the product.
A document is either read by the system or confirmed by a person, and the two behave differently.
02
Let only confirmed records drive anything.
Reminders, renewals, reporting and the audit history never read a value nobody has checked.
03
Confirm field by field.
Operators fix one wrong date far more often than they reject a document. A field that can’t be read is left for a person to fill, never guessed.
03In use
Where it lives.
Scroll sideways.
04Built and run
From the first interview to the support inbox.
- 01DiscoveryCompliance lived in a drawer. The failure was missed expiry dates, not missing documents.
- 02In productionUploaded, read, confirmed, then reminded before it expires, for one vehicle or a whole fleet.
What running it taught usA value the software reads becomes a record you can trust only when the product remembers the moment a person confirmed it.
05What followed
What followed
Livein production with fleet operatorsSource: Product record
—Who leads the workAbout us →
The same people, from the first call to launch.
Tomiwa OgunmodedeOwns framing, product, brand, experience and the critical creative and commercial decisions.
Adejoke AdedapoOwns client strategy, communications, media thinking, delivery and the commercial rhythm around the work.
Balogun AbiodunOwns engineering architecture, feasibility, integrations and turning decisions into resilient working software.
—Keep going
