How web application development in Dhanmondi actually goes wrong
Most failed web apps in Dhanmondi were never scoped — they were sold.
The way web application development in Dhanmondi usually gets sold is the problem, not the code. An owner says "I want a system," a sales rep nods at everything, and a quote arrives for a sprawling platform with twenty modules nobody asked for — patient management, HR, payroll, a mobile app, an SMS gateway, a reporting suite. Six lakh, six months, 50% up front.
What gets built is a generic template with the owner's logo on it, the front-desk staff refuse to touch it, and by month three everyone is back on the old Excel file. The app did not fail because the developer couldn't code. It failed because nobody scoped it down to the four screens that actually change someone's working day, and nobody who watched the work happen ever sat in the room.
I am RH Fardin, a web designer and developer in Bangladesh working solo for about five years. When you hire me for web application development in Dhanmondi you get one accountable person from first call to launch and after — I sit with you to understand how your front desk really runs, draw the screens, design the database, write the React front-end and the Laravel or Node back-end, wire in payments if you take them, and push it live.
There is no junior quietly rebuilding your spec overnight, no account manager between you and the person typing the code. Most Dhanmondi owners who message me have already paid an agency once, where the senior in the pitch was never the person who built the thing — and the thing buckled the first busy Saturday.
The reason I start every project by scoping down instead of up is that a web app is judged on one thing: does the person who lives inside it eight hours a day reach for it, or for the register? A receptionist in a Satmasjid Road clinic during a rush of walk-ins 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, on what device, and what single number on a screen would change their day — and I cut everything that does not earn its place. That is unglamorous work and 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.
Pricing is plain and in BDT. My floor is 50,000 BDT for a focused single-purpose tool. The tiers run 50,000 / 90,000 / 1,50,000 BDT for scoped multi-screen apps with logins and a core workflow, and a genuine custom multi-role system — database, admin panel, user roles, payments, reporting — starts from 3,00,000 BDT. Always 50% advance, 50% on launch, by bKash, Nagad or bank transfer. Every project carries a design-approval guarantee: you sign off the screens in Figma before I build, and the final balance is not due until the UI is approved. The full source code sits on your own GitHub or GitLab from week one, so you are never locked in.
See pricing in BDT