Skipping food delivery for 30 days saves less than the order total suggests, because you still have to eat. In this worked example, 12 orders at ₹350 come to ₹4,200. Subtract ₹1,500 of extra groceries and cooking gas, and the real saving is ₹2,700. All numbers are hypothetical; yours will differ, and finding them is the first step.
How do you find your own baseline?
Look at the last full month of bank, card or UPI history and pick out every delivery app and restaurant payment. Count the orders and add up the amounts. Do not use memory; it undercounts.
- Open last month's statement and mark each delivery or restaurant payment.
- Count the orders (say 12).
- Add the amounts (say ₹4,200 in total, which is ₹350 an order on average).
- Note the days of the week. Most people find the orders cluster on two or three recurring evenings.
- Write the baseline on a card or in your notes before the challenge begins.
What is the net saving, line by line?
| Line | Amount | Working |
|---|---|---|
| Baseline delivery spend | ₹4,200 | 12 orders x ₹350 |
| Extra groceries for home cooking | ₹1,000 | Hypothetical |
| Extra cooking gas | ₹500 | Hypothetical |
| Extra cost of cooking at home | ₹1,500 | ₹1,000 + ₹500 |
| Net saving for the month | ₹2,700 | ₹4,200 - ₹1,500 |
The delivery total already includes fees, platform charges and tips, so the comparison is fair as long as you use what actually left your account. The extra grocery line should only be the additional food you buy because you are cooking more, not your usual shopping.
What are the rules of the challenge?
- No orders through any delivery app, including grocery and snack apps, unless the item is a household essential you cannot get locally.
- Eating at a restaurant is allowed but gets logged. Decide a limit, say two visits.
- Takeaway you collect yourself counts as a restaurant visit, not delivery.
- Ordering for a sick family member or a guest is an exception, written down with the reason.
What do you do when the craving hits?
Most failed attempts break on the same few evenings, so plan those. Keep two fast meals ready: for instance khichdi ingredients, or a pack of dosa batter. Cook double on days you are not tired, and freeze the extra portion. Put your usual delivery evenings on the calendar and write the plan for that meal next to them.
If you do break the rule, log the order, add it to the tally and carry on. One extra ₹350 order lowers the saving by up to ₹350, and a little less, since you skipped cooking that meal. You are still well ahead. Do not abandon day 12 because day 11 went wrong.
Is the saving worth repeating every month?
Only you can say, and only after the numbers. A saving of ₹2,700 a month is ₹32,400 across twelve months if nothing else changes, which is a simple multiplication and not a forecast. Some people decide to keep two delivery nights a month and bank the rest. Others find the cooking time costs them more than the money saved. Both are reasonable conclusions.
How can an expense tracker help here?
Your baseline is hidden in your statements. SpendixAI lets you upload a bank or card statement as PDF, CSV or Excel, review the rows, and group the delivery merchants under one category, so last month's order count and total are a filter away. After the challenge, import the new statement and compare the two months. It does not connect to your bank, so you upload each statement yourself.
- Baseline recorded: number of orders, total, average per order.
- Rules written: what counts, what is an exception.
- Two backup meals planned for the usual delivery evenings.
- Day 30 comparison: new delivery total, new grocery total, net saving.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

