Estimate the revenue opportunity if DoorDash improves conversion in Merchant Portal

Problem Statement Description

Product context: DoorDash is a local commerce and delivery platform; its products include restaurant delivery, DashPass, grocery and retail delivery, merchant tools, and dasher tools.

DoorDash wants to estimate the revenue opportunity from improving conversion in its Merchant Portal—the platform restaurants and local businesses use to onboard, manage store settings, review performance, run promotions, and adopt DoorDash services. The focus is on merchants who are sensitive to fees, commissions, and return on investment, and who may compare DoorDash against alternatives such as Uber Eats, Grubhub, Instacart, local delivery fleets, or direct ordering channels.

In this guesstimate, define what “conversion” means in the Merchant Portal and estimate the incremental revenue DoorDash could capture if that conversion rate improves. The conversion could relate to merchant sign-up completion, activation after onboarding, adoption of a paid product, promotion setup, menu/store optimization, or another revenue-driving merchant action. Be explicit about the scope you choose.

The estimate should reflect DoorDash’s marketplace dynamics: merchant ROI, customer demand, order volume, commission or subscription economics, delivery reliability, dasher supply, and potential cannibalization or churn. The opportunity should be framed as incremental annual revenue, with clear assumptions and sensitivity to key drivers.

The experience should consider:

- The conversion funnel being estimated, including starting population, denominator, and final conversion event.

- Merchant segments in scope, such as restaurants, grocery, convenience, SMBs, enterprise merchants, new merchants, or existing merchants.

- Baseline merchant volume, adoption rate, conversion rate, and expected lift from improving the portal experience.

- Revenue mechanics, such as commissions, advertising spend, subscription fees, delivery fees, or incremental order volume.

- Frequency and value assumptions, including average orders per merchant, average order value, take rate, and retention.

- Adoption constraints, such as merchant price sensitivity, setup effort, perceived ROI, operational readiness, and competitive alternatives.

- Sensitivity checks for optimistic, base, and conservative cases.

- Sanity checks against DoorDash’s scale, marketplace balance, and unit economics.

The goal is to produce a structured, defensible estimate of the revenue opportunity, showing how the calculation is built, which assumptions matter most, and what additional data would be needed to make the estimate decision-ready.