A self-initiated UX exploration — not a Tesla project. The hypothesis: turn 4 million parked Teslas into a peer-to-peer ride-sharing network, using the car's existing dashboard, the existing mobile app, and the Supercharger network as the rails. No new hardware. No new app. Just a new revenue layer Tesla already has the infrastructure for.
Role
Prospective Product Designer
Products
Prospective Concept · Self-Initiated
Dates
Early 2024
Designing a $41M ride-sharing layer inside Tesla's existing ecosystem.
Four million cars, mostly parked.
Most personal vehicles sit unused 95% of the time — including Teslas. But Tesla isn't a typical car company: every vehicle is already a connected node, with a screen, a driver profile, navigation, payment, and a charging network mapped to it. The infrastructure for a ride-sharing layer is already built. It just isn't pointed at that use case yet.
The exercise was to ask a different question than "how would Tesla build an Uber competitor?". The real question is: "how could Tesla unlock peer-to-peer mobility from within the product its owners already use every day?". A revenue line, not a new product.
A $400K bet, modeled at $41M return in year one.
I modeled the opportunity with conservative inputs: 4 million Teslas on the road, 10% of drivers activating the feature, one shared ride per active driver per week, $20 average ride, 10% commission to Tesla. The math holds up even with much harsher assumptions.
Three decisions that kept it inside the existing ecosystem.
The hardest part wasn't designing screens. It was deciding what NOT to design — which surfaces to reuse, which interactions to avoid, and how to ship the feature without breaking the calm of the Tesla product language.
No new app. No new screen system.
Ride requests live inside the existing Tesla mobile app and the in-car dashboard. A single new accent color signals an incoming request — calibrated to be visible at a glance but invisible until needed.
One-touch accept, eyes-on-road.
Accepting a ride is a single tap from the dashboard, after which navigation auto-updates to include the pickup point. Communication uses VOIP and pre-baked messages — no typing while driving.
Reuse the trust Tesla already has.
Driver and passenger identities pull from existing Tesla accounts. Payment runs through the wallet already used for Supercharger billing. The product trades on Tesla's existing trust capital instead of building a new one.
What I'd validate before shipping.
Three open questions kept me honest about the limits of this exercise. First — regulation: peer-to-peer ride-sharing carries insurance and licensing risk that varies by market, and the rollout would need a country-by-country compliance strategy. Second — safety: the system trades on Tesla's autopilot maturity, so the activation window for ride-sharing should likely depend on autopilot availability, not just driver consent. Third — adoption: 10% uptake is conservative on paper, but the actual driver of adoption is whether Tesla owners self-identify as service providers — a brand-positioning question more than a UX one.
The exercise was never about pretending to ship this product. It was about practicing the muscle of looking at a mature product and asking — where's the revenue line that doesn't need new hardware to exist?
Designing a $41M ride-sharing layer inside Tesla's existing ecosystem.
A self-initiated UX exploration — not a Tesla project. The hypothesis: turn 4 million parked Teslas into a peer-to-peer ride-sharing network, using the car's existing dashboard, the existing mobile app, and the Supercharger network as the rails. No new hardware. No new app. Just a new revenue layer Tesla already has the infrastructure for.
Four million cars, mostly parked.
Most personal vehicles sit unused 95% of the time — including Teslas. But Tesla isn't a typical car company: every vehicle is already a connected node, with a screen, a driver profile, navigation, payment, and a charging network mapped to it. The infrastructure for a ride-sharing layer is already built. It just isn't pointed at that use case yet.
The exercise was to ask a different question than "how would Tesla build an Uber competitor?". The real question is: "how could Tesla unlock peer-to-peer mobility from within the product its owners already use every day?". A revenue line, not a new product.
A $400K bet, modeled at $41M return in year one.
I modeled the opportunity with conservative inputs: 4 million Teslas on the road, 10% of drivers activating the feature, one shared ride per active driver per week, $20 average ride, 10% commission to Tesla. The math holds up even with much harsher assumptions.
Three decisions that kept it inside the existing ecosystem.
The hardest part wasn't designing screens. It was deciding what NOT to design — which surfaces to reuse, which interactions to avoid, and how to ship the feature without breaking the calm of the Tesla product language.
No new app. No new screen system.
Ride requests live inside the existing Tesla mobile app and the in-car dashboard. A single new accent color signals an incoming request — calibrated to be visible at a glance but invisible until needed.
One-touch accept, eyes-on-road.
Accepting a ride is a single tap from the dashboard, after which navigation auto-updates to include the pickup point. Communication uses VOIP and pre-baked messages — no typing while driving.
Reuse the trust Tesla already has.
Driver and passenger identities pull from existing Tesla accounts. Payment runs through the wallet already used for Supercharger billing. The product trades on Tesla's existing trust capital instead of building a new one.
What I'd validate before shipping.
Three open questions kept me honest about the limits of this exercise. First — regulation: peer-to-peer ride-sharing carries insurance and licensing risk that varies by market, and the rollout would need a country-by-country compliance strategy. Second — safety: the system trades on Tesla's autopilot maturity, so the activation window for ride-sharing should likely depend on autopilot availability, not just driver consent. Third — adoption: 10% uptake is conservative on paper, but the actual driver of adoption is whether Tesla owners self-identify as service providers — a brand-positioning question more than a UX one.
The exercise was never about pretending to ship this product. It was about practicing the muscle of looking at a mature product and asking — where's the revenue line that doesn't need new hardware to exist?