Uber Eats
1/9
Product Autopsy9 Stages~20 min read

Uber Eats

Follow one user from a hungry Tuesday night to a twice-a-week habit — and see the product machine running behind every moment

Stage 1 of 9

Acquisition

Where do they come from — and at what cost?

Priya did not wake up thinking about Uber Eats. She was scrolling TikTok during a break, half-watching someone unbox a sushi delivery. Fifteen seconds. A green logo. A caption: "First order free delivery + $25 off."

She almost scrolled past. But the ad was hyper-targeted — female, 25–34, urban, food-content affinity, no competitor app installed — and the creative hit at exactly the right moment: she was already hungry, already tired, already thinking about food. She tapped.

That single tap cost Uber Eats about $32 in ad spend. And she had not ordered anything yet. Most people who get to the home screen never place an order. The acquisition funnel leaks at every step: roughly 3.5% of ad impressions become app installs, and only 35% of those installs convert to a first order.

Uber Eats compounds acquisition from a uniquely powerful asset: 150 million monthly active Uber riders globally. Riders who open the Uber app for a car are one tap away from ordering food — same account, same saved payment, same address. This cross-sell funnel converts at 3–5x the rate of cold paid traffic because trust is already established. That ride network is a structural advantage DoorDash cannot replicate.

The organic channel is equally critical. Priya had seen the green logo before — in coworkers' Instagram stories, in office Slack channels, in a referral text from a friend. Multiple low-cost touches over weeks made the paid ad feel like a confirmation rather than an introduction. The paid dollar closes the deal; the organic impressions make it cheap.

Organic CAC runs around $12. Paid CAC in dense markets like New York City exceeds $40. The blended number matters most, and the ratio between organic and paid determines whether the unit economics hold. When paid spend grows faster than organic, CAC inflation precedes every other warning sign by quarters.

$12Organic CAC
$40+Paid CAC (NYC)
~35%Install to First Order

War Room

4 perspectives
PM

"Should we show estimated total on the restaurant card — before they tap in?" Testing showed fewer clicks but 40% higher checkout completion. Net revenue went up. Honest pricing loses browsers but converts buyers.

ENG

Attribution pipeline is the single most revenue-critical system. UTM params, deep links, AppsFlyer install attribution, promo code redemption tracking. If this breaks, marketing spends millions blind — and nobody notices for days.

DATA

Building the channel mix model: what is the marginal CAC per channel? When does the next dollar in TikTok ads stop returning value? The model must account for organic cannibalization — paid ads that take credit for users who would have come anyway.

DESIGN

The address entry screen kills 15–20% of signups. GPS is not precise enough for apartments. The team is iterating on a map-pin-drag feature with fuzzy address matching and saved-address prompts.

Priya has the app open. She is browsing Siam Kitchen's menu. She adds pad thai and spring rolls to her cart. ↓

Stage 2 of 9

Activation

Did the product actually deliver for them?

Priya hits Place Order at 7:24 PM. The app says 30–38 minutes. She puts on sweatpants, opens Netflix, and waits. At 7:52 PM — twenty-eight minutes — her phone buzzes. Marcus is arriving. She opens the door. The bag is warm. The pad thai is exactly right. She did not have to talk to anyone, wait in line, or drive in the rain.

She rates it 5 stars without thinking. That is activation. Not the signup. Not the download. The moment Uber Eats actually delivered on its promise.

But this delivery was not an accident. Behind the scenes, Uber Eats pulled three levers specifically because this was Priya's first order. Priority dispatch: first orders are system-flagged. The algorithm did not assign the nearest available driver — it assigned Marcus, an experienced partner with a 4.95 rating and 2,340 deliveries. The system traded efficiency for reliability because a bad first experience kills lifetime value permanently.

Padded ETA: the real estimate was 25 minutes. The app said 30–38. Priya expected to wait. When food arrived in 28, it felt early. That 2-minute surprise was engineered — a first-order coefficient in the ETA model that under-promises by 5–10 minutes for new users specifically.

