Why I Renamed My Budget Categories to Feelings — and Stopped Spending with Shame
I swapped neutral budget labels for emotional ones (Security, Freedom, Fun). A practical, messy habit that stopped impulse shame and made my ₹30k salary actually feel usable.
Written by: Devika Iyer
It was 8pm on a Sunday, I was standing in a tiny bakery in Koramangala, and I had just spent ₹420 on a pastry I didn’t really want. The pastry tasted fine. The feeling afterward didn’t. I felt both guilty and a little thrilled — like I’d broken some rule I’d promised myself I wouldn’t break.
That feeling — the shame-after-spend — had been recurring for months. I had spreadsheets, an envelope system, and two SIPs. None of it actually stopped the small, irrational buys that piled up into a ₹3,000 “why-did-I-do-that” tab each month. My finance tools were clinical. My behaviour was messy. Labels like “Groceries” and “Discretionary” were not helping.
So I tried something weird: I renamed my budget buckets after feelings.
Why labels matter more than math Numbers are easy to rationalise. Feelings are not. When I opened my expense tracker I wasn’t seeing “Food — ₹420”, I was seeing “Fun — ₹420” if I renamed it. That tiny semantic shift changed my internal dialogue.
I set up three real buckets that map to real accounts/cards I already had:
- Security (₹30,000 target): emergency buffer + fixed bills. This lives in my primary savings (SBI), because I want penetration of bank features and easy NEFT for emergencies.
- Autopilot (₹12,000 monthly): rent, utilities, SIPs, recurring UPI mandates. This is a second savings account I treat as untouchable.
- Fun (variable, ₹3,000–₹6,000): weekend eats, clothes, random buys. I put this on a prepaid card and one pocket-wallet.
Concretely: with a take-home of ~₹63,000 a month, I transfer ₹30k to Security (sweep-in), ₹12k to Autopilot via standing instruction, and the rest stays in my salary account for day-to-day. Every Friday I top up the prepaid card for Fun with whatever remains after groceries and transport. I see “Fun” not “Groceries” when I reach for the card.
What actually changed
-
Permission to spend Before: every small spend felt like a breach. Now: spending from Fun is explicitly permitted. The pastry wasn’t a failure; it was a Fun transaction within the cap. That removed the post-spend shame loop that drove me to impulsively “compensate” by skipping dinner and then binge-buying the next week.
-
Easier trade-offs If I wanted to splurge on a ₹1,800 dinner, I could — but it would cost two weeks of Fun. Seeing “Fun balance: ₹1,200” on my phone made that trade-off feel real, fast. No spreadsheet math needed.
-
Habit-friendly nudges I automated Autopilot for rent and SIPs. Security is auto-deposited twice a month. Fun is the only manual top-up. This mix of automation + a human-facing emotional label forces me to think only about what I want to feel, not which GL code a transaction fits into.
The tools I used
- My bank’s standing instruction for Autopilot and Security
- A ₹500 prepaid card (SBI/Axis) I top up with UPI for Fun — works offline and prevents accidental overspend on my main cards
- A simple Notion page that shows three balances and rules — no complex formulas
- A weekly 10‑minute check on Sunday nights: update Fun top-up, move leftover to Security if untouched
The honest failure and the tradeoff This broke when two things happened at once: a family wedding and a delayed salary. Weddings are emotional, not rational. I blew past Fun into my Autopilot account and then into Security. The neat separation collapsed in a week. Worse, after the wedding I felt awkward telling my parents “no” — emotional buckets and family obligations collided.
The other tradeoff is precision. I stopped granular categorisation. “Transport” and “Groceries” now are often lumped into Autopilot or Fun depending on context. That cost me detailed insights; I can’t say with confidence how much I spent on groceries versus eating out. For someone who likes line-item control, this will feel sloppier.
Why it still worked despite the failure When salary arrived late, I had a mental priority map — Security first, Autopilot second, Fun last. I delayed the Fun top-up for a fortnight and communicated clearly with my parents about reimbursements. The emotional labels made those conversations simpler: “I can’t move Security, it’s the emergency buffer.” I wasn’t negotiating numbers; I was protecting a feeling that matters: safety.
When the wedding blew the Fun cap, I did one practical thing: I set a temporary “Wedding Fund” inside Fun and made a rule: no more than two expenses above ₹2,000 without moving money from Security (only with a plan). Rules reduce regret.
What I’d tell a friend trying this
- Use real accounts/cards. Don’t just rename spreadsheet columns. Move money. Feeling the absence of funds is what changes behaviour.
- Start small: one “feeling” bucket (Fun) and your regular bills. See if permission to spend reduces shame.
- Keep one automated safety layer (Security). If you break Fun, repair Security first.
- Be honest about social costs. Emotional buckets help personal spends, not family obligations. Set a separate “Family” process if needed.
One takeaway I actually kept The lesson wasn’t that emotions should run my budget. It was that money behaviours respond faster to language than to logic. Renaming my buckets from neutral accounting terms to feelings gave me permission where spreadsheets didn’t — and that permission stopped the small, stupid spends that used to add up into real problems.
I still lose my cool sometimes. I still overpay for a pastry. But now I either let it come out of Fun with a smile, or I decide it’s not worth it before I reach into my pocket. That tiny pause — a semantic checkpoint — saved me more than a dozen budget lines ever did.