2025.07.07.

Starting Pezeta

Finally decided to start building Pezeta today. It’s been in my mind for years – since we started Agyvihar, our Hungarian podcast about personal finance and productivity.

What’s Pezeta?

Simple: a budgeting app that tells you one number – how much you can spend right now.

That’s it.

No charts. No categories. No endless reports. Just open the app and see: $47. Or $134. Or whatever you can actually spend without screwing up your budget.

The features (keeping it minimal)

The One Number – Your daily spending limit. Updated in real-time. Factors in your bills, savings, everything.

Goals – Want to save $2000 by December? Cool. The app adjusts your daily number automatically. No spreadsheets required.

That’s basically it. If budgeting were simpler, maybe more people would actually do it.

Starting with Rails

I’m not jumping straight into building native apps. Starting with a Rails MVP instead.

Few reasons:

  • Rails 8 has some new stuff I want to try
  • Need a reference implementation anyway for the iOS/macOS versions
  • I can actually use it myself while building

This Rails version won’t go public. It’s just for me to validate the idea and work out the kinks.

Building in public (might regret this)

I’m putting it all out there because watching someone figure things out might be more useful than another perfect tutorial.

Partly for feedback – maybe someone will tell me this is a terrible idea before I waste six months on it.

Partly for accountability – harder to quit when people are watching.

Partly because I’m curious what happens when you share the messy process instead of just the polished result.

The plan

Starting with Rails 8 setup, basic models, authentication. The boring foundation stuff that nobody talks about but takes forever.

After that, we’ll see. Building software is weird.

Testing app subscriptions on the long-term

Many people don’t like app subscriptions, but it provides a way to test these apps long-term.

When I see a potential tool that I’ll likely use long-term, after the initial trial, I subscribe to its monthly plan, and I keep testing it for 2-4 months. While the initial testing phase is happening, I create a new category in my budget and save money for the yearly subscription plan. Usually, annual subscriptions are cheaper than paying every month for a year, so it makes sense to subscribe to them with an app that I will use for a long time.

When I conclude my testing and decide that I’m going to use the app, I’ll have the yearly subscription price already collected in my budget. This way, I can switch my monthly subscription to the annual plan without any problem. I also keep saving money each month for next year’s payment. I use YNAB for keeping a budget which makes this process easier with its Targets feature.

If I decide that I’m not going to use the app, I cancel my monthly subscription, and I move the money I saved for the yearly plan into a different budget category.

By using this system, although I’m going to pay more for the subscription in the first 2-4 months during the testing phase, in the long-term, I’ll save money because I’ll subscribe to apps and services that I actually use.