MERITALL FAMOUS IDEAS

Famous ideas — DoorDash — as pitched in 2013

59/100

Weak Fit

Something is there. Key dimensions hold it back.


THE DAY-ONE PITCH — WHAT THE INSTRUMENT WAS GIVEN

Palo Alto Delivery — we deliver from restaurants that don't deliver

Most small restaurants can't afford their own drivers, so they lose every customer who won't come in. We put a one-page website online with menus from local spots; when an order comes in, one of us drives to the restaurant, buys the food, and delivers it for a $6 fee. We are four students doing all the driving ourselves in our own cars. If demand is real, we'll build dispatch software and recruit drivers. The menus on our site are PDFs we found online — the restaurants don't know about us yet.

Traction at grading: Landing page live. We did our first real deliveries this week — actual orders from strangers who found the site.

CategoryMarketplace
AudienceBusy people in Palo Alto who want restaurant food without leaving the house
BudgetUnder $500
TimelineDays
Hours15–30
Build statusEarly prototype
SkillsCoding, and all four of us have cars

Graded from these facts only. No hindsight — the instrument knew nothing after 2013.

MDEMANDMONEYSPEEDSKILLLAUNCHSCALEUNIQUE

THE FULL REPORT — ALL SEVEN DIMENSIONS

Market Demand

7/10

You have actual strangers placing orders through your landing page this week — that is real demand signal, not speculation. The gap you're filling (restaurants that don't deliver) is a proven category that DoorDash and Uber Eats built billion-dollar businesses around, though you've found a local niche within it.

Money Potential

4/10

A $6 flat fee per delivery is likely below your true cost once you factor in gas, car wear, and your time — at 15–30 hours per week across four founders, you're already constraining volume, and margin-per-order is thin even for a mature delivery operation. Your revenue ceiling at this fee structure and founder-driver model is low hundreds of dollars per week before you build dispatch software and recruit drivers, which is the actual business.

Speed to First Sale

9/10

You've already made real deliveries from real strangers this week — the first sale has happened. This dimension is functionally answered.

Skill Fit

6/10

Coding plus four cars plus the hustle to stand up a site and do live deliveries in days is a real advantage at the scrappy stage you're in. The coding skill becomes the unfair advantage if and when you build dispatch software, but right now you're operating as gig drivers, and nothing about your stated background gives you a structural edge over DoorDash at scale.

Ease of Launch

8/10

A landing page is live and orders are flowing — you are already launched, and you did it under $500 with PDF menus and your own cars. The main friction ahead is not launch complexity but operational and legal exposure as you scale.

ScalabilityWEAKEST

3/10

Right now your delivery capacity is literally capped by how many hours four students have to drive, and your cost scales linearly with every order — this is the definition of an unscalable model. You know this and say you'll build dispatch software and recruit drivers, but until that infrastructure exists, growth means you burn out faster, not that revenue compounds.

Uniqueness

4/10

The 'restaurants that don't deliver' angle is real and the local focus is smart, but DoorDash, Uber Eats, and Grubhub all operate in Palo Alto and have done exactly this business model at scale — you are not differentiated in concept, only in current execution speed and local hustle. If you begin signing restaurant partnerships with a revenue share, that would change this score.

THE SUMMARY

You have something rare: a real idea with real early traction, bootstrapped to live deliveries in days on under $500. The core problem is that your business model is a manual service operation, not a marketplace — every dollar of revenue right now requires a founder in a car, and your $6 fee likely doesn't cover true costs at any serious volume. The single change that would most raise this grade is signing even one restaurant as a formal partner with a revenue-share arrangement, which transforms you from a legal gray-area courier into an actual two-sided marketplace with defensible economics.

WHAT'S WORKING

  • Real orders from strangers within days of launch — this is the most credible early signal a submission can show, and most ideas evaluated here can't say it.
  • The four-founder, all-cars setup means you can test demand, learn order patterns, and identify which restaurants drive repeat orders before writing a line of dispatch code — cheap market research disguised as operations.
  • Your coding skill means the dispatch and driver-recruitment infrastructure is something you can build yourselves rather than pay for, which is the actual lever that turns this into a scalable business.

