Why nobody gives you a real number for an app in Dhanmondi
The price of an app isn't a price list. It's a function of what the app has to do.
Every Dhanmondi business owner I talk to opens with the same line: "app development e koto taka khoroch?" It's a fair question and it deserves a fair answer, but here's the thing most quotes hide — the same sentence, "I need an app," can mean a 50,000 BDT booking screen or a 5,00,000 BDT platform, and the words give nothing away.
A diagnostic centre off Road 27 that wants patients to pick a test, book a slot and pay an advance is a different invoice from a restaurant on Satmasjid Road that wants its own ordering, delivery tracking and a kitchen dashboard. The price isn't arbitrary. It tracks the number of screens, the number of user roles, whether there's a backend and admin panel, which payments you wire in, and whether you need both Android and iOS.
Anyone who gives you a single flat figure before asking those things is either guessing or padding.
So I price the way an honest contractor prices a renovation: I look at what you actually need built, then I give you one fixed number in BDT — not a USD figure you have to convert at today's rate, and not an "estimate" that quietly doubles by launch week. The smallest engagement I take is 50,000 BDT. A focused, single-purpose app or a tight booking or ordering flow can sit inside my 90,000 and 1,50,000 BDT tiers when the scope is clean.
A genuine custom mobile app — real user accounts, a backend, an admin panel, bKash or Nagad inside, push notifications — starts from 3,00,000 BDT and gets scoped piece by piece so you can see exactly what each part of the number is buying. Payment is always 50% advance, 50% on launch, by bKash, Nagad or bank transfer.
I'm RH Fardin, a website and app designer-developer working solo in Bangladesh for about five years. That matters to your price more than it sounds, because a software house in Dhaka has to fund an office, a sales team, project managers and three layers of staff before a single screen gets drawn — and that overhead is in your quote whether they show it to you or not. With me, the person who gives you the price is the person who builds the app. There's no markup for a lobby, no junior "learning on your project" at your expense, and no account manager whose salary you're indirectly paying. You're buying the work, not the brand around it.
The part that actually saves Dhanmondi clients money happens before any number is agreed: I'll tell you straight if you're about to overbuy. A lot of owners walk in convinced they need a full native app for both stores, when their customers would happily use a one-tap booking app that costs a third as much. Cutting scope you don't need is the single biggest lever on the final price, and I pull it on purpose even though it shrinks the invoice — because a 50,000 BDT app people actually use beats a 3,00,000 BDT one that gets eleven downloads. That's how I'd want to be quoted, so it's how I quote.
See pricing in BDT