Web Application Development Company in Gulshan

How to actually evaluate a web app company in Gulshan

Most Gulshan offices pick the wrong web application development company because they evaluate the proposal, not the person.

If you are searching for a web application development company in Gulshan, you have probably already collected two or three proposals, and they all look reassuring — a logo, a glass meeting room on Gulshan Avenue, a deck full of the right words, a Gantt chart, maybe a 'team of 15+ developers.' Here is what that deck does not tell you: the senior who impressed you in the meeting is almost never the person who writes your code.

Once your advance clears, the work drops to whichever junior is free that week, the senior moves to the next sale, and you find out months later — when a screen is half-built and nobody seems accountable. A web application is not a brochure site you can eyeball and approve. It has logins, permissions, data that has to stay correct, and a hundred decisions made out of your sight. The single most important thing you can evaluate is not the proposal.

It is who, by name, will be elbow-deep in your database, and whether that person is reachable directly when something breaks.

I am RH Fardin, a Dhaka-based developer who has run solo for about five years, and I will be blunt about what I am and am not. I am not a 15-person firm. I am one senior operator who personally scopes your workflow, designs every screen, writes the backend, wires the integrations, and is on the call when production hiccups at 9pm.

For the kind of web application most Gulshan businesses actually need internally — a customer portal, a distributor order-entry system, an internal CRM, an inventory and stock dashboard, an HR and leave tracker, a service-ticket queue, an approval workflow, a reporting screen the MD reads on a phone — that is a feature, not a limitation. One to five user roles, role-based permissions, a clean admin panel, bKash or Nagad wired in where money moves. No requirement gets lost across a sales-to-PM-to-junior relay, because there is no relay.

There is a Gulshan-specific reason this matters more here than almost anywhere else in Dhaka. So many companies in Gulshan deal with foreign principals, embassies and multinationals that vendors have learned the postcode will tolerate foreign pricing — so the quote arrives in USD, with an annual license attached and 'integration' billed as a separate phase. Strip the theatre away and your web app is a database, a few user roles, an admin panel and some reports. The same engineering whether your office is in Gulshan 2 or Bogura.

I price that in taka, fixed after one scoping call, and I put senior attention on every screen because there is no junior bench I need to keep billable. If your scope genuinely needs a ten-person team and a nine-month roadmap, I will tell you that on the first call and refer you out — I would rather lose a project than oversell a system I cannot ship well alone.

Pricing is in BDT and it does not move once we sign. A focused single-purpose web app — one role, a couple of core screens, the kind of thing that replaces one painful Excel workflow — fits my tiered builds 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 runs 50% advance and 50% on launch, by bank transfer, bKash or Nagad. Nothing gets coded until you approve the screens and the data flow in Figma — that is the design-approval guarantee — and 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.'

See pricing in BDT

In focus

The 'team of 15' is selling you redundancy. For most Gulshan web apps, it costs you accountability.

There is a comfortable assumption in Gulshan boardrooms that a bigger web application development company is the safer choice — more developers, more resilience, a 'team' rather than a single point of failure. It sounds responsible, and for a genuinely large platform it can be true. But for the internal web app a typical Gulshan office actually needs — the order portal, the inventory dashboard, the CRM under a few lakh — a team of fifteen does not buy you fifteen people on your project.

It buys you one or two juniors on your project and thirteen people you are subsidising through overhead, plus a layer of project managers whose job is to stand between you and the people doing the work. What you experience is not extra safety. It is diffused accountability: when something is wrong, no single person is clearly responsible, the answer is always 'we're looking into it,' and the senior whose name sold you the deal has long since rotated to the next client.

The redundancy is real — but it protects the firm's delivery risk, not your project's outcome.

I work the opposite way, and I will tell you plainly where the trade lands so you can decide with your eyes open. With one senior operator, there is genuinely one point of failure — me.

The honest mitigation is not a junior bench; it is that I take on a deliberately small number of projects so each gets real attention, I scope tightly so timelines are realistic instead of optimistic, and I hand over your full source code on your own Git from the start, so you are never dependent on me to keep running.

If I get hit by a bus, any competent Dhaka developer can pick up a clean, documented codebase on a standard stack — React or Next.js on the front, Laravel or Node on the back, PostgreSQL or MySQL underneath — and that is a far better insurance policy than a team you can't reach.

So when you compare the web application development company Gulshan options in front of you, run them past two questions: 'Who, by name, writes my code?' and 'Can I log into a live web app real staff use every day, today?' Check my answer to both at rhfardin.com. For web application development Gulshan BD businesses under a few lakh, one accountable senior beats a team of five mid-levels you'll never meet — and the firms that go quiet on those two questions filter themselves out fast.