Slidr Team
A data-driven look at what we learned from thousands of rides across hotels, universities, and communities, from peak demand patterns to rider behavior.
When you operate microtransit across multiple verticals, including hotels, universities, and residential communities, you accumulate data that no single deployment can provide. After crossing a major ridership milestone across our active programs, we sat down with our operations and data teams to analyze what the numbers actually tell us about how people use microtransit. Some findings confirmed our assumptions. Others surprised us. All of them have changed how we design and operate service.
Peak Demand Is Not When You Think
Before launching any program, we build demand models based on population, geography, and use case. Those models typically predict peak demand during traditional rush hours. The reality is more nuanced.
At university programs, the highest demand consistently occurs late in the evening, driven by safe ride service. This far exceeds the volume of the morning class-change peak. For communities, the demand peak is mid-morning, as residents run morning errands and attend medical appointments. Hotels peak in the early evening as guests head to dinner reservations.
The lesson: do not staff and schedule based on assumptions from traditional public transit models. Microtransit demand curves are shaped by the specific population you serve, and they often look nothing like a typical commuter pattern.
Average Ride Distance: Shorter Than Expected
Across all programs, most rides are short. Community and university rides are the shortest. Hotel rides are the longest, reflecting the distance between resorts and off-property dining and entertainment destinations.
These short distances have significant implications for fleet planning. Electric low-speed vehicles can complete many rides on a single charge, making them ideal for the use case. Range anxiety, one of the most common concerns we hear from prospective clients, is essentially a non-issue in practice. We have never had a vehicle run out of charge during a service shift.
Wait Time Is the Make-or-Break Metric
We tracked rider satisfaction against every operational variable in our system. The single strongest predictor of satisfaction is wait time. When wait times are short, satisfaction scores are high. As waits stretch out, satisfaction drops, and once waits run long, repeat usage drops sharply.
This finding drove us to restructure our dispatching algorithms to prioritize wait time reduction over route efficiency. The previous algorithm minimized total fleet miles traveled. The updated algorithm minimizes maximum individual wait time, even if that means slightly less efficient routing. The result: average wait times dropped noticeably, and rider satisfaction rose across all programs.
The Friday Effect
Friday is the highest-demand day across every vertical, but for different reasons. At universities, Friday evening safe rides spike as students head to social activities. In communities, Friday morning sees the week's highest ridership as residents combine errands and social plans. At hotels, Friday check-ins create a surge of guests needing orientation rides and dinner transportation.
Saturday is the second-highest day for hotels and universities but drops to fourth for communities, behind Monday and Wednesday. Sunday is consistently the lowest-demand day across all verticals, well below Friday volume.
Rider Demographics: Not Who You Expect
In community programs, we expected the primary user base to be older adults. The data tells a different story. While older adults are the most frequent riders on a per-capita basis, the largest absolute ridership group in mixed-age communities is younger adults, often parents shuttling to and from community amenities with children. This finding has changed how we design service zones and schedule vehicles, ensuring coverage of family-oriented destinations like pools, playgrounds, and sports facilities during afternoon hours.
At universities, graduate students and staff use the service at higher per-capita rates than undergraduates, despite most programs being marketed primarily to the undergraduate population. Graduate students tend to live farther from campus core and have less flexible schedules, making reliable transit more valuable to them.
How Real Operations Differ from Projections
Our initial demand projections, built from population data and comparable program benchmarks, have been directionally accurate but consistently underestimate two things:
- Ramp-up speed: We typically project that programs will reach steady-state ridership gradually. In practice, university programs hit steady state much faster, driven by rapid word-of-mouth adoption. Community programs take somewhat longer. Hotels reach steady state soon after staff training is complete.
- Weekend demand: Projections based on weekday patterns consistently underestimate weekend ridership. Weekend riders take longer trips, use the service for recreational rather than utilitarian purposes, and are more likely to ride in groups. This has led us to adjust weekend staffing upward across all programs.
Conversely, projections consistently overestimate demand during the mid-afternoon window in communities and during mid-week at universities. These are the valleys where we now reduce fleet deployment to improve cost efficiency.
The Repeat Rider Effect
Across all programs, a small share of registered riders accounts for most total rides. These power users ride several times a week. Understanding and serving power users is critical because they are also the most vocal advocates and the most sensitive to service disruptions. When a power user has a bad experience, the ripple effect through word of mouth is disproportionate.
We now proactively monitor power user satisfaction and have implemented a feedback loop where any low rating from a power user triggers an automatic follow-up from our operations team. This single process change sharply reduced negative app store reviews.
What We Changed Based on the Data
This analysis led to concrete operational changes:
- Restructured dispatch algorithms to prioritize wait time over route efficiency
- Shifted fleet deployment to match actual peak patterns rather than projected ones
- Increased weekend staffing across all programs
- Added family-oriented stops in community programs based on the family demographic finding
- Implemented power user monitoring and proactive outreach
- Reduced mid-week and mid-afternoon fleet deployment to improve cost per ride
Data-driven operations is not a marketing phrase for Slidr. It is how we make every ride better than the last. As we continue to scale, these insights will continue to sharpen, and we will continue to share what we learn.
