MotorHub Pro — a project by Ahsan Mahmood
The ultimate multi-vehicle dealership platform for car dealers
A dealership's stock is not a product catalogue.
Every vehicle is one of one. It carries a mileage reading, a registration, a service history and a condition somebody assessed by walking around it, and the price moves with all four. Sell it and the row does not decrement. It disappears.
None of that fits the shape of software written for a shop that sells forty of the same thing.
MotorHub Pro is built for the other shape. It is a multi-vehicle dealership platform, which in practice means four surfaces that have to keep agreeing with each other: vehicle inventory, a customer relationship record, sales tracking, and a reporting dashboard sitting over all three.
The dashboard is the part that decides whether the rest is worth maintaining.
A dealer who cannot see what is ageing on the forecourt finds out at the point of a discount instead. So the reporting is not a decorative panel added at the end of the build. It is the reason anybody keeps the other three accurate, and a platform whose reports are an afterthought teaches its users that the data underneath them is optional.
The customer record is the half that usually gets built badly.
A buyer looking at a car is not a row in a contacts table. They are a conversation. They arrived asking about one vehicle, they will be shown two others, and the useful thing to know six weeks later is which of the three they kept coming back to. So the customer side and the sales tracking are the same subject seen twice rather than two features that happen to sit in one menu, and the reporting reads across both.
The stack is React and TypeScript with Tailwind over the top, Firebase underneath, and Capacitor for the mobile build.
That last choice matters more here than in most products, because the person entering a vehicle is usually standing next to it. Registration, mileage, photographs and the walk-around condition are recorded where the car is rather than where the desk is, and a system that assumes a desk gets a forecourt's worth of data entered twice.
The Firebase choice carries a constraint worth naming.
A free tier is a ceiling rather than the absence of one, so every list read carries an explicit limit and the database does the filtering and the counting rather than the browser. Four hundred vehicles is not a large collection by any measure, and it is comfortably large enough to make an unbounded query into a bill somebody has to explain.
What it cost is that this one is not finished, and there is nowhere to send you.
The project record carries no live address, no store listing and no repository. Its status is in progress. Both of those facts belong on the page rather than in a footnote, because the alternative is a portfolio entry that reads like a product and resolves to nothing when a reader goes looking.
That is a real limit and it is worth stating plainly rather than dressing up.
A dealership platform is a category with capable incumbents in it, and an unfinished one has no argument to make against them yet. What it has is a data model built for vehicles instead of adapted to them, which is the part that is hard to retrofit and the part worth getting right before anything else is built on top.
The rest is written down. It is not yet built.
What it does, and what that costs to build
- Vehicle inventory management
- Customer CRM
- Sales tracking
- Reporting dashboard
Built with
- React
- TypeScript
- Firebase
- TailwindCSS
- CapacitorJS
Worth knowing
- automotive
- dealership
- crm
- inventory
Who built MotorHub Pro?
Ahsan Mahmood built it, working alone. The same person modelled the vehicle record, wrote the customer side, built the reporting dashboard over both and configured the mobile build. There is no team behind that name and no agency. What the record does not contain is a link, because MotorHub Pro has no published address, and this page will not point at something a reader cannot open. The honest position is that it exists, it is unfinished, and there is nowhere to send you yet.
Can I try MotorHub Pro?
Not today. The project record carries no live URL, no store listing and no repository, so there is nothing to open and nothing to install. Its status is in progress rather than finished, and a dealership platform half way through is not a thing to hand a dealer. When there is an address worth visiting it will be on the record first and on this page second, which is the order that keeps a portfolio honest rather than aspirational.
What makes a dealership different from an ordinary shop?
Every vehicle is one of one. A shop sells forty identical items and decrements a number; a forecourt sells a specific car with its own mileage, registration, service history and condition, and when it goes the row does not decrease, it disappears. Pricing moves with all four of those facts rather than sitting in a column. That difference is why general inventory software fits a dealership badly, and it is the reason this exists at all.
Does MotorHub Pro work on iPhone?
No, there is no iOS build. The interface is a web application and the packaged build is Android through Capacitor, because there is no Apple Developer account here and nothing I build has shipped to the App Store. A phone browser will open the web side when there is a web side to open. Until then the platform question is the second question, and the first one is that there is no published address at all.
What does it cost to use?
The record does not say, so neither does this page. There is no pricing statement, no tier and no trial recorded anywhere in the project's own data, and inventing one for a portfolio page would put a number in front of a reader that nobody has committed to. A price that appears here before it appears in the product is a promise made by the wrong document. When there is one, it will come from the product.
https://aoneahsan.com/projects/com.aoneahsan.motorhub