Vehiko
A B2B automotive marketplace that flips car buying: instead of a person hunting for a car, dealers compete for them by answering their request
My Role
About Product
About
A product that had been built without a designer
Design startingWhen I joined there was no design at all – no files, nothing. The project had been assembled by a frontend developer, with exactly the kind of gaps you get when the interface is designed while the code is being written. The app had never shipped, and the first job was to get it usable fast: a buyer can find the car they want, a dealer can sell it to them. I closed the gaps, built the missing flows and took the product to release
The work
GrowthAfter launch it ran at roughly 5 deals a week. Fine for the car market, but the ceiling was obvious – and it wasn’t on the buyer’s side. Requests don’t grow if handling them is expensive for the dealer, so we started with the dealer’s economics. Inventory management first: stock stopped being guesswork, and it cleared a class of backend problems along the way. Then automated auctions – the dealer sets a floor price, a price-drop step and an interval, and the car sells itself without them touching it. Only then did we go to the buyer’s side: a request builder so a request arrives already answerable, and AI price prediction
Results
x5 more buyer requests
Dealers selling x3 more often
Inventory management resolved part of the backend problems
After these improvements the project raised $2M






