One platform to run the whole operation, instead of ten tools that don't talk.
Logistics and mobility businesses lose time, money, and sleep to disconnected systems and manual spreadsheets. We build the platforms that pull it together, fleet, dispatch, loads, drivers, tracking, and proof of delivery in one place, so your operation runs from a single control tower and holds up under real load.
The constraint
In this industry most of the constraints belong to somebody else, and breaking one is not a bug. A driver's hours are set by federal regulation and enforced at the roadside. A delivery window is set by a customer. A dock's availability is set by a warehouse. A trailer's temperature range is set by what is inside it. Software in most industries can be wrong and corrected. Here a wrong decision produces a violation, a refused load, a spoiled shipment, or a claim, each with a cost attached before anybody notices software was involved. That changes what a dispatch platform is for. It is not a faster way to make the same decisions. It is a system that knows the rules the decision has to satisfy.
Two of the operations platforms we have built, chosen because each one turned on a different constraint.
Skylark, a fleet and logistics platform
A dispatcher looking at a board that shows a driver as available assigns a six hour run to somebody with two hours left on their day. The driver refuses and the load moves late, or takes it and runs over, and the fleet now owns a violation that a person planned without knowing they were planning it.
It is harder than it looks because availability is not one number. A Canadian driver is running four clocks at once: driving time today, total on-duty time today, a cycle total across several days, and a mandatory reset that cannot be borrowed against. Loading and waiting consume the second, which is why a driver can run out of day without having driven far.
So remaining hours sit on the dispatch board next to the driver's location, and a run that will not fit is visible at assignment rather than at the pickup. The platform reads the certified device's log. It does not become one, and it does not compute compliance.
Six separately licensed tools and a spreadsheet were replaced by one platform, which is where the cost came out.
Taxi On Spot, a ride-hailing platform
We were handed the platform partway through, part-built by another team, and audited it before extending it, which is standard practice on any inherited codebase and rare in the market.
The business sells a fixed price, and the software was not the thing deciding that price. A number produced elsewhere was being accepted and recorded as a booking, which means the central commercial commitment of the company was being set outside the company. Nobody had noticed, because nobody had looked.
So pricing moved to the server entirely, and the rule generalised past price: anything that costs money, grants access, or creates an obligation is decided server-side. The device asks, it never tells.
These are two of the platforms we have worked on in this sector. The full set is in our case studies, including work we cannot name.
What we would expect to deal with on your platform
Not a service list. Four problems that show up on most operations platforms, and the decision we made when each showed up on ours.
Availability is four clocks and a date rather than a yes or no, so a board showing a green tick beside a driver with forty minutes of cycle left is telling the dispatcher something untrue.
Proof of delivery is captured at exactly the moment a driver is least likely to have a connection, inside a warehouse or an underground bay. An app that needs signal to record a delivery is an app that gets worked around, and the workaround is paper.
A truck that has not moved for an hour is either stationary or out of contact. Those look identical if the platform only renders the last known position, and they mean opposite things.
Highway and city work are not the same problem with different mileage. On a long run the driver's clock binds. On a multi-stop day the delivery windows and the dwell at each site bind, and one site overrunning by an hour delays every remaining stop.
The parts that decide whether it works in the field
Capture happens on the device. A scan, a signature, an arrival, or a status change is recorded locally with the time it happened, and syncs when there is something to sync to. The driver's job is finished when they finish it rather than when the network agrees.
Every event carries two times. When it happened and when it arrived. A delivery completed at two and synced at five is a two o'clock delivery, and which timestamp the system treats as authoritative is what decides a detention claim.
Every event carries its own identity. A phone that regains signal mid-upload will retry, so a repeat has to update rather than create a second delivery against the same load.
Absence of data is displayed as absence, because a control tower that renders silence as a position is telling the office something untrue.
Condition is monitored, not just entered. A validated setpoint catches the typo. It does not catch a correct setting on a failing unit, a switched-off reefer, or a door left open, all of which ruin the same load. So the trailer reports what it is actually holding and divergence raises an alert in minutes rather than on the third day.
And on a mobility platform, the server decides anything that costs money. A fare, a discount, a vehicle class, a cancellation charge. A quote is an object with an identity and an expiry, and the booking refers to it rather than restating its number, so what was agreed and what is charged are the same record rather than two values that have to match.
Data, residency and what gets kept
Operational and fleet data, including driver location and scanned documents, can be held in the country the operation runs in. For a federally regulated carrier that is a procurement question before it is a technical one.
And the honest part: this software tracks a person's location continuously, records their hours, and knows how long they spent at every stop. That is necessary to run the operation and it is also continuous employee monitoring, which carries obligations of its own. So retention is a defined period rather than an indefinite one, and a driver's detailed movement is visible to the people who need it operationally rather than to anyone with a login.
Drivers are scarce, and a fleet with a reputation for watching them badly recruits worse. The operational benefit is kept and the surveillance surface is bounded.
Which trust services criteria this work is judged on
Availability, and on this platform it is measured at a loading dock with one bar of signal rather than in a datacentre. The infrastructure can be perfectly healthy and the platform useless to the person it exists for, because they are standing inside a metal building. That is why capture happens on the device and why absence is rendered as absence.
Processing integrity, which is what the reefer incident argues. A system that accepts a value nobody could have meant, acts on it, and reports nothing has not failed in any way it would notice. Input ranges, live readings compared against intent, alerts on divergence, and a recorded actor behind every change are answers to that criterion rather than to a security one.
Confidentiality, in the multi-tenant separation, including the harder half where partner companies share a job without sharing rates, margin, or customer lists.
The boundary, stated plainly. The control set is designed against the criteria rather than mapped to them afterwards. That is a statement about how a platform was built, not a claim to hold an attestation, and where a client needs one, the work is theirs to complete with an auditor. We don't claim certifications we don't hold.
What this costs to run
Four things a finance leader should know, from the sector where the answer is clearest.
The largest saving on a consolidation project is usually the licensing, not the efficiency. A licence that no longer renews is a line on a statement, where a productivity claim is an argument.
Spoiled cargo is a controllable loss that most operations treat as a fact of life, because nothing in their process makes the problem visible before it becomes one.
Detention becomes claimable, because timestamped arrival and departure captured in the field is the evidence, and an operation without it absorbs the cost silently.
A violation planned by accident costs a fine and the load, and the information that would have prevented it was available at the moment of assignment.
What the platforms actually do
Structural facts about the builds rather than measured results. Every one is checkable from the product.
How you'd work with us
Pick the level of ownership that suits you.
Staff augmentation
Add senior operations-experienced engineers to your team.
Dedicated team
A committed team that runs like your own.
Full delivery
Hand over the build and we deliver it end to end.
Frequently asked questions
Can you replace our existing patchwork of tools with one platform?
Yes, and it is where the clearest saving usually is: licences that no longer renew are a line on a statement rather than a productivity argument. We consolidate incrementally, integrating with what you run today and replacing tools as the platform covers them, so the operation never stops while the stack shrinks.
Do you integrate with telematics, including driver hours?
Yes. Vehicle position, engine data, and trailer condition come from the telematics provider, and driver hours come from the vehicle's own certified logging device, surfaced on the dispatch board next to the driver's location so a run that will not fit is visible at assignment. The platform reads the certified device's log. It does not become one, and it does not compute compliance.
Can you build a driver app that works where there is no signal?
Yes, and it is a design requirement rather than a feature, because proof of delivery is captured exactly where connections fail. Scans, signatures, and status changes are recorded on the device with the time they happened and sync when there is something to sync to, each event carrying its own identity so a retry updates rather than duplicates.
Can you support an operator and its partner companies on one platform?
Yes, including the harder half of that question: partner companies share a job without sharing rates, margin, or customer lists. Separation is structural, with each company isolated but able to work the same load.
Running an operation on ten tools that don't talk?
Tell us what you're running, and we'll tell you honestly how we'd approach it.