Software development company · Dhaka
We build the systems a business actually runs on: orders, stock, accounts, staff and the reporting across all of it. Stable enough to depend on, built to grow with you, and automating the manual steps your team does by hand today.
How work moves
An order moves through these steps on its own. Staff and customer see the same status, and nobody updates a spreadsheet to make it true.
What we do
Most projects need more than one of these. We build them together rather than stitching them together afterwards, and we are still here once they are live.
Line-of-business systems built around how your organisation actually runs, not around a template you have to bend yourself into.
Fast, accessible web products: customer-facing storefronts and the admin consoles that keep them running.
One codebase on both app stores, with the release process set up so updates ship on a schedule instead of becoming an event.
Connected devices wired into the same platform as everything else, so field data lands where decisions are made.
The manual steps between your systems, done for you: the data that moves today by spreadsheet, email or re-typing.
The work after launch: fixes, upgrades and changes as the business changes. The people who built the system are the ones who maintain it.
Our own products
All built on one core foundation, which is why a new product takes months rather than years. Everything we learn hardening them goes straight into what we build for you.
E-commerce platform
A full commerce stack: a customer storefront, a merchant admin console and the API behind both. Variants, inventory across warehouses, orders, payments, shipping and reporting.
Returns and refunds run through the same flow as the sale, so the books and the stock stay correct without a separate spreadsheet.
Merchant admin
Education platform
Administration for a single school or coaching centre. One deployment per institution, with the same permission model and admin foundation as every other Revolop product.
| Permission code | Support | Admin |
|---|---|---|
| order:manage | granted to Support | granted to Admin |
| customer:view | granted to Support | granted to Admin |
| user:reset-password | granted to Support | granted to Admin |
| report:view | not granted to Support | granted to Admin |
| role:manage | not granted to Support | granted to Admin |
| settings:menu | not granted to Support | granted to Admin |
Accounts and finance management for real-estate operators: ledgers, receivables and the reporting a property business is audited on. In design on the same foundation as the others.
Rebuilds
A good share of our work starts with software someone else delivered: slow, unreliable, or only standing up because staff work around it every day. Replacing it is not starting again from nothing.
Before anything is rewritten we go through the existing system and its database to establish what genuinely works, what is actually used, and where the failures come from.
Years of orders, customers and records are migrated rather than abandoned. Nothing your business is accountable for gets left behind on the old system.
Sign-in, permissions, storage and configuration are already proven in systems we run ourselves. The rebuild starts from working parts instead of being written again under time pressure.
How we work
A short list of decisions we make on every project, because they are the ones that decide what maintenance costs two years in.
Sign-in, permissions, file storage and configuration are built once into a core that every system inherits. Correct something in one place and all of them pick it up, instead of the same fault being repaired separately in each one.
Access is granted one action at a time, not by job title. Someone on support can reset a customer password without also getting the reports, the settings, or the ability to change who else has access.
Publishing an update is one automated step, not a manual procedure run late at night. Every previous release stays on the server, so if a change looks wrong we switch back to the last working one straight away instead of repairing it live.
Anything solved once for one client is built so the next project can begin from it rather than from nothing. It is the same reason our own products share one foundation.
Sign-in, permissions, file storage, configuration and email are not rebuilt per project. They are two libraries every product installs as a dependency, so a fix made once reaches every system we run for you.
What we build with
Core foundation
com.revolop:revolop-sharedMaven@revolop/sharednpmA fix in a core package lands once and every deployment inherits it on the next release.
Get in touch
A short description of the problem is enough to start. We will come back with what we think it takes: scope, sequence and the parts we would push back on.