Start from real life, not a segment
The finder asks for budget, daily drive, passengers, and must-haves, then shortlists trims against Indian prices and usage — so the answer fits a life, not a brochure category.
← Back to selected work
Car Decision Engine / 2026
DriveScope.
A car decision tool for Indian budgets, roads, and ownership — not a classifieds site or a dealer pitch.
What I owned
From the first decision
to the shipped product.
Solo full-stack product: Next.js, React, Three.js, Framer Motion, Firebase, and structured vehicle data across explore, compare, cost, guides, and simulation.
Look closer / Interface notes
The decisions,
right there on screen.
Select a numbered detail to explore it.
Question → shortlist
Ask in plain language
The hero finder takes a real need — budget, family use, city driving — and turns it into a shortlist. The product starts from life context, not a vague segment.
Existing product artwork from the live DriveScope experience. Vehicle counts and modeled costs refer to the shipped dataset and calculators, not third-party audited results.
Product decisions
Keep ownership cost attached
EMI, fuel, and five-year running cost stay beside the recommendation. Spec sheets look close until ownership pressure shows up; DriveScope surfaces that earlier.
The shipped work
Live at carsim-lovat.vercel.app with 138 cars and 509 trims, plus compare, cost modeling, buyer guides, and a driving lab. Independent of any automaker or dealer.