talo started from a very unglamorous problem: four engineers in one flat, recurring rent, messy grocery math, UPI everywhere, and no product that really understood shared home life in India.
I had already spent years building systems in fast-moving startups, from mobile apps and search infrastructure to analytics platforms, distributed backend services, and AI-heavy internal tooling. So when the spreadsheet-and-Splitwise routine got annoying enough, my instinct was simple: build the thing I wished already existed.
That is still how I think about talo. It should feel calm enough to live with every day, but be technically sharp enough to handle real money workflows, real flat dynamics, and the messy operational details that most expense apps ignore.
01
Four flatmates, one recurring problem
Rent, groceries, Wi-Fi, utilities, UPI everywhere, and no tool that really understood shared home life in India.
02
The usual options were not good enough
Spreadsheets broke, upgrade prompts got annoying, and the product taste was miles away from how a calm money tool should feel.
03
So the engineer in the flat built one
That turned into talo: self-hosted, UPI-first, quiet on the surface, serious underneath.