Direct answer
It makes sense as an MVP (minimum viable product) scoped tightly to small, lightweight, same-city packages, using the existing driver network as supply, because that reuses the hardest part (trusted, verified drivers and a live dispatch system) that a from-scratch competitor would have to build. The two things that actually make or break it are insurance coverage for commercial goods transport (most rideshare driver policies don't automatically cover paid package delivery) and whether the unit economics clear the fixed cost of running that insurance and compliance program at all, not just clear it per delivery.
Structured elaboration
MVP scope, deliberately narrow:
- Package limits: small dimensions and weight (for example, under 30 lbs, fits in a trunk), same-city, same-day delivery windows only.
- Core flow: merchant or consumer creates an order, a driver accepts within their existing app, proof of delivery via photo, basic dispute flow.
- Explicitly out of scope for the MVP: multi-stop batching, cross-city routes, and anything requiring specialized handling (perishables, fragile, hazardous).
Pricing structure: a base fee plus a distance component plus a size surcharge, which mirrors how the existing ride product is already priced, so it's explainable to both drivers and customers using a mental model they already have.
Regulatory and insurance issues, ranked by how likely each is to actually kill the idea:
- Commercial goods transport insurance. This is the binding constraint. Standard rideshare liability policies typically don't cover paid delivery of someone else's goods; without an insurer willing to underwrite this (or a rider on the existing policy), the business can't legally operate regardless of how good the unit economics look.
- Driver classification and opt-in design. Adding a new paid activity to an existing contractor relationship needs a clean opt-in, not an assumed extension, to avoid disputes about what drivers agreed to.
- Local delivery licensing, which varies by city and is a real but more manageable constraint than insurance, since it's usually a paperwork problem rather than a fundamental blocker.
Worked example
Price one delivery using the base-plus-distance-plus-size structure: $3 base fee, $0.90 per mile, 5 miles, $1 size surcharge for a medium package:
Price=$3+($0.90×5)+$1=$3+$4.50+$1=$8.50
If the driver keeps 80% of the trip fee as payout:
Driver payout=$8.50×0.80=$6.80
Platform gross take=$8.50−$6.80=$1.70
Subtract an estimated $0.50 per-delivery cost for insurance and claims handling:
Net contribution per delivery=$1.70−$0.50=$1.20
Now size the volume needed to clear a fixed insurance and compliance program cost, say $50,000 per month for underwriting, claims administration, and licensing:
Breakeven deliveries per month=$1.20$50,000≈41,667
≈1,389 deliveries per day
That's the real go/no-go number: not "is $1.20 per delivery positive" (it is), but "can this city or region plausibly generate about 1,400 deliveries a day" during the pilot. If the answer is clearly no for the pilot markets under consideration, the fixed regulatory and insurance cost is what kills the idea, not the per-delivery unit economics.
Trade-offs & pitfalls
- Pitfall: validating only the per-delivery margin. A positive $1.20 contribution margin means nothing if volume can't clear the fixed insurance and compliance overhead; both numbers have to be checked together.
- Pitfall: assuming existing driver insurance extends automatically. This is the single most common wrong assumption in adapting a rideshare fleet to goods delivery, and confirming it (not assuming it) has to happen before writing any product code.
- Trade-off: tight MVP scope limits addressable package types, which caps early revenue, but a broader scope (larger packages, multi-stop routes) multiplies the insurance and liability complexity before the core model is even proven; the narrow MVP is a deliberate sequencing choice, not a permanent limitation.
- Common wrong turn: pricing the product to match a specialized courier competitor's rates without checking whether that price covers this specific cost structure (existing driver payout expectations plus new insurance overhead), which are different from a courier-only competitor's cost base.