Matply Infotech LLP

BACKGROUND

Please describe your company and position.

I am the Director of KTS CAB

Describe what your company does in a single sentence.

KTS CAB is not just another cab service, it is something we built by listening closely to both drivers and daily riders in cities like Jaipur.

When we started, we saw a clear gap. Drivers were struggling with low earnings and high commissions, and passengers were dealing with unreliable service, cancellations, and safety concerns. That is exactly what we decided to fix.

At KTS CAB, we offer daily rides, outstation travel, and one of our key differentiators is pool rides, which are still not widely available in many cities. Our focus is to make travel affordable for users while ensuring drivers earn fairly and consistently.

We have built a platform where drivers are treated as partners, not just service providers. We offer better payout structures, subscription-based models instead of heavy commissions, and real-time support from our team. On the customer side, we focus strongly on safety, reliability, and transparent pricing.

Today, we have already onboarded thousands of drivers and are working towards expanding across Rajasthan and beyond. Our goal is simple. To create a ride ecosystem that is fair, efficient, and truly built for the people who use it every day. 

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire Matply Infotech LLP to accomplish?

• Build a smooth, reliable, and scalable mobile app for both riders and drivers, with real-time ride matching, accurate tracking, and a seamless booking experience.
• Develop a strong driver-focused system, including instant ride alerts, easy accept or reject flow, navigation support, and stable background operation to ensure higher ride completion.
• Create a flexible and scalable backend that supports our unique model like subscription plans, pool rides, and future expansion across multiple cities without performance issues.

SOLUTION

How did you find Matply Infotech LLP?

Online Search

Why did you select Matply Infotech LLP over others?

• High ratings
• Close to my geographic location
• Company values aligned

How many teammates from Matply Infotech LLP were assigned to this project?

6-10 Employees

Describe the scope of work in detail. Please include a summary of key deliverables.

The scope of this project was to design and develop a complete, end to end ride-hailing platform for KTS CAB, covering both customer and driver experiences along with a strong backend system to manage operations at scale.

The work included building two mobile applications. One for customers to easily book rides with features like real time driver matching, live tracking, fare transparency, ride history, and multiple ride options including daily, outstation, and pool services. The second app was designed specifically for drivers, focusing on a smooth and efficient workflow with instant ride notifications, quick accept or reject actions, navigation support, earnings tracking, and the ability to run reliably in the background.

On the backend side, the project involved creating a scalable and secure infrastructure capable of handling real time data, ride allocation logic, user management, payment tracking, and system monitoring. Special attention was given to performance so that the system remains stable as the number of users and drivers grows across cities.

A key part of the scope was integrating KTS CAB’s unique business model into the platform. This includes subscription based plans for drivers instead of high commissions, support for pool rides, and flexible configurations for pricing and operations.

Safety and reliability were also core deliverables. Features like live ride tracking, emergency support options, and mechanisms to reduce cancellations and improve ride completion were included to build trust among users and drivers.

In addition, the project covered admin controls and dashboards to manage drivers, users, rides, and performance metrics, along with the ability to scale and introduce new features in the future without major redevelopment.

Overall, the deliverable was not just an app, but a complete, scalable mobility solution built to support long term growth of KTS CAB. 

RESULTS & FEEDBACK

What were the measurable outcomes from the project that demonstrate progress or success?

From a founder’s perspective, we measured success not just by launching the platform, but by how effectively it started working in real conditions.

One of the biggest outcomes was successful onboarding. We were able to bring in over 6000 drivers onto the platform, which clearly shows trust and acceptance from the supply side.

On the operational front, we started seeing consistent daily ride activity. Even at an early stage, getting 10 to 15 rides per day helped us validate that the system is functional and users are willing to book through KTS CAB.

Driver engagement also improved. With a better payout structure and smoother app experience, drivers are more active on the platform and more willing to accept rides, which directly impacts completion rates.

From a technical side, the app performance has been stable. Real time ride allocation, tracking, and notifications are working reliably without major breakdowns, which is critical for scaling.

Another key outcome is the successful implementation of our unique model. Features like subscription plans and pool ride capability are now part of the system, setting the foundation for differentiation in the market.

Overall, the project has moved us from just an idea to a working, growing platform with real users, active drivers, and a system that is ready to scale further. 

Describe their project management. Did they deliver items on time? How did they respond to your needs?

From our experience working together, their project management was structured, responsive, and aligned with our business priorities.

In terms of timelines, most of the critical deliverables were completed as per the agreed schedule. Wherever there were delays, they were usually tied to scope changes or additional feature requests from our side, and those were communicated clearly in advance rather than becoming last minute surprises.

What stood out was their responsiveness. Whenever we raised issues or needed changes, especially around driver app performance or booking flow, their team was quick to acknowledge and act. They were open to feedback and made iterations without resistance, which is important when you are building a product in a fast moving space like ride-hailing.

They also showed flexibility in adapting to our evolving requirements. As a startup, our needs kept changing, whether it was adding subscription models, improving the ride allocation logic, or enhancing background functionality for drivers. They were able to adjust priorities and accommodate these changes without disrupting the overall progress.

Communication was consistent throughout. We had regular updates on development status, and their team made sure we were aware of what was completed, what was in progress, and what needed our input.

Overall, they did not just execute tasks. They collaborated with us as a technology partner, helping us move from idea to a working, scalable product while staying reasonably on track with timelines and being responsive to our needs. 

What was your primary form of communication with Matply Infotech LLP?

• In-Person Meeting
• Virtual Meeting

What did you find most impressive or unique about this company?

What we found most impressive was their ability to truly understand the ground reality of our business, not just the technical requirements.

They did not approach this like a typical development project where you just build features and deliver. They took time to understand how drivers operate, what challenges riders face, and how platforms like ours actually function in real conditions. This helped them build solutions that were practical, not just technically correct.

Another standout point was their flexibility. As a startup, our requirements kept evolving, and instead of pushing back, they adapted quickly and worked with us to refine features like the driver workflow, subscription model, and ride allocation logic.

Their focus on the driver side experience was also unique. Many companies focus more on the customer app, but they understood that in our model, driver experience directly impacts growth. The effort they put into making the driver app smooth and reliable made a noticeable difference.

Lastly, their responsiveness and problem solving approach stood out. Issues were not just fixed, they were understood and improved upon, which gave us confidence that they were invested in building a long-term product, not just completing a project.

Overall, it felt less like working with a vendor and more like working with a team that genuinely cared about building KTS CAB the right way. 

Are there any areas for improvement or something Matply Infotech LLP could have done differently?

To be fair, the overall experience was positive, but there are a few areas where things could have been handled better.

One area is timeline predictability. While most deliverables were completed, in some cases the timelines shifted, especially when features became more complex. A more proactive estimation and clearer buffer planning would have helped us manage expectations better from the start.

Another point is documentation and clarity during handovers. At times, we had to rely on discussions instead of having well structured documentation for certain features or backend logic. More detailed documentation would make it easier for future scaling and onboarding new team members.

There were also moments where we felt more proactive suggestions could have been given from their side. Since they have experience in building similar systems, stronger inputs around product decisions, performance optimization, or user experience improvements at earlier stages would have added more value.

Lastly, faster turnaround on minor fixes or UI level changes could improve the overall experience. While major issues were handled well, smaller refinements sometimes took longer than expected.

Overall, these are improvements rather than major concerns. With stronger planning, better documentation, and slightly more proactive guidance, their delivery could become even more effective.