Pincode entry
The first screen asks for a pincode, not a login.
Design note
Coverage is the product's biggest question in a tier-4 town. Answering it before asking for anything removes the top reason people bounce.
Food Delivery Platform
Feesto
Food. Fair. Fast.
A food delivery platform for tier-4 towns in Bihar and Jharkhand — zero platform fee, zero delivery fee, and 5% restaurant commission instead of the usual 25–30%.
Visit the live sitefeesto.app
Open ↗Loading Feesto…
Role
Sole Designer
Timeline
Mar – Jun 2026
Scale
8 pages
Built with
Figma · React · Tailwind · Supabase
5%
Commission vs 25–30% market rate
₹0
Platform + delivery fee
3
Districts live at launch
The problem
Swiggy and Zomato don't serve Banka, Munger or Godda — and where they do operate, they take 25–30% from restaurants and stack platform fees, delivery fees and surge pricing onto the customer. In a tier-4 town where a full meal is ₹180, that structure simply doesn't work for anyone.
The approach
I designed the pricing model as the interface. Every screen states the fee structure in plain numbers rather than burying it at checkout — ₹0 delivery, ₹0 platform, 5% commission. Restaurants keep their own riders, so the app had to fit around workflows that already existed rather than replace them.
What shipped
A customer app, a partner app and a marketing site, all live across three districts. The order flow shows the real menu price at every step, and partner onboarding runs on a four-field form instead of a sales call.
Process
How it came together
Market constraint
Mapped what actually blocks delivery in tier-4 towns — thin order volume, no rider supply, and restaurants that cannot absorb 30% commission.
Pricing as product
Worked the fee structure alongside the wireframes rather than after them, because the number was the differentiator.
Two-sided design
Designed the customer app and partner app in parallel so order states matched on both sides from day one.
Brand & launch
Built the identity, the marketing site and the Play Store presence for the three launch districts.
Design system
Colour & type
Colour system
Ink
#111827
Primary text & dark surfaces
Feesto Orange
#F97316
Primary action, brand
Fresh Green
#047857
Zero-fee & success states
Violet
#6D28D9
Partner-side accent
Slate
#6B7280
Secondary text
Paper
#FFFFFF
Cards & app background
Typography
Display
Aa
Plus Jakarta Sans — Bold
Body
Aa
Plus Jakarta Sans — Regular / Medium
One family across app and web. Plus Jakarta Sans has a tall x-height that stays legible on the low-cost Android screens most of our users are on.
Key screens
What each screen has to do
Menu & real pricing
Menus show the restaurant's actual in-store price.
Design note
No inflated listing price to absorb commission. The price you read is the price you pay — that claim only holds if it is visible on every card.
Live order tracking
Real-time status from Preparing through to delivery.
Design note
Riders belong to the restaurant, so tracking states had to map to a kitchen's real workflow rather than a fleet dispatch system.
Partner onboarding
Four fields: restaurant, owner, phone, pincode.
Design note
Restaurant owners sign up on a phone between service rushes. Anything longer than one screen does not get completed.
Design decisions
What got cut, and why
Fee disclosure
Rejected
Show the item total upfront and reveal delivery + platform fees at checkout, like every major competitor.
Shipped
State ₹0 delivery and ₹0 platform fee on the hero, the restaurant card, and the cart — before the user commits to anything.
Why
The zero-fee model is the entire reason to choose Feesto. Hiding it until checkout would waste the one advantage the product has.
Delivery fleet
Rejected
Build a rider network and route orders through Feesto-managed delivery.
Shipped
Let restaurants use their existing delivery staff, and design the order states around that.
Why
A rider fleet is the single biggest cost in food delivery. Removing it is what makes 5% commission possible — so the design had to support it, not fight it.
Partner signup
Rejected
A full onboarding flow with documents, menu upload and bank verification before activation.
Shipped
A four-field form that starts the conversation; everything else happens after.
Why
Owners were abandoning long forms. Getting the phone number first turned a form problem into a follow-up call.
What I owned
Mobile appMarketing sitePartner appBrand system
It's live. Go use it.
Every screen described here runs in production — real routing, real data, real interactions.
Open FeestoNext up
APL Digital