Why the koto-taka answer is hardest with web apps in Sylhet
With a website you can guess the price. With a web app, a guess is how projects quietly double
Ask about the web application development price in Sylhet and you get a vaguer answer than you would for a website. There is a reason. A website is mostly visible: pages, photos and text. So even a rough quote lands close. A web app is mostly invisible. You pay for a database that does not break when forty retailers order at once. You pay for a login nobody can get around.
You pay for a bKash flow that handles a failed payment without charging a customer for nothing. You pay for an admin panel that lets you refund without calling the developer. None of that shows in a demo. So that is exactly where a quote gets padded. Worse, it gets quietly skipped to win you with a cheap price. You find the gap three months in, when the data is a mess and the 'developer' has stopped replying.
In Sylhet there is a second layer everyone here knows about. Before a local web shop names a price for software, it first works out who is funding the project. Say it senses a brother in Whitechapel or a father with a restaurant in Manchester. Then the figure climbs. The investor abroad cannot walk up the stairs in Zindabazar to argue, and pounds convert to a lot of taka.
With a web app that game is even easier, because the buyer rarely knows what the invisible work should cost. My published price exists to shut that down. The tiers are fixed, and they match the logic your app really needs. They do not move whether the money comes from a shop in Sobhanighat or a takeaway in Bradford.
Here is what really moves the number, so it stops feeling like a read on your funding. First, how many user types the app serves. A single admin is one thing. Customers, staff with roles and a manager dashboard are another. Second, whether it takes real bKash and Nagad payments, failure cases included, or only enquiries. Third, how much it does on its own: stock that counts down, bookings that block double-booking, and emails and receipts that send without you.
Fourth, whether it connects to anything outside itself, like courier APIs, SMS or an existing accounts system. Fifth, whether a clean, proven base fits the brief, or your business is unusual enough to need a build from a blank canvas. The tiers exist so the figure follows that work, not your relatives' postcode.
When you hire me, the person quoting is the person building. There is no sales desk that lowballs to win the job, hands it to a junior who learned React last month, then pads the scope later. There is no agency overhead, like office rent, account managers or a margin stacked on every hour. That is why my price undercuts both a local 'IT solutions' firm chasing diaspora money and a Dhaka agency. You pay one senior developer with about five years of shipping Bangladeshi apps.
And the price holds. You pay 50% advance to start and 50% on launch. You sign off the full design before I write any backend code. The number you quote to whoever is paying is the number on the final invoice. No creep, no surprise 'maintenance' trap and no second figure once the database is half built.
See pricing in BDT