Proactive recovery standing by: if Marcus had been delayed, a pre-written notification was ready to fire — "Your order is taking longer than expected — here is $5 off your next order." It did not need to send tonight. But it was loaded and waiting.

Right after her 5-star rating, Priya saw a push notification prompt. Not at app open — not before she had experienced value — but at the exact moment she was happiest. 72% of users opt in when asked after a 5-star rating, versus 45% at app open. She tapped Allow. She also saved her address and payment. Users who complete all three within 48 hours retain at 3x the rate of those who do not.

72%Push Opt-In After 5-Star Rating
Retention Lift (48hr Setup)
~90%First-Order On-Time Target

War Room

4 perspectives
ENG

The DeepETA model — gradient-boosted decision tree regression running on the Michelangelo ML platform. 26% improvement in delivery time prediction. The first-order coefficient pads estimates for new users. Getting this wrong by 2 minutes is a product failure with measurable retention consequences.

PM

"First-delivery reliability is an SLA, not a metric." If on-time rate drops below 90% for first orders, 30-day retention drops proportionally. PM tracks this daily and escalates faster than any revenue metric on the dashboard.

DATA

Running the notification prompt timing experiment. Three variants: at app open (45% opt-in), after delivery (65%), after 5-star rating (72%). The winning variant triggers on a rating action, not a session state. Emotional context outperforms logical timing.

OPS

Driver quality matching for first orders. The dispatch algorithm now weights partner rating and experience, not just proximity, for flagged first-order deliveries. Trade-off: slightly longer ETAs in some cases, but dramatically better first impressions.

Priya's first order went perfectly. She saved her address, her card, and turned on notifications. It has been one week. ↓

Stage 3 of 9

Engagement

Is the product earning repeated attention?

Tuesday, 11:32 AM. Priya is in a standup meeting, half-listening to a sprint update. Her phone buzzes: "Craving pad thai? Siam Kitchen has a lunch deal today. Free delivery with Uber One." She was not thinking about food. Now she is. She taps the notification, sees her last order with a Reorder button, taps it, confirms. Ninety seconds. Twenty-six dollars. Done.

That notification was not random. It fired at 11:32 because Uber Eats' data shows the lunch decision window is 11:15–11:45 — after that, people commit to other plans. It mentioned Siam Kitchen because that is what Priya ordered last. It said "Free delivery with Uber One" to plant a seed for the subscription pitch coming later.

The following Friday, it rained. At 6:14 PM, a push fired: "Perfect night to stay in. Rain detected in your area. Free delivery tonight — on us." This was not triggered by a marketing calendar. It was triggered by a weather API that detected rain in Austin at 6:02 PM. The system auto-fired a personalized push within 12 minutes. Order volume spikes 20–30% during rain events — not because people are hungrier, but because the cost of the alternative just went up.

By week three, Priya has ordered four times. She is developing a pattern: Thai on Tuesdays, burritos on Fridays. She does not think about what to eat anymore — she thinks about which of her usual spots to reorder from. The reorder button reduced her decision from "what should I eat?" to "same as last time?" For habitual users, one-tap reorders account for 40% or more of all orders.

The engagement machine runs on two rails. Contextual triggers — weather, time of day, day of week, order history — that surface the app at the exact moment a food decision is forming. And friction removal — the reorder button, saved favorites, pre-filled address and payment — that makes acting on that trigger nearly instantaneous. Remove either rail and engagement drops.

The real risk is notification fatigue. CTR on mealtime pushes averages around 4%. Doubling notification frequency doubles opt-outs, and opt-outs are permanent. Every optimization for short-term engagement has to be weighted against the long-run cost of losing the push channel entirely.

~4%Mealtime Push CTR
40%+Orders via One-Tap Reorder
20–30%Order Volume Spike in Rain

War Room

4 perspectives
ENG

Weather-triggered push pipeline. Real-time weather API integration, geo-fence matching, user eligibility filter, personalized message assembly, push delivery. End-to-end latency target: under 15 minutes from weather event to notification. This is event-driven architecture, not batch marketing.

PM

