Custom software development in Dhaka.
Nimikh is a custom software development company in Dhaka, Bangladesh, building the systems small and medium businesses actually run on — CRM, ERP, POS, inventory management, HR and payroll, customer portals and workflow automation. Fixed scope, fixed price, from ৳ 25,000, and the code is yours at the end.
What we build
Three shapes of engagement, each with a published price and a published delivery window. Which one you need usually becomes obvious in the first conversation.
- Shape 01
Business websites
৳ 25,000one-timeA public presence for a service business, a shop or a practice: pages, a contact form, a WhatsApp handoff, local business markup and search-engine setup. Responsive down to a 360 px phone, because that is what most of Bangladesh reads it on.
Delivery2–3 weeks - Shape 02
E-commerce stores
৳ 65,000one-timeA storefront wired into the rails that actually operate here: bKash and Nagad checkout, cash on delivery, Pathao, Steadfast and RedX courier integration, order management, stock and customer accounts.
Delivery4–6 weeks - Shape 03
Custom business systems
৳ 1,20,000starting fromThe system one operation runs on — point of sale, inventory, customer records, resource planning, human resources and payroll, a booking engine, a management portal, an internal tool. Custom database and backend, role-based access, and an admin surface your own team can operate.
Delivery8–16 weeks
What each tier includes, beside the product subscription bands
The systems we are asked for most
Each has its own page explaining what it does, who it suits, what it costs and how long it takes — including the cases where we would tell you to buy off-the-shelf software instead.
What it gets wired into
A business system in Bangladesh is mostly integration work. These are the rails we build adapters against — none of them is a partnership, and we do not present them as one.
| Area | What we integrate | How it works |
|---|---|---|
| Payments | bKash, Nagad, SSLCommerz, aamarPay, card gateways | Built as adapters against each gateway’s published interface. Money settles into your own merchant account, never through us. |
| Courier and delivery | Pathao, Steadfast, RedX | Order creation, label generation and status callbacks, so fulfilment state lives in the same system as the order rather than in a spreadsheet beside it. |
| Messaging | SMS through a domestic aggregator, WhatsApp Business Platform, email | Metered and capped. A Bangla message runs to two or more SMS parts at seventy Unicode characters each, so the cost is made visible rather than buried. |
| Whatever you already run | Accounting packages, spreadsheets, attendance hardware, existing databases | Migration of existing data is scoped and priced explicitly, because it is usually the part that decides whether a rollout succeeds. |
What it is built on
Chosen for the constraints of the place it runs in rather than for what is currently fashionable. Each choice has a reason you can argue with.
| Layer | Choice | Why |
|---|---|---|
| Interface | React and Next.js, server-rendered | The first screen has to arrive on a mid-range Android phone over a mobile connection, which rules out shipping the whole application before anything is readable. |
| Backend | Node.js or Go | Chosen per project. Go where throughput or long-running work dominates, Node where the surface is mostly orchestration and the team will maintain it themselves. |
| Database | PostgreSQL | Constraints, transactions and row-level security enforced by the database rather than remembered by the application. Money and stock are the two places a lost write is unrecoverable. |
| Hosting | Chosen with you, and yours | No hyperscaler operates a region in Bangladesh. Where data has to stay in-country that means colocation; where it does not, it is a managed platform in your own account, under your own billing. |
The performance budget is set by the cheapest phone likely to open it. More than 30% of Bangladeshi devices run Android 12 or older (StatCounter, 31 Aug 2026), so that is what the interface is measured against — not an office desktop on office broadband. How the systems are built.
How a project runs
Five stages: a call about the problem, a written scope with a price fixed against it, a build you can log into from the first week, handover with the source code and the keys, and a fixed support period after launch. Each stage is set out in full on the practice page.
Who owns what
You do. Source code, database, deployment configuration and documentation transfer to you on final payment, in full. There is no runtime licence, no per-seat fee, and no component that stays ours and has to be rented back. If you later hand the system to another team, everything they need is already in your possession.
Tell us what breaks every week
Describe the thing that goes wrong repeatedly and what it costs when it does. We will come back with a scope, a price and a timeline — or with the name of something you can buy instead of building.