How to validate a SaaS idea from Nepal before you build

To validate a SaaS idea from Nepal before writing code, prove three things in order: the problem hurts, people will hand over contact details to fix it, and at least a few will pay before the product exists. Interviews, a landing page and a pre-sale test all three for a few weeks of effort. The Nepal-specific catch is getting paid from abroad, and you should solve that before launch, not after.

This guide is for Nepali founders building for customers overseas, at home, or both. It covers why products die, the cheap tests that catch the fatal flaw early, how to price, and the unglamorous plumbing of cross-border payments. If you're an agency thinking about your first product, our earlier piece on moving from outsourcing to products sets the scene.

Why do most startups actually fail?

The number everyone quotes is 42%. That came from an older CB Insights review of 101 startup post-mortems, where 42% listed "no market need" among their reasons for failing. CB Insights refreshed the study in March 2026 with 431 venture-backed companies that shut down since 2023. In the new data, 70% ran out of capital and 43% cited poor product-market fit.

Read those figures with care. They come from founders explaining their own failures, so they're self-reported. Companies list several reasons, so the percentages add up to more than 100. And the sample is venture-backed companies, mostly in the US, not bootstrapped Kathmandu teams. Still, the pattern holds. Running out of money is usually the symptom. Building something too few people wanted is often the cause, and it's the one cause you can test cheaply before you spend.

What are the cheapest ways to test demand?

Each method below buys a stronger signal than the last, and each costs a bit more. Run them in order and stop when the answer is clearly no.

• Problem interviews: 15 to 20 conversations with people who have the problem. Ask about the last time it happened and what they did, never whether they'd like your idea.
• Landing page and waitlist: one page describing the outcome, a price, and an email field. Traffic comes from the communities where your interviewees hang out, or a small paid test.
• Concierge or manual MVP: deliver the result by hand, with spreadsheets, forms and email, for a handful of customers. You learn the workflow before you automate it.
• Pre-sales and smoke tests: ask for money, a deposit or an annual plan at a founding discount, before the product exists. Refund anyone you can't serve.

Should you price in USD or NPR?

Price in the currency of the buyer, not the builder. If your customers are in the US, UK or Australia, charge in dollars, pounds or euros at a level that makes sense to them. A price that feels high in rupees can look cheap to a foreign team, and underpricing to match local salaries is the most common mistake we see. It also leaves no margin for payment fees and currency conversion.

If you sell inside Nepal, price in NPR and expect a lower ceiling and more hand-holding. Many local buyers prefer annual invoices or monthly bank transfers over card subscriptions. Some founders run both: a USD plan for export and a local plan paid through wallets. Keep them as separate products on the pricing page, not a hidden discount.

Can a Nepali company take card payments from abroad?

This is the hard part, and it trips up founders late. As of September 2026, Nepal is not on Stripe's list of countries where businesses can sign up. Even India is listed only as a preview. So a Nepal-registered company can't simply open a Stripe account and start charging cards.

The practical options are a merchant of record, a payout service for invoiced clients, or a foreign company. A merchant of record, such as Paddle or Lemon Squeezy, sells your software to the customer on its own paper. It handles the card, sales tax and VAT, and pays you out. Paddle's help centre says it works with software businesses anywhere except a listed set of unsupported countries, and Nepal is not on that list. Both Paddle and Lemon Squeezy list their fee as 5% plus 50 cents per transaction. Lemon Squeezy's own supported-countries page, when we checked, did not include Nepal among its bank-payout countries, and PayPal payouts are awkward to use from Nepal. Confirm with its support before you depend on it.

Payoneer suits a different shape of business. It's widely used by Nepali freelancers and agencies to receive invoiced payments and marketplace earnings, then withdraw to a local bank. It works for B2B customers who pay by invoice. It isn't a subscription checkout.

The heavier option is a foreign entity. Stripe Atlas forms a Delaware LLC or C-corp for a one-time $500, and Stripe says founders in most countries can use it. That gets you a Stripe account and a US bank relationship. It also brings US filing duties, registered-agent fees after year one, and Nepali rules about Nepali residents holding companies and money abroad. Get a Nepali chartered accountant or lawyer involved before you do this, not after.

What do NRB rules mean for export income?

Keep this general, because the details change and depend on your structure. Money earned from exporting IT services should come into Nepal through formal banking channels. In 2020, Nepal Rastra Bank simplified this, confirming that foreign currency earned from IT services could be received through bank accounts and converted to rupees within central-bank limits, as myRepublica reported. Banks report those receipts to NRB. That paper trail matters: it's what proves your revenue is export income when you claim tax treatment or talk to investors.

The 2083/84 budget added incentives for IT exports. We covered them in our budget breakdown, so we won't repeat them here. The point for validation is simple: route even your first pre-sale through a channel that leaves clean records.

What about selling to customers inside Nepal?

Domestic payments are the easy side. Khalti, eSewa and Fonepay QR cover most online buyers, and all three offer merchant integrations for websites and apps. Fees and setup charges are negotiated, so ask each provider for a current quote. For B2B software, bank transfer against a VAT invoice is still normal, and many buyers will expect it.

How does the validation pipeline actually work?

Treat it as a pipeline with a gate at each stage. Write one testable hypothesis: who has the problem, how often, and what they pay today to cope. Interviews test the problem. The landing page tests the promise and the price. The pre-sale tests willingness to pay. Only then do you scope the MVP, and you scope it to the smallest thing that serves the people who already paid.

The build itself should be boring. A static marketing page on a CDN, one web app, a managed database, sign-in, and a checkout from your payment provider that tells your app about payments through webhooks. That's enough for your first hundred customers.

What should you do this month?

• Write your hypothesis in one sentence and list 20 people who fit it.
• Book the interviews before you design a logo.
• Pick your payment route now. Open a Paddle account, or talk to an accountant about a foreign entity, before you promise anyone a checkout.
• Put a real price on the landing page. A waitlist with no price tells you very little.
• Ask for money. Five paid pre-orders beat five hundred signups.

We've seen this pattern in our own blueprints, from a SaaS MVP built in nine weeks to a marketplace that started as a concierge service. The build went fastest when the founder arrived with paying users and a narrow scope.

If you've validated an idea and want help scoping the first version, or want a second opinion on your payments setup, talk to us. Our Product Forge team builds MVPs for founders in Nepal and abroad.