Hiring a Software Team in Nepal: A Buyer's Guide

Disclosure: this guide is published by Lattice Nepal, a software studio in Bharatpur and Kathmandu. We sell the thing this page is about, so treat our judgement as interested and the sourced figures as checkable — every one is linked. Where a number is our estimate rather than a survey, we say so.

Nepal usually enters an offshore shortlist the same way: a Kathmandu firm quotes below what you pay in Bengaluru, Hanoi or Manila, and you want to know whether the number is real. It generally is. Whether it is a good trade depends on four things the rate card does not tell you — how many hours of your working day you can share, how deep the market runs above senior individual contributor, whether your IP assignment survives contact with Nepali law, and how money moves in and out. Every figure below traces to a named source; where no survey exists, that is said.

What Nepal costs next to India, Vietnam and the Philippines

There is one survey-grade public figure for this region. Accelerance's 2026 rates guide, from a survey of 60 development partners, puts Asia at USD 24–31 per hour for junior developers and USD 31–41 for seniors, about 8% below its 2025 figures (Accelerance). It publishes no country split, and Nepal has no rate survey of its own.

The country bands below are therefore derived, not measured: the Asia band is the spine, and each country is positioned against it on market structure — brand premium, employer competition, size of the exporting industry. Treat each as plus or minus roughly 20%, and any quote outside USD 15–55 per hour as something to explain.

Market	Rate basis	EF EPI 2025: score, rank of 123	UTC offset	Industry scale
Nepal	No public per-country survey	514, rank 58 (moderate)	+05:45, no DST	~100,000 in IT; 106 exporters in 2022
India	No public per-country survey; tier-1 firms quote well above	484, rank 74 (low)	+05:30, no DST	By far the largest of the four; the only true tier-1 option
Vietnam	No public per-country survey	500, rank 64 (moderate)	+07:00, no DST	Large, product-engineering weighted
Philippines	No public per-country survey	569, rank 28 (high)	+08:00, no DST	Large; best English of the four

The rate column is deliberately empty. Accelerance surveys Asia, not individual countries, and we could not find a survey-grade public source that splits these four markets by rate. Any per-country table you see — including one we could easily have written — is somebody's estimate presented as data. Use the Asia bands above as your reference point and make each vendor justify where they sit against them. If a quote falls outside roughly USD 15–55 per hour, ask why; that range is wide because the honest one is.

One more thing the table does not say out loud: India sits at UTC+05:30, fifteen minutes from Nepal. Every overlap conclusion in the next section applies to India almost identically, at comparable cost, with a far deeper market. If timezone is your main reason for looking at Nepal, it is not a reason to prefer Nepal over India.

English scores are from the EF English Proficiency Index 2025. Nepal sits in the moderate band, above Vietnam and well above India; the Philippines is in a different league, which matters if your engineers will be client-facing.

Where Nepal is better, and where it is worse

Better on price at the mid-market, because Nepali agencies compete with a smaller local employer set than firms in Bengaluru or Hanoi. That is structural reasoning, not a measured attrition figure.

Better on tax pass-through, part of why quotes look low. Nepali IT exporters earning in foreign exchange get a 50% concession on the standard 25% company rate — an effective 12.5% through FY 2084/85 — and service exports are zero-rated against a 13% general VAT rate (Baker Tilly Nepal, Tax Fact 2025/26). No VAT line on your invoice.

Worse on depth and optionality. Nepal's IT service exports were about USD 515 million in 2022, from 106 exporting companies and 66,509 freelancers (IIDS, via OnlineKhabar). Industry bodies estimate exports crossed USD 1 billion in 2025, with around 100,000 people in the sector and 90% of IT employment in Kathmandu (The Kathmandu Post). If your vendor fails the replacement list is short, and one bad week in Kathmandu hits every vendor on your shortlist at once.

Timezone: UTC+05:45, and what it does to your day

