Jagadeeswaran Ganesan

Indian fleet owners run their business on WhatsApp and paper. AMV had to be simpler than both.

Brand identity, product strategy and a design system for a fleet platform built with the owners who use it, in one of India's largest lorry towns.

Sector
Road freight, India
Year
2026
My role
Branding, business and creative strategy, research, design system, art direction
Scope
One app, multiple stakeholders
1:40
LT Jagadeeswaran Gane…Good afternoon · Sun, 16 Aug Owner 🔔10
₹3.2LTotal Revenue
5Total Trips
₹15.0KBalance to receive
AllLive Trips (1)Cancelled · Due (1)
Search truck, load company or driver…
Live trips 1All trips →
Chennai → 2 No Bokanala₹5,000Balance
TN37D7777 · JAGADEESWARAN GANESAN
🧾 Senthur
! 1 approvals pending
Cancelled · balance due 1
Coimbatore → Chennai₹25,000Balance
TN37D7777 · JAGADEESWARAN GANESAN
! Cancelled · balance due
6:04
Tiruppur → NagapattinamTN52R5332 · JAGADEESWARAN GANESAN Edit
Tiruppur → Nagapattinam
Started 11 Aug 2026
● En Route
7/7 stops
Loaded11 Aug
DeliveredPending
PaidPending
TN52R5332Cotton20⚠ 1 pending review
Freight Cost₹60,000
Expenses−₹12,400
• Commission−₹10,400
• On-road−₹2,000
Earnings₹47,600
Driver advance
₹1,000
5:59 pm
Driver advance
₹2,000
5:58 pm
5:37
Accounts 🚚 All trucks ⌄
₹2.7LRevenue
₹1.9LReceived
₹1.3LSpent
₹63.5KNet
₹83.0KTo receive
Trend
DayWeekMonthYear
RevenueReceivedSpentNetTo receive
Statement
Driver advance · Tiruppur →…Driver advance · 5:32 pm−₹10,000
Driver advance · Tiruppur →…Driver advance · 4:27 pm−₹5,000
11:08
Diesel Receipt
WELCOME!!!
GSTIN 18IOIIC4056A9Z5
Neel Chatterjee
23 Hilltop Colony, Ahmedabad
Receipt No.: INV-2024-0292
● Low match

AI Scan Complete

Checked against this trip

✦ Relevance24%
! This bill may not belong to this trip — check the flagged items.
Genuine bill98% confidence
Vehicle numberTG08AB1372 ≠ TN37D7777
Bill date161 days off trip
Locationoff route
Discard⚠ Save Anyway
Home Trips Fleet More

Owner homeWhat is live, what is owed, and what needs approving, before any scrolling.

Live HTML built from AMV's own tokens, not screenshots.

The challenge

Sankagiri moves a serious share of South India's freight on relationships, cash and WhatsApp. The businesses are established and profitable. Nobody had offered them software built for how they actually work.

  • The money goes missing. Fuel, tolls and advances pass through hands before they reach any record. An approval chain, so nothing leaves without the owner seeing it.
  • The people go missing. Drivers move between fleets, so an owner hiring one cannot see what he drove, what he was advanced, or whether he finished his last three trips. A per driver ledger that quietly becomes his record.
  • Everything on the market was built for someone else. Enterprise logistics, with the staff and the hardware budget to match. Nothing to install, on the phone he already carries.

The insight

The category sells visibility. Operators do not lose sleep over where a truck is. They lose sleep over what a trip cost and whether the number they were given is real.

0

Trucks based in Sankagiri, one of India's largest lorry towns

0

Of diesel bought every day through one owners' association, at pump price

0

Fleet owners in that association, almost all of them on paper

Sankagiri Lorry Owners' Association. The rupee figure is about one lakh litres a day at pump price, indicative.

What that decided

AMV is built around an approval chain rather than a map. A manager submits, an owner approves, and every rupee lands in a per driver ledger either side can open.

That ledger answers the second problem for free. Keep the money against the driver and his record builds itself, so an owner can see a man's history before he hires him instead of asking around.

The product

One app, One Ecosystem for owner, team, truck and driver.

A fleet is not one job. The owner decides, the manager records, the driver reports from the road. One build, three ways in, and the same money visible to all of them.

One build

JGJagadeeswaran GanesanOwner10
₹3.2LRevenue
5Trips
₹15.0KTo receive
Live trips 1
Chennai → Bokanala₹5,000
TN37D7777 · Senthur
! 1 approval pending
Coimbatore → Chennai₹25,000
TN37D7777 · balance due
This week
Diesel₹42,800
Driver advances₹18,000
Net₹63,500
RejectApprove all
SKSenthur KManager3
Add expense
TypeDiesel
Amount₹8,400
TripTiruppur → Nagapattinam
Paid byCash
Bill photo attached
Goes to the owner for approval before it touches the trip.
Save draftSubmit
Submitted today
Toll · ₹1,200Pending
Advance · ₹2,000Approved
Unloading · ₹600Pending
RMRamesh MDriver
Tiruppur → Nagapattinam● En route
LoadedDeliveredPaid
Trip expenses
Diesel · Erode₹8,400
Toll₹1,200
Unloading₹600
My advances
Today · 5:59 pm₹1,000
Today · 5:58 pm₹2,000
10 Aug · 8:10 am₹1,500
Every advance lands against your name, so your record travels with you.
Request advance
OwnerApproves the money and sees the whole fleet
ManagerRecords what was spent, with the bill attached
DriverReports the trip and asks for what he needs

