What a business app actually costs in Bangladesh

Ask ten development shops in Dhaka or Chattogram to price the same booking app and you will get ten numbers spanning an order of magnitude. That spread is not dishonesty — it is mostly different answers to questions the brief never asked. This post is the short list of questions that make any quote comparable, written from the side of the table that has to stand behind numbers.

The five questions behind every quote

• How many surfaces? A customer app is one product; a customer app plus a business dashboard plus an ops panel is closer to three, each with its own screens, permissions and edge cases.
• Who owns the money flows? Reading a payment gateway's docs is a day; reconciling failed captures, partial refunds and settlement reports into your ledger is a phase of work. Quotes that ignore this are quoting a demo, not a system.
• What happens on a bad network? Tolerating a dropped connection mid-submit is invisible engineering — it costs the same whether you ask for it or not, and only one of those versions works in Bangladesh.
• What is maintenance priced at? A launch without a support lane is a subscription to surprise invoices. Compare quotes on the first year of upkeep, not only the build line.
• What do you own at the end? Repos, accounts, design files, and whether you can walk to another studio with them. Lock-in makes a cheap quote expensive exactly once.

Where the money honestly goes

In a serious build, code is not the biggest category — decisions are. Requirements held to a signed brief, weekly demos against working software, and a change price agreed while everyone is still friendly all convert into fewer expensive surprises later. A quote should show you the shape of that process; if the proposal is only a feature list with a number under it, you are not being quoted a project, you are being quoted a hope.

The question to ask instead of "can you do it cheaper"

Ask "what do we cut first, and what does each cut cost later?" Good studios keep a list: defer the admin panel and operations run on spreadsheets for three months, then pay for staff training in confusion; skip offline tolerance now, pay for support calls forever. A transparent quote prices the deferrals honestly, and lets you choose them with eyes open.

Our own posture: fixed scope against a signed brief, a written rate for every change, maintenance named as a line item on day one — and the client owning every repository and account from the first commit. Compare any quote, ours included, against exactly that.