ExpressMOJO: Logistics and Data Systems

Dipankar Sarkar
Dipankar Sarkar · · 3 min read

What ExpressMOJO worked on

ExpressMOJO (2017–2019) applied software and data systems to India’s trucking and logistics sector, an industry where the useful product has to fit fragmented operations, physical constraints, and the people who keep goods moving. The product was a digital classifieds platform connecting fleet owners, transporters, and commission agents — the intermediaries who match loads to trucks in an industry that had run on phone calls and personal networks.

The operating environment

India’s logistics sector carries a large share of the economy but had seen little technology penetration: most trucking capacity sits with operators running a handful of vehicles each, and a meaningful share of the fleet sits idle for lack of a return load after a delivery. That fragmentation — many small operators, no shared source of truth on available capacity — was the specific problem the product targeted.

Product and technical approach

  • Mobile-first. The primary product was an Android app built to run acceptably on the lower-end smartphones common among the target users, not just flagship devices.
  • Messaging-native distribution. Recognising how much business communication already happened over WhatsApp, the platform was built to be shareable through existing messaging apps rather than requiring a separate destination.
  • Backend built for volume of listings. The backend handled a continuous stream of load and capacity listings and the user interactions around them.
  • Data feedback into the product. Usage data fed back into product decisions rather than being collected and left unused.

Technical challenges

Building for an industry with low prior technology adoption raised specific design constraints rather than generic engineering ones: interfaces had to stay usable for people opening a business app for the first time, listing data needed active verification to build platform trust among wary operators, and the backend needed continuous tuning to keep pace with a growing volume of listings and interactions without degrading for existing users.

The broader lesson

The grounded lesson is broader than a historical product description: industrial software succeeds when workflow truth, operational ownership, exception handling, and incentives are designed with the technology. This experience remains relevant to current work in warehousing, robotics, supply chains, and AI systems that act on real operations.

This page intentionally avoids historical network-size, revenue, funding, or market-share claims about ExpressMOJO itself until a primary public record is linked.

FAQ

What did ExpressMOJO build? A mobile-first digital classifieds platform connecting fleet owners, transporters, and commission agents in India’s trucking industry, distributed through messaging apps already in common use.

Why was India’s trucking industry a hard problem? Truck capacity was fragmented across many small operators with no shared source of truth on availability, and a meaningful share of trucks sat idle between loads for lack of a way to find a return haul.

What lesson from ExpressMOJO carries into current work? That industrial software succeeds only when workflow truth, operational ownership, and exception handling are designed alongside the technology — the same test now applied to warehousing, robotics, and agentic systems that act on real operations.

Did ExpressMOJO use AI, blockchain, or IoT? Later plans explored those directions for the platform; this page describes the operating period and product it shipped, and does not claim outcomes for exploratory technology plans that are not independently documented here.