
Vulcanizare Mobila
First AI-native roadside assistance API, open SDK, MCP ready
Most founders chase the next AI tool or SaaS dashboard. I built something unglamorous: an app that sends a tire technician to your car when you get a flat.
Not sexy. But here's why I did it.
I got tired of watching people stranded on the side of the road, calling 10 numbers trying to find someone to come fix a flat tire. The existing "solution" in Romania was: good luck, figure it out yourself. Traditional tire shops don't do mobile. Roadside assistance takes hours. And this happens to thousands of people every single day.
So I built vulcanizaremobila.com — a marketplace that connects drivers with mobile tire technicians who come to you, wherever you are.
What I've learned so far:
The hardest part wasn't building the app. It was convincing tire technicians to change how they work. Supply-side is always the real challenge in a marketplace.
The customer side was surprisingly easy — when someone has a flat tire, they're not price-sensitive, they're not comparison shopping. They just want the problem solved now. That urgency is both a blessing and a pressure to actually deliver fast.
I'm now exploring B2B — fleet operators, leasing companies, courier services. A flat tire on a delivery van isn't just annoying, it's a broken SLA and lost revenue. That's a very different conversation than B2C.
Currently figuring out: how to scale the technician network outside of the cities I'm already in, and whether fleet contracts are a better growth lever than consumer marketing.
Would love to hear from anyone who's built a marketplace with a strong offline/ops component. What did supply-side growth actually look like for you?
About
First roadside tire service marketplace with native AI integration via MCP (Model Context Protocol). Live in Romania with 95+ active partners, expanding to Italy. → AI agents (Claude, ChatGPT)

Comment