The case for building where you live

We started with a simple observation, not a business plan: the places we live deserve software made with the same care as anything built for Silicon Valley, and almost never get it. Everything since has followed from that one sentence, including which products we chose to build and how.

Trinetra and Urban Hood don't share a category. One is a guide to a pilgrimage city, the other is a neighborhood social space. What they share is a starting condition: we were our own first users. We weren't designing for a market we'd researched from outside it. We were designing for a gap we felt from inside it, standing in the same crowds, living on the same streets. That's a different discipline than empathy mapping a persona you've never met.

There's a real cost to this approach: you can't build for "where you live" and also chase every market at once. It forces a kind of commitment that founders are often told to avoid, because it looks like a ceiling instead of a strategy. We think it's the opposite.

Building for a place you actually inhabit means you get corrected constantly, by the place itself.

That correction loop is worth more than a bigger addressable market with none of it.

We don't think this only applies to consumer apps we happen to run ourselves. It's the same standard we now bring to client work: build for a real place and real people first, and let the market-sizing conversation happen after, not instead of, that decision.