Logistics & mobility

Fleet and logistics software that cuts downtime

We build fleet systems that show where every vehicle is, when it needs service and where the fuel goes. One rollout by our engineering team cut vehicle downtime by 40% and delivery delays by 30%.

Start a project

See our work

Organisations we've built for

Where we come in

When the fleet runs you, not the other way round

These are the situations we are asked to fix.

Breakdowns

Vehicles break down without warning, and repairs are planned after the fact.

Maintenance schedules built on usage, with reminders before a vehicle fails.

Fuel costs

Fuel is a large cost, and nobody can say where it goes.

Fuel tracked per vehicle and driver, so unusual use shows up early.

Late deliveries

Dispatchers don't know where vehicles are, so delays are found out from the customer.

Live positions and trip history, so the next step is planned with facts.

Disconnected data

Fleet data sits apart from your ERP and accounting, and people copy figures between them.

Integration with your ERP and accounting, so data is entered once.

What we build

One system for vehicles, drivers and costs

Built around how your dispatchers and workshop work.

Live tracking

Vehicle positions, trips and history on a map your team can use.

Maintenance planning

Service schedules, repairs and downtime, tracked per vehicle.

Drivers and fuel

Driver records, safety compliance and fuel use, tied to each vehicle.

ERP and accounting

Connections to your ERP and accounting, so costs and records match.

Platforms we start from

Fleet Management Platform

Rules we build for

Tracking vehicles means handling people's data

We plan for these in the data plan before any work starts. This isn't legal advice: your lawyer has the final say.

Transport is a NIS2 sector.

Transport is a sector under NIS2, which expects security in your supply chain (Art. 21(2)(d)). We make that check easy to answer.

Works councils decide on tracking.

In Germany, systems designed to monitor employees' behaviour or performance need the works council's agreement (§87(1) Nr. 6 BetrVG). We build settings for what is collected and for how long, so you can agree it.

Driver data is personal data.

Positions and trips of named drivers are personal data. We collect only what the purpose needs, and delete it on a schedule you set.

How we protect your data

What we've built

A fleet system that cut downtime by 40%

What was built

A fleet management system for a farmers' cooperative in Ethiopia: vehicle registration, live tracking, maintenance, drivers and fuel, with ERP and accounting integration and training for the team.

What changed

Vehicle downtime fell by 40% and delivery delays by 30%. Fuel expenses fell by 20%, and driver safety compliance rose by 50%. The system went live six months after kickoff.

FAQ

Questions about fleet and logistics software

Vehicles, drivers, trips, maintenance and fuel, tied together in one place. We agree with you what to collect, because every extra field is more data to protect.

One rollout by our engineering team reported 40% less vehicle downtime and 30% fewer delivery delays, with fuel expenses down 20%. Results depend on your fleet and starting point, so the proposal sets targets for your case.

It can be, when it has a clear purpose and, where you have a works council, its agreement. This isn't legal advice: your lawyer has the final say. We build the settings so you can agree what's collected and how long it's kept.

Usually, through their APIs or data imports. We check what each system offers during the plan, and test every integration on each release.

Yes. Mobile apps for iOS and Android can be built from one codebase where that fits, so drivers and dispatchers work from the same data.

The fleet system our engineering team delivered went live six months after kickoff. The written proposal after our first call sets out the timeline for your scope.