Why We're Building From Bangladesh, Not Just For It
Most software gets built somewhere convenient and shipped everywhere else. A team in a market with reliable infrastructure, predictable habits and forgiving assumptions builds something that works for that market, and then discovers — usually the hard way — that the rest of the world doesn’t behave the same way.
We decided to do the opposite. NeedTown starts in Bangladesh, and it starts here on purpose.
The gaps are visible here
Bangladesh is a place of close communities, fast adoption and restless entrepreneurship, sitting on top of genuinely complicated everyday systems. A tenancy might be a handshake and a stack of paper receipts. A shop’s entire accounting might live in a single physical khata, refilled by hand every evening. A family’s records — property documents, warranties, appointments, the things that matter — might be scattered across drawers, phones and memory.
None of that is a failure of the people living it. It’s what happens when the digital tools available don’t fit the way life here actually works. And because the gap between physical and digital life is so visible and so immediate in Bangladesh, it’s a harder starting condition than most places offer — and a better one to build against.
Harder is the point
If a product only has to work for someone with a stable job, one landlord, one bank and reliable internet, it’s easy to build something that looks complete while quietly excluding almost everyone else. Bangladesh doesn’t let you get away with that. The people we’re building for are running a single shop with no back office, managing a rental property through a notebook, or trying to keep their own life organized without an assistant, a filing cabinet or a spare hour in the day.
Solve it here and it tends to work anywhere. The reverse is rarely true — software designed for the easy case first almost never gets simplified enough to work for the hard one later. So we’re not treating Bangladesh as a test market to learn in before “really” launching somewhere else. It’s the actual starting point, and the standard the rest of the work has to meet.
What that means in practice
It shows up in decisions that are easy to skip when you’re not paying attention: designing for patchy connectivity instead of assuming it away, keeping interfaces usable for someone’s first ever app rather than their fiftieth, and building records — a tenancy, a ledger, a Space — around how people actually track them today, not how a spreadsheet would prefer they did.
It’s also why the products are built to work on their own before they’re built to work together. Nobody in a shop deciding whether to try a new tool cares that it’s part of a bigger ecosystem — they care whether it solves today’s problem. Everything NeedTown builds has to clear that bar first.
We’re at the beginning of this work. Bangladesh is where it starts, not where it stops.