Blogs

June 2026
5 min read

Why we built Tabby on Telegram

The decision to build a chat-first expense tracker instead of another app.

When I started building Tabby, the first question everyone asked was: "Why not just build an app?" It's a fair question. The App Store is full of expense trackers with beautiful dashboards, fancy charts, and every feature you can imagine.

But here's the thing: most people don't use them.

The real problem: Expense tracking apps fail not because they lack features, but because they add friction. You have to open the app, find the right screen, fill out a form, pick a category from a dropdown, choose a date. By the time you're done, you've spent 30 seconds on what should take 3.

Chat is the lowest-friction interface

Think about what you already do dozens of times a day: send messages. It's muscle memory. You don't think about "opening an app." You just type.

That's the insight behind Tabby. Instead of asking people to learn a new app, we meet them where they already are: in their chat. Type 12 lunch and you're done. No forms, no dropdowns, no navigation.

Why Telegram specifically?

A few reasons:

  • Bots are first-class citizens. Telegram's bot platform is powerful: inline keyboards, mini apps, webhooks, file sharing. We can build a full experience inside the chat.
  • Groups work naturally. Adding a bot to a group chat for shared expense tracking is seamless. Try doing that with a standalone app. You'd need everyone to download it, create accounts, add friends.
  • Mini Apps bridge the gap. When you do want a dashboard with charts, Telegram's Mini App platform lets us provide that, without asking you to download anything.
  • Global reach. Telegram has 900M+ users across 200+ countries. Many of our users are travelers and expats who already live in Telegram.

The trade-off

Building on Telegram means we don't control the entire experience. We can't send push notifications the way a native app can. We can't do background processing on the user's device. We're constrained by what the Telegram bot API allows.

But here's what we've learned: The constraint is actually a feature. It forces us to keep things simple. Every interaction has to work in a chat message. That discipline has made Tabby better, not worse.

The result

Our most active users log expenses multiple times a day, because it takes 3 seconds. They'd never do that with a traditional app. The best expense tracker isn't the one with the most features. It's the one you actually use.

That's why we built Tabby on Telegram. Not because it's the most powerful platform, but because it's the one that gets out of the way.

Tabby, the product behind the writing.

Tabby lives in your Telegram chat — nothing to install.

Start Using Tabby

More from Behind the Build

5 min read

How we killed the hourly cron

The scheduler wasn't a performance problem. It was a product constraint.

Read →

4 min read

Why we keep the core free

Our philosophy on what's free, what's Pro, and why it matters.

Read →

4 min read

Why we built Listen Mode

How we made group expense tracking feel like a normal conversation.

Read →

3 min read

The thinking behind Group Contexts

Why we let you track multiple projects in a single group chat.

Read →

4 min read

Why budgets should text you back

The behavioral design behind Tabby's budget alerts at 50%, 75%, and 100%.

Read →

3 min read

Why we added receipt scanning

The case for letting your camera do the logging.

Read →

4 min read

Recurring transactions vs. subscription tracking

They sound similar, but they solve very different problems.

Read →