THE RISKS

  • You are buying food at retail price and reselling it without restaurant knowledge or consent — if a restaurant objects, sends a cease-and-desist, or a customer has a food safety issue, you have no contractual protection and real liability exposure. This is not a hypothetical; it has happened to copycat delivery startups.
  • Your $6 fee almost certainly doesn't cover gas, car depreciation, and your time at even minimum wage once average delivery distance and wait time are factored in — you may be growing a business that loses money on every order and you won't know until you do the math with real data from this week's deliveries.
  • DoorDash and Uber Eats are already in Palo Alto and can undercut your fee, poach your restaurant relationships once restaurants know you exist, or simply offer the same restaurants you're serving — you have no moat beyond local speed of action right now.

THE NEXT STEP MERIT GAVE THEM

Pull your delivery data from this week — every order, the restaurant, the distance driven, time spent, and gas used — and calculate your true cost per delivery. You need to know whether $6 covers your costs before you take one more order, because if it doesn't, growth is making the problem worse.

What happened next: they fixed the capacity ceiling the grade called out — four students in four cars became a marketplace of drivers — and grew into the largest food-delivery platform in the US.

THE DEEP DIVE — THE $29 REPORT, PUBLISHED IN FULL

This is the actual paid product: we took the 2013 DoorDashpitch and resubmitted it today. The research maps the market a founder walking in with this idea right now would face — because that's what every Deep Dive does: fresh research, at purchase, on your exact submission.

THE EXPANDED READ

Your idea is not merely similar to DoorDash — it is DoorDash's literal origin story. <cite index="24-6">DoorDash was founded in a Stanford dorm room in 2013</cite> as PaloAltoDelivery.com: students in their own cars, PDF menus, a $6 flat fee. That is both validation and warning — the model works, but the company that ran your exact playbook now operates in your city with a national driver network, and it got sued for the same unauthorized-menu tactic you are using right now. The research also shows your $6 fee is priced below what even at-scale operators charge for the courier leg alone — <cite index="32-13">Uber Direct starts at $7.99 per delivery</cite> — so you are subsidizing every order with founder labor. Your one real opening is the restaurant side: independents deeply resent the <cite index="2-4">15% to 30% commission DoorDash charges depending on plan</cite>, and a signed, cheaper, local alternative is a wedge the free report gestured at but could not price.

THE TEARDOWN — WEAKEST DIMENSIONS

Scalability

3/10 — can reach 6/10

Every order requires a founder in a car, so revenue is capped by four students' 15–30 combined hours, and your costs scale one-to-one with orders. The dispatch software you say you'll build is the actual product, and right now you have zero of it — you are running the operations phase of DoorDash's 2013 playbook without the data instrumentation that made their software good. Worse, on-demand one-order-one-trip delivery is the least efficient possible routing; batching is the only scalability lever available to you this week.

  • 01Instrument every order starting today: a shared Google Sheet with timestamp, restaurant, order value, miles driven, minutes from order to drop-off, and wait time at the counter. This costs nothing and becomes the spec for your dispatch software — you cannot write good routing code without knowing your real order-to-drop-off distribution.
  • 02Switch from on-demand to two delivery windows (11:30–1:00 and 5:30–8:00) posted on the site, and batch 2–3 orders per trip within a hard radius (Palo Alto zip codes 94301–94306). Deliveries-per-driver-hour is the only number that makes this model scale, and batching is how you double it without hiring anyone.
  • 03Build dispatch v1 as a Twilio SMS flow plus a simple assignment script — order comes in, nearest free founder gets a text, replies to claim it. Roughly $20–30/month, well inside your budget, and it converts your coding skill from a stated asset into shipped infrastructure.
  • 04Recruit one non-founder driver from the Stanford student jobs board or the Stanford Marketplace Facebook group for weekend dinner windows, paid per delivery. The first order fulfilled by someone who isn't a founder is the first evidence this scales at all.

Money Potential

4/10 — can reach 7/10

Your $6 fee is below market even for operators with none of your cost disadvantages: <cite index="32-13">Uber Direct — Uber's white-label courier product — starts at $7.99 per delivery</cite>, and <cite index="10-2">ChowNow charges restaurants a flat $7.98 per order for third-party delivery through DoorDash or Uber, up to 8 miles</cite>. If networks with thousands of drivers price the courier leg at $8, four students in their own cars cannot profitably do it for $6. You are also capturing only the consumer side of a two-sided market — <cite index="3-1,3-2">DoorDash charges restaurants a commission on each order of 15% for Basic, 25% for Plus, and 30% for Premier</cite>, and you charge restaurants nothing.

  • 01Do the math the free report assigned, this week: from your delivery log, compute true cost per delivery using $0.70/mile plus wait time. If it exceeds $6 — it almost certainly does — you are paying customers to order.
  • 02Raise the fee to $8 with a $20 order minimum and watch conversion for one week. The market has already validated $8 (Uber Direct, ChowNow Flex); if your orders survive the increase, you just raised revenue 33% with zero work.
  • 03Open the restaurant revenue side: pitch a flat 10% commission to restaurants you already deliver from, explicitly framed against <cite index="2-4">DoorDash's 15% Basic, 25% Plus, and 30% Premier rates</cite>. A 10% take on a $40 order is $4 of margin you currently hand to no one.
  • 04Kill on-demand singles: only accept orders that can batch into a window run. Two orders per trip halves your per-order drive cost immediately.

