━ CASE STUDY ━ TEAMS AS A SERVICE ━ MOBILITY
How M.M.'s Product Development Center Backed
Three Mobility Ventures
━ Delivered Result ━
Key Outcomes
M.M. built a dedicated product development center that powered three mobility development ventures: Zemcar, Grip Mobility, and an Uber-related engagement.
A secure in-ride video broadcasting system, driver onboarding, and a recommendation engine all delivered by the same development center.
Provided extensive support for demos and systems integrations
About the Engagement
This case study covers a multi-product engagement delivered through M.M.’s product development center — a partnership that began with Zemcar (a ride-share platform), evolved into a white-label mobility platform called Grip Mobility, and extended into an engagement built on the same technology foundations as Uber.
Zemcar, based in Boston, was founded by Bilal Khan and Juliette Kayyem for people who need more than generic ride share services: such as unaccompanied minors, seniors, and anyone whose journey needs supervision. The platform’s value lives in its trust layer — vetted drivers, in-ride monitoring, live video streamed to a parent or guardian, and a panic button wired into a real support team.
Grip Mobility extended that idea into a configurable white-label platform, designed to instil the same safety and trust capabilities. When the engagement then required capabilities similar to platforms like Uber, M.M.’s same development center pivoted with it — this time with an Android-first and integration-heavy build.
Through all three chapters, M.M.’s Mobility Product Development Center operated as the technology delivery backbone the client could rely on: an embedded product engineering capability covering iOS, Android, backend, frontend, QA, architecture, and project management, supported by senior technical and delivery leadership.
The Challenge
Grip Mobility’s primary need was a secure in-ride audio-video broadcasting system: the capability to capture and stream what was happening inside a moving vehicle in real time. Around it sat the platform’s supporting machinery — ETL jobs, a custom driver onboarding engine, and a driver recommendation engine.
Each of those builds called on a different mix of specializations across mobile, backend, data, integration, and QA. But hiring iOS, Android, backend, frontend, QA, architects, and project managers — each at the right seniority, ready to coordinate — demands both time and a significant long-term investment. The roadmap couldn’t wait that long.
Overall, Grip Mobility required:
- A complete product engineering center that could deliver the in-ride broadcasting system, ETL jobs, driver onboarding engine, and recommendation engine as a coordinated whole.
- Mobile-first builds for iOS and Android, with the same crew supporting demos, releases, and iterations.
- A team that could carry the technology forward as the requirements shifted, from Zemcar’s consumer experience, into Grip Mobility’s white-label platform, into an Uber-related engagement involving integrations and demonstrations.
- Senior architecture and delivery leadership embedded inside the team.
- Integration and demo readiness on tight timelines.
The solution: a dedicated product development center
M.M. assembled a product development center — a coordinated group of squads, each responsible for a slice of the platform, all reporting into shared technical and delivery leadership. The squads were sized and shaped around the actual builds the platform needed, with capacity that could expand or contract as priorities moved.
The structure looked like this:
- Product Engineering Squad. Built and extended the core mobility features that powered all three ventures — from Zemcar’s ride flow into Grip’s configurable foundation.
- Mobile Application Squad. iOS and Android for Zemcar and Grip; Android-first for the Uber chapter.
- Backend & Integration Squad. APIs, services, ETL jobs, and the system integrations needed for demos, including the work that supported the demos in São Paulo.
- Quality Assurance Squad. Full-time QA running in parallel with the build cycle — feature testing, regression testing, mobile and backend validation, and demo readiness.
- Architecture & Delivery Leadership. A solution architect, a development head, and project management capacity providing senior technical oversight and delivery coordination.
Grip Mobility’s team retained product authority, while the development center was tasked with translating that direction into tangible outcomes.
How it played out across three ventures
Zemcar: building the trust layer
M.M. came in as Zemcar’s technology partner and accelerated product development by rapidly building out new features and capabilities. The work done during this phase laid the engineering patterns that would later become reusable for developing the Grip Mobility platform.
Grip Mobility: turning the trust layer into a product
Grip Mobility used Zemcar’s foundations and applied them to different markets and clients, including the in-ride audio-video broadcasting system as the safety capability anchoring the platform, the ETL jobs moving and reshaping mobility data, the driver on boarding engine handling vetting at scale, and the recommendation engine matching riders with drivers.
The client provided product direction, while M.M.’s product development center owned solution design, build, QA, and delivery coordination across the whole stack.
The Uber-related engagement: demo-ready in a different gear
When the engagement pivoted to Uber-related requirements, the demo cadence and integration burden changed. The development center absorbed that change, with Android development moving to the front of the line and the backend squad picking up the integration work needed for external presentations.
Demo readiness was a recurring focus, including for external presentations in São Paulo. The platform, the apps, and the supporting integrations all had to be ready for those moments, and the squads coordinated around them.
What made the engagement different
The engagement wasn’t your typical, rigid sprint-only model: it worked through a flexible, product-led cadence: the client-side product leadership identified features and priorities while our teams adapted, executed, and iterated in response.
This set up translated to regular feature discussions, frequent status updates, progress reviews when needed, and weekly updates when the rhythm shifted.
Across Zemcar, Grip Mobility, and the Uber-related engagement, the client got the equivalent of a full product engineering capability without needing to build a complete internal technology department from scratch.
Why Team as a Service?
Our Mobility Product Development Center is a demonstration of the specific problem that our team as a service model is built for: a roadmap that demands specialized talent to land, timelines that can’t wait out a full hiring cycle, and a mix of niche skills that doesn’t always justify permanent headcount once the headline builds are done.
The same delivery model has carried teams through modernizing legacy applications, expanding into new domains like OTT, clearing feature backlogs in parallel with in-house engineering, adding AI capabilities to existing applications, and moving AI pilots into production.
With TaaS, clients ship faster, stay lean, and get access to specialised expertise on demand without absorbing the long-term overhead of building it themselves.
Rather than offering individual resources to our mobility platform partners, M.M. provided a structured product engineering capability that could be assembled into squads and governed as a dedicated product development center.
What makes us really stand out is how we bring these teams together. Our bench is vetted before any engagement starts, and squads are assembled around the actual builds the work demands, with the right specializations brought in for the right phase.
A dedicated lead owns delivery accountability from week one. And as priorities move, the team reshapes — roles added, swapped, or scaled back — without contract restarts or rehiring cycles. That is the model that carried three sequential mobility ventures under a single engagement.
Send us your requirements today and get your first squad assembled in under two weeks.
Interested in your own Team?
Contact us with your requirements.
Get your team assembled in 2–4 weeks. Ship faster, stay lean.