Four roles including a private admin view, one codebase, one design system. A driver never sees a margin. An owner never has to ask what a number means.


What came out of it

In beta, with 54 vehicles onboarded and running real trips. That is a small number and it is the true one. What it buys is a working product in the hands of owners who can tell me whether it is right, before a rupee goes on growth.

The more interesting number is the one it sits next to. Sankagiri alone has 25,000 trucks and no software written for how those businesses actually run, so the category has no incumbent to displace. Get it right in one lorry town and the same product travels to the next one unchanged.

0

Vehicles onboarded, in beta and running trips

0

Trucks in Sankagiri alone, the first town of many

No direct competitor is serving this market today, which is the reason the small number matters less than the open one.


How the work was done

Field research

Time in booking offices and yards with owners, managers and drivers, watching how a trip is actually run and actually paid for.

Competitor analysis

Read the market three ways, enterprise software, telematics hardware and load boards, to find the gap none of them serve.

Co-design with owners

Designed and built alongside the people who would use it. Every release went straight back to the same owners, so the problem and the solution never sat in different rooms. Nothing here came out of a workshop.

AMV Shipped, not proposed

Design system

Tokens, shared components and a written check, so quality holds across four kinds of user without me reviewing every screen.

AI standards

References, limits and an honest test for AutoPilot output, because the model was never the part that decides whether it is usable.


Positioning

Plot the market on two axes, what they sell and who they sell it to, and one quadrant is empty. Small owners running on cash, who need control of money rather than sight of a vehicle.

Who they serve What they sell Large fleets, with staff Small owners, on cash The vehicle The money Where nobody else is
Trimble · fleetx · TrackoBit Enterprise transport management and compliance, for fleets with staff to run it.
LocoNav · Vamosys A device fitted to the truck. Tracking and fuel control, priced per vehicle.
Vahak · BlackBuck Loads to fill an empty truck, monetised by taking a cut of the freight.
AMV Control of what a trip actually costs. Nothing to fit, nothing to install, no staff to run it.

Hover a plot to see what each one sells.

Business model

Everyone else sells a box for the truck or a load to fill it. Both assume the owner's problem is the vehicle, which is the part he already understands. Subscription is the only model that works here, and it is easiest to see by elimination.

Ruled out

  • Commission on freightNeeds you inside a transaction that is struck on relationships and settled in cash. There is nothing to sit inside.
  • Hardware subscriptionNeeds capital, and a fitter for every truck, before a single rupee comes back.
  • AdvertisingNeeds a scale this audience does not have, and attention they will not give.

Chosen

A flat monthly fee, per truck.

It matches how an owner already counts his business, because he counts trucks. He can weigh it against what one trip earns in about five seconds, decide once, and stop thinking about it. Predictable for him, predictable for the business.

Then the marketplace, but not before

40trucks on AMV
0100 · marketplace opens150
Subscription live From the first truck. Revenue that does not depend on anybody else showing up.
Marketplace locked A load board with thin supply is an empty room, and launching early spends the trust the product runs on. Earn the density, then monetise it.

Art direction

The mark is a shock absorber. Three bars at the centre for what a business is made of, its fleet, its trips, its drivers. Two covers holding them steady. Anyone who has stood in a yard knows the suspension is why the load arrives whole. Carry some of the shock, so the owner does not carry all of it.

Nothing else is allowed to add any. One accent, one job, what to do next or where you are. Warm off white, soft near black, because the light here is hard and the screens are not built for it. A number plate looks like a number plate. Made here, not translated.

Fleet  ·  Trips  ·  Drivers

One shock absorber. The technology takes the shock so the business does not.

Scroll
AMV Live, not a screenshot

Tokens

Spacing

4
8
12
16
24
32

Type

₹63,500 Net this week

The same components, three money states

Tiruppur → Nagapattinam ₹12,400
Cotton · 20 t · JAGADEESWARAN GANESAN
TN 52 R 5332 Pending review
Mark as delivered Approve
TN 09 K 1180 Erode → Salem Pending review ₹12,400

The same components at two densities. Nothing is redrawn between them, only the status token changes.

  • One accent per screen. It marks the action or the state, never decoration.
  • No raw values. A stray hex or an off-scale size is a bug, not a preference.
  • Reuse before you build. If a shared component exists, it is used.
  • Nothing ships until it passes the written check.

AI in production

A driver photographs a fuel bill and it becomes a structured expense on the right trip. The interesting part is what happens when it is not sure. It scores the match, names the fields that disagree, and hands the decision back rather than quietly deciding.

The model was never the hard part. What decides whether AI output is usable is everything around it: what good looks like written down, how the request is built, and an honest test of what comes back.

Relevance to this trip0%
  • Genuine bill98% document confidence
  • Vehicle numberTG08AB1372 ≠ TN37D7777
  • Bill date161 days off trip
  • Locationoff route

Built with Claude

AMV was designed and built end to end with Claude. The standards were written before any of it was generated, which is the only reason it held. A model will clear whatever bar you set and no higher, so the check that sends work back is worth more when work costs nothing to make, not less.

What I would do differently

I built the approval chain before the reporting that proves its worth, so owners felt the benefit but could not see it. I would instrument the outcome from the first release.


Want the longer version?

Happy to walk through the research, the rejected directions and the parts that did not work.