TL;DR: Fleet owners in India pay for fuel, tolls, challans, insurance and servicing through different apps, cards and paper bills, so nobody knows what a vehicle really costs to run. FleetOS is the bet that whoever already supplies a fleet's fuel can become the one place it sees and pays for every running cost. Start narrow: small and mid-size fleets, where one wallet and one bill saves real admin time.

PRD v2.0 · Product owner · Concept, not built

The problem

A fleet owner with dozens of trucks can't answer "what did each vehicle cost me to run last month?" without a day of reconciling fuel slips, FASTag statements, challans and workshop bills.

Segment Pain Why start here
Small and mid-size fleets (primary) Spend scattered across fuel cards, FASTag, challans, insurance and service; no cost per vehicle Pain is monthly, measured in rupees, and one account brings many vehicles
Individual owners (later) Missed renewals and challans; no idea of true cost per km Big market, low willingness to pay

Evidence

This is a concept. No pilot has run and no fleet has used it. The framing comes from working on the fuel-supply side of B2B fleet relationships, where the supplier sees only one line of a fleet's running cost. The three conditions below are the tests a pilot would have to pass before anything else gets built.

What has to be true

  1. Fleets will route non-fuel spend (FASTag, challans, insurance) through the same account.
  2. Partners (insurers, FASTag issuers, workshops) will pay a commission for that demand.
  3. One consolidated monthly bill is worth switching for.

If any of these fails in the pilot, we stop and rethink before building more.

How it works

flowchart LR
	A["Fleet account<br>vehicles, drivers, roles"] --> B["Fuel spend per vehicle<br>from the supplier's data"]
	A --> C["FASTag recharge<br>and low-balance alerts"]
	A --> D["Challan lookup<br>and payment"]
	B --> E["One wallet,<br>one monthly bill"]
	C --> E
	D --> E
	E --> F["Cost-per-vehicle<br>monthly report"]
	F --> G["Next: insurance and<br>service via partners"]

Decisions and trade-offs

The bet. A fuel supplier is a thin-margin vendor that's easy to switch. The place where a fleet sees and pays all its running costs is an operating system: recurring, sticky, with room to cross-sell.

Decision Why What it cost
Fleets first, consumers later One account brings many vehicles and the pain is measured in rupees every month Gives up the larger consumer market for now
Lead with challans and the monthly report Neither needs the fleet to switch away from an incumbent provider Commission revenue from insurance and FASTag arrives later
One partner per category at launch Integrations are the slowest part of the build Less choice for fleets in v1
Licensed payment partners, no card data stored Keeps RBI and DPDP Act exposure small Less control over the payment experience

What I cut

Cut Why
Parking marketplace Fragmented supply, low frequency
Gamification and social sharing No link to the core job
Calendar sync and app theming Nice to have; doesn't move adoption
Consumer app in v1 Gated behind fleet traction

Personas