Nepal has run at UTC+05:45 since 1986 with no daylight saving (IANA time zone database). Its clock never moves, so overlap changes twice a year when yours does. The table assumes a Nepal day of 10:00–18:00 against 09:00–17:00 at your end.

Your day	Standard Nepal day	Shifted Nepal day	Verdict
Gulf (UTC+4)	7h 15m	7h 45m (11:00–19:00 NPT)	A shared day; best fit here
Europe (CEST / CET)	5h 15m / 4h 15m	6h 15m / 5h 15m (11:00–19:00)	Comfortable all year
UK (BST / GMT)	4h 15m / 3h 15m	5h 15m / 4h 15m (11:00–19:00)	Standup in the UK morning
Sydney (AEST / AEDT)	2h 45m / 1h 45m	3h 45m / 2h 45m (09:00–17:00)	Thin but real, your afternoon
US Eastern (EDT / EST)	None	2h 15m / 1h 15m (13:00–21:00)	Needs a shifted roster
US Pacific (PDT/PST)	None	None at any civilised hour	Needs a genuine night shift

Plainly: In northern-hemisphere summer, 09:00 in London is 13:45 in Kathmandu, 09:00 in New York is 18:45, and 09:00 in San Francisco is 21:45. In winter each shifts an hour later: 14:45, 19:45 and 22:45. The Gulf and Europe get a real working relationship, the UK a good one, Sydney a workable one if Nepal starts at 09:00. The US East Coast gets one to two hours, and only if you pay for a shifted roster and accept the retention cost. The US West Coast gets a handoff model — want that deliberately, or look elsewhere.

Two calendar facts catch buyers out. Nepal had 33 public holiday dates in 2026 — 28 distinct observances, several of which run over more than one day — including six consecutive days for Dashain, 17–22 October, plus a Tihar cluster in early November (Office Holidays). And the Labour Act 2017 sets 48 hours a week and one weekly day off (Labour Act, 2017). The single rest day is Saturday by long-standing national convention rather than by that statute, so it is not a two-day weekend. If you need Monday to Friday, write it in.

The talent pool, and where it runs out

The market is freelancer-heavy: 66,509 freelancers against 106 exporting companies in 2022. That ratio matters, because a "team" presented to you may be a coordinator plus contractors with no employment relationship to the entity signing your contract.

Nepal is deep in one band: PHP/Laravel, Node, Python/Django and .NET backends, React and Next.js front ends, React Native and Flutter mobile, commerce builds, QA. If your work is a web application or commerce platform or a cross-platform mobile app, supply is good. It thins fast in five places:

• Staff-plus engineers who have operated systems at scale — not "worked on a big project", but owned the pager for one.
• Platform and reliability engineering. Many deploy to AWS; few have run infrastructure, cost control and on-call as a discipline.
• Security engineering. Application security review and threat modelling are scarce.
• Native iOS at depth, and anything embedded.
• Data and ML engineering beyond calling a hosted model API, and product managers who run discovery rather than take dictation.

The pressure behind that thinness is emigration: the arbitrage that makes Nepal attractive to you makes remote Western contracts attractive to its best engineers.

Contracts, IP assignment and NDAs across a border

Nepal has been a WTO member since 23 April 2004, so TRIPS-level obligations apply — which says nothing useful about your specific code. Four clauses do the real work.

Present assignment, not a promise to assign. The vendor should "hereby assign" all rights in the deliverables, effective on creation. "Agrees to assign" leaves you needing a future signature from a company that may by then be dissolved.

Flow-down to every individual. The entity's assignment is worthless if the person who wrote the code never assigned anything to the entity. Require a warranty that every employee and subcontractor touching your work has signed an IP assignment and confidentiality agreement with the vendor.

Define deliverables to include what you need: source, full repository history, infrastructure-as-code, design files, credentials, and a licence inventory of every third-party component — plus a warranty on AI-assisted code.

