Nepal’s Policy Problem: Late, Broad, and Afraid
A country that writes policy for yesterday while pretending it is preparing for tomorrow
There is a very Nepali style of economic policymaking: ignore a sector while it is messy and early, panic once other countries have scaled it, and then announce a policy with the tone of national awakening. By then, the opportunity is older, the margins are thinner, and the neighbors are already on version 3.0.
That, in one line, is Nepal’s policy problem: late, broad, and afraid.
Late, because Nepal usually notices an industry after the market has matured elsewhere. Broad, because it responds with sweeping slogans instead of sharp strategy. Afraid, because when something new shows up, the instinct is often to ban it before understanding it.
Late
The “late” part is the easiest to see.
Nepal only got a formal data-center and cloud-service directive in 2025. By then, India’s data-center market had already crossed 1 GW in 2024 and is projected to reach 1.8 GW by 2027. Nepal is formalizing the rulebook while the region has already moved into scale.
That is the first tell. Nepal keeps confusing finally recognizing an industry with being ready for it. We act as though issuing a directive means we have entered the future. No. More often, it means we have finally acknowledged the present — late.
And this lateness would be bad enough on its own. But Nepal is not arriving into an open field. It is arriving into a market that is already far more competitive and far less forgiving.
Broad
The “broad” part is where Nepal becomes especially fond of sounding visionary.
Instead of choosing narrow, difficult, high-conviction bets, we love giant national language: digital transformation, IT promotion, startup ecosystem, innovation economy, hub status. The problem is not ambition. The problem is vagueness.
That same vagueness shows up in how Nepal talks about becoming an “IT hub”. It sounds ambitious until you remember what market we are actually entering. In the middle of global AI disruption and tech layoffs, Nepal is still tempted to speak about generic IT outsourcing as if it were some untouched frontier. It isn’t.
Global tech firms are cutting tens of thousands of jobs. Automation is repricing routine digital work. Entry-level coding is becoming cheaper, faster, and more automated. In other words, Nepal is not entering a fresh market. It is trying to enter a giant, saturated, AI-restructured market dominated by countries that arrived years ago and built serious scale.
So when Nepal still speaks in generic outsourcing-era language, it is not just optimistic. It is badly out of date.
Afraid
And then there is the third part: afraid.
The clearest example is crypto. While jurisdictions like Singapore allowed digital-asset activity to develop inside a licensing perimeter, Nepal’s instinct was much simpler: declare it illegal and move on.
The posture was never, “How do we regulate exchanges, custody, payments, investor protection, and risk?” It was, “Shut it down.” Not just trading. Not just payments. Mining too. Blockchain got flattened into the same category of bureaucratic discomfort.
That difference matters.
When a state does not understand a technology and responds by banning the whole category, it is not being wise. It is outsourcing the learning curve to other countries. The entrepreneurs leave. The engineers leave. The experiments leave. The ecosystem leaves. Then, years later, the same bureaucracy starts talking about innovation and wonders why there is no domestic depth.
That is not caution. That is fear dressed up as policy.
The data-center fantasy
Now, to be fair, Nepal does have real advantages for digital infrastructure. Renewable power is real. Cooler ambient conditions in some places are real. The new directive is real. These things matter.
But this is exactly where the national conversation becomes unserious.
We reduce a brutal infrastructure business into a tourism brochure: rivers, mountains, cold climate, opportunity.
A real data-center business is not a postcard business. It is a power-quality business, a network-resilience business, an uptime business and a capital-allocation business.
Start with electricity. Nepal’s hydropower story sounds attractive until you remember the seasonal reality: building “next to hydropower” is not the same thing as having firm, bankable, year-round electricity for high-density compute. Rivers are not reliability guarantees.
Then there is connectivity. Serious digital infrastructure depends on route diversity, peering, redundancy, interconnection quality, and operational maturity — not just cheap land and patriotic optimism.
And then there is the economics. Even in countries that know what they are doing, data centers are hard businesses. A meaningful share of power still goes to overhead rather than IT load. AI hardware only raises the difficulty. The future people casually pitch in Nepal is not “some servers in a cool valley”. It is a dense electrical, cooling, uptime, and utilization problem with very expensive consequences if you get it wrong.
So yes, Nepal may have ingredients. But ingredients are not a business model.
The serious answer
So where does that leave the serious answer?
It leaves us with a pretty uncomfortable conclusion: Nepal’s problem is not that it lacks opportunities. It is that it keeps arriving at them in the wrong way.
Late to the market.
Broad in the response.
Afraid of the unfamiliar.
That is why “become an IT hub” should probably be retired as a national slogan. It is too broad to guide decisions, too late to be impressive, and too detached from the actual shape of the market.
If Nepal wants to matter in the AI era, it needs to stop mistaking policy announcements for strategy.
That means five things.
First, stop banning unfamiliar technologies by instinct.
Regulate them properly. Prohibition is not sophistication.
Second, stop talking about generic IT outsourcing as if it were still a frontier.
It is not. Nepal needs narrower digital niches where it has an actual edge.
Third, if Nepal wants data centers, build the boring foundations first.
Firm power contracts. Import clarity for compute equipment. Route-diverse fiber. Credible compliance. Not slogans. Plumbing.
Fourth, stop marketing hydropower and cold weather as if they automatically add up to competitiveness.
They help. They do not replace uptime, customers, utilization, and execution.
And fifth, measure success by capability, not ceremony.
Not by whether a ministry launched another framework with the word “digital” in it, but by whether Nepal built real depth before the window closed.
That is the real point.
We may still build real digital industries. But we will not do so by showing up after everyone else has scaled the market, issuing a directive, and pretending the policy itself is the achievement.
The achievement is getting there early enough that the market still cares.
Author’s note: I used ChatGPT as a research and drafting tool while writing this essay. The perspective, conclusions, and final edits are mine.