We build no-commission ordering websites for Indian restaurants — single-outlet to multi-outlet chains. WhatsApp-first menu, UPI checkout, kitchen-display, owner dashboard. You own the customer list and the code.
If aggregator commission is now bigger than your rent, a direct-ordering website pays for itself in 2-4 months. Big Helpers builds restaurant ordering sites with WhatsApp menu links, UPI checkout, kitchen-display, and a one-screen owner dashboard — for ₹60,000 to ₹3.5 lakh, live in 3-6 weeks. No per-order commission, ever.
On a ₹500 order you keep ₹350-390 before food cost. On a ₹150 quick-service order you barely break even. Commission has overtaken rent in many outlets.
You can't message your own regular about a new dish, a Holi special, or a private-event slot. The customer is on Swiggy's CRM, not yours.
Counter staff juggling walk-ins and calls means wrong items, wrong addresses, and ~5-7% remake rate. Each remake is a hit on margin and on the review score.
You end up paying Petpooja for billing, an aggregator for delivery, a separate WhatsApp tool for marketing, and still missing a clean direct-order flow.
Tier-2 and tier-3 customers won't download a third app for one restaurant. App-first builds quietly die in the App Store.
You don't know which outlet's prep time is dragging, which menu items dropped 30% week-on-week, or which day's revenue came from regulars vs aggregators.
You have 800+ customers in WhatsApp groups, broadcast lists, or your phone contacts. They keep asking how to order direct.
Aggregator commission is now ₹2-6 lakh per month across outlets and growing. Owner needs one dashboard, not three.
You need brand-wise menus, brand-wise routing, and brand-wise P&L on one ordering stack.
High-frequency, low-AOV orders where 25% commission destroys the unit economics. WhatsApp ordering fits your customer behaviour perfectly.
You take ₹8-50K orders by phone with photos and notes flying around. A direct site with quote builder cleans this up.
You want a customer-facing layer that talks to your existing POS and KOT printer, not a parallel system.
Tell us your outlet count and rough monthly aggregator spend. We'll sketch what a direct-ordering channel would look like for you, and what it would cost. No sales pressure.
Single-page menu per outlet, no app, no signup. Customer taps WhatsApp link, builds cart, picks slot, pays UPI. Designed for 3G and old Android.
Send your opted-in regulars an outlet-specific menu link 1-2 times a week. Sunday brunch, Friday biryani, festival specials — straight from your dashboard.
UPI handles ~75% of payments in India. Card backup for higher AOV. Cash-on-delivery with QR confirm at door for the rest.
₹6-8K Android tablet on the kitchen wall shows incoming orders with prep timer + auto-print to your existing thermal printer. No staring at a phone screen.
Live orders, prep time, rider status, day-end revenue, top items, commission saved. One screen. Works on phone.
Item runs out? Mark it 86 from the kitchen tablet — it greys out instantly on the customer site. No more refunds for unavailable items.
Plug in your existing 2-3 riders for the bulk; auto-fall-back to Dunzo or Porter for surge times. You stay in control of the customer experience.
Orders flow into your existing POS as if they came from any other channel. KOT prints, billing, GST report — all unchanged.
Auto-WhatsApp customers idle for 30+ days with a small offer. Tag VIPs (top 10% by spend) for early festival access.
Explicit opt-in at checkout, easy unsubscribe link in every broadcast, documented retention policy. Built right from day one.
We sit with you, the head chef, and the counter manager. Understand peak-hour flow, KOT printer, current Petpooja/Restroworks setup, and the regulars list. Lock outlet count, brand count, and integration scope.
We turn your existing menu PDF into a structured digital menu (categories, modifiers, half/full, jain/non-jain). Click-through wireframe of the customer flow + KDS + dashboard. You sign off before we code.
You see a working ordering site every Friday. Real menu, fake payments. Course-correct early. Tech: Laravel/Next.js + PostgreSQL + WhatsApp Business API + Razorpay.
Soft-launch with 200-300 regulars. Kitchen team gets used to the tablet during off-peak. We ride along, fix friction in real time.
All outlets go live. We send the first broadcast to your opted-in regulars on a quiet weekday. Watch orders, watch prep time, adjust.
Direct WhatsApp line to the engineer who built it. Free fixes for any bug from day-1 scope. Weekly performance call for the first month.
Indicative range: ₹60,000 — ₹350,000 (excl. GST). Final estimate after a free 30-min scoping call.
Pvt Ltd since 2008. CIN U72200MP2008PTC021190. We've built ordering, POS, KDS, and CRM stacks across food, retail, and hospitality.
Hand-over via GitHub from the first commit. No hostage-taking. Any local Laravel/Next.js developer can extend it.
Direct WhatsApp line to a senior engineer for the first 30 days, then to support. No tickets, no queues.
No surprise USD billing. Quote in INR, invoice in INR, GST 18% added. Real Pvt Ltd, not a freelancer.
We've watched enough kitchens during dinner rush to know what fails. Auto-print, large-touch buttons, no signup screens — non-negotiable defaults.
Aggregators are useful for customer discovery. We won't tell you to kill them — we help you convert their customers into your direct channel.
Note: illustrative example — not a specific client engagement.
An example use case: a 3-outlet North Indian chain in tier-2 Maharashtra was paying ₹3.4L/month in aggregator commission across outlets. They had ~6,400 regulars on WhatsApp from 4 years of operation but only a phone number to take direct orders, with ~6% order errors. Owner had no dashboard across outlets.
We built a direct-ordering site in 5 weeks: single-page menu per outlet, WhatsApp broadcast to opted-in regulars every 3-4 days, Razorpay UPI checkout, kitchen tablet with auto-print, in-house riders with Dunzo overflow, and a single live owner dashboard. Source code in their GitHub.
Within 90 days roughly 22% of total delivery volume moved to direct, saving ₹2.4-2.8L/month in commission. Order-error rate dropped below 1%. Build cost ₹2.6L; payback inside month two. Aggregator orders weren't killed — they remained as a discovery channel, with the WhatsApp prompt converting first-time aggregator customers to direct on the second order.
No, and you shouldn't try. Aggregators bring you new customers, which is genuinely useful. The smart play is to use them for discovery and convert those new customers into direct on the second or third order via WhatsApp. Most clients see aggregator volume stay flat while direct grows on top — net result is more orders, lower blended commission.
In tier-2 and tier-3 cities, yes — strongly. They prefer messaging over apps, they trust the restaurant directly more than the aggregator, and many will tip the kitchen if the channel is direct. Tier-1 metros are more app-comfortable, but even there, the WhatsApp + web flow outperforms a native app for restaurants under 10 outlets.
Yes. Petpooja's API is solid; Restroworks needs a partner-API request which we handle. Integration adds ~1 week and ~₹40-60K to the build. Worth it if your kitchen team already lives in those systems and you don't want a parallel order screen.
Roughly ₹0.40-1.20 per outbound message in India depending on category (utility vs marketing) and provider. For a 6,000-contact list sending one message per week, that's about ₹10-15K/month — far less than the commission saved on the orders it generates. Inbound replies are free.
For 95% of Indian restaurants, the website (PWA — installable from the browser if the user wants) is enough. A native app makes sense only above 8-10 outlets with a 50K+ active customer base, or if you want loyalty/coupons that benefit from push notifications. Start with PWA, add native later if the data justifies it.
We build the opt-in checkbox into the cart with explicit, plain-English consent. Every WhatsApp broadcast carries an unsubscribe link. The retention policy is documented and visible in your privacy page. We've shipped this stack for several restaurants without a complaint.
One Android tablet per outlet (₹6-10K, even an older one works) and your existing thermal KOT printer. The tablet runs the kitchen-display in a browser; the printer connects via USB or LAN. We test it with your actual printer before go-live.
No — pricing on this page is excluding GST. As a Pvt Ltd we charge 18% GST on the invoice. The full breakdown comes with the proposal.
Talk to a senior engineer in 24 hours — no juniors, no sales reps, no jargon. Just a clear scope, an honest estimate, and a build plan.