Janky MVP

Janky MVP is a rough minimum viable product that deliberately tests the important assumption while leaving most of the eventual product unbuilt. In Tony Xu on Building DoorDash from a Class Project into a Global Marketplace, PaloAltoDelivery is the source’s example: eight PDF menus, a Google Voice number, founders answering calls, founder pickups, and a Square reader at the door.

The point was not to simulate the final DoorDash experience. The point was to test one question: whether consumers wanted delivery from restaurants that had never offered it. The first order and repeat Stanford-area usage became early Customer Pull before the company had marketplace software.

Key Claims

• A rough MVP is useful when it isolates a demand question that would otherwise be hidden beneath engineering, branding, or operational complexity.
• Manual fulfillment can be acceptable in a first test if the founder is clear about what is being learned.
• Payment friction, phone calls, and founder labor do not invalidate a test when customers still complete the behavior.
• A janky MVP is not a license to ignore operations; the manual work should reveal what the later system must automate or redesign.
• The pattern complements Fast Product Validation and Validated Learning because it turns a vague idea into observable customer behavior.

Connections

• PaloAltoDelivery, DoorDash, and Tony Xu - source case.
• Customer Discovery By Doing Work - field discovery that preceded the MVP.
• Three-Sided Marketplace Validation - broader marketplace validation that followed.
• Customer Pull, Product Led Willingness To Pay, Fast Product Validation, and Validated Learning - adjacent validation concepts.