About

Two kinds of work, one company

We started by building products we wanted to exist. HostelPalika came out of watching hostels run on registers and WhatsApp; QuestionCall came out of the same instinct applied to a different problem. Both are live, both are ours, and both pay for themselves.

Project work came second and stayed, because it turns out the two feed each other. Building for a client teaches you what a product should do; running a product teaches you what a client's system will look like in two years.

What we believe about software

Correctness is not a feature. Books that balance, invoices that number without gaps, payments that cannot be recorded twice — these are not extras to add later. They are the reason the software exists, and they belong in the foundations.

Boring choices age well. We prefer the database enforcing a rule to a comment asking people to remember it, and a smaller system that works to a larger one that mostly works.

Nepal is not an edge case. Bikram Sambat dates, eSewa and Khalti, wallet limits, a Sunday-to-Friday week, and the fact that nobody here can auto-debit a subscription — these shape the software from the start rather than being bolted on for a local release.

Where we are going

More products of our own, and enough project work to fund them. We would rather grow slowly and still be here in ten years.