Choose a forum you can enforce. A foreign court judgment is generally not directly enforceable in Nepal. An arbitral award is: Nepal acceded to the New York Convention on 4 March 1998, in force 2 June 1998, with the reciprocity and commercial reservations (UNCITRAL status list). Use your governing law, arbitration seated in a convention jurisdiction such as Singapore or London, and make the Nepali operating company — not an offshore shell with no assets — the counterparty.

On data: Nepal's Individual Privacy Act 2018 is not a GDPR-equivalent regime — no dedicated regulator with real enforcement, no mandatory breach notification — and Nepal is not on the European Commission's list of countries with an adequacy decision. EU or UK personal data needs Standard Contractual Clauses plus a processing agreement specifying real measures: named individuals with access, managed devices, no production data in development, deletion evidence on termination.

One tax trap: Nepal treats a non-resident providing services in Nepal for more than 90 days in any 365-day period as creating a permanent establishment, taxed as a resident entity with 5% on profit repatriation (Baker Tilly). Take advice before stationing your own staff there.

Getting money in — and the constraint on money going out

Inbound is straightforward. A SWIFT wire in USD, GBP or EUR to the vendor's Nepali bank is the default, converted to rupees on arrival; Wise also pays out to Nepali bank accounts in NPR. Do not assume a consumer wallet works — ask which channel the vendor receives on and test it with a small payment.

One inbound detail is a useful diagnostic. Where a Nepali individual not operating as a business receives foreign currency for software services provided outside Nepal, the bank deducts 5% at source (Baker Tilly). Payment instructions pointing at a personal account mean you are contracting with a person, not a firm — and the IP flow-down above cannot work.

The outbound constraint is the one nobody warns you about. Under the Unified Forex Circular 2081 as amended in April 2026, a foreign-currency-earning Nepali IT business may pay only up to USD 100,000 a year through banking channels for software and related IT service purchases, against a general USD 50,000 limit; prepaid cards for IT industries are capped at USD 3,000 a year, rising to USD 5,000 for service exporters (PKF TR Upadhya & Co.; circulars at Nepal Rastra Bank).

The rule that follows: never let a Nepali vendor carry your cloud, SaaS or API bills. Own the AWS or GCP account and the GitHub, Datadog and CI seats, and grant access. Otherwise you have imported a hard regulatory ceiling into your own infrastructure spend. For US buyers, payment for services performed outside the United States is generally foreign-source income, which is why a Nepali vendor's fees normally sit outside US withholding (IRS) — collect a W-8BEN-E anyway.

One constraint no clause fixes: travel. Nepali passport holders face real friction obtaining US, UK and Schengen visas, and processing can run months. If your plan depends on an onsite kickoff, key staff embedded at your office, or annual team visits, test that assumption before you sign rather than after — and expect to fly to Kathmandu more often than the team flies to you.

Engagement models, and when each fits

Model	Buying	Fits when	Fails when
Fixed scope	A defined deliverable for a defined price	The spec is stable — a migration, an integration, a known rebuild	You are still discovering the product; every change becomes a negotiation and quality becomes the release valve
Dedicated team	Named engineers at a monthly per-seat rate	Continuous product work and someone setting priorities weekly	Nobody owns the backlog on your side. Also the vendor-side failures, which are the ones you pay for: bench-warming, quiet substitution of the engineers you interviewed, juniors billed at mid rates, and a seat that stays invoiced after the person left. Insist on named people in the contract, notification before any swap, and the right to stop paying for a seat you did not approve
Staff augmentation	Individuals slotted into your process	You have engineering management capacity to spare	You lack management capacity — this model consumes it, not supplies it

For most companies evaluating Nepal the honest answer is the middle row. A dedicated team gives you named people, continuity and a forecastable monthly cost while leaving prioritisation with you, and it is where the cost advantage compounds — you are not repaying ramp-up on every statement of work.

What goes wrong, and the clauses that stop it