"CTR on mealtime pushes is only 4%. How do we double it without spamming?" Debate: send fewer, better-timed notifications using order-history prediction versus sending more with personalized restaurant mentions. The fear: notification fatigue leads to opt-outs, which is permanent revenue loss.

DATA

Building the next-order prediction model. Features: day of week, time of day, cuisine history, weather, recency of last order, reorder versus explore ratio. Goal: predict when a user is 15 minutes away from a food decision and hit them before they default to cooking.

DESIGN

The reorder flow is the highest-ROI screen in the app. A/B test showed home-screen placement of recent orders increased reorder rate by 18% but decreased new restaurant discovery by 12%. Current compromise: top section of home feed, scrollable.

Priya orders twice a week now. But every time she checks out, she winces at the total. ↓

Stage 4 of 9

Monetization

Is the business model real and sustainable?

Priya adds pad thai ($16) and spring rolls ($9) to her cart. Subtotal: $25. She taps checkout. Then she sees the real number: $41.24. Delivery fee $4.99. Service fee $3.75. Taxes. A tip prompt. The math just happened quietly while she was browsing.

This is the sunk cost ramp. By the time Priya sees the real total, she has already browsed, chosen, and customized. The psychological cost of backing out exceeds the price premium. The checkout was designed so that investment precedes revelation. And that green banner at the bottom — "Save $4.99 on delivery with Uber One" — is planting a seed for Stage 5.

Here is where Priya's $25 in food actually goes. The restaurant pays a 25% commission, keeping about $18.75. Uber Eats takes the $6.25 commission plus the $3.75 service fee. The delivery fee is split between the driver and the platform. After paying the driver's share, refunds, and ops, contribution margin is often single-digit dollars per order — or negative in competitive markets.

The delivery business alone does not work. What makes Uber Eats viable is everything around the delivery. Sponsored restaurant placements are Google Ads for food — pure margin, restaurants bid for visibility. Checkout upsells add $3–5 to average order value with zero extra delivery cost. CPG advertising — Coca-Cola pays for the 'Add a Coke for $1' placement. Dynamic pricing charges more during peak hours and less during off-peak to smooth demand and protect margins.

The advertising platform is the most underappreciated revenue stream. A self-serve auction where restaurants bid for sponsored placement in search results costs Uber Eats nothing to fulfill — no driver, no delivery, no logistical complexity. At DoorDash, this stream has scaled toward $1B annually. It is the highest-margin revenue the food delivery model generates, and Uber Eats was late to build it.

The structural tension in food delivery monetization is that all three revenue streams — restaurant commission, consumer fees, and advertising — create perverse incentives if taken too far. Commission pressure pushes restaurants to raise menu prices. Service fee pressure pushes consumers toward competitors. Advertising pressure degrades search quality and consumer trust. Every take-rate decision is a tradeoff between short-term margin and long-term platform health.

~25–30%Gross Take Rate
$4.50Est. Revenue Per Order
$74.6BGross Bookings (2024)

War Room

4 perspectives
PM

"Should we show the estimated total earlier — on the restaurant card?" Experiment result: fewer users tapped into restaurants, but those who did checked out at 40% higher rates. Net revenue increased. The debate now: roll out globally or keep testing by market?

ENG

Batched delivery routing algorithm. One driver, two pickups, one route. User waits 5–10 extra minutes but the system pays one driver instead of two. The routing optimization directly determines contribution margin. Every minute shaved off a batch route is money.

PM

Building the retail media and ad platform. Sponsored placements, promoted search results, checkout add-ons. This is the Amazon playbook: turn the marketplace into a media platform. Highest-margin revenue stream because there is zero delivery cost.

DATA

Dynamic pricing model: surge multiplier based on real-time demand, driver supply, weather, and time of day. Goal: maximize revenue during peak while using $0 delivery as a demand lever during off-peak. Getting the elasticity curves wrong means either leaving money on the table or killing conversion.

Priya has been ordering for three months. She has done the math on those delivery fees. ↓

Stage 5 of 9

Retention

