Ujwol Shrestha

Available for new projectsKathmandu, Nepal

AI can build a website. I build the solution behind it.

I'm Ujwol, a software developer in Kathmandu. I build custom websites, dashboards and web applications around the way your business actually works, not around a template.

Or chat on WhatsApp(opens in a new tab)
projects built
12
on production software
Since ’25
Example: what one “simple” order form actually has to do. When a customer places an order, the system checks the details, saves the order, notifies the owner, confirms with the customer and updates the dashboard.
  • React
  • TypeScript
  • Next.js
  • Node.js
  • Java · Spring Boot
  • PostgreSQL
  • pgvector
  • Supabase
  • Tailwind CSS
  • Electron
  • Python · FastAPI
  • Gemini API
  • Docker
  • MongoDB
  • GSAP
  • SQLite
  • Android
  • Unity

Selected work

Real projects, explained properly.

Client work, a product, production software and the projects that got me here. Open any of them for the full story.

Experiments, practice projects and everything else I've built lives on GitHub.

What I build

From a proper website to the tools your team uses every day.

Everything starts the same way: with a real problem, not a feature list. This is the kind of work I take on.

Business Websites

A fast, clear website that explains what you do and makes it easy to contact you, book or order. Built mobile-first, because that's where your customers are.

Service businesses · Shops · Landing pages

Discuss a project like this

The approach

Yes, I use AI. Every day.

It makes me faster, and that speed goes straight into your project. But AI doesn't know your customers, your edge cases or your constraints. Deciding what to build, and making sure it's reliable, secure and maintainable, is still the job.

AI speeds up

  • Writing boilerplate and UI faster
  • Drafting queries, tests and docs
  • Trying out approaches quickly
  • Catching mistakes earlier

I stay responsible for

  • Understanding your problem and how you work
  • Deciding what should (and shouldn't) be built
  • Data, security, integrations and edge cases
  • Testing, deploying and keeping it running

From first conversation to working software.

Four steps. You see progress the whole way through.

  1. 01

    Understand

    We talk about your business, the problem and how things work today. I ask a lot of questions, especially about the messy parts.

    You getA short written summary of the problem and what success looks like.

  2. 02

    Plan

    I work out what actually needs to be built, cut it down to a focused first version and propose how to get there.

    You getScope, timeline and a quote, agreed before any building starts.

  3. 03

    Build

    I build in small steps and connect what's needed: databases, payments, email, the tools you already use.

    You getRegular updates and a preview link you can click through.

  4. 04

    Launch

    I deploy it, test it with real data, fix what comes up and walk you through everything.

    You getA live, working system, plus a handover so you know how it all works.

Ujwol Shrestha in sunglasses, sitting at a wooden table, in black and white

Kathmandu, Nepal

About

Hi, I'm Ujwol.

I'm a software developer from Kathmandu in the final year of my BCA. Day to day, I work on the frontend of a production AML/KYC application in React and TypeScript: complex forms, data tables, reporting screens and the careful debugging you need when real businesses depend on the software.

Beyond the frontend I build with Java and Spring Boot, PostgreSQL and REST APIs, and I've shipped AI features like retrieval-augmented generation. AI tools make me faster, but the part I care about is the part they can't do: understanding the problem, and building something that keeps working after launch. You work directly with me, from the first conversation to handover.

  1. Jan 2026 – nowFrontend Developer (Full-Time)Datum Systems
  2. 2025Frontend Developer InternDatum Systems
  3. NowBCA, final yearKathmandu
  • React
  • TypeScript
  • Next.js
  • Java & Spring Boot
  • PostgreSQL
  • Node.js
  • Electron
  • Gemini & LLM APIs

Have a problem to solve?

Tell me about your project.

No technical brief needed. Tell me what you're trying to achieve, or what you're still doing by hand. I'll help you work out what makes sense, including whether you need software at all.

A good first message can be as simple as

What happens next

  1. 1

    I read your message and reply with questions, or a time to talk.

  2. 2

    We talk it through, by call or chat, whichever suits you.

  3. 3

    You get a clear proposal: what I'd build, how long it takes and what it costs.

Project type *

What are you doing today, what's not working, and what would “done” look like?

* Required. I only use your details to reply to you.