FIELD DOSSIER · WAYPOINT 04
Scaling corporate mobility: how MoveInSync RentLz reached 8× ARR
How a fragmented corporate car rental service became a SaaS platform serving 70,000+ monthly users across 50+ locations in three countries.
- Product
- MoveInSync RentLz
- Role
- Senior Product Manager
- Timeline
- Apr 2022 — Oct 2024
- Impact
- 8× ARR · 12× usage
Executive summary
MoveInSync RentLz started from a plain observation: enterprises ran corporate transportation on phone calls, paper logs, and disconnected vendors. As the Senior Product Manager for this vertical, I turned that service-heavy offering into a SaaS platform — the system of record for bookings, billing, and fleet operations.
Over 2.5 years the numbers moved: 8× ARR and 12× product usage, 15+ enterprise clients onboarded, taking the platform to 70,000+ monthly active users across 50+ locations in India, the Philippines and South Africa. Client onboarding alone added 30,000+ new monthly users. Implementation time fell 20%; support tickets fell 15%.
The terrain: problem & market opportunity
Run corporate transport in India the traditional way and it's all manual: bookings over the phone, trips on paper logs, expenses reconciled in spreadsheets months later. For the enterprise transport managers we sold to, that added up to three recurring problems.
Visibility deficits: transport managers lacked real-time insight into vehicle locations, driver assignments, and trip status. When an executive needed to know why their airport transfer was delayed, the answer required phone calls across multiple vendors with no centralized source of truth. This opacity extended to cost tracking, where monthly invoices arrived with line items that were nearly impossible to audit or optimize.
Vendor fragmentation: large enterprises typically engaged 5–10 different fleet providers across regions, each with their own booking interfaces, billing formats, and service standards. For a company operating across 25+ cities, this meant maintaining relationships with dozens of vendor contacts while trying to enforce consistent service quality. The overhead was real, and no single vendor ever saw enough volume to offer a better rate.
Employee experience gaps: the friction landed hardest on the travelers themselves — executives, sales teams, senior management. Booking meant wading through corporate travel policies, tracking meant SMS updates from drivers, and calling a driver often meant handing over a personal number. For companies answerable for employee safety, that informality was a compliance exposure.
“MoveInSync manages Wipro’s employee transportation across 8 cities. We chose them for their app’s ability to ensure employee safety and security, operational transparency, and cost efficiency, replacing our previous manual management approach.”
Enterprises were spending heavily on corporate transportation with no way to see or manage the spend. Industry benchmarks put optimized fleet management at 20%+ cost reductions, with employee satisfaction rising alongside. The hard part was delivering that across enterprise requirements: travel policies, vendor contracts, audits.
The route: product vision & strategy
The vision call I had to make: is RentLz a better booking interface, or the system a transport team runs on? I chose the second. Bookings, billing, fleet operations, vendor contracts — all of it belongs on one platform. That choice drove everything downstream, from what we built first to how the architecture was shaped.
Three commitments: the roadmap held three things we wouldn't trade away. Reliability: every booking, driver assignment and trip completion has to work, every time. Visibility: from transport managers to CFOs, people see what they need when they need it. Cost control: the numbers to manage transportation spend and show ROI.
From service to SaaS: RentLz began as a service offering — MoveInSync’s ops team managed vendor relationships and coordinated trips by hand. I moved it to a SaaS model where the platform did that work: vendor onboarding workflows, automated assignment, self-service for enterprise admins and employees alike.
Phased roadmap: Phase 1 was the MVP — core booking and tracking, enough to prove value to early adopters and start earning. Phase 2 added automated billing, ERP integration and VoIP calling. Phase 3 was built for scale: multi-location support, analytics, AI-assisted optimization.
What was built: key features & the development journey
Every feature below traces back to something a customer said. I ran 50+ interviews with transport managers, travel coordinators and frequent business travelers, and this feature list is what fell out of them.
Intelligent booking engine
A unified interface supporting airport transfers, intercity travel, and intracity commutes with automated vendor assignment based on company policies, location, and vehicle preferences.
AI-powered safety monitoring
Real-time telematics integration detecting risky driving behaviors, with automated alerts and incident reporting to ensure employee safety across all trips.
VoIP communication layer
Privacy-preserving voice communication between employees and drivers without phone number exchange, achieving 70% adoption among active users.
Automated billing & invoicing
End-to-end financial workflow from trip completion to invoice generation, with support for corporate cards, vendor payments, and ERP integration.
Executive dashboards
Real-time analytics on transportation spend, utilization rates, and service quality metrics, enabling data-driven decisions on fleet policy optimization.
Universal API gateway
Standardized interfaces enabling integration with fleet management systems, HR platforms, and external ERP solutions, reducing implementation time by 20%.
The VoIP feature is the one nobody asked for by name. In user research I kept hearing that employees declined trips or asked for changes because they were uncomfortable giving drivers their personal numbers. In-app calling that masked the numbers on both ends removed the friction outright — 70% adoption within three months of launch settled the question.
The universal API gateway came from a repeated headache: every new client needed custom integration work with their existing fleet providers. We standardized the data formats and protocols, so onboarding a new fleet vendor became configuration instead of engineering — days instead of weeks. That’s where the 20% implementation-time reduction and the jump to 50+ locations across three countries came from.
Under the hood: technical implementation
A platform that ends up serving 70,000+ monthly users across 50+ locations can’t be retrofitted for scale later. With engineering leadership I set the architecture early: cloud-native, with security baked in from the start because enterprise compliance demanded it.
Mobile-first: 80%+ of end-user interactions would happen on phones, so that’s where the design effort went. The employee app optimizes for speed — key actions in under three taps. The driver app minimizes cognitive load, because chauffeurs already juggle complex schedules. Manager dashboards live on larger screens and stay responsive.
API-first integration strategy: rather than building point-to-point integrations with each fleet provider, we developed a universal API gateway that normalized data across vendors. This abstraction layer allowed us to onboard new fleet partners by configuring translation rules rather than rewriting core logic. The gateway also enabled our 5+ fleet provider integrations controlling 75% of vehicles in the network — a depth of integration a competitor would have to rebuild one vendor at a time.
Security & compliance: Fortune 500 evaluators weren’t going to wave our platform through on promises. I worked with the security team to get the certifications that unblock enterprise deals — ISO 27001, ISO 27701, SOC 2 Type 2 — and put encryption at rest and in transit, role-based access control and audit logging in from day one.
Getting to market: go-to-market strategy
RentLz didn’t launch from a standing start — it launched on MoveInSync’s existing enterprise relationships. The GTM plan leaned on that, while still giving RentLz its own position in the market.
Land-and-expand: instead of chasing enterprise deals from cold outreach, I looked inside MoveInSync’s own customer base. Companies already running our employee transportation product kept asking for a fuller corporate rental solution. Selling to them meant shorter cycles and built-in credibility: they knew us, we knew their transport footprint, and the expanded offer came from a partner rather than a stranger.
Pilot program structure: for new prospects, I designed a structured pilot program that reduced evaluation risk while demonstrating value quickly. Pilots ran for 60 days with focused success metrics: booking completion rate, employee adoption percentage, and positive feedback score. This approach enabled us to onboard 8 new clients in FY 2022–23 alone, with each pilot converting to a full deployment upon meeting success criteria.
Sales enablement: I established monthly product demo sessions for the Customer Success and Pre-Sales teams, ensuring they could articulate new feature benefits and handle technical questions. These sessions covered everything from API capabilities to security certifications, creating a knowledgeable sales organization that could compete effectively against entrenched competitors.
Q2 2022
Market research & MVP definition
Conducted 50+ user interviews, defined product roadmap, and built MVP with core booking and tracking capabilities.
Q3 2022
First 8 client onboardings
Launched pilot program, onboarded initial clients, achieved 7× product usage improvement in the first year.
Q1 2023
VoIP & self-onboarding launch
Introduced privacy-preserving communication features, achieved 70% adoption, expanded to 25+ locations.
Q4 2023
Enterprise scale achieved
15+ clients, 70,000+ monthly users, 50+ locations, 8× ARR growth milestone reached.
Results & impact
Two and a half years in, here’s what moved:
Revenue growth: the 8× ARR came from three moves stacked: re-pricing, expansion inside existing accounts, and new customers. The model itself changed too — from per-trip transactions to a platform subscription with usage-based components — which made revenue predictable and kept our incentives aligned with the customer’s.
User engagement: 12× product usage told us the platform was pulling people in rather than just processing their bookings — usage spread into tracking, trip history, the app itself. The 20% cut in implementation time came from standardized APIs and written playbooks, not from throwing more support hours at clients.
Operational efficiency: support tickets fell 15% mostly because users stopped needing us. They could track their own trips, fix their own bookings and find answers without writing in. The customer success team got those hours back for the actual job: relationships, not firefighting.
“MoveInSync's automation software has minimized manual workload and errors, proving very effective for our daily transportation operations.”
Hard parts: challenges & how they were met
Four problems cost us real time: vendor resistance, Fortune 500 security reviews, feature-prioritization pressure, and expanding into two new countries. Here’s what we did about each.
Vendor adoption resistance
Fleet vendors were accustomed to their own booking systems and viewed our platform as additional administrative burden. We addressed this by designing vendor-facing workflows that reduced their operational overhead: faster payment cycles, automated trip assignments, and simplified documentation. The incentive structure made adoption beneficial rather than mandatory.
Enterprise security concerns
Fortune 500 companies had stringent data security requirements that initially seemed to exceed our capabilities. Rather than abandoning these opportunities, I initiated a dedicated compliance program achieving ISO 27001, ISO 27701, and SOC 2 Type 2 certifications. This investment opened doors to enterprise accounts that had previously been inaccessible.
Feature prioritization pressure
Every client had feature requests, and sales teams naturally wanted to accommodate them. I implemented a structured prioritization framework weighing customer impact, development effort, and strategic alignment. This framework, combined with transparent communication about roadmap decisions, managed expectations while ensuring we built what mattered most.
Multi-region complexity
Expanding to the Philippines and South Africa introduced new requirements around local payment systems, regulatory compliance, and vendor ecosystems. I established regional product managers who understood local market dynamics while maintaining global platform consistency. This distributed approach enabled rapid localization without fragmenting the codebase.
Field lessons & what came next
What stayed with me after RentLz:
Enterprise sales cycles require patience but reward persistence
Our longest enterprise deal took 18 months from initial contact to signed contract. During this time, we built relationships, addressed concerns iteratively, and demonstrated commitment through pilot programs. The eventual contract value justified the investment.
User research must be continuous, not episodic
Early in the product lifecycle, I treated user research as a discrete phase before development. This led to assumptions that aged poorly. Shifting to continuous discovery — ongoing interviews, behavioral analytics, and feedback loops — kept us aligned with evolving user needs.
Platform strategy creates defensible advantages
The universal API gateway and the fleet network behind it made the platform harder to copy than any single feature. Future product strategies should prioritize platform capabilities over point solutions.
Metrics should drive action, not just reporting
We tracked numerous metrics, but the most impactful were those that directly triggered decisions. The 70% VoIP adoption metric prompted feature expansion into video calling. The 15% support ticket reduction justified additional UX investment.
What’s next for RentLz: the roadmap when I left pointed at three directions: EV integration, because enterprise clients were signing sustainability commitments; predictive trip optimization on historical patterns; and computer-vision safety features, in a market where employee security is the thing buyers actually get judged on.