Uniqueness

4/10 — can reach 6/10

There is nothing conceptually novel here — DoorDash ran this exact play from this exact city, and it now serves Palo Alto alongside Uber Eats and Grubhub. Your one uniqueness lever is the restaurant relationship, and your current setup actively burns it: delivering from restaurants that don't know you exist is the precise behavior that got DoorDash sued — <cite index="21-2,21-3">In-N-Out sued DoorDash for delivering the chain's burgers without permission, filing trademark infringement and unfair competition charges</cite>, arguing <cite index="21-5,21-6">that unauthorized delivery vehicles didn't comply with food code requirements and that the chain had no control over delivery times or food temperatures</cite>. DoorDash survived that on venture money; you cannot. The genuine opening is that restaurant resentment of platforms is real and documented — <cite index="43-8,43-10">one restaurant-co-op founder describes platform-restaurant relationships as bad, estimating most restaurants hate them and would love an alternative</cite>.

  • 01This week, walk into the restaurants whose PDF menus you posted and convert them from unwitting suppliers into partners: offer a free pilot week of delivery in exchange for written permission to list their menu. Ten minutes per owner, zero dollars, and it retires your single largest legal risk.
  • 02Sign a one-page agreement with at least one restaurant: 10% commission, their menu at their real prices, their name on your site with consent. This is the exact change your Merit report said would move this score — a signed partner makes you a marketplace instead of a gray-market courier.
  • 03Target restaurants that are deliberately NOT on the big apps — cash-heavy family spots, places that tried and quit over fees. They are the segment platforms structurally cannot serve at 15–30%, and each one you sign is a listing DoorDash does not have.
  • 04Rename the value proposition on your landing page from 'we deliver' to 'the delivery service your restaurant keeps more money from' — the differentiator is the restaurant deal, not the driving.

THE 4-WEEK PLAN

WEEK 1

Unit economics and legal cleanup — know your real cost, stop the unauthorized listings

  • Build the delivery log from this week's orders: restaurant, order value, miles, minutes, wait time. Compute cost per delivery at $0.70/mile plus time. This is free and it is the number every other decision depends on.
  • Visit every restaurant currently listed on your site. Ask for written permission to keep the menu up, offer a free pilot week of deliveries. Remove any menu where the owner says no or you can't reach them — the In-N-Out v. DoorDash precedent is exactly this fact pattern.
  • Raise the consumer fee to $8 with a $20 minimum and record conversion daily. Uber Direct and ChowNow Flex both price the courier leg near $8, so you have market cover.

WEEK 2

Sign the first restaurant partner and open restaurant-side revenue

  • Pitch 5 restaurants that don't deliver and aren't on DoorDash a one-page deal: 10% flat commission versus <cite index="2-4">the 15% Basic / 25% Plus / 30% Premier DoorDash charges</cite>. Bring your Week 1 delivery data as proof of demand.
  • Sign at least one. Put 'Official delivery partner of [name]' on the landing page the same day.
  • Switch the site to two batched delivery windows (lunch and dinner) and stop accepting on-demand singles.

WEEK 3

Dispatch v1 and the first non-founder delivery

  • Build the Twilio SMS dispatch flow (order in → nearest free driver texted → reply to claim). Budget ~$30. Use the Week 1–2 log data to set radius and batching rules.
  • Post a per-delivery driver gig on the Stanford student jobs board and Stanford Marketplace group; hire one driver for weekend dinner windows.
  • Track deliveries-per-driver-hour before and after batching — this is the scalability number for your re-grade.

WEEK 4

Re-run the economics with real partner data and decide

  • Recompute cost per delivery and revenue per order with the $8 fee, 10% commission, and batching in place. You need contribution margin per order to be positive before any talk of growth.
  • Ask your signed partner(s) for a testimonial and their view on what they'd pay monthly — this tests whether a ChowNow-style flat fee (their plans start around $229/month) is a better second revenue line than commission.
  • Write the one-page summary: partners signed, margin per order, deliveries per driver hour, first non-founder delivery. That document is your re-grade submission.

