Questions we get asked, answered directly

Cost depends on four things: how many user roles the system has, how many external systems it must talk to, whether data has to be migrated from an existing system, and how much compliance reporting is required. We give a written range after a discovery call, before any contract is signed.

A focused first version typically reaches real users in three to four months, with working software on a staging link every two weeks from the first sprint. Full ERP or core banking work runs longer because migration and parallel running take time, not because development does.

Yes. We build against bKash, Nagad, Upay, SSLCOMMERZ, aamarPay and ShurjoPay, including the parts teams usually discover late: refund handling, failed-callback recovery and end-of-day reconciliation against the provider statement.

Yes, and it is a large part of what we do. We start with a paid audit of the existing code, data and infrastructure, then give you an honest recommendation — continue, partially rebuild, or start again — with the cost of each option written down.

You do, from the first commit. Code sits in a repository your organisation owns, infrastructure runs in your own cloud account where you prefer that, and there is no licence fee or lock-in that makes leaving expensive.

Yes. We work with clients across Bangladesh, including Chattogram and Sylhet, and with overseas teams in Europe, North America, Australia and the Gulf. Bangladesh Standard Time overlaps a full working day with the Gulf, South Asia, South-East Asia and Australia, and a morning with Europe.

Support continues on a monthly agreement: monitoring, security patching, dependency upgrades and a fixed allocation of engineering hours for changes. Most systems need the most work in the three months after launch, when real usage exposes what testing could not.

Yes. Interfaces, training material and user documentation are delivered in Bangla, English, or both, and staff training at the client site is run in Bangla by default. Bengali numerals and date formats are handled properly rather than bolted on.

A written note every week covering what shipped, what is in progress and what is blocked, plus a staging link you can open at any time. Progress is something you verify rather than something you are told.

The engineers doing the work, plus a lead accountable for delivery. There is no account manager sitting between you and the people writing the code.

Work stops at the end of the current sprint with everything committed, documented and deployed to staging. Pausing is not penalised, and restarting does not mean re-scoping from zero.

Raise it immediately rather than at the end. Sprint reviews exist for exactly this, and the notice period in the contract means you are never locked into a bad engagement for months.