About me
What to build, in what order, and who should decide how. Then making sure it gets delivered well.
I started in 2013 as a frontend engineer at agencies, close to the implementation. Working with companies and teams across Nepal, Europe, Australia and the United States taught me how much good delivery depends on understanding the context around the code.
Most software goes wrong in the first few decisions: the wrong scope, the wrong priorities, the wrong order. That is the part of the work I care about most. What does the business actually need? Which constraint matters most? What can the team realistically maintain?
My job is to make sure those questions get asked early, while there are still options, and answered by the right people. I own the scope, the plan, the priorities and the client relationship. My senior engineers own the deep technical design.
Two companies: the engineering company behind the work, and the product we built for a problem at home.
A team in Kathmandu building web platforms, connected devices, data systems and AI. They shape the solution, challenge assumptions and carry the work through delivery and long after launch.
ERP vendors, software companies and other subscription-heavy businesses had nothing meaningful to bill on. SUQO runs the whole cycle, from sign-up to renewal, and orchestrates collection across Nepal’s payment providers.
Running my own product keeps me honest about trade-offs: I see them from the owner’s side too.
I remain curious about new technology and what it makes possible. But I want to know why we should use it, what it will cost to maintain, and who will be responsible for it once the initial excitement has passed.
What working together has been likeA 20-minute call, no preparation needed. Tell me what you are trying to achieve and where things stand.
Book a 20-minute call