Why software dies in a Gulshan office
The expensive part of custom software isn't the code. It's deciding, precisely, what the thing has to do.
Here is the pattern I see again and again in Gulshan offices that already tried once. An MD or a GM decided the business needed 'a system' — for orders, for inventory, for the dealer network, for service complaints. Someone was hired or a small firm was signed.
Six months and a few lakh later a tool exists, there is a login screen, there are dashboards in the demo — and the staff are still running the real work in Excel and a WhatsApp group, because the software does eighty percent of a job nobody actually had, and zero percent of the one they did. The code wasn't the problem. Nobody ever sat with the storekeeper, the accounts assistant and the sales coordinator and wrote down, screen by screen, what the system had to do on a normal Tuesday.
That conversation is the real work of custom software development in Gulshan, and it is the part most vendors skip because it is unglamorous and unbillable.
So that is where I start, and it is the honest reason to hire one senior person instead of a sales-and-junior pipeline. Before I quote a final taka figure, I spend time with the people who will actually live in the software — not just the MD who signs the cheque.
I want to know how an order really gets taken, where it currently breaks, who needs to approve what, which numbers the GM checks on a phone at 9pm, and which 'requirements' on the wishlist are real versus things someone added because they sounded modern. Then I write that down as screens and a data flow you can read and argue with, in plain language, before a single line of code exists.
Most of the cost and most of the risk in custom software development gulshan businesses take on is decided in that week — get it right and the build is almost boring; get it wrong and no amount of clean code saves you.
Around 5 years of building for Bangladeshi companies has shown me the systems Gulshan head offices genuinely run on, and they are more modest than the brochures suggest: order and dealer-distribution management, inventory and stock movement across one or two branches, HR and payroll with bKash or Nagad disbursement, appointment and chamber systems for clinics, service-ticket and complaint tracking, procurement and approval workflows, and a clean dashboard a director can actually read on a phone.
A handful of user roles, sensible permissions, NBR-shaped VAT and Mushak where money is invoiced, local payment and SMS where money or alerts move, and an admin panel your own staff operate without calling me every week. That is the realistic shape of custom software development gulshan bd companies need — not a 300-screen global ERP that a solo developer would be reckless to take on alone, and when your scope honestly is that size, I will say so on the first call rather than after your advance clears.
Pricing is in BDT and it is fixed once the scope is signed — no dollar meter, no 'phase two' that quietly doubles the number. A genuine custom software product — real database, admin panel, user roles, integrations — starts at 3,00,000 BDT. A focused internal tool or single-workflow web app often fits my tiered builds at 50,000, 90,000 or 1,50,000 BDT, with 50,000 BDT the floor for the smallest engagement. Every project is 50% advance and 50% on launch, by bank transfer, bKash or Nagad.
Nothing is coded until you approve the screens and the data flow — that is my design-approval guarantee, and it exists precisely because the costliest mistakes in software are misunderstandings about what it should do, caught cheaply on a Figma screen instead of expensively in finished code. On launch day the source code, database and server access are yours.
See pricing in BDT