How the numbers add up
We don't have named case studies yet — so instead of inventing them, here's exactly how Lookup arrives at a rupee figure, modelled on the fleets we're built for.
These are illustrative scenarios, not real customers. They model how the recoverable number is built for a fleet of each shape. Nothing here is a guaranteed outcome — your own figures come from your own data.
A full-truckload operator whose billing lags delivery. Most of the recoverable money is cash already earned but not yet invoiced or collected.
A regional distributor bleeding dead kilometres on return legs. The leak isn't cash trapped — it's cost incurred on empty trucks, concentrated on a few lanes.
An operator leaning on brokers for peak demand. Overpaid hire and a handful of loss-making lanes were quietly subsidised by the profitable core.
Illustrative scenarios modelled on typical Indian fleets — not real customers or guaranteed outcomes. Your own figures are computed from your data, and every one drills to the exact source rows.
Why the number is trustworthy
A figure is only worth acting on if you can audit it. Here's what stands behind every one.
Every number drills to rows
A finding isn't a headline — it's the exact trips, invoices or lanes behind it, exportable to Excel. If it can't be opened, it isn't shown.
Modelled, then verified on your data
The scenarios below are models of typical fleets. Your real figures are computed only from the data you provide, in your first 48 hours.
Tracked against your fee
Recovered rupees are logged in an ROI tracker over time, so the value defends itself at renewal instead of relying on a claim.
Real quotes, when they're real
We're onboarding our first fleets right now.
Real, named case studies will live here — with the customer's permission and their actual numbers. We'd rather show nothing than invent a quote. Want to be one of the first, on preferential terms?