What drives the cost of custom software in Bangladesh

Why the question is hard to answer

Nobody can price custom software from a one-line brief, and any vendor who does is quoting a guess they intend to renegotiate later. What can be priced is discovery — the work of mapping the process and writing down the scope. That is why we price it separately and why you should be suspicious of anyone who skips it.

The four things that actually move the price

User roles. A system with one kind of user is a fraction of the cost of one with six. Every role adds permissions, screens, and a set of edge cases where roles interact.

Integrations. Each external system — accounting package, payment gateway, courier API, government portal — adds work that is mostly invisible in a demo and unavoidable in production: authentication, retries, reconciliation, and what happens when the other side is down.

Data migration. Moving five years of records from spreadsheets or an old system is frequently the single largest line item. The extraction is straightforward; deciding what inconsistent historical records should become is not.

Compliance reporting. A system that produces a regulatory return has to reconcile to the ledger. That constraint shapes the data model and adds testing that a purely internal tool does not need.

Counting your own scope

Before talking to any vendor, count the four drivers for your own system. A school management system makes a useful worked example:

Driver	What to count	School example
User roles	Each kind of person who logs in	5: principal, accounts office, teacher, guardian, student
Integrations	Each outside system, by name	3: bKash, Nagad, an SMS gateway
Data migration	Sources and years of history	1 source: Excel registers going back several years
Compliance outputs	Each regulatory return or format	2: eSIF registration and the annual BANBEIS return

Other common integrations in Bangladesh are SSLCOMMERZ, aamarPay, ShurjoPay and Upay for payments, Pathao Courier, Steadfast and RedX for delivery, NID verification for identity, and NBR VAT reporting for anything that issues invoices. Each one you list is a line every vendor should price, and a quote that does not mention it has not included it.

What a cheap quote usually excludes

Typically excluded	What it costs you later
Discovery	Scope discovered during build, as change requests
Automated testing	Every release becomes manual regression
Data migration	A separate project, usually urgent
Training and documentation	Low adoption, then blame on the staff
Deployment and monitoring	Outages you find out about from customers
Post-launch support	A new negotiation at your least convenient moment

None of these are optional in practice. They are optional in the quote.

How to compare proposals properly

Ask every vendor the same five questions, in writing:

1. What is explicitly excluded from this price?
2. Who owns the source code, and where does it live during development?
3. What happens in the first three months after launch, and what does it cost?
4. How is a change priced once work has started?
5. Who, by name, will do the work?

The answers separate serious proposals from optimistic ones faster than the numbers do.

A reasonable way to spend

Commission discovery first, from one or two vendors, and pay for it. You will end up with a process map, a written scope and a cost range — all of which you own and can take to anyone. If a vendor will not sell you that without a commitment to the full build, that itself is information.