We are a software company that designs, builds and runs systems for institutions — schools, clinics, community organisations and the businesses around them. We start from the process that currently runs on paper, and replace it with something people actually trust.
Students
1,240
Present
1,186
Due
৳42,500
Attendance this term
LiveWe take on the whole job — understanding the process, designing it, building it, and keeping it running once real people depend on it.
Taking a product from an idea and a manual process to something running in production, with the same approach we use on our own.
Learn moreDashboards, portals and internal tools — the systems an organisation runs its day on rather than its marketing.
Learn moreApplications for the people who are not at a desk — guardians, patients, members, field staff.
Learn moreDesign that starts from the record and the task, not from a template. The same design system discipline behind our own products.
Learn moreConnecting a new system to the ones already in place, including the ones nobody documented.
Learn moreThe unglamorous half of software. We run our own products, so this is not a separate department.
Learn moreSchools, clinics, community institutions and the businesses around them — places where the day depends on a register being right.
Admissions, attendance, results, fees and guardian communication.
Chamber schedules, serials, queues and appointment coordination.
Profiles, health history, vaccination schedules and reminders.
Student and teacher records, attendance, fees and notices.
Destination discovery, community posts and recommendations.
Members, meal counts, grocery spend and monthly accounts.
Student records, tuition income, dues and reporting.
These are the sectors we know best because we operate in them. The approach works anywhere a process still runs on paper.
Start with a conversation
Show us the register, the spreadsheet or the notebook. We will tell you honestly whether software helps — and whether we are the right people to build it.
Most of the tools built for schools, clinics and community institutions assume a full-time IT department. Ours do not. We want the systems we build to be usable by the person who is already doing the job — the office assistant, the chamber attendant, the mess manager — on the device they already own.
Every product we build targets a process that currently runs on paper or memory: an attendance register, a serial queue, a monthly meal count, a tutor's notebook. Our job is to make the digital version genuinely better than the paper it replaces — faster to fill in, harder to lose, and trusted by everyone who depends on it.
Take each product from working to genuinely dependable before widening its scope. A module an institution relies on daily is the only real measure of progress.
Consolidate the half that every product repeats — identity, roles, notices, billing — into a shared layer, so each new product starts further along than the last.
Bangla-first interfaces, low-bandwidth tolerance and mobile-first flows, because that is the reality of the institutions these systems are for.
Everything we ask an institution to trust, we already run ourselves. That is the difference between a studio that ships and one that stays.
We build and operate 7 software platforms of our own, across 7 sectors.
See what we run
Design, engineering and running it in production sit with the same team. Nothing important is handed to someone whose name is not on it.
No invented client counts, no borrowed logos, no numbers we cannot evidence. If a product is still in development, the site says so.
Support, migrations and maintenance are part of the product, not a separate contract signed later.
Before a schema exists we sit with the register, the ledger and the whiteboard. The software has to win on the paper's own terms.
No methodology branding. This is the sequence we actually follow.
We look at how the work is done today — the forms, the workarounds, the person who remembers everything.
We define the record first. What must be captured, by whom, and what it has to be true of.
A narrow, working slice goes into real use early, rather than a broad demo that impresses nobody who uses it.
We keep it running — monitoring, fixes, migrations, and the training that makes it stick.
One team that designs, builds and runs everything here — the same people from the first conversation through to production support.
Whether you run an institution, a chamber, a mess or a tuition batch — if one of these worlds is your problem, we would like to hear how you handle it today.
