Software built for one operation, and owned by it.
Most of what we do today is custom engineering for businesses in Bangladesh — a point-of-sale system, an inventory ledger, a customer record, a school office, a booking engine. Fixed scope, fixed price, and at the end of it the code is yours.
This is the work that funds the product line.
We are a software company moving from services to products, and we are honest about which half is earning today. The engineering practice is the half that ships: real systems, real deadlines, running in real businesses.
It is also where the method gets tested. Every constraint the product line is built against — a Friday–Saturday weekend, a phone running Android 12, a loading dock with no signal, money that has to reconcile against the gateway’s own settlement file — was learned on this side of the company first.
So the engineering standards do not drop when the client is yours rather than ours. It is the same people and the same refusals.
What we build
Two routes in. If you know the kind of system you need, go straight to it. If you are not sure yet, start with the practice page — it lists every type of system we take on and what each one costs.
Business systems, one page each
Point of sale, inventory, customer records, resource planning, human resources and payroll, accounting, restaurant, school and clinic systems, online stores, and workflow automation. Each page states what the system does, who it suits, what it costs, how long it takes, and when you would be better off buying something off the shelf.
Custom software development
The full practice page: the kinds of software we develop, the payment and courier rails we integrate against, the stack we build on, and the process a project runs through from the first call to handover.
How an engagement runs
Five stages, in this order, on every project regardless of size. The first one is the one most vendors skip.
Stage 1: A call about the problem, not the software
Thirty minutes. We want the thing that goes wrong repeatedly, who it happens to, and what it costs when it does. If the answer is that an off-the-shelf product already solves it, that is where the call ends and you have lost half an hour instead of half a budget.
Stage 2: A written scope with a price against it
Screens, workflows, integrations, data to be carried across, and what is deliberately excluded. The price is fixed to that document. Anything outside it is quoted separately as a change rather than absorbed quietly and argued about at handover.
Stage 3: Build in the open, on a staging environment you can log into
You get a URL and an account from the first week, not a demo at the end. Every milestone has something you can open and use attached to it, which is what a milestone payment is released against.
Stage 4: Handover, with the keys
Source code, database, deployment configuration, an administrator account and written documentation. Transfer of the intellectual property happens on final payment and it is total — there is no runtime licence, no per-seat fee and no part of the system that stays ours.
Stage 5: Support for a fixed period, then a decision
One to six months included depending on the tier. At the end of it you either take it in-house, keep us on a maintenance arrangement, or hand it to someone else — and because you hold the code and the documentation, the third option is genuinely available to you.
What it costs
Three published tiers. The figure in your proposal is fixed against a written scope before anything is built.
| Engagement | What it is for | Price | Delivery |
|---|---|---|---|
| Website | For a service business or a shop that needs a credible, fast public presence. | ৳ 25,000 one-time | 2–3 weeks |
| Online store | A storefront wired into the payment and courier rails that actually operate here. | ৳ 65,000 one-time | 4–6 weeks |
| Custom system | A system built for one operation — a dashboard, a booking engine, a management portal, an internal tool. | ৳ 1,20,000 starting from | 8–16 weeks |
Prices exclude VAT. Engagements over ৳ 50,000 are split across three milestones — 40% to begin, 40% at the midpoint review, 20% on delivery — each released against something you can open and use. The full price list.
What we will not do
Each of these has cost us work, which is why they are worth more to you than a list of technologies.
- Refusal 01
We will not start building before we have watched the work
A request for a dashboard is usually a request to stop finding out about a problem two days late. The two produce different software, and the difference is only visible if somebody sits with the person who has the problem first.
- Refusal 02
We will not sell you a build you do not need
Accounting, payroll and general e-commerce have mature products that cost less than we would. Where one of those fits, we say so — each system page under /solutions names the cases where buying beats building.
- Refusal 03
We will not keep your code
Intellectual property transfers on final payment, in full. A vendor who keeps the source is selling you a dependency, and the price of leaving is what makes it profitable.
- Refusal 04
We will not quote a figure before we can defend it
A number given on the first call is a number that moves. The proposal names how many workflows, how much data migration and how many external systems are in scope before it names the price, so you can see what would change it.
Start with the problem
Tell us what goes wrong and how often, and we will come back with a scope, a price and a timeline — or with the name of something you can buy instead.