Built in Bengaluru, for the world.
Why we are starting with Indian errands, Indian payments and Indian languages, and what that teaches us about everywhere else.
We are building AskGogo in Bengaluru, and we are building it for India first. Not because the rest of the world does not matter, but because the everyday errands here are some of the hardest to get right.
Hard problems make a better assistant
Think about what a single week involves. A train ticket with a waiting-list PNR to watch. An electricity bill that arrives as a photo in a family group. A service centre that confirms by phone call, not email. A pharmacy that delivers but only takes orders on WhatsApp. Payments through UPI, three different wallets, and occasionally cash on delivery. Five languages in one household.
An assistant that can handle that week has learned to work with messy inputs, many small services with no clean API, and people who expect it to understand them the way a person would. Those lessons carry anywhere.
We would rather solve the difficult version of the problem first and simplify later than the other way round.
What India-first means in practice
It means prices in rupees, written the way people read them. Booking flows that know IRCTC, local cab services and regional pharmacies. Reminders that understand "the 5th" means the day the society maintenance is due. And approval before payments built around UPI, because that is how most people actually pay.
And then the world
Many of the people we build for live between countries, with family in India and work in the Gulf, Singapore, the UK or the US. The parts of Gogo that matter most, memory with sources, approval before anything consequential and proof when something is done, do not change from country to country. The local parts do: currency, services, language, holidays. We are building those country by country rather than pretending one version fits everyone.
So: built in Bengaluru, tested on some of the busiest errands anywhere, and opening to the world in small groups.