Do users genuinely need this — or just like it?

Three months in. Thai Mondays, burrito Fridays. Priya opens Uber Eats and sees, for the hundredth time, that green banner: "Save $4.99 on delivery with Uber One." She finally does the math. She orders roughly 10 times a month. Delivery fee averages $5. That is $50 a month in delivery fees. Uber One costs $9.99. She would save $40. She subscribes.

Something shifts after she subscribes. Her order frequency goes from 1.5x/week to 2.5x/week. Not because she is hungrier — because the delivery fee, the thing that made her hesitate every time, is gone. And there is a new psychology at work: "I am paying $9.99 a month for this. I should use it."

This is the Uber One flywheel. The subscription removes the friction that slowed ordering. Ordering more makes the subscription feel like a better deal. Feeling like a better deal makes cancellation feel like a loss. The loop reinforces itself with every order. Subscribers reach 30M+ globally and growing 60% year-over-year.

Four months later, a delivery arrives 25 minutes late. Cold food. Priya contacts support, waits 10 minutes, gets a $5 credit. She does not order for two weeks. Uber Eats notices. The churn escalation ladder begins: Day 7, a warm push mentioning Siam Kitchen with no discount. Day 14, an email with $10 off and her restaurant's name in the subject line. Day 21, a push and email combo with $15 off and free delivery expiring in 48 hours. Day 30, a final $20 off with no minimum.

Priya gets the Day 14 email. The mention of Siam Kitchen — her restaurant, not a generic promo — brings her back. But the real anti-churn strategy is not the escalation ladder. 40% of churned users never return regardless of incentive amount. The real retention investment is preventing the bad delivery that caused the churn in the first place.

Users consistently matched with 4.8+ rated drivers had 15% higher 30-day retention. That single insight drove the partner-quality-weighted dispatch algorithm. Retention is an upstream engineering and operations problem disguised as a downstream marketing problem.

30M+Uber One Members
60%YoY Subscriber Growth
$1B+Subscription Revenue/yr

War Room

4 perspectives
PM

"Uber One free trial converts at 80% to paid — but 20% cancel before month 1." The debate: what value moments need to happen in the first 14 days? Should we front-load savings (lots of orders) or front-load delight (prioritize delivery quality)?

ENG

Churn prediction model. If a weekly user has not ordered by Day 5, probability of churn spikes. The system needs to detect this early enough to intervene with a push on Day 7 — not Day 14. Feature set: order cadence, last delivery rating, support tickets, session drops.

DATA

Win-back email A/B testing. Best subject line: 'We saved your favorites' (3.2% open) versus 'Come back to Uber Eats' (1.8%). Personalized restaurant names in the body had 2x the CTR of generic messages. The escalation ladder cost is tracked per user — if Day 30 does not work, user enters a quarterly cycle.

OPS

Delivery quality correlation with retention. Users consistently matched with 4.8+ rated drivers had 15% higher 30-day retention. This insight drove the partner-quality-weighted dispatch algorithm — not just proximity-based, but retention-aware.

Priya is retained. She orders 2.5 times a week and has Uber One. Now she starts spreading the word. ↓

Stage 6 of 9

Referral

Does the product spread without paid marketing?

Wednesday lunch. Priya is eating pad thai at her desk. Her coworker Anika walks by: "Where is that from? That smells amazing." Priya pulls up her app, copies her referral code, and texts it to Anika. Give $20, get $20. Anika downloads the app, uses the code, and orders dinner that night.

Uber Eats just acquired a new user for $20 in credits instead of $40 in ad spend. And Anika will retain 2–3x better than a cold paid user — because trust was pre-established by Priya. Referred users do not need to discover value; someone they trust already told them it works. That pre-sold trust compresses the time to first order and eliminates the trust deficit that new-user acquisition normally has to overcome.

The referral prompt appeared after one of Priya's 5-star deliveries — not during onboarding, not at a random session moment. Referral conversion is 3x higher when prompted at the emotional peak of a great experience. The timing is not a UX nicety; it is the reason the program converts.

