The questions that decide a software purchase.

In build. Nimikh EduOps, AgriOps and VisionEdge are named, specified and being built; none of them is live, shipping or generally available, and none has a customer. Each product page states which stage that product is at and what has to happen before it moves to the next one. If you read anything on this site as "available now", that is our mistake and we would like to know about it.

No. What you can do is talk to us about being one of the institutions we build with. The requirements document treats design partners as an outstanding dependency rather than an asset, which is an honest way of saying there are none yet and we need some.

Because an institution budgets a year ahead and a price that appears at the end of a sales conversation is worth less than a price you could have planned against. The bands are published on the pricing page along with the year-one total, which is the number that actually matters and is considerably larger than the subscription line.

No. There are no customers, no pilots, no signed design partners, no testimonials and no case studies, so there is nothing to show you. What we publish instead is the research the products were specified against, with the publication and the date attached to every figure, and the method they are being built by. That is checkable in a way a logo wall is not.

Yes, and it is most of what we do today. Point of sale, inventory, customer records, resource planning, human resources and payroll, accounting, school and clinic systems, online stores, internal tools and workflow automation. Each of those has its own page under /solutions describing what it does, who it suits and what it costs — including the cases where buying an existing product beats building one.

A business website takes 2–3 weeks. An online store takes 4–6 weeks depending on catalogue size. A custom business system takes 8–16 weeks, confirmed in your proposal. Those are working windows, not marketing figures: the proposal names a delivery date and the milestones that lead to it before you commit to anything.

React and Next.js on the interface, Node.js or Go on the backend, PostgreSQL for data. Hosting is chosen with you and sits in your own account under your own billing. The choices are made for the constraints this software runs in — a mid-range Android phone on a mobile connection — rather than for what is currently fashionable, and each one is explained on the software development page.

Yes. Payments through bKash, Nagad, SSLCommerz, aamarPay and card gateways, and delivery through Pathao, Steadfast and RedX. These are integrations built against each provider’s published interface — none of them is a partnership and we do not describe them as one. Money settles into your own merchant account; it never passes through us.

Yes, and we do it often enough that it is worth saying out loud. Accounting, payroll and general online retail all have mature products that cost far less than we would. Where one of those fits, the honest answer is the name of the product rather than a proposal, and you will get it on the first call.

Usually one to two weeks after a scope is approved, which is the honest answer for a two-founder company that does not keep a bench. If we cannot start when you need us to, we say so on the first call rather than holding the slot and hoping.

A business website from ৳ 25,000, an online store from ৳ 65,000, and a custom business system from ৳ 1,20,000. Those are the published tiers and the starting points; the figure in your proposal is fixed against a written scope before anything is built. What moves it is how many distinct workflows the system holds, how much existing data has to be carried into it, and how many outside systems it has to talk to.

For an engagement over ৳ 50,000, payment is split across three milestones: 40% to begin, 40% at the midpoint review and 20% on delivery. Each milestone has something you can open and use attached to it, so a payment is released against work rather than against a date in a calendar.

It is quoted separately as a change, with its own price and its own effect on the delivery date, and you approve it before it is built. Absorbing changes quietly is how a fixed price becomes an argument at handover, so we do not do it in either direction.

No. Domestic software and IT-enabled services attract 5% VAT, which is deducted at source whether or not an invoice is issued. We quote excluding it and issue a compliant invoice in taka against a gapless serial.

Three, and they are named in the proposal rather than hidden in it: domain registration and renewal, hosting, and any third-party service the system depends on — a payment gateway’s own fees, an SMS aggregator’s per-message charge, a mapping or email provider. They are billed to your own accounts so you can see and control them.

For a system we build for you: wherever you choose, in an account you own and pay for directly. We do not hold your production data on our own infrastructure, and we hand back the credentials at handover. No hyperscale cloud provider operates a region, local zone or edge zone in Bangladesh, so keeping data physically in-country means colocation and a database somebody runs rather than a managed service you can buy. We will say what that costs before you decide.

Confidential personal data stays in Bangladesh. The Personal Data Protection Act came into force on 15 April 2026 and imposes class-based localisation, so that commitment is a requirement rather than a preference. Because no hyperscaler region exists here it means colocation, and we have not selected a facility yet. The readiness obligations that go with the Act — processing records, a breach runbook, a named owner — are future work with a date on them, not a completed state, and we do not describe ourselves as compliant.

You do. Source code, database, deployment configuration, designs and documentation transfer to you in full on final payment. There is no runtime licence, no per-seat fee and no component that stays ours and has to be rented back. A vendor who keeps the source is selling you a dependency, and the cost of leaving is what makes it profitable for them.

Nothing stops. You already hold the source code, the database, the hosting account and the documentation, so the system keeps running and another team can pick it up without asking us for anything. If you want it, we will do a handover call with whoever takes it over. We would rather be easy to leave than difficult, because the alternative is keeping clients who would rather not be.

Yes, and in an open format rather than a proprietary one. For a system we build for you, the database is yours and you can take a dump of it at any time. The product line carries an export requirement from day one as a shipped feature rather than a sales promise.

No. No ISO 27001, no SOC 2, no third-party audit and no accessibility badge. An external penetration test is a condition of the first paid production tenant rather than something already behind us. The honest verbs for where we are is "built to" and "designed against", and we will not display a seal we have not earned.

One of the two founders. Headcount is two, there is no account management layer and no sales team, and the person who scopes the work is the person who builds it. That is a real constraint as well as an advantage, and it is why we sequence work rather than running several builds at once.

Yes, across Bangladesh. Discovery for an operational system usually needs at least one visit to the place where the work happens, because watching the work is the part of the method that cannot be done over a call. Everything after that runs over email, WhatsApp and video.

Yes. Interfaces are built for both Bangla and English from the start rather than translated afterwards — different fonts, different line heights, different line lengths, and Western digits for money, dates and reference codes so a number means one thing in both languages.

One month on a website, three months on an online store, six months on a custom system. After that you either take it in-house, keep us on a maintenance arrangement, or hand it to another team — and because you hold the code and the documentation, the third option is genuinely open to you rather than theoretically open.

Not as a number, because a number attached to a service that has not run for a year is a guess dressed as a commitment. What we commit to is where the system runs, who has access to it, how it is backed up, and how quickly we respond when it breaks — all written into the engagement rather than into a marketing page.