Nine Months of Running a Food Delivery App in a Tier-2 Town

In March 2021 I shipped Strato Foods through Strato Inc — a food delivery app for my hometown. By December I had nine months of production data: orders, complaints, restaurant churn, rider no-shows, and revenue that was real but not venture-shaped.

This is not a growth hack post. It is what running local delivery actually feels like when you are 19, building from your room, and nobody in Bangalore is returning your emails.

What I Thought I Was Building

The pitch in my head was simple: restaurants in my town did not need a national aggregator’s commission structure or onboarding bureaucracy. They needed orders on their phones and riders who showed up.

Strato Foods was Flutter on Android, Firebase on the backend, and me playing customer support at midnight when someone’s biryani went to the wrong lane.

I was trying to make a marketplace work where the “market” was three kilometers wide and everyone already knew each other’s phone numbers.

What Actually Worked

Density. One town, a handful of restaurants that trusted me, repeat users who ordered because I fixed things personally when they broke.

Founder on WhatsApp. Terrible for scale. Excellent for retention in month two through six. People forgave bugs when a human answered in ten minutes.

Low burn. No office. No salaried ops team. Rider payments and restaurant settlements were spreadsheets I understood because I built them in pain.

Shipping cadence. Play Store updates every two weeks. Small fixes visible to merchants: “he actually listens.”

By autumn we had a rhythm. Restaurants called me before they called Swiggy’s local rep — not because we were bigger, but because we were reachable.

What Did Not Work

Pretending to be an aggregator. Swiggy and Zomato win on subsidies, brand, and rider pools I could not match from a hostel room.

Feature envy. I kept sketching “dark store” ideas and loyalty programs while basic ETA accuracy was still flaky.

Ops as an afterthought. Software was the fun part. Rider incentives, rain-day surge, restaurant payout disputes — that was the company. I underestimated it until month five.

Sleep. The 2021 year-in-review numbers do not lie. December me made worse decisions than April me.

flowchart LR
    subgraph worked [What compounded]
        A[Single-town density]
        B[Founder-led support]
        C[Low burn / fast ship]
    end

    subgraph failed [What hurt]
        D[Aggregator cosplay]
        E[Ops debt]
        F[Feature envy]
    end

    worked --> Revenue[Real but local revenue]
    failed --> Ceiling[Growth ceiling]

The Numbers I Care About (Approximate)

None of this is unicorn math. It is proof that Strato Inc could ship something strangers paid for — which mattered more to me than another pitch deck revision.

What I Was Learning in Parallel

Strato Foods was not the only thread. I was running other Android experiments under Strato Inc and poking at a transformer attention side project for document classification. The GAN synthetic data work had mostly died by summer. The lesson that stuck: ML papers and food delivery ops do not share a calendar. I could not be in lab-head mode and dispatch-head mode on the same Tuesday.

That tension would define the next few years. In 2021 it just felt like being bad at focusing.

Restaurants, Riders, and the Unsexy Truth

The product was an app. The business was phone calls.

Restaurants wanted:

• Predictable settlement cycles
• Fewer canceled orders
• Someone to yell at who could fix menus same-day

Riders wanted:

• Clear per-delivery pay
• No ambiguous “bonus maybe” language
• Respect when it rained and roads disappeared

Users wanted:

• Food hot
• Accurate ETA
• Refunds without a ticket system designed for enterprises

Every item on that list is operations. The Flutter UI was maybe 30% of whether people reordered.

Why I Kept Going

I stopped fundraising in the fall. Not because I became anti-VC — I wrote about that summer separately — but because Strato Foods was teaching me things no incubator lecture covered: local trust, settlement float, and how fast word-of-mouth travels in a town where your mother might hear about a bad delivery before you see the complaint.

That knowledge compounds. Even when the app does not scale nationally.

Takeaway

If you are a young founder building in a tier-2 city: local delivery is not a smaller Swiggy. It is a logistics and relationships business that happens to have an app attached.

Ship in one geography until the ops are boring. Treat every restaurant owner like your first investor. Log the failures in a spreadsheet, not in your memory.

Nine months in, Strato Foods was not a unicorn. It was a real company in a real town. That was enough to keep building — and enough to write the honest version down before the LinkedIn highlight reel kicks in.