When the spreadsheet finally breaks
A freelance web app developer who maps your workflow before he writes a line
It usually starts the same way in Chittagong. An importer in Agrabad is tracking LC numbers, shipment ETAs, and pending duty payments across four Excel files and a WhatsApp group with the C&F agent. A wholesale distributor near Khatunganj is taking stockist orders one phone call at a time, then re-typing them into a register. A clinic off CDA Avenue is chasing follow-ups on paper.
Nothing is technically broken — until two people edit the same sheet, an order gets billed twice, or a shipment slips through because nobody owned the reminder. That's the moment you stop needing a website and start needing a web app: something with logins, roles, a database that updates all day, and a screen that tells each person exactly what's theirs to do.
I'm the only person on your project. The one who replies to your first message is the one writing your authentication logic, designing your order table, configuring your hosting, and pushing the final build. There's no Dhaka account manager forwarding your email two days later, no junior learning Node.js on your timeline, no PM whose whole job is to schedule the meeting that explains why nothing shipped.
Before I write production code, I sit with your actual workflow — who logs in, what they need to see, the four or five actions that move money or goods — and I scope that on paper first. The design-approval guarantee applies here too: we don't start the real build until you've signed off on the screens, so what you approve is what you get.
The stack stays deliberately boring so it survives: React or Next.js on the front, Node.js or Laravel on the back, MySQL or Postgres holding your data, deployed somewhere you actually own. Every credential — GitHub repo, domain, hosting, database — is in your name from day one. Nothing lives 'temporarily' on my personal account to quietly lock you in. If you hire another developer next year, they clone the repo, read the handover doc, and get to work. That's the difference between hiring a senior operator and hiring a hostage situation.
I take one or two app builds at a time, on purpose, because real software needs a person paying attention to it — not a name on an invoice. That's the honest trade-off of hiring solo: genuine senior attention, but not unlimited capacity. So the koto taka question gets a straight answer up front. A small internal tool starts at 50,000 BDT, the standard tiers run 50,000 / 90,000 / 1,50,000 BDT, and a full multi-module application starts at 3,00,000 BDT after a proper scoping call. Payment is 50% advance via bKash, Nagad, or bank transfer, 50% on launch.
See pricing in BDT