Products
Three products carry our name rather than a client's. We fund them, build them, operate them in production, and get paged when they break — which is precisely why the client work is better.
The portfolio at a glance
| Product | Category | Sector | Revenue model | Market | Stage |
|---|---|---|---|---|---|
| KHEL | Consumer marketplace | Sports & recreation | Transactional | Nepal | Live |
| 1M Stay | B2B SaaS | Hospitality | Subscription | Nepal, US, then wider | In development |
| 1M Expedition | B2B SaaS · ERP | Travel & expeditions | Subscription | Nepal, US, and the global expedition trade | In development |
Scroll the table sideways →
KHEL
KHEL is our own product — a futsal venue booking platform for Nepal — designed, built, and operated in-house across web, mobile, and admin.
1M Stay
1M Stay is our own CRM for hotels — an independent product we design, build, and run in-house, so a property can hold every guest, enquiry, and booking in one place instead of spread across a WhatsApp thread, a spreadsheet, and the front-desk diary.
1M Expedition
1M Expedition is our ERP SaaS for trekking and expedition companies. We learned the domain the hard way — by mapping every department of a leading operator and building their ERP from scratch — and we are turning that into a product any trekking company can run on. Seven Summit Treks is the operator it is being built for first.
How a product gets into the house.
Usually inside a client engagement, or inside one of our own operations. Something is broken in a way that is clearly not unique to one company.
Not a template we resell — a product, with its own roadmap, its own architecture, and a team that owns it.
Every product is operated by us or with an operator close enough that we feel it break. The support inbox is the spec.
Shared infrastructure, shared components, shared operating discipline. What we solved once becomes the head start for the next one.
Why a services company builds its own software.
Read the long version →A slightly awkward admin flow is a backlog note on a client build. On our own product it is a member of our team doing something annoying forty times a week until it is fixed.
A studio that only builds to order gradually optimises for what is easy to sign off. Owning products means real usage, not an invoice, tells us whether the work was good.
1M Expedition exists because we mapped every department of one of the hardest operations in the trekking trade. That knowledge does not come from a brief.
To be the parent of a family of products — SaaS and non-SaaS alike — connected by one engineering spine into a technical ecosystem that works across borders.