Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Rideshare Company Cut Driver Churn 20 Percent With a Single Policy Change
Transcript
- Lucas: There's a question that keeps rideshare executives up at night — and it's not self-driving cars or regulatory battles. It's driver churn. The cost of losing a driver and recruiting a new one can run into the thousands of dollars per person, and some platforms were seeing annual churn rates north of 100 percent — meaning they were essentially replacing their entire driver base every year. Luna: And when you think about it, that's a massive operational leak. Every new driver needs background checks, onboarding, and often a sign-on bonus. So what did one company do to plug that leak? Lucas: They made a single policy change: they doubled the rider cancellation fee from five dollars to ten dollars. That's it. No new technology, no algorithm overhaul. Just a price adjustment for one specific transaction type. And it reduced driver churn by roughly 20 percent within a quarter. Luna: Twenty percent — that's huge. But I have to ask, did they worry that the higher fee would scare riders away? I mean, nobody likes paying for a ride they didn't take. Lucas: Exactly the concern. For years, the conventional wisdom inside the company was that riders would revolt if the fee went up. They ran surveys, focus groups — and riders did say they'd be less likely to use the app if cancellations cost more. But here's the thing: what riders say they'll do and what they actually do are often very different. Luna: So they ran an experiment? Lucas: They did. They tested the ten-dollar fee in a handful of mid-sized markets over three months. And what they found was that cancellation rates actually dropped — by about 15 percent. Riders just became more careful before hitting that request button. They'd check the wait time, make sure they were at the right spot. The fee wasn't punitive; it was a nudge toward better behavior. Luna: So riders adapted, and drivers benefited. It's a classic case of aligning incentives. But what about the driver side — did the fee actually make them feel more valued? Lucas: That's where the behavioral economics gets interesting. In driver surveys, the number one complaint wasn't pay per mile — it was wasted time. Drivers would drive ten minutes to a pickup, wait another three, and then get a cancellation with no compensation. The old five-dollar fee barely covered the gas. The ten-dollar fee felt like the company was acknowledging their time. Several drivers in the test markets reported feeling 'respected' — that's their word — for the first time. Luna: And respect translates into loyalty. I can see that. But did the company see a measurable impact on driver hours or supply? Lucas: Yes — and this is the part that really sold the leadership team. In the test markets, drivers logged about 8 percent more hours per week. And the number of drivers who went offline after a cancellation dropped significantly. Previously, if a driver got cancelled on twice in a row, they'd often just end their shift. After the change, they'd stay on. The supply became more stable, which in turn reduced wait times for riders — a virtuous cycle. Luna: So the rider experience actually improved too, because there were more drivers consistently available. Did the company roll it out everywhere after the pilot? Lucas: They did, but not without a fight internally. The product and marketing teams were worried about a PR backlash. They even did a soft launch — only notifying drivers about the change, not riders. And the rider backlash never materialized. In fact, rider satisfaction scores in the pilot markets remained flat. People grumbled in the moment, but they didn't leave the platform. Luna: It makes you wonder what other small operational tweaks are sitting on the table, just waiting for someone to try them. I mean, a five-dollar change — that's basically the price of a coffee — and it moved a core metric by 20 percent. Lucas: Honestly, if today's conversation was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's the smallest possible ask for an ad-free show that digs into exactly these kinds of stories. Luna: Yeah, and if these conversations have moved your work forward in some small way, it's a simple way to keep them coming. No pressure, just a genuine thanks. Lucas: Right. So back to the rideshare case — what struck me most was that the company almost didn't run the test. They had a whole deck of slides showing why a higher fee would fail. But a small product team pushed for it, and good thing they did. Luna: What was the tipping point that got the test approved? Lucas: A single data point from driver support calls. They realized that the number-one reason drivers contacted support was to dispute cancellations — and the vast majority of those calls were about the five-dollar fee not being enough. The cost of handling those calls alone was eating up any revenue from cancellation fees. So the team framed the test as a way to reduce support costs, not just improve driver satisfaction. That argument got the green light. Luna: Clever framing. It shows how a cross-functional perspective can unlock a decision. What happened to the support call volume? Lucas: It dropped by about 30 percent. Drivers were much less likely to call in when they felt the fee was fair. And the calls that did come in were shorter — less complaining, more just confirming the charge. So the company saved money on two fronts: lower churn and lower support costs. Luna: That's a double win. And it all started with a willingness to question a sacred cow — the idea that riders would flee. Lucas: Exactly. And it's a reminder that small changes, when rooted in a deep understanding of how people actually behave, can have outsized impact. Most companies focus on big initiatives — new features, new markets — but the low-hanging fruit is often a tweak to an existing process that you've been ignoring because 'that's just how it's always been.' Luna: Are there other examples you've seen of similar small policy changes with big effects? Lucas: A fast-food chain I looked at reduced employee turnover by 15 percent just by changing the shift scheduling window — giving workers their schedules two weeks in advance instead of one. The cost was zero. It just required a shift in manager training. But it dramatically improved work-life balance perception. Luna: It's almost like the biggest operational wins aren't about spending more money, but about removing friction that you've normalized. Lucas: Right. And that's why I love this rideshare case. It's a perfect example of operational leverage: a tiny change in one policy ripples into driver behavior, rider behavior, support costs, and supply reliability. The ROI on that five-dollar increase must have been enormous. Luna: Do you know if the company has since tried any other pricing tweaks based on the same logic? Lucas: They experimented with dynamic cancellation fees — higher during peak times — but that got more pushback from riders. The flat ten-dollar fee turned out to be the sweet spot. Simple, predictable, and easy to communicate. Luna: So the lesson: sometimes the best fix is the one that's right in front of you, disguised as a minor policy detail. Lucas: Exactly. And it's not about the cancellation fee itself. It's about asking: what is the one point of friction that, if addressed, would change the entire experience for your most critical stakeholder? For a rideshare company, that's the driver. And they found it in a five-dollar gap.