What Ridekarma taught us

We started Ridekarma because we wanted to give independent drivers more control over their work. The idea was to build software around their needs and explore a different model for connecting them with riders.

We built a beta app and received positive feedback from riders, which gave us confidence that we were solving a real problem. We applied to Y Combinator and reached out to investors, but neither effort led to the support we needed to continue.

As we worked on it, we learned how much the business depended on questions outside the software.

The first was regulation. We struggled with where Ridekarma fit: were we operating as a Transportation Network Company, or providing software as a service? That distinction affected the path we could take, and we couldn’t treat it as a detail to figure out later.

Insurance was another challenge. We had to understand what coverage the model would require and how it would work in practice. It was more complicated than we had expected when we began building.

We considered pivoting to software for limo businesses. That gave us a clearer direction to explore, but it was already a crowded market. More than that, it would have taken us away from the people we most wanted to serve: independent drivers. We decided to move on.

Ridekarma taught us to examine regulation, insurance, and fundraising requirements early when an idea touches the physical world. It also taught us that positive user feedback is valuable, but it does not guarantee that a business can attract investors or overcome operational barriers. A path can look promising on paper and still be the wrong one for us.