Back to Home
Product thinking and engineering notes from building Tabby.
Why Tabby works the way it does, and the trade-offs behind it.
Why we built Tabby on Telegram
The decision to build a chat-first expense tracker instead of another app.
Read article
Why we keep the core free
Our philosophy on what's free, what's Pro, and why it matters.
Why we built Listen Mode
How we made group expense tracking feel like a normal conversation.
The thinking behind Group Contexts
Why we let you track multiple projects in a single group chat.
Why budgets should text you back
The behavioral design behind Tabby's budget alerts at 50%, 75%, and 100%.
Why we added receipt scanning
The case for letting your camera do the logging.
Recurring transactions vs. subscription tracking
They sound similar, but they solve very different problems.
How Tabby is built underneath - the infrastructure and the decisions.
How we killed the hourly cron
The scheduler wasn't a performance problem. It was a product constraint.