I’m Ujjwal Rupakheti, a full-stack developer in Itahari who builds SaaS products in Nepal. I’ve built and launched SaaS products like Jhino, Eknas and Nimtto, so I build your first version with the whole business in mind: sign-up, plans, billing in rupees, dashboards, roles, backups and the marketing site.
01SaaS MVP
A SaaS MVP is the smallest version of your product that a real customer will pay for. It needs fewer features than most founders plan, but it can’t skip the basics: accounts, a plan and a way to pay, the one workflow that solves the problem, an admin view and a way to get help.
Not sure where your cut-off is? A free consultation call is often enough to agree what the first version needs.
02Proof
Three of my SaaS products are live with public pricing, each on a different model: monthly plans with a free tier, monthly plans per location, and one-time plans. The case studies show the pricing pages, the architecture and the trade-offs.
App publishing SaaS · Free tier, monthly upgrades
Upload an HTML file or ZIP and it goes live with sign-ins, sharing and live sync. One TypeScript program on Fastify 5 and SQLite, tested in Chromium, Firefox and WebKit.
Loyalty SaaS · Monthly plans per location
A customer wallet, a counter app and an owner dashboard for cafés, salons, gyms and shops, with rotating signed QR codes and a public API documented in OpenAPI 3.1.
Wedding invitation SaaS · One-time plans
52 animated designs with Bikram Sambat dates and RSVP per ceremony. Paid once by Khalti, eSewa or Fonepay QR in Nepal, or PayPal and card abroad on a separate international site.
Also built: RecruitFlowAn AI recruitment SaaS on Next.js 15 and Supabase, with a free plan and paid plans from NPR 299 a month for recruiters in Nepal.
Also worked on: PrishtaCAS and report card SaaS for Nepali schools, grades 1 to 10, priced per student per year, with 1,061 API tests against a real database.
Also built: SajilaiA vehicle rental marketplace for Nepal with desk software for rental businesses, monthly plans from NPR 1,500 and a 90-day free trial.
I saw a real problem in the Nepali market: online wedding invitations were made for Western weddings, not for ours. Ujjwal Rupakheti helped me bring my idea to reality. He built Nimtto with Nepali and English, Bikram Sambat dates and RSVPs for every ceremony, exactly the way I imagined it.
Businesses in Nepal rarely know who their regular customers are, or whether an offer actually brings anyone back. Ujjwal Rupakheti built Eknas to change that: a free wallet for customers, a counter app where staff record a purchase by phone number or QR code, and a dashboard where owners run offers and see results by branch. He understood the problem and built every part of it properly.
03Architecture
Multi-tenant means one application serves many customer accounts, and each account sees only its own data. For most MVPs the safest approach is one shared database where every record carries an account ID, filtered on the server for every query, never in the browser.
SELECT * FROM bills
WHERE account_id = $current
Cheapest to run and simplest to update. It suits almost every early SaaS.
A second check inside the database itself, in case application code ever forgets the filter.
The strongest separation, but it costs more and makes every update slower.
In Eknas, every shop is an account with branches and staff, and one permission model means a cashier, a manager and an owner see different data from the same screens. In Jhino, each customer’s app runs in a sandboxed iframe and reaches its own data only through a private handshake. The schema side of this is on my database design page.
04Billing
A SaaS sold in Nepal usually takes payment through eSewa, Khalti, Fonepay or bank QR and handles renewals and invoices itself, because Stripe doesn’t support businesses registered in Nepal. Customers abroad can pay by PayPal or card.
Renewal reminder sent
Paid, confirmed with Khalti on the server
Every payment is confirmed with the provider on the server and recorded exactly once. How I build those integrations is on my API and payment integration page.
05Included
Four areas: the product your customers use, the business tools you use to run it, the security that protects their data, and the marketing site that brings them in. Most items come straight from products I’ve already shipped.
The Growth column is where my SEO work comes in. For a product that needs to be found, see SEO in Nepal and my guide on how to do SEO in 2026.
06Process
A first version usually takes 6 to 12 weeks. We fix the scope and data model first, build in weekly releases you can click through, put the product in front of a few real users, and launch when payments and support work end to end.
Week 1: users, plans, the core workflow and the database design, in writing.
The main screens as a working link, so you can show early users.
Accounts, the core workflow, billing and admin, one release a week.
A small group of real customers uses it while I fix what they find.
Payments live, marketing site indexed, backups and monitoring on.
Founders abroad: we talk over video calls, email or WhatsApp, and I work on Nepal time (UTC+5:45).
07Pricing
With me, the first version of a SaaS product starts from NPR 70,000 and usually takes 6 to 12 weeks. The price depends on user roles, integrations and payment flows, and it is fixed in writing before the build starts. The calculator below prices each of those, line by line.
| Project | Starting price | Typical timeline |
|---|---|---|
| SaaS product, first versionAccounts, plans, payments, an admin console and the marketing site | NPR70,000 | 6–12 weeks |
| Larger SaaS productSeveral roles, integrations or a public API | After a paid discovery week | Released in stages |
| After launchFixes, new features, backups and monitoring | Monthly retainer | Optional |
Hosting, domain, email sending and any AI or SMS services are paid by you directly. For an early product on one server they are usually small, and SQLite on one server, as in Nimtto and Jhino, is often enough until real traffic arrives.
Building something simpler first? Websites start from NPR 18,000 and online stores from NPR 60,000 on my web developer in Nepal page. All prices are on my services page.
08Quotation
The first version covers sign-up, two customer roles with invites, one core workflow of up to 8 screens, plans with eSewa or Khalti, invoices and your admin console. Tick what your product needs on top, see the total and the payment stages, then download the quotation as a PDF or send it to me.
Each extra user role adds NPR 15,000 because it needs its own permissions, screens and tests; each extra payment method adds NPR 10,000 for the server-side check and the record that stops a payment counting twice, as I describe in my eSewa and Khalti integration guide. A product with several workflows is scoped in a paid discovery week instead. Running a simpler business online? Compare the static website, WordPress website and online store packages.
09Global
You can build a SaaS from Nepal for customers in Nepal, abroad, or both. For founders abroad I work as your full-stack developer on a weekly release schedule. For Nepali founders selling abroad, I add USD pricing, card payments and a separate international site.
Nimtto shows the second case: a Nepal site in rupees and an international site in USD with its own design range, kept apart with hreflang so Google shows each audience the right version. Founders abroad get contracts and invoices in USD, payment by bank transfer, Wise or PayPal, and an NDA if they want one. More on how I work on my software development page.
Cost, timelines, payments and ownership, answered before you ask.
Ask me on WhatsAppWith me, the first version of a SaaS product starts from NPR 70,000. The price grows with the number of user roles, integrations and payment flows: an extra role adds NPR 15,000, an extra payment method NPR 10,000 and a public API NPR 20,000. Hosting, domains and paid services such as email or AI APIs are billed to you directly, and founders abroad are quoted in USD. My guide on how to build a SaaS in Nepal covers scope, stack and billing in rupees.
Yes. Tick what your product needs in the SaaS cost calculator on this page and press “Download quotation”. You get a PDF with a quotation number, every line and its price, the payment stages, what isn’t included and the terms. Send it to me, and I confirm the scope on a short call before anything is fixed.
Most first versions take 6 to 12 weeks. The first week fixes the scope and the data model, and from then on you get a working link every week. Cutting the feature list is the fastest way to launch sooner, and larger products are released in stages.
Yes. Products I’ve built take payment through Khalti, eSewa, Fonepay and bank QR in Nepal, and PayPal or card for customers abroad. Plans can be one-time, monthly or yearly, with VAT invoices where you need them, and every payment is confirmed on the server.
Not directly, because Stripe doesn’t support businesses registered in Nepal. A Nepali SaaS usually takes eSewa, Khalti, Fonepay or bank QR and handles renewals and invoices itself, and adds PayPal or card for buyers abroad. Founders with a company registered abroad can use Stripe through that company.
Multi-tenant SaaS means one application serves many customer accounts, and each account sees only its own data. Almost every B2B SaaS needs it. For most MVPs I use one shared database where every record carries an account ID, and every query is filtered by it on the server.
Usually Next.js or React with TypeScript on the front end, Node.js with Fastify or Express on the server, and PostgreSQL through Prisma or Drizzle. For a small product on one server, SQLite is often simpler and cheaper. Everything runs in Docker behind Cloudflare.
Yes. After the final payment, the code, the repository, the domain and every service account are in your name. I hand over deployment notes and admin logins, and the product is yours to run, sell or hand to another developer.
Yes. I can build a product priced in USD with PayPal or card payments, or one product with a separate international site, as I did for Nimtto. For founders abroad, I invoice in USD and accept bank transfer, Wise or PayPal, and I’m happy to sign an NDA.
It launches ready for both: a server-rendered marketing site, structured data, a sitemap, hreflang and an llms.txt file, as on Nimtto and Jhino. Rankings still take content and time, so I can stay on for monthly SEO after launch if you want that.
Every project includes a free bug-fix period. After that, I can stay on for a monthly retainer covering fixes, new features, backups and monitoring, so the person who built the product keeps improving it. You can also take the code to another developer at any time.
Send a short note about your customers, the problem you solve and how you plan to charge. I reply within one working day with questions or a first estimate.
Ujjwal RupakhetiReplies within one working day
Where are you now?
Opens WhatsApp with your message started.
