Inside Uber's Push Beyond Rides: Why Product Chief Sachin Kansal Is Betting on Hotels and Autonomy
The company's product leader explains how Uber is threading the needle between expansion and focus, while navigating a delicate dance with Waymo and building infrastructure for the autonomous era.

The Expansion Paradox
Uber is not trying to become a super-app that does everything. That might sound counterintuitive for a company now offering hotel bookings alongside ride-hailing, but Chief Product Officer Sachin Kansal insists the strategy is more surgical than scattershot. The question Kansal faces daily is how to grow Uber's surface area without diluting what made it valuable in the first place: getting people and things from point A to point B reliably.
At DailyTechWire, we've tracked dozens of platform companies in Asia and North America attempt this balancing act. Most fail by either staying too narrow or sprawling into irrelevance. Uber's current product roadmap suggests the company believes it has found a middle path, one that hinges on occasions rather than categories.
The hotel push represents the clearest test case. Uber isn't building a travel marketplace to compete with Booking or Expedia across every dimension. Instead, Kansal frames hotels as a natural extension of the journey that already begins in the Uber app when someone books a ride to the airport. The company's thesis: if you trust Uber to get you there, you might trust it to sort where you sleep when you land.
Financial Services as Connective Tissue
Kansal's ambitions for financial services run deeper than payments processing. Uber has been experimenting with earned-wage access for drivers, allowing them to cash out earnings instantly rather than waiting for weekly deposits. The infrastructure built for that feature is now becoming a platform in its own right.
The logic mirrors what we've seen with Grab in Southeast Asia and Gojek in Indonesia, where ride-hailing companies leveraged their transaction volume and user trust to move into digital wallets and lending. Uber's advantage in North America and Europe is different: regulatory complexity is higher, but so is the average transaction value and the sophistication of financial partnerships available.
Kansal describes financial services not as a standalone business line but as connective tissue. Better payment rails reduce friction for riders. Instant payouts increase driver retention and flexibility. Credit products tied to ride history could eventually allow drivers to access capital for vehicle upgrades or maintenance, a capability that would tighten Uber's grip on supply without requiring the company to own fleets outright.
The risk, of course, is that financial services introduce regulatory exposure and operational complexity that distracts from the core marketplace. Kansal's challenge is ensuring these tools remain enablers rather than becoming their own gravitational centers.
Waymo, Competition, and the Autonomous Tightrope
Uber's relationship with Waymo has always been complicated. The two companies settled a bitter intellectual property lawsuit in 2018, then became partners when Uber integrated Waymo's autonomous vehicles into its platform in Phoenix. Now, as Waymo expands commercially and Uber builds out its own autonomous vehicle infrastructure through AV Labs, the partnership looks increasingly like a prelude to competition.
Kansal positions AV Labs as a data and integration layer rather than a hardware play. Uber is not building its own self-driving cars. Instead, the company is creating the software scaffolding that allows any autonomous vehicle, from any manufacturer, to plug into Uber's demand network. That means mapping, routing, rider communication protocols, and safety telemetry that works across different AV platforms.
The strategic bet is that Uber's two-sided marketplace, with millions of riders and drivers already transacting daily, gives it leverage over AV manufacturers who need access to demand. Waymo has its own rider app, but consumer habit is hard to shift. If Uber can remain the default interface for requesting a ride, whether that ride is human-driven or autonomous, it retains control over the customer relationship.
But the balance is precarious. Waymo's parent, Alphabet, has deep pockets and a decade-plus head start in autonomy. If Waymo decides it no longer needs Uber's distribution, or if it builds enough consumer awareness to bypass the platform entirely, Uber's autonomous strategy becomes significantly harder. Kansal's AV Labs initiative is essentially an insurance policy: build enough integrations with enough AV providers that no single partner can hold Uber hostage.
AI That Riders and Drivers Actually Notice
Kansal is careful to distinguish between AI as infrastructure and AI as user-facing feature. Uber has been using machine learning for years to optimize routing, predict demand surges, and match drivers to riders. That's table stakes now. The newer work involves surfaces where AI becomes legible to users.
One example: dynamic trip planning that suggests multi-stop routes based on context. If a rider books a trip to a restaurant district on a Friday evening, the app might prompt them to add a return trip home later, locking in pricing and availability. Another: natural language support that allows drivers to resolve account issues or update preferences by typing or speaking in plain language, rather than navigating nested menus.
These features sound incremental, but they reflect a shift in how Uber thinks about AI. The goal is not to automate everything or replace human judgment wholesale. Instead, Kansal describes AI as a way to reduce cognitive load, to make the app feel less like a transaction processor and more like a service that anticipates need.
The challenge, as with any consumer AI, is avoiding the uncanny valley where suggestions feel intrusive or inaccurate. Uber has access to rich behavioral data, but using it too aggressively risks creeping users out. Kansal's team is iterating on how much proactivity feels helpful versus invasive, a calibration that varies by market and user cohort.
Why "Everything for Everyone" Is a Trap
Kansal returns repeatedly to the idea that Uber must remain opinionated about what it builds. The company has said no to grocery delivery in some markets, no to certain categories of local services, no to features that might generate revenue but dilute focus. The discipline comes from painful experience: Uber's previous attempts to expand into on-demand staffing, freight brokerage, and other adjacencies yielded mixed results.
The filter Kansal applies is whether a new product or feature strengthens the core loop: more riders attract more drivers, more drivers reduce wait times, lower wait times attract more riders. Hotels and financial services pass that test because they either extend the journey or reduce friction within it. A generic marketplace for home services or retail goods does not.
This philosophy positions Uber in explicit contrast to companies like WeChat or Meituan in China, which have pursued super-app strategies with broad horizontal expansion. Kansal argues that works in markets with different consumer behavior and regulatory environments. In the West, he believes users want apps to be excellent at one thing, with carefully chosen extensions, rather than mediocre at many.
Whether that bet pays off depends on execution. If Uber's hotel and financial products feel bolted-on rather than integrated, users will ignore them. If AV Labs fails to attract enough partners, Uber risks being disintermediated by autonomous fleets that go direct to consumers. But if Kansal's team can make each new surface feel like a natural continuation of the ride, Uber has a credible path to expanding revenue per user without becoming everything for everyone.