80% of referral codes are shared via text message, which means the deep link has to work perfectly — with or without the app installed, on iOS and Android, attributing correctly across devices and deferred install scenarios. The engineering behind a referral link is not simple: universal links on iOS, App Links on Android, deferred deep linking for app-not-installed states, attribution window logic.

Referral fraud is the program's silent tax. People create multiple accounts to redeem their own codes. Detection signals: same device fingerprint, same IP address, same delivery address, order placed within minutes of signup. Reward fulfillment is delayed until legitimate behavior — a real delivery to a new address — is confirmed. Without this layer, the referral program becomes a discount harvesting mechanism for sophisticated users.

The data team's finding: referred users have 16% higher LTV and 2–3x better 90-day retention versus paid-acquired users. But the causal question matters — is that because referrals are inherently better users, or because the type of person who gets referred is different from the type who clicks an ad? Measuring this correctly changes the economics of how much referral credit is worth offering.

$20Referral Credit Per Side
16%Higher LTV vs. Paid Acquired
Referral Conversion Lift (Post-5-Star)

War Room

3 perspectives
ENG

Referral fraud detection. Signals: same device fingerprint, same IP, same delivery address, order placed within minutes of signup. Reward fulfillment is delayed until legitimate behavior (real delivery to a new address) is confirmed. This engineering layer is what separates a referral program from a discount exploit.

PM

"When do we show the referral prompt?" After 5-star rating: 3x conversion versus random session moment. Testing a new variant: showing referral stats on the home screen for power users. Hypothesis: making referrals visible turns it into a game and increases share frequency.

DATA

Measuring referral LTV versus paid. Referred users have 16% higher LTV and 2–3x better 90-day retention. But is that because referrals are inherently better, or because the type of user who gets referred is different? The team is running an experiment with randomized referral incentive levels to isolate the causal effect.

Priya started with dinner. But Uber Eats has bigger plans for her wallet. ↓

Stage 7 of 9

Revenue Expansion

Can the business grow without just adding users?

Month five. Priya opens Uber Eats at 7:30 AM and sees a new section: "Breakfast near you." She had never thought of using Uber Eats for breakfast. She orders a coffee and a breakfast burrito. Three days later, she orders lunch at work. Then a grocery run on Sunday. Then Advil at 11 PM through convenience store delivery.

Priya's monthly spend: $80 to $220. Same user. No new acquisition cost. Uber Eats just expanded her wallet by 2.75x by expanding the occasions where the product is relevant — not by acquiring a new customer.

Each new meal occasion (breakfast, lunch, late-night) represents a 30–40% frequency uplift from the same user. Each new category (grocery, alcohol, pharmacy) increases share-of-wallet and deepens the habit. The strategic logic is clear: Uber Eats is not trying to be the dinner delivery app. It is trying to be "get me anything" — the universal fulfillment layer for urban convenience.

Cross-category data shows these expansions are additive, not substitutive. Grocery users order restaurants 15% more often, not less. Adding a new category to a user's behavior increases their total platform engagement rather than fragmenting it. This is the key insight that justifies the expansion investment beyond the obvious TAM arithmetic.

The technical complexity of expansion is underappreciated. A stale restaurant menu is a canceled order. Grocery adds SKU-level inventory that updates hourly. Alcohol delivery requires age verification and jurisdiction-specific regulatory compliance. Each category has fundamentally different logistical, legal, and UX requirements than restaurant delivery — but all share the same courier network, the same checkout flow, and the same saved payment method.

Expansion done poorly creates category confusion. When grocery recommendations appeared in users' restaurant feed without sufficient UI separation, session abandonment increased. The categories need the same app shell but different product modes — different discovery patterns, different delivery time expectations, different packaging norms. Getting the UX architecture right for expansion is as hard as the logistics.

$26Average Order Value
3.1BTotal Trips (2024)
$74.6BGross Bookings

War Room

3 perspectives
PM

