Table of Contents▼
A Pattern We Kept Seeing
A developer has a site. The hydrology looks good. The grid connection is feasible. The numbers work at the right tariff.
Then an international investor arrives — often referred by an embassy, a DFI country officer, or a mutual contact. They spend two days in meetings. They ask about DoED licensing status, IEE approval, NEA PPA terms, SPV structure, beneficial ownership documentation, source of equity funds.
The developer answers some questions confidently, defers others to a lawyer who hasn't been briefed, and promises to follow up on the rest.
The investor flies home. The follow-up emails arrive. Some get answered. Some get answered partially, with documents that address a different question than the one asked. A few don't get answered at all — not out of bad faith, but because the developer genuinely doesn't know which authority to contact, which document format the DFI requires, or which regulatory standard applies.
Three months later, the investor has moved capital to Vietnam.
Nepal's FDI inflows fell to USD 57 million in 2024 — down 69% from USD 185 million in 2019. That is not a story about Nepal lacking good projects. It is a story about what happens between a good project and a closed financing.
The Real Gap Is Not Capital
There is a persistent belief in Nepal's development community — understandable, but incorrect — that the primary obstacle to project financing is access to money. That if the right fund, the right DFI, or the right bilateral relationship could be secured, projects would move.
They don't. Not primarily for lack of capital.
Foreign investors have repeatedly cited procedural delays, lack of government coordination, and a complex regulatory environment as the reasons projects don't proceed. Nepal has organized three Investment Summits — 2017, 2019, 2024 — generating pledges in the billions. Net FDI inflows stood at USD 67 million in FY 2023/24, less than 0.2% of GDP. The gap between pledge and inflow is not a financing gap. It is an execution gap.
The execution gap has a specific anatomy. It is the distance between a developer who has a good project and knows it, and a financier who needs that project documented, structured, and presented to a standard they can take to their own credit committee.
That distance is where projects die.
What "Institutional Infrastructure" Actually Means
The phrase gets used loosely. We use it precisely.
When an international DFI sits across from a Nepali project developer, they are not just evaluating the project. They are evaluating the system around the project. They are asking: is there a legal structure here that can hold international capital? Is there environmental compliance documentation that meets our standards, not just the local authority's? Is there a beneficial ownership structure that our compliance team can approve? Is there an AML/KYC framework that survives our post-grey-listing enhanced due diligence?
Most Nepali projects — good projects, projects with real potential — cannot answer all of those questions at the moment they are asked. Not because the developers are incapable. Because nobody built the institutional layer that would allow them to answer those questions quickly, accurately, and to an international standard.
That is the layer Silicon Himalayas exists to provide.
Why Advisory Infrastructure Must Come Before Capital
There is a logic to sequencing that the Nepal project finance space has not always respected.
Capital deployed into an environment without institutional infrastructure does not multiply. It disappears into the gap between intent and execution. It funds feasibility studies that don't meet DFI standards. It capitalizes SPVs that are structured incorrectly for the financing they're trying to attract. It gets tied up in regulatory navigation that should have been mapped before the first dollar was committed.
We have watched this happen enough times to believe — firmly — that the right sequence is infrastructure first, then capital.
Before a fund can deploy into Nepal's project pipeline with confidence, someone needs to have built the infrastructure that makes that pipeline investable. Standardized feasibility documentation. Structured SPVs. Regulatory compliance frameworks that DFIs can evaluate without a six-month due diligence detour. Expert committees that provide domain-specific technical review — not a single consultant's opinion, but a structured body whose work can be verified and relied upon.
This is not a modest ambition. It is a prerequisite.
The Navigation Problem
There is a specific experience that most people who have tried to develop or finance a project in Nepal share.
They don't know who to call.
Not because the authorities don't exist. DoED, NEA, SEBON, IBN, NRB, MoFE, DoI, ERC — the regulatory architecture is actually reasonably comprehensive. But the question of which authority, for which decision, at which stage, with which documentation, under which standard — that knowledge is not documented anywhere accessible. It lives in the heads of a small number of practitioners who have navigated the system enough times to know it.
New developers — Nepali entrepreneurs with their first project, international investors doing their first Nepal transaction — walk into this environment and encounter a wall. Not malicious. Not even necessarily inefficient by intention. Just opaque. Just undocumented. Just reliant on knowing the right person who knows the right process.
The regulatory environment's complexity, combined with a lack of coordinated guidance, has caused investors to walk away from projects they genuinely wanted to pursue. This is the specific problem Silicon Himalayas was built to solve — not by simplifying the regulatory environment (that is the government's work), but by making it navigable for the people trying to build within it.
The Expert Committee system exists precisely for this. Twenty committees across four domain clusters, each chaired by a practitioner who has navigated that specific regulatory and technical terrain professionally. Not a directory of contacts. A structured institution that produces documented, reliable guidance — the kind that a developer can act on and a financier can rely on.
What This Makes Possible
When institutional infrastructure exists — when the layer between a project and a financier is populated with structured feasibility studies, compliant SPVs, mapped regulatory pathways, and documented expert review — capital flows differently.
It moves faster, because due diligence is not starting from scratch. It closes more often, because the compliance questions that stall transactions have been answered before the DFI asks them. It attracts better terms, because a well-structured project with institutional-grade documentation is a different risk profile than an undocumented project of equivalent technical quality.
This is the thesis Silicon Himalayas is built on. Advisory infrastructure is not a stepping stone to something more ambitious. It is the foundation that makes ambition executable.
Nepal's projects are good enough. The pipeline is real — hydro, solar, infrastructure, green economy assets that international capital is actively seeking. What has been missing is the institutional layer that connects project quality to capital confidence.
We are building that layer. Deliberately. Before deploying capital into it.
Because that is the only sequence that works.
\