• The team you were sold is not the team you get. Named-personnel schedule with CVs, substitution only on written approval, two-week handover overlap.
• Velocity collapses after month two. A working demo in your own environment every week from week one, with payment tied to demonstrated increments, not effort reports.
• Nobody but the vendor can run the build. Your repositories, cloud account and CI from day one, with "reproducible from a clean machine following the README" as an acceptance criterion you test in month one.
• Dashain arrives and nothing moves for a fortnight. Holiday schedule as a contract annexe, a roster with named on-call engineers, no releases in that window.
• Communication looks fine and is not. Nepal's moderate EF band understates written English and overstates live-call fluency in disagreement. Keep written decision logs, and in the first call ask a question whose honest answer is "no".
• Key-person concentration. Require a bus factor of at least two on every critical component, enforced by a review rule.
• Country risk. In September 2025 the government blocked more than 20 social media platforms; protests followed in which at least 51 people died, the prime minister resigned, parliament was dissolved and elections were called (Al Jazeera). Those elections were held on 5 March 2026. The Rastriya Swatantra Party won 182 seats — the first single-party majority since 1999 — and Balen Shah formed a government later that month (2026 Nepalese general election). A settled majority government is a better starting point than the position this paragraph described a year ago, but eighteen months is not a track record, and roughly 90% of Nepal's IT employment sits in one valley that also carries real seismic exposure — the 2015 earthquake is within the operating memory of every firm you will talk to. Ask about power backup, a second connectivity path per engineer, and what happened to delivery during the September 2025 shutdown; the answers are more informative than the risk itself. Require a continuity plan, a second connectivity path per engineer, and artefacts mirrored outside Nepal.

Before you sign: get three quotes and make each explain any figure outside USD 15–55 per hour, ask for twelve-month retention on the specific team and the employment status of every named person, and run a short paid pilot in your own repo and cloud account first. Nepal is a good buy for the right shape of work and the right geography, and a poor one for a US West Coast team needing live collaboration or a product needing deep platform, security or ML specialists on day one. To work out which you are, get in touch and bring the awkward questions.

Frequently asked questions

Is Nepal actually cheaper than India?

At the mid-market, generally yes, though not dramatically. Neither country has a published rate survey; the only survey-grade regional figure is Accelerance's 2026 Asia band of USD 24–31 per hour for juniors and USD 31–41 for seniors. Nepal sits at or below it because there is no tier-1 brand premium, while India spans a much wider range. Cost alone is not a wide enough gap to decide on.

Can a Nepal team cover US working hours?

Only with a deliberately shifted roster. A standard 10:00–18:00 Kathmandu day has zero overlap with either US coast. Shifting Nepal to 13:00–21:00 buys about 2 hours 15 minutes with US Eastern in summer, 1 hour 15 minutes in winter. US Pacific gets nothing usable — 09:00 in San Francisco is 21:45 in Kathmandu.

Who owns the code, and how do I make that stick?

Whoever your contract says, provided the chain is complete: a present assignment from the vendor entity, plus a warranty that every individual who touched the work has a signed IP assignment with that entity. Then pick an enforceable forum — foreign judgments are generally not enforceable in Nepal, but arbitral awards are, Nepal having been a New York Convention party since 1998.

How do foreign clients pay a Nepali vendor?

Usually a SWIFT wire in USD, GBP or EUR to the vendor's Nepali bank, converted to rupees on arrival; Wise also pays out to Nepali accounts. Service exports are zero-rated, so there should be no VAT on your invoice. Agree who bears correspondent bank charges and send a test payment first.

Can we send personal or regulated data to Nepal?

You can, but the country does not do the work for you. Nepal has no EU adequacy decision, so EU or UK personal data needs Standard Contractual Clauses plus a processing agreement with specific technical and organisational measures. For anything under HIPAA, PCI DSS or a financial regulator, keep regulated data in infrastructure you control and give the team scoped access to masked data.