When you operate microtransit across multiple verticals, including hotels, universities, and residential communities, you accumulate data that no single deployment can provide. After crossing the 10,000-ride 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 between 9:30 PM and 12:30 AM, driven by safe ride service. This is 2-3x the volume of the morning class-change peak. For communities, the demand peak is 10:00 AM to 12:00 PM, as residents run morning errands and attend medical appointments. Hotels peak between 5:30 PM and 7:30 PM 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, the average ride distance is 1.8 miles. For community programs specifically, it drops to 1.4 miles. University rides average 1.2 miles. Hotel rides are the longest at 2.9 miles, 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 with a 25-30 mile range can complete 15-20 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 under 8 minutes, satisfaction scores average 4.7 out of 5.0. Between 8 and 15 minutes, satisfaction drops to 4.1. Above 15 minutes, it falls below 3.5, and 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 from 11.2 minutes to 7.8 minutes, and rider satisfaction increased by 0.4 points 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, typically 40-50% of 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 adults over 65 are the most frequent riders on a per-capita basis, the largest absolute ridership group in mixed-age communities is 30-45 year olds, 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 in 90 days. In practice, university programs hit steady state in 30-45 days, driven by rapid word-of-mouth adoption. Community programs take 60-75 days. Hotels reach steady state within two weeks of staff training completion.
- Weekend demand: Projections based on weekday patterns underestimate weekend ridership by 20-30%. 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 2:00-4:00 PM 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, 23% of registered riders account for 71% of total rides. These power users ride an average of 4.2 times per 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 power user rating below 4 stars triggers an automatic follow-up from our operations team. This single process change reduced negative app store reviews by over 60%.
What We Changed Based on the Data
The 10,000-ride 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 by 25% across all programs
- Added family-oriented stops in community programs based on the 30-45 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 scale toward 50,000 rides and beyond, these insights will continue to sharpen, and we will continue to share what we learn.
