How web application development in Dhanmondi goes wrong
Most failed web apps in Dhanmondi were never scoped. They were sold.
The real problem with web application development in Dhanmondi is how it gets sold, not the code. An owner says "I want a system," and a sales rep nods at everything. A quote arrives for a huge platform with twenty modules nobody asked for. It has patient management, HR, payroll, a mobile app, an SMS gateway and a reporting suite. The price is six lakh, the timeline is six months, and 50% is due up front.
What gets built is a generic template with the owner's logo on it. The front desk staff refuse to touch it. By month three, everyone is back on the old Excel file. The app did not fail because the developer could not code. It failed because nobody cut it down to the four screens that change someone's working day. And nobody ever watched how the work really happens.
I am RH Fardin, a web designer and developer who has worked solo for about five years. When you hire me for web application development in Dhanmondi, you get one accountable person from the first call to launch and after. We walk through how your front desk really runs on a Google Meet call. Then I draw the screens and design the database.
I write the React front end and the Laravel or Node back end. I wire in payments if you take them, and I push it live. No junior quietly rebuilds your spec overnight. No account manager stands between you and the person writing the code. Most Dhanmondi owners who message me have already paid an agency once. The senior in the pitch never built the thing, and it broke on the first busy Saturday.
I start every project by scoping down, not up. A web app is judged on one thing. Does the person who uses it eight hours a day reach for it, or for the paper register? Picture a receptionist in a Satmasjid Road clinic during a rush of walk-ins. She does not want twelve fields and a side menu of features she never uses. She wants the four fields that register a patient and the one button that prints the slip.
So before I quote, I ask who logs in and on what device. I ask which single number on a screen would change their day. Then I cut everything that does not earn its place. That is plain, unglamorous work. It is exactly why the apps I build survive past the demo. The flashiest dashboard on Dribbble is useless if your Jigatola front desk opens a second tab to get around it.
My pricing is plain and in BDT. The floor is 50,000 BDT for a focused, single-purpose tool. The tiers run 50,000 / 90,000 / 1,50,000 BDT for scoped apps with several screens, logins and a core workflow. A true custom multi-role system starts from 3,00,000 BDT. That means a database, admin panel, user roles, payments and reporting. It is always 50% advance and 50% on launch, by bKash, Nagad or bank transfer.
Every project comes with a design-approval guarantee. You sign off the screens in Figma before I build. The final balance is not due until you approve the UI. The full source code sits on your own GitHub or GitLab from week one, so you are never locked in.
See pricing in BDT