"Should grocery be a tab in the existing app or a separate experience?" Tab won: reduced friction, higher discovery. But the grocery UX — add to cart, substitutions, produce quality — is fundamentally different from restaurant ordering. Building a grocery mode within the same app shell without degrading the restaurant experience is the product challenge.

ENG

Menu data pipeline at scale. Thousands of restaurants with constantly changing menus, prices, and availability. Grocery adds SKU-level inventory that updates hourly. A stale menu is a canceled order is a support ticket is a churn risk. The pipeline ingests, normalizes, and serves this data with sub-second latency.

DATA

Cross-category uplift measurement. Does adding grocery increase total platform spend, or does it cannibalize restaurant orders? Early data: grocery users order restaurants 15% more often, not less. The categories are additive, not substitutive. This is the key insight that justifies the expansion investment.

Priya is deeply embedded. But the market around her is shifting. ↓

Stage 8 of 9

Sustainability

Will this product still matter in 3 years?

Priya does not know it, but she is being fought over. DoorDash sends her $15-off emails every week. A new Austin-based app called LocalBite launches with lower fees and a 'support local' angle. The Austin city council is debating capping delivery commissions at 15%. Her employer starts subsidizing office lunch catering three days a week. Every one of these threats is a real vector that could pull her away.

DoorDash dominates the US with 67% market share. Uber Eats holds 23%. But Uber Eats leads globally — roughly 50% in Japan, 40% in Australia, strong in France and Spain. The real battlefield is not the US. It is the international TAM where Uber's ride platform gives it a cross-sell advantage DoorDash cannot match.

The existential threats are stacking: regulatory risk — commission caps at 15–20%, gig worker reclassification adding 20–30% to labor costs per delivery. Restaurant direct ordering — Toast, Square, and Shopify helping restaurants bypass the 25% commission with their own digital ordering. Autonomous delivery — if drones or autonomous vehicles cut delivery cost by 60%, whoever has the best routing technology wins regardless of current market share.

The real moat is not the app. It is the three-sided marketplace: users attract restaurants, restaurants attract users, demand attracts drivers, drivers enable faster delivery, faster delivery retains users. Breaking into this loop from scratch is nearly impossible. This is why Uber Eats survives despite DoorDash's US dominance — and why DoorDash has never gained meaningful international traction.

Regulatory strategy has evolved from adversarial to pragmatic. Early Uber fought regulations. Modern Uber Eats proactively collects and remits applicable taxes, shares data with local governments on demand, and engages restaurant industry associations before legislation is proposed. Converting regulators from adversaries to revenue partners is a product and policy strategy, not just a legal one.

The gig worker classification risk is the most structurally threatening issue. A shift to employee classification in the US and EU would increase per-delivery costs by an estimated 20–30%, requiring a fundamental repricing of the platform. Every product decision about how couriers are assigned, how earnings are calculated, and how work is structured has legal classification implications that product teams must understand.

23%US Market Share
45+Countries with Active Listings
67%DoorDash US Share (Context)

War Room

3 perspectives
PM

"If commission caps hit 15%, we need a new P&L for every affected market within 90 days." Options: raise service fees, accelerate ad platform revenue, restructure restaurant tiers (lower commission for high-volume partners), or exit unprofitable markets entirely.

ENG

Autonomous delivery integration. Sidewalk robots and drone delivery pilots are running in select markets. The technical challenge: routing algorithms that handle mixed fleets (human drivers plus robots plus drones), handoff protocols, and reliability SLAs for autonomous delivery.

PM

"How do we prevent restaurant defection to direct ordering?" Strategy: make Uber Eats so good at demand generation that leaving means losing 30%+ of orders. The restaurant cannot replicate Uber Eats' user base, discovery algorithm, or delivery network — even with a Toast website.

Priya uses Uber for rides, Eats for food, and just started ordering groceries. She is not using an app anymore — she is inside an ecosystem. ↓

Stage 9 of 9

Ecosystem

Has the product become bigger than itself?

