Case study · AxleOneIn development
Engineering for an operator who does not want another GPS app
Designing a fleet platform for operators running one to fifty trucks, where the product has to answer a financial question rather than display a map.
Context
What existed
before this.
Over 85% of India's road freight capacity sits with operators running fewer than five vehicles. They reconcile receipts over WhatsApp, absorb 60 to 90 day payment cycles, and lose margin to fuel pilferage they cannot audit. Enterprise fleet software is not built for them and consumer tracking apps do not address the actual loss.
The problem, as constraints
- Location data alone does not explain where margin is disappearing.
- The operator is the dispatcher, the accountant, and the maintenance manager, usually from a phone.
- Compliance paperwork is a deadline, not a feature, and missing it stops the vehicle.
Approach
How we
built it.
The shape of the solution, described at the level a reviewing engineer could argue with.
Every operational signal is tied back to trip-level profit and loss, so the interface answers a financial question rather than a positional one.
Fuel anomaly detection and predictive maintenance alerts are framed as margin protection rather than telematics features.
Compliance automation, covering e-way bills, a document vault and expiry alerts, is part of the core product.
Delivery is sequenced: operational core first, network intelligence second, working capital and fintech third.
Decision records
Every call,
with what we rejected.
These are the calls that shaped the product, each with the option we turned down and the reasoning that decided it. Where one has since looked wrong, we leave it in.
Trip-level P&L as the primary object
The operator's question is where margin went, not where the truck is. Making location the primary object would have rebuilt a product that already exists and does not sell.
Mobile-first for one to fifty vehicles
The target operator manages the business from a phone. A desktop-first fleet console would go unused.
Fintech deferred to phase three
Working capital products need trustworthy trip and settlement data to underwrite against. Shipping them first would have meant lending on numbers we could not yet stand behind.
Outcome
Where it
stands now.
Described in words where no measurement exists yet. Market figures carry their source.
Result
- A phased roadmap from operational core through to fintech ecosystem
- Positioned against a $317B logistics market and 12.5M commercial vehicles
- Designed in alignment with Digital India and PM Gati Shakti
Status: Phase one in build. Open to strategic and investor conversations.
What it runs on
Other case studies
Turning a dead business card into a live relationship record
Nine modules, one backbone, adopted one piece at a time
Same discipline, applied to your platform
Decision records like the ones above are a deliverable on every engagement, written as the work happens.