How web application development actually runs when you commission it in Gulshan
You are past 'do we need this'. The real risk is who builds it and whether it ships.
Most people who land on this page are not browsing — they have a project. A buying house in Gulshan needs an order-entry portal their merchandisers can fill from a supplier's office. A clinic off Gulshan Avenue needs a booking and patient-queue system the front desk and the doctor both see live. A distributor needs stock visible across two godowns in real time. The decision to build is made.
What is not settled is the part that actually sinks projects here: who scopes it correctly, who writes the code, who is still answering messages in month three, and whether the thing ships or dies as a half-built demo on a server nobody renews. That is the problem I solve, and it is a different problem from 'we are thinking about software someday.'
I am RH Fardin, and I run solo on purpose. A web application is software that lives in the browser — your team logs in from a laptop in the Gulshan office, a phone in a meeting, or a branch in Banani, and they all see the same live data with nothing to install. Customer portals, internal CRMs, inventory and stock dashboards, distributor order systems, HR and leave trackers, service-ticket queues, the reporting screen a managing director reads on their phone between meetings — that is the work.
One to five user roles, role-based permissions, a clean admin panel, and bKash or Nagad wired in wherever money moves. The reason it gets to me directly matters: when you message me, you are talking to the person who will design the screens and write the backend, not a salesperson who hands you off the moment the advance clears.
The development itself runs in a fixed order, and I am strict about it because that order is what keeps a project from drifting. First, a scoping call where we nail down user roles, the screens that earn their place, and which integrations are real versus nice-to-have. Then I build the screens and the data flow in Figma — and nothing gets coded until you approve them.
That is the design-approval guarantee, and it exists because the most expensive mistake in web application development is discovering in week six that what got built is not what you pictured. Once screens are signed off, I build in the open, you see progress on a staging link, and we ship. The whole point of one senior operator is that the person who understood your scope is the same person shipping it — no telephone game through a junior team.
Pricing is in BDT and it is fixed once we sign. A focused single-purpose web app — one role, a couple of core screens, the kind of build that replaces one painful Excel workflow — fits my tiered packages at 50,000, 90,000 or 1,50,000 BDT, with 50,000 BDT the floor for the smallest engagement. A genuine custom multi-role application — multiple logins, permissions, payment integration, real reporting — starts at 3,00,000 BDT. Every project is 50% advance and 50% on launch, by bank transfer, bKash or Nagad.
On launch day the source code, the database and the server credentials are yours — no annual license you did not ask for, no lock-in dressed up as 'support'. If your scope genuinely needs a ten-person team and a nine-month roadmap, I will say so on the first call and point you elsewhere rather than oversell a build I cannot ship well alone.
See pricing in BDT