What Shifts in US Tech Hiring Mean for Teams in Nepal

A large part of Nepal's software services industry is downstream of decisions made in American companies. When US hiring tightens, contract and outsourced work usually follows a quarter or two later, and when it loosens the same lag applies in reverse. Nobody in Kathmandu controls that cycle. What you can control is which kind of work you are holding when it turns, and what your contracts say when a client's budget review lands.

Who you are actually being compared against

Not other Nepali firms. A US buyer evaluating an offshore team is choosing between four options, and knowing which one you are losing to changes what you should fix.

• Nearshore teams in Latin America. Their advantage is the working day: a Bogota or Buenos Aires team shares most of a US afternoon. They cost more than you and they win on overlap, so overlap is the thing you have to answer for.
• Large Indian and Filipino vendors. They win on scale, process maturity, certifications and the ability to absorb a headcount change without drama. A ten-person Nepali firm cannot win that comparison and should not try.
• Eastern European teams. Positioned on seniority and engineering depth, at a rate closer to US contractor pricing.
• One more in-house engineer with AI tooling. Increasingly the real alternative for small US companies, and the reason a lot of routine implementation work no longer goes out at all.

Against that field, the openings for a small Nepali team are depth in a narrow domain, ownership of a whole outcome rather than a seat, and being reliable in a way that is visible from the first week. Those are slow to build and slow to erode, which is exactly why they are worth building.

Which work is getting cheaper, and which is not

The price of turning a clear specification into working code is falling, and it will keep falling. If your offer is a competent engineer executing someone else's decisions, you are selling the thing the market is automating. What has not got cheaper is deciding what to build, integrating with systems nobody documented, operating something in production at 3am, and carrying accountability for an outcome. Price accordingly, and be honest internally about which category most of your revenue sits in. Our note on what changes when coding agents join a small team is the practical version of this for delivery.

Price is the only thing a client can compare instantly, which is why it is the worst thing to lead with.

Seats or outcomes: pick deliberately

The two viable models behave completely differently in a downturn. A dedicated engineer on a monthly retainer, around $2,200 a month with a three-month minimum in our own arrangement, gives you predictable revenue and a relationship that deepens, and it is the first line item a CFO cancels when budgets are reviewed because it looks like headcount. Fixed-scope project work, from around Rs 320,000 or about $4,200 for software with logins, payments and dashboards, is lumpier but it survives budget cuts better because it is attached to a specific outcome with a specific end date.

A team running only retainers is exposed to hiring cycles. A team running only projects is exposed to sales cycles. Most stable firms run some of each and know which side is thin at any given moment. These are starting points against a written scope, not quotes, and you should present them that way.

The contract terms that decide how much a downturn hurts

This is the part small firms leave to a template and then regret. Every clause here is negotiable at the point of signature and unnegotiable afterwards.

• Notice period. Thirty days for convenience is normal on retainers. Fifteen is not enough time to redeploy an engineer; sixty is worth asking for on longer engagements and is sometimes granted.
• Minimum term. A three-month minimum is standard and does real work. It converts a client's casual trial into a decision they have committed to.
• Ramp-down rather than a cliff. Half the hours for a final month costs the client less than an abrupt stop and gives you a month to fill the seat.
• Payment terms and late fees. Net 15 or net 30, stated on the invoice, with a late fee clause you may never enforce but which changes behaviour.
• A kill fee on fixed-scope work. Cancellation part way through should still pay for work delivered plus a defined percentage of the remainder.
• Rate review. An annual adjustment clause, so a three-year relationship is not still priced at year-one rates.
• IP assignment and confidentiality, unambiguous and settled before the first commit, for the reasons set out in our guide to selling into the US.

Overlap is the objection you have to answer

Nepal is UTC+5:45, roughly nine and three quarter hours ahead of US Eastern in summer and ten and three quarter in winter, and around twelve and three quarter to thirteen and three quarter ahead of the Pacific coast. A 6pm to 9pm block in Kathmandu covers a New York morning; extending to 9pm or later reaches the West Coast start of day. That is a genuine cost borne by your team, so staff it deliberately, pay for it, and do not pretend it is free.

Two structural details are worth putting in front of a US client early. First, the Nepali week runs Sunday to Friday with Saturday off, so your Sunday covers their Monday morning before it starts, and the only lost day is Saturday. Second, Dashain and Tihar fall between late September and mid-November and shift each year with the lunar calendar, closing offices for roughly a week to ten days and then a further three to five. Announce that in July with a coverage rota for anything live and a release freeze in the fortnight before Dashain. Clients accept planned absence; they do not accept discovering it.

Concentration risk is the thing that actually kills firms

It is rarely the market that ends a small services company. It is one client at sixty per cent of revenue deciding to bring work in-house. Track the percentage every month and treat anything above about a third as a live risk with a plan attached. Keep a cash buffer measured in months of payroll rather than weeks. Keep the pipeline warm while you are busy, because pipeline built during a quiet quarter arrives two quarters too late.

Diversifying across industries helps more than diversifying across clients in one industry, because budget cycles correlate within a sector. A mix across the sectors we work in behaves differently from three clients in the same one.

What to do when the market is soft

• Move up the value chain rather than down the price list. Discounting a rate is permanent; it does not come back when demand does.
• Write down what you know. Published judgement is the cheapest sales asset available to a small firm and it compounds.
• Deepen two or three existing accounts. Expanding a client you already have is far cheaper than winning a new one.
• Use quiet weeks to fix your own delivery: the deployment pipeline, the onboarding document, the security answers procurement always asks for.
• Look beyond the US. Australian, UK, EU and Gulf buyers run on different cycles and, in the Australian case, on a friendlier time zone.

On forecasting

Anyone confidently predicting the next twelve months of US tech hiring is guessing, and the confident ones are usually selling something. The useful posture is not prediction but resilience: a client mix where no single account can take the business down, contract terms that give you thirty days of warning rather than three, a cash buffer you would be embarrassed to spend, and enough evidence of your own work published that buyers arrive already half-convinced. If you want the longer case for why offshore engineering from Nepal holds up commercially, we set it out here.