Skip to content
All articles
Business7 min read

How to choose a software development company in Nepal

How to choose a software development company in Nepal: check registration, open their live work, meet the builders, and get ownership and changes in writing.

EK

EK Ra Sunya team

EK Ra Sunya Inc.

To choose a software development company in Nepal, check five things before you compare prices. Is it a registered company you can look up? Has it shipped live work like yours that you can open and use? Who will actually build your project? What will you own at the end, in writing? And how does it handle changes, testing and support after launch? Price comes last, and only between companies quoting the same written scope.

Most "top software companies" lists won't answer any of that. They are a place to find names, not a way to choose between them. Before you trust a ranking, check who published it and whether they appear on it themselves.

Here is how to check each point yourself, in about a week, without needing to read code.

Is it a registered company you can look up?

A company that will hold your code, your data and possibly your app store listing should exist on paper. Ask for its full registered name, its company registration number and its PAN, and check them yourself.

The Office of the Company Registrar runs a public company data portal where registered companies can be looked up. The Inland Revenue Department has a public PAN search. If the name on the quote, the name on the registration and the name on the invoice don't match, ask why before you pay anything.

A freelancer or a small team without a company isn't automatically a bad choice. But you should know which one you are hiring, because it changes who signs the contract and who you can hold to it.

Have they shipped something like your project?

Ask for live work, not screenshots. A website you can visit, a web app you can sign in to with a demo account, an app you can install from Google Play or the App Store. Then use it on your own phone, on mobile data, for ten minutes.

Look for work close to yours in kind, not just in industry. A team that has built a booking system or a records system with user roles has solved problems a brochure website never raises. A long portfolio of marketing sites tells you little about whether they can build the admin panel your staff will use every day.

Then ask to speak to one past client, and ask that client two questions: did the project finish close to the agreed scope and date, and is the company still around when something breaks?

Who will actually build it?

The people in the sales meeting may not be the people who write the code. Ask by name who will lead the project, who will build it and who will test it, and ask to meet the lead before you sign.

Ask what happens if that person leaves halfway through. A good answer involves code in a shared repository, written documentation and a second person who already knows the project. "Don't worry, we have many developers" isn't an answer.

If you are weighing a dedicated team against a fixed-scope project, that choice also changes who you manage day to day. Settle it before you compare companies, because the two models are quoted and run differently.

What will you own when it's finished?

Ownership is easy to skip at the start and hard to fix later. Get these in the contract, in your company's name:

  • The source code, in a repository your company controls, with access from day one, not handed over at the end.
  • The domain name and the accounts for any paid service the software depends on.
  • The app store accounts, if there is a mobile app. Apps can be moved between developer accounts later; Google documents how to transfer an app to a different Play developer account, and both accounts must be registered and active. It is still simpler when the listing starts in your name. Our post on who should own your app store accounts covers the trade-offs.
  • The data, with a way to export it in a standard format if you ever leave.

At EK Ra Sunya, if a client's app was published under our Play or App Store account, we transfer it to the client's own account free, on request. Whoever you hire, get the equivalent promise in writing.

How do they handle changes?

Every project changes after it starts. What matters is whether the process is written down. Ask to see it.

A fair process has three steps: the change is requested in writing, the company replies with the time and cost it adds, and nothing is built until you approve. That is how we run change requests, and our post on change requests in fixed-price projects explains why each step protects both sides. Be wary of a quote that promises "unlimited changes", because someone pays for them, and it is usually the timeline.

How do they test and secure what they ship?

Ask who tests the software and what they test against. A good answer names a person or role, describes testing on real devices, and gives you a sign-off step of your own before launch. Our user acceptance testing checklist shows what that sign-off should cover.

For security, you don't need to judge their code. Ask which standard they build and test against. The OWASP Application Security Verification Standard is an open framework of security requirements for web applications and services, and a company that works to it, or to something like it, will know what you mean when you ask. If the answer is only "our code is secure", ask again.

What happens after launch?

Software needs looking after once it's live: bug fixes, security updates, operating system and browser changes, and the small improvements users ask for. Ask, in writing:

  • How long is the free bug-fix period after launch, and what counts as a bug?
  • What does ongoing support cost, and what does it include?
  • How do you report a problem, and who replies?
  • What recurring costs will you pay to third parties, such as servers, app store fees or paid APIs?

How do you compare the quotes?

Only compare quotes for the same written scope. Write down what you need first; our guide to what to write before asking for a quote gives a template. Send the same document to every company.

Then read each quote line by line: what is included, whether VAT is in the number or on top of it, what recurs every year, and what is left out. Our post on how to read a software development quote in Nepal walks through each of those.

CheckWhat to ask forA good sign
RegistrationRegistered name, registration number, PANThey match the public records and the invoice
Live workLinks, demo logins, store listingsYou can use it yourself, today
TeamNames of the lead, builders and testerYou meet the lead before signing
OwnershipCode, domain, accounts and data termsAll in your company's name, in the contract
ChangesTheir written change processRequest, estimate, approval, then build
Testing and securityWho tests, and against what standardA named role and a named standard
SupportBug-fix period, support terms, recurring costsWritten answers with numbers

Frequently asked questions

Should I choose the cheapest software company in Nepal?

Not on price alone. A lower quote often covers a smaller scope, leaves out recurring costs or treats every change as extra. Compare quotes only for the same written scope, then compare what each one includes.

Is a big company safer than a small one?

Not necessarily. Size matters less than whether the company is registered, has shipped similar work you can open, names the people on your project and puts ownership in writing. A small team that passes those checks is a safer choice than a large one that doesn't.

Can I hire a Nepal software company from abroad?

Yes. The checks are the same, and the ownership and support terms matter more because you can't visit the office. Agree on meeting times and release days before you start; EK Ra Sunya, for example, works Sunday to Friday, 9:00 AM to 6:00 PM Nepal time (GMT+5:45).

How long should choosing a company take?

Long enough to run the checks above with two or three companies. Asking for registration details, opening their live work and speaking to one past client each takes days, not months.

Talk to us

If you are comparing software companies in Nepal, include us in the comparison. Send us your written scope and ask us every question on this page; we would rather answer them before you sign than after. Request a software project consultation.

Have a project in mind?

Let us help you build something scalable, fast, and built to last.

Start a conversation