I build custom software
people actually open every morning.

Custom software solutions from Kathmandu. I work with companies to ship systems end-to-end — database, backend, frontend, auth, deployment — designed around how their teams already work. Open to remote work worldwide.

Internal ToolsSoftware SolutionsFull-Stack DevelopmentData Systems
No more: Monday reporting drills · Manual repetitive work · Spreadsheet sprawl

How I got here

I came into development from a data analyst background. I spent two years cleaning messy datasets, writing SQL and Python, and making dashboards for teams that didn't have a technical person in the room. That's where I learned the hardest part of a data system isn't the code — it's understanding what people actually do with their data.

Since February 2025 I've been the sole developer at a multi-branch education company in Kathmandu that processes around fifteen thousand student leads a year. Three production systems so far — database, backend, frontend, auth, deployment, all of it. The analysis work hasn't stopped either. Alongside the builds, I still run company-wide Power BI reporting and cross-branch data cleanup for teams that still don't have a technical person in the room.

The thing that separates tools people use from tools they ignore isn't the code. It's whether you understood the workflow before you started building. The system I'm most proud of isn't the most complex one. It's the one people open every morning because it solved a problem they'd given up complaining about.

Understand first. Build once.

01

Sit with the problem

Shadow the people who'll use the tool. Ask what's painful, what they've already tried, what they're quietly working around. The real problem is rarely the one stated in the meeting.

02

Design around the workflow

The best system is the one that fits habits people already have. If a spreadsheet works, build around the spreadsheet. If the workflow is broken, redesign it — but do that honestly, not by hiding it behind a new UI.

03

Ship end-to-end

Database, backend, frontend, auth, deployment. Owning the whole thing means the seams line up and the decisions are consistent. One person's context beats five people's handoffs.

04

Live with it

A tool isn't done at launch. I stay on it — watching what people actually click, what they ignore, what breaks when data gets weird. That's where v2 comes from.

What I work with

Languages

PythonTypeScriptJavaScriptSQLHTMLCSS

Backend

FlaskNode.jsExpressPrismaREST APIsGoogle Apps Script

Frontend

React 18TypeScriptViteTailwind CSSVanilla JS (IIFE modular)Chart.js

Databases

PostgreSQL (CTEs, timestamptz)MySQLGoogle Sheets API

Auth & Security

Microsoft SSO (MSAL)Google OAuth 2.0PyJWTRole-Based Access Control

Deployment & DevOps

Windows Server 2019IISCloudflare TunnelPM2WaitresscronRenderDigitalOcean

Data & Tooling

PandasgspreadopenpyxlSheetJSGit/GitHubPower BI

Currently open to remote roles.

Full-time or contract. Comfortable with most timezones from Kathmandu (UTC +5:45). The fastest way to reach me is email.