SoftwareDevelopmentCaseStudiesfromNepal
Real projects. Real users. Measurable outcomes. These case studies document the technical challenges I solved, the architectural decisions I made, and what the finished product delivered — for clients in Nepal and worldwide.
Why this matters
What Case Studies Reveal.
A portfolio of screenshots tells you what something looks like. A case study tells you how it was built, why specific decisions were made, what went wrong and how it was fixed, and what the outcome was.
“For clients evaluating a software developer, case studies are the closest thing to a reference that scales.”
Each project documented here is a production system with real users — not a side project or coding challenge. All 8 are here rather than a curated shortlist, because a portfolio that only shows its best work tells you nothing about the rest of it. Between them they cover mobile apps, web backends, AI systems, real-time features and offline-first field tools.
Every one names the year it was built, the stack, my role, and what the finished thing measurably did. Where a number has not been confirmed, the page says so instead of estimating — you can read how the work actually runs and what the clients said alongside them.
Projects Documented In Full
Apps Live on App Stores
ML Model Accuracy
Active App Users
All projects
Case Studies.
What to look at next
Read The Work, Then Read The Terms.
How an engagement runs
The six stages from your first message to launch, the weekly and fortnightly cadence, which tools we work in, and how many hours of the day overlap with the UK, Europe, the US and Australia.
How I work →What it costs
Fixed-price, hourly and retainer models with real starting figures, plus indicative budgets and timelines for the kinds of project on this page.
Pricing & engagement models →Who you would be hiring
One developer, working directly with you. Background, technologies, and the clients who have said something about the work.