Before You Build
Mobile AppShut Down

Dazo

Dazo tried to simplify food ordering with curated meals, but shut down within about a year as funding, competition, and city-level delivery economics caught up.

View original story

Product snapshot

What it was

Dazo let mobile users order from a curated set of meals and restaurant partners while coordinating delivery logistics.

Who it was for

Bengaluru food-delivery customersoffice meal buyershome meal buyersmobile-first urban consumers

Problem / value

Make food ordering faster and less overwhelming than browsing many restaurant menus.

Core workflow

A user opened the app, picked from a curated set of meal options, placed an order, and received delivery through Dazo’s partner and logistics setup.

Core dependency

The model needed enough local demand, restaurant supply, delivery reliability, and capital to compete in Indian food tech.

Product form

mobile food-ordering appcurated meal marketplaceselected restaurant partner networkdelivery coordination

Pricing model

Food-ordering and delivery model; public sources do not disclose commission rates, delivery fees, subsidies, average order value, or margins.

Competitors or alternatives

SwiggyZomatoFoodpandaother Indian food-tech startupsrestaurant delivery alternatives

What happened

Summary

Dazo shut down after trying to scale a curated food-ordering app in a competitive, capital-hungry food-tech market.

Outcome

Shut down.

Core risk

Curation can improve product experience, but local delivery marketplaces still need capital, density, and a defensible acquisition channel.

Shutdown reason

Business Standard reported lack of funding and quoted the CEO saying Dazo was short on capital while scaling and lagged behind other players.

Demand signal

Dazo targeted a real consumer need, but public sources do not show enough repeat demand or margin resilience to support expansion in a competitive food-delivery market.

Distribution issue

Dazo had to acquire diners, retain restaurant partners, coordinate delivery, and compete with better-funded food-tech players. Curation lowered browsing friction, but it did not automatically create defensible distribution.

Timeline

  • 2014: TapCibo/Dazo began operations, according to TechCircle context.
  • April 2015: Business Standard reported Dazo raised angel funding from notable Indian startup operators and executives.
  • October 2015: Dazo wound up operations and stopped taking new orders.

Before you build

Why it matters

Local delivery products must win demand, supply, logistics, and repeat behavior in a specific geography. If the category is subsidy-heavy, a small team needs a clear cost or distribution edge before scaling.

Primary check

A curated marketplace still needs dense demand, repeat orders, and a cost advantage. Prove one city or neighborhood can work before scaling a logistics-heavy app.

Checklist

  • Run a single-zone pilot and measure repeat orders by cohort.
  • Track contribution after delivery, support, refunds, discounts, and partner operations.
  • Compare conversion from curated choice against a broader marketplace experience.
  • Can one neighborhood produce repeat orders without discounts?
  • Do restaurant partners stay reliable without heavy operational support?
  • What is your cost advantage over larger food-delivery apps?
  • How many orders per day does one delivery zone need?
  • Can the business survive without another funding round?

Relevant if

  • You are building a local marketplace, delivery app, restaurant tool, or curated commerce product.
  • Your product depends on both consumer demand and partner supply.
  • You need capital to expand before one geography is profitable.

Less relevant if

  • Your product is pure software without local fulfillment.
  • Your supply is proprietary and not available to better-funded competitors.
  • You already have profitable repeat demand in one narrow geography.

Pre-build tests

  • Pre-sell to one office or apartment cluster before city expansion.
  • Operate manually for one meal window to measure real delivery cost.
  • Stop discounts for a cohort and test whether repeat ordering survives.

Transferable lessons

  • Validate one dense local market before adding cities.
  • Measure repeat orders without discounts.
  • Curation must improve conversion or retention enough to beat broader marketplaces.

If you build this today

Start with one narrow meal occasion and one geography. Measure repeat orders, restaurant reliability, delivery cost, and unsubsidized margins before adding more partners, areas, or categories.