THE COMPETITOR READ

The field has three layers, and all of them are established. The marketplaces — DoorDash, Uber Eats, Grubhub — all serve Palo Alto and monetize the restaurant side hard: <cite index="4-1,4-21,4-23,4-24">DoorDash charges restaurants 15–30% per order depending on plan, Uber Eats charges 15–30%, and Grubhub charges 15–25% plus marketing fees that can push effective costs above 30%</cite>. A second layer of commission-free SaaS exists precisely because restaurants resent that take rate: <cite index="13-2">ChowNow plans start at $229 per month plus 2.95% + $0.29 per transaction</cite>, and <cite index="18-1,18-2,18-3">Owner.com charges a flat $499/month with 0% restaurant fee, aimed at restaurants doing $5k+/month in online orders</cite>. A third layer — local and co-op delivery services — proves restaurant appetite for alternatives; <cite index="43-2">the founder of one Iowa City restaurant co-op reports an inbox flooded with independent owners wanting to start local franchise co-ops without any marketing spend</cite>. Your idea sits in that third layer, but currently without the restaurant consent that makes the layer defensible.

DoorDash15–30% commission per delivery order

Proves the model at billion-dollar scale — it started as your exact business in your exact city — and it operates in Palo Alto today. Its weakness is the restaurant relationship: <cite index="4-15">its tiering creates a pay-to-play dynamic where restaurants pay more commission to be seen or pay less and disappear from search</cite>.

Uber Eats20–30% marketplace commission; Uber Direct from $7.99/delivery

Second incumbent in your market; its Uber Direct product sets the real market price for the courier leg you're doing for $6. <cite index="32-13">Uber Direct starts at $7.99 per delivery</cite> — evidence your fee is underwater, and a ceiling you can price just beneath.

Grubhub15–25% commission plus marketing fees

Third incumbent; demonstrates how consolidation squeezes restaurants — <cite index="43-7">after Grubhub acquired local platform OrderUp in 2017, it doubled the 15% commission restaurants had been paying</cite>. That history is your best sales slide when pitching restaurant owners.

ChowNowFrom $229/mo + 2.95% + $0.29/transaction; Flex Delivery $7.98/order

Proves restaurants will pay a flat monthly fee to escape commissions — the restaurant-side pain is monetizable. It handles ordering but outsources the driving, which is the one thing you actually have.

Owner.com$499/mo flat, 0% restaurant fee

Shows the top end of what commission-averse restaurants will pay for a direct channel. Its price point filters out exactly the small, low-volume spots you deliver from — leaving those to you.

LoCo (restaurant delivery co-ops)

Restaurant-owned local delivery co-ops that exist because <cite index="43-8,43-10">platform-restaurant relationships are bad and most restaurants would love an alternative</cite>. Proves your local-partnership wedge has demand; no presence in Palo Alto found, which leaves the ground open.

THE WEDGE

You cannot win on delivery logistics — DoorDash and Uber Eats own that in Palo Alto. You can win on the restaurant deal: a signed, flat 10% commission with independents who currently face <cite index="4-1,4-20">15–30% at DoorDash, where most multi-unit brands pay 25–30%</cite>, delivered by people the owner knows by name. Your four cars and 15–30 hours are enough to serve a handful of partnered restaurants in a 3-mile radius during batched windows, and your coding skill makes the ordering-plus-dispatch layer buildable inside your $500 budget. The wedge only exists once the menus on your site are there with permission — until then you are a liability, not an alternative.

THE SCORE PATH

Three things move your number on a re-grade, and all are evidence, not effort. First, one signed restaurant partnership with a revenue share — the single change your report named — moves uniqueness from 4 toward 6 and opens the restaurant-side revenue that moves moneyPotential from 4. Second, the completed cost-per-delivery math plus a repriced $8 fee with survival data moves moneyPotential further, because it converts 'likely below cost' into a known, fixed margin. Third, a working SMS dispatch flow and one delivery completed by a paid non-founder driver moves scalability from 3 toward 6, because it is the first proof that revenue can exist without a founder in the driver's seat.

Your idea gets this same teardown.

START WITH THE FREE GRADE

The $29 Deep Dive is offered after your score.

Next: OnlyFans43/100GRADE MY IDEA