It has been a year. Priya takes an Uber to a restaurant for date night and earns Uber Cash. She orders Uber Eats for a team lunch and her company's expense system auto-categorizes it. She uses her Marriott Bonvoy points to pay for delivery on vacation. She orders groceries on Sunday morning and gets 10% off because she has Uber One. She is not choosing Uber Eats over DoorDash anymore. She is not making a decision at all.

Users who interact with 3 or more Uber products — Rides plus Eats plus Grocery — churn at one-quarter the rate of single-product users. The data team is building a 'platform depth' score that predicts churn risk based on ecosystem engagement, and routing at-risk users to cross-product promotions before they drift. Each additional product layer roughly halves the churn rate of the previous one.

Uber One is the glue. The cross-product subscription is the mechanism that converts separate app relationships into a unified platform relationship. A user who receives delivery fee waivers on Eats AND Uber Cash on rides has switching costs that span two separate purchase behaviors. To leave, they would need to find a replacement for both simultaneously — a much higher bar than switching delivery apps.

The restaurant technology layer adds a B2B moat behind the consumer product. When a restaurant depends on Uber Eats' POS integration, demand analytics, and delivery logistics to run their delivery business, the switching cost is not just lost demand — it is lost tooling. Restaurant partners using Uber Eats' infrastructure for order management have near-zero churn because the cost of migration is operational, not just economic.

The ecosystem model changes how you think about competitive threats. A competitor can outbid Uber Eats on commission rates for a restaurant. They cannot simultaneously offer that restaurant a replacement POS integration, demand analytics dashboard, and corporate meal program. The more layers of the ecosystem a partner uses, the harder it is to displace the platform with a single competing offer.

A product is vulnerable. An ecosystem is defensible. Uber Eats stopped competing on delivery speed a long time ago. Now it competes on how deeply embedded it is in users' wallets, companies' expense systems, loyalty programs, and restaurant operations. Switching would mean unwinding a dozen connections, not just downloading a different app.

1/4Churn Rate (3+ Products vs. 1)
~35%Eats Subscribers Using Rides
55%Target Cross-Product Usage

War Room

4 perspectives
ENG

Ecosystem engineering is API-first. Restaurant POS integrations, corporate expense APIs, loyalty point interchange protocols, unified identity across Uber products. The challenge: make Uber Eats interoperable with everything. This is platform engineering, not feature engineering.

PM

"Uber One needs to span Rides plus Eats plus Grocery as a single value prop." Cross-product usage rate is the KPI: what percentage of Eats subscribers also use Rides? Current: ~35%. Target: 55% within 12 months. Every cross-product user is dramatically harder to churn.

PM

Restaurant technology platform: POS integration, menu management, demand analytics, delivery logistics. When a restaurant depends on Uber Eats' infrastructure to run their delivery business, the switching cost is not just demand — it is tooling. This is the B2B moat behind the consumer product.

DATA

Cross-ecosystem stickiness measurement. Users who interact with 3+ Uber products churn at 1/4 the rate of single-product users. The data team is building a platform depth score that predicts churn risk based on ecosystem engagement and routes at-risk users to cross-product promotions.

Priya started as a tired data engineer with an empty fridge. Nine stages later, she orders 2.5 times a week, refers friends, buys groceries, and earns loyalty points across an ecosystem she would need real effort to leave. ↓

The Full Picture

Priya started as a tired woman with an empty fridge. Nine stages later, she is a subscriber who orders 2.5 times a week, refers friends, buys groceries, and earns loyalty points across an ecosystem she would need real effort to leave. That transformation was not luck. It was a product machine — designed, built, and iterated by PMs debating checkout psychology, engineers optimizing ETA models, data scientists measuring churn cadences, and ops teams matching drivers to moments that matter. The unit economics of food delivery are genuinely hard — contribution margins are thin, competitive pressure is relentless, and regulatory risk is structural. What makes Uber Eats viable is not the delivery itself but everything built around it: the subscription that changes ordering behavior, the advertising platform that generates margin without logistics, the cross-product ecosystem that raises switching costs across an entire lifestyle. Understanding these nine stages is not academic. It is how you think about any product that turns a moment of need into a recurring business.

Back to all autopsies