DEV Community

GaniBook
GaniBook

Posted on

I Tracked Every Rupee for 30 Days — Here's What I Learned

One month. Every single transaction, written down the moment it happened. No bank sync, no automation, no excuses. The numbers told a story I wasn't expecting.

I used to think I was good with money. Not rich, not careless — just… fine. My salary came in, my bills went out, and whatever was left carried me to the next payday. Sometimes comfortably. Sometimes not.

Then one month ended with my account nearly empty a full week early, and I realised I had no idea why. I hadn't bought anything big. Nothing had gone wrong. The money had simply… gone. And I couldn't account for it.

So I ran an experiment on myself: for 30 days, I would track every single rupee. Every chai, every auto fare, every UPI payment, every rupee lent to a friend. Written down the moment it happened — not reconstructed from memory at the end of the day, but logged live.

Here's what a month of radical honesty about my own spending taught me.

The system: deliberately low-tech at first

I'm a builder at heart, so my first instinct was to automate everything — connect the bank, pull the data, build a dashboard. But that was exactly the wrong move for this experiment, and it's worth saying why.

Automation tells you what happened. It doesn't make you notice it happening.

So the system was deliberately manual, and deliberately simple:

  1. Log it the moment it happens. Not later, not "I'll remember" — right then, in the moment, before the next thing distracts you.
  2. One line per spend. Amount, what it was, and which pot it came from. Nothing more.
  3. Five pots, decided in advance. Essentials, food beyond groceries, transport, fun, and money lent to people. If a spend didn't fit a pot, the pots were wrong — and I'd fix the pots, not fudge the entry.
  4. A five-minute review every Sunday. Look at the week, look for surprises, adjust nothing yet. Just observe.

The tool I used was GaniBook — the app my father built after tracking every rupee in a notebook for years — because it does exactly this kind of manual logging well: quick entry, multiple accounts (cash, bank, cards, wallets, UPI) in one place, and visual reports that turn a list of entries into a picture. The tool mattered far less than the rule: log it now, or it didn't happen.

Week 1: the observer effect is real

The first thing I learned is that tracking changes behaviour before you change anything on purpose.

By day three, I caught myself standing at a food delivery app, about to order something I didn't really want — and I stopped. Not because of willpower, but because I could already see the entry I'd have to write: ₹350, dinner, food beyond groceries, third time this week. The spending became visible before it happened, and that visibility was enough.

This is the part most budgeting advice skips. People treat tracking as the boring admin you do before the "real" work of budgeting. But tracking is the work. The moment spending becomes visible, it starts correcting itself. I spent less in week one than in a normal week — without a single rule telling me to.

Week 2: the small spends were the story

By the end of week two, the pattern was undeniable. My essentials were fine — rent, bills, groceries all roughly where I expected. The leak was the small stuff, and it was bigger than I'd ever have guessed.

Snacks, top-ups, a coffee here, a random online order there. Individually, nothing over ₹200. Added up over two weeks: nearly ₹4,000. That's a real chunk of a month's money, gone in increments too small to notice.

This is the flaw in how most of us think about spending. We remember the big transactions and forget the small ones, so we conclude the big ones are the problem. The data said the opposite. The small spends were doing the damage precisely because they were too small to notice.

The fix wasn't to ban small spends. It was to give them a home: a fixed "fun pot" I could spend guilt-free, and once it was empty, it was empty. The pot turned an invisible leak into a visible, bounded choice.

Week 3: the money that wasn't spent

Week three surfaced the leak I least expected: money that had left my account but wasn't really spending at all.

₹500 lent to a friend for a train ticket. ₹1,000 covering a group dinner, half of which nobody paid back. ₹2,000 to a cousin "until Friday" — three Fridays ago. None of this showed up in my mental model of "what I spent this month", but all of it had left my account. When you can't remember where your money went, some of it is sitting in other people's pockets.

This is why a lending and borrowing ledger matters, and why it's one of the first things my father built into GaniBook. Real life isn't just salary minus rent. Money flows to people, and if you don't track those flows, your numbers will never add up — and you'll blame the wrong things for the gap.

I started logging every loan the same way I logged every spend: who, how much, when, and when it's due back. Two things happened. First, the mystery gap in my accounts shrank. Second, asking for money back stopped feeling awkward — I wasn't chasing a friend, I was checking a record.

Week 4: the weekly review is the whole game

By the final week, the experiment had settled into a rhythm, and the rhythm was the real discovery.

Five minutes every Sunday: open the reports, look at the week's pattern, check each pot. A monthly check is an autopsy — by the time you see the problem, the month is already spent. A weekly check is a course correction. You catch the food-delivery creep in week two, not on the 28th when there's nothing left to fix.

The visual reports did the heavy lifting here. A list of transactions tells you what happened; a chart shows you the pattern at a glance. Seeing food delivery as my second-biggest category — bigger than transport — made the fix obvious in a way a spreadsheet never had.

And the privacy mattered more than I expected. My finances are personal, and I wouldn't have kept logging if the numbers were on display every time I opened the app. Manual entry with no bank connection, plus one tap to hide every amount on screen, meant I could log a spend in a crowded metro without thinking twice. A system you won't use in real life is a system that doesn't work.

What the 30 days actually changed

Here's the honest scorecard, a month later:

  • I found the leaks. Small spends and forgotten loans — roughly ₹6,000–7,000 a month that used to vanish without a trace.
  • I stopped guessing. I know what a normal week costs me now, in each pot, because I measured it instead of estimating it.
  • I kept the habit. Thirty days of logging took about two minutes a day, and the Sunday review takes five. The system survived the experiment because it was small enough to survive a busy week.
  • I kept the fun. The fun pot didn't shrink my life — it protected it. Knowing the money is allowed makes it enjoyable instead of guilty.

The uncomfortable truth is that the app mattered less than the habit. My father tracked every rupee in a notebook for decades before he built an app, and the notebook worked — because writing it down, seeing it clearly, and deciding on purpose is the entire system. The app just made the notebook better: visual reports, EMI schedules with calendar reminders, savings goals you can actually watch grow, and a lending ledger for the money that flows between people.

If your money keeps disappearing and you can't say where it went, don't start with a budget. Start with 30 days of tracking — every rupee, logged the moment it moves. The numbers will tell you the story. You just have to be willing to read it.

Try GaniBook free at ganibook.com — the first month is free, no card required. Know your money.

Built by a father. Launched by his children.

Top comments (0)