Key highlights
- A one or two page brief makes agency quotes comparable and shows which firms ask the right questions.
- Verify registration and PAN, meet the engineers, and call past clients before you trust a portfolio.
- Because Nepal's Copyright Act lists computer programs as protected works, the contract must clearly assign code, designs and documents to you.
- Keep repositories and cloud, domain and app store accounts in your own name from day one to avoid vendor lock-in.
- Agree on a written support agreement with response times before launch, not after the first outage.
Choosing the wrong software partner is expensive in ways that never appear on the first invoice. The app launches late, the code is hard to change, the original developers leave, and when you ask for the source code you discover it was never really yours.
Finding a software development company in Nepal is not the hard part. Kathmandu has plenty of them, from two person studios to firms with large teams serving foreign clients. The hard part is telling the strong teams apart from the ones that pitch well and deliver poorly, before you have signed anything.
This guide gives business owners, school and hospital managers and startup founders a practical checklist: how to prepare a brief, review portfolios, judge a tech stack, protect your code with an NDA and contract, sanity check timelines and budgets, and agree on support after launch.
Choose a software company in Nepal by checking evidence, not promises. Verify its registration, review live projects and talk to past clients, meet the people who will build your product, and insist on a contract that gives you the source code, accounts and documentation. Then tie payments to working software and sign a support agreement for after launch.
- Verify registration and PAN before you sign
- Judge portfolios by live products and client calls
- Own the source code, repositories and accounts
- Tie payments to demos of working software
- Put support and maintenance terms in writing
Start with a clear brief before you contact agencies
Agencies can only quote what you describe. A one or two page brief makes quotes comparable and quickly shows you which firms ask good questions.
- The problem: what the software should achieve for the business, in one paragraph.
- Users: who will use it, on which devices, and roughly how many.
- Must have features for the first release, kept separate from nice to have ideas.
- Integrations: payment gateways, accounting software, SMS, existing databases.
- Constraints: deadline, budget range, languages and any rules you must follow.
If the scope is still fuzzy, pay for a short discovery phase first. A good agency will help you cut the first version down to something you can test with real users, as explained in our guide on how to build an MVP.
A shortlisting checklist for software companies in Nepal
Start with five to eight firms from referrals, people you know and search results, then cut the list to three with these checks.
- Legal registration: a registered company with a PAN. You can look up a PAN on the Inland Revenue Department website.
- A real team: visit the office if you can, or ask for a video call that includes engineers, not only sales.
- Relevant experience: projects of similar size and type, not just a long list of logos.
- References: at least two past clients you can call.
- Communication: timely replies and questions that show they actually read your brief.
- Process: how they plan sprints, test, deploy and report progress.
| Area | Green flag | Red flag |
|---|---|---|
| First call | Asks about your users, goals and constraints | Quotes a price before understanding the scope |
| Team | Introduces the developers who will do the work | Only a salesperson, with the team named after signing |
| Estimate | Phases, assumptions and exclusions listed | One number with no breakdown |
| Code ownership | Repository in your account from day one | Code handed over only at the end, if at all |
| Testing | Explains code review, automated tests and staging | Testing means the developer clicks around |
| Support | Written agreement with response times | Just call us if anything breaks |
- 1
Write the brief
Problem, users, must have features, integrations and constraints on two pages at most.
- 2
Build a long list
Collect five to eight firms from referrals and search, and send each the same brief.
- 3
Shortlist three
Apply the checklist above and drop firms that miss basic checks or reply vaguely.
- 4
Meet the team and call references
Talk to the engineers and to at least two past clients of each finalist.
- 5
Compare proposals line by line
Look at scope, assumptions, team, timeline, payment terms and support, not only the total.
- 6
Start with a small paid phase
Begin with discovery or one feature before committing to the full build.
How to review a software company's portfolio properly
Portfolios are marketing. Treat them as a starting point for questions, not as proof.
- Open live products on your phone. Check speed, design consistency and whether forms and payments actually work.
- Ask what the agency built: the whole product, only the design, or one module.
- Ask whether they still maintain the product, and if not, why the relationship ended.
- Call past clients and ask about deadlines, communication and what happened when things went wrong.
- Ask for a short screen share of a real repository or a code sample with client details removed.
Questions worth asking in the first meeting
- Who exactly will work on my project, and what else are they working on?
- What would you build first, and what would you leave out of version one?
- What is the biggest risk you see in this project?
- How will I see progress each week?
- What happens if a key developer leaves your company mid-project?
Strong teams answer these directly and often push back on parts of your plan. Vague answers, or agreement with everything, tell you just as much.
Be careful with portfolios full of famous logos and no detail. A smaller portfolio with clear explanations of the problem, the solution and the agency's exact role is usually more trustworthy.
Choosing a sensible tech stack
You do not need to be a developer to judge a tech stack. Ask the agency why it recommends its choice, and what would happen if you later moved to another vendor.
- Mainstream and well supported: widely used tools such as React, Next.js, Node.js, Python with Django or FastAPI, and PostgreSQL are easier to hire for later.
- Matched to the product: a content website, a SaaS dashboard and a real-time chat app need different tools.
- No unnecessary lock-in: avoid custom in-house frameworks or proprietary platforms that only one vendor can maintain.
- Clear licensing: paid libraries and services should be listed, along with who pays for them.
Also ask whether you really need native mobile apps on day one. For many Nepali businesses, a fast mobile friendly web app reaches users sooner and costs less, and native iOS and Android apps can follow once usage proves the need. A good agency will explain this trade off honestly, even when the larger build would earn it more.
Lock-in is not a theoretical risk. In August 2026 the Kathmandu Post reported widespread crashes across government systems, and noted that because the national ID platform is closed-source, the government does not own its source code or database design. Private businesses face the same problem on a smaller scale when a vendor holds the only copy of the code. Our guide to the best tech stack for startups explains common choices in more detail.
NDA, contract and source code ownership
Sign a simple mutual NDA before sharing detailed business plans, internal documents or sample data. An NDA protects confidential information, but it does not decide who owns the code. That belongs in the main contract.
Nepal's Copyright Act, 2059 (2002) lists computer programs as protected works, according to the text published on WIPO Lex. Since software is a protected work, do not leave ownership to assumption. Your contract should spell it out.
- Source code, designs, database schema and documentation transfer to you, usually as each milestone is paid.
- Code lives in a Git repository in your organization's account, with the agency added as members.
- Cloud, domain, email, app store and payment gateway accounts are registered to your company.
- Third-party and open source components are listed with their licences.
- The agency may reuse its general know-how and generic libraries, but not your business logic or data.
- Handover covers documentation, credentials and an agreed number of knowledge transfer hours.
This section is general guidance, not legal advice. For larger projects, ask a lawyer to review the contract, especially the IP, liability, termination and dispute resolution clauses.
Timelines: how to tell if a schedule is realistic
Unrealistic timelines usually come from skipped steps, not slow developers. A credible plan includes discovery, design, development in short sprints, testing, user acceptance and launch support.
- A complex app promised in a few weeks with no discovery phase.
- No time set aside for testing, app store review or content entry.
- Every feature delivered at the very end instead of in visible steps.
- No mention of who on your side approves designs and features, or how quickly.
Ask for a demo of working software every one or two weeks. That single habit exposes delays early, while they are still cheap to fix. Also plan around Dashain and Tihar, when many teams in Nepal take extended leave.
Budgets and payment terms
Quotes for the same brief can vary widely between agencies, because each assumes different scope, quality, testing and support. Compare the breakdowns and assumptions, not just the totals.
- Fixed price suits well defined work, with a written change request process.
- Time and materials suits evolving products, with timesheets and a monthly cap.
- Milestone payments should follow demos of working software, after a modest advance.
- Inclusions such as design, QA, project management, hosting setup, VAT and post-launch support should be stated, not assumed.
The biggest cost drivers are usually the number of user roles, the number of screens and workflows, integrations with outside systems, whether you need web and mobile apps, and how polished the design must be. Cutting one integration or one user role from version one often saves more than negotiating the rate.
For typical price drivers on Nepali projects, see our guide to website development cost in Nepal.
Hold back a small final payment until a short warranty period after launch has passed, for example 30 days, so bugs found by real users are fixed as part of the project rather than billed as new work.
Quality and security standards to ask about
Ask how the agency prevents bugs and security holes, not only how quickly it fixes them.
- Code review on every change by a second developer.
- Automated tests for important business logic, and a staging environment where you approve features.
- Security practices checked against the OWASP Top 10, which OWASP calls the reference standard for the most critical web application security risks. The current edition is the 2025 list.
- API keys and passwords kept out of the code and stored in secure environment settings.
- Backups, logging and uptime monitoring set up before launch, not after the first incident.
Support and maintenance agreements after launch
Software needs care after launch: security updates, server maintenance, bug fixes and small improvements. The same Kathmandu Post report found that government contracts are regularly awarded without binding service-level agreements, and noted that offices may now allocate up to 20 percent of a system's initial cost for annual maintenance. The lesson for private projects is simple: agree on support before you need it.
- Response and fix times by severity, such as hours for a site outage and days for a minor bug.
- Uptime target and monitoring if the agency hosts the system.
- What is covered: bug fixes, security patches, dependency updates and backups.
- What costs extra: new features, design changes and third-party fees.
- Monthly hours or a retainer, with a clear rule for unused hours.
- An exit plan describing the handover if either side ends the agreement.
Security and maintenance go together, because most breaches exploit software that was never updated. Our guide to web application security best practices explains what ongoing care should include.
Conclusion: choose evidence over promises
The right software partner is rarely the cheapest firm or the one with the slickest pitch. It is the one that asks good questions, shows real work, introduces its engineers, gives you your code from day one and puts testing, timelines and support in writing. Use the checklist above with every shortlisted company, start with a small paid phase, and you will know quickly whether the partnership works. If you are planning a project now, send your brief to Brahmabyte Lab and our team will help you think it through, whether or not you end up working with us.
Frequently asked questions
Ask for its company registration details and PAN, and check the PAN on the Inland Revenue Department website. Visit the office or hold a video call with the engineers, not only sales staff. Finally, call at least two past clients.
Ownership should be set out in the contract, so do not assume it. Include a clause that transfers source code, designs, database schema and documentation to you on payment. Keep the Git repository in your own account so you always have the latest code.
A simple mutual NDA is sensible before you share detailed plans, internal documents or sample data. It protects confidential information but does not settle who owns the code. Ownership belongs in the main development contract.
Not on price alone. Quotes for the same brief vary because firms assume different scope, quality, testing and support. Compare the breakdowns and assumptions, and remember that rework on poor code usually costs more than the savings.
It should define response and fix times by severity, what is covered such as bug fixes and security updates, and what costs extra such as new features. If the agency hosts the system, add an uptime target and monitoring. Include an exit plan for handover.
It depends on scope, but a credible plan always includes discovery, design, development sprints, testing and launch support. Be cautious of complex apps promised in a few weeks with no discovery phase. Ask for demos of working software every one or two weeks to track real progress.
Sources and references
- Widespread server crashes point to Nepal's digital state failure, The Kathmandu Post
- Copyright Act, 2059 (2002), Nepal, WIPO Lex
- OWASP Top 10, OWASP Foundation
- PAN search, Inland Revenue Department, Nepal
Cover photo by Smartworks Coworking
Stay in the loop
Get our latest guides on software, SaaS and growth delivered to your inbox.
By subscribing, you agree to get updates from Brahmabyte Lab. You can unsubscribe any time.


