Field research
Time in booking offices and yards with owners, managers and drivers, watching how a trip is actually run and actually paid for.
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.
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 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.
Trucks based in Sankagiri, one of India's largest lorry towns
Of diesel bought every day through one owners' association, at pump price
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
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
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.
Vehicles onboarded, in beta and running trips
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
Time in booking offices and yards with owners, managers and drivers, watching how a trip is actually run and actually paid for.
Read the market three ways, enterprise software, telematics hardware and load boards, to find the gap none of them serve.
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.
Tokens, shared components and a written check, so quality holds across four kinds of user without me reviewing every screen.
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.
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
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 AMVArt 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.
Tokens
Spacing
Type
₹63,500 Net this weekThe same components, three money states
The same components at two densities. Nothing is redrawn between them, only the status token changes.
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.
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.
Happy to walk through the research, the rejected directions and the parts that did not work.