Lend to a project, not a company

One sentence first, then the precise version

Plain version: project finance is lending money to a project, not to a company. Every technical idea in the later modules flows from that one fact. The lender is betting on the project's cash flow, not on you.

Contrast it with how you normally borrow. When a company takes a bank loan, the bank underwrites the whole company: its balance sheet, its other assets, its track record, the owner's guarantee. If the specific thing bought with the money fails, the bank still pursues the company and the owner. That is corporate finance, also called on-balance-sheet or full-recourse finance. The borrower's entire creditworthiness backs the loan.

In project finance the bank deliberately gives up that broad claim. It agrees to be repaid only out of one project's cash, secured only by one project's assets. It accepts a narrower, riskier position. Which raises the question this module has to answer: why would a lender accept less security, and why would a sponsor give up the cheaper, easier corporate loan?

Recourse: the word the whole subject turns on

"Recourse" means the right to come after someone for the money. Mechanically it is the single most important concept in the field, so be exact about it. There are three positions on a spectrum.

Why this matters in practice: it is the whole game. Finance a development inside a dedicated SPV on a limited-recourse basis, and if the project goes badly your exposure is the equity in that SPV plus whatever specific guarantees you signed. Your holding company and other assets stay insulated. That ring-fence is the product you are buying. It is also why lenders charge more and demand far heavier documentation, because they have surrendered the easy claim on your whole balance sheet.

Why an SPV exists: four jobs, one structure

The Special Purpose Vehicle (also SPE, or "ProjectCo") is a company created to own and operate only this one project. No history, no other assets, no other liabilities. It looks pointless until you see the four problems it solves at once.

1. Ring-fencing / bankruptcy remotenessBecause the SPV holds only this project, its cash flows and assets are isolated. The project's lenders are protected from the sponsors' other troubles, and the sponsors' other businesses are protected from this project's troubles. The isolation runs both ways.
2. A clean security packageThe lender wants security over everything that matters to repayment: the land, the buildings, the project bank accounts, the project's rights under every contract, and the shares of the SPV itself. Because the SPV owns only the project, that security can be taken cleanly, with no competing creditors and no unrelated assets cluttering the claim.
3. A contracting hubA project has many parties: sponsors, lenders, the construction contractor, the operator, the buyer of the output, suppliers, sometimes the state. They all need to contract with one counterparty. The SPV is that hub. Every contract points at it — the contractual matrix, which is the whole of Module 2.
4. Off-balance-sheet treatment & risk-sharingBecause the debt sits in the SPV and (if structured right) the sponsor neither consolidates nor fully guarantees it, the sponsor's own balance sheet stays cleaner. It can take on a large project without that debt crushing its credit or breaching existing covenants. And several sponsors can jointly own one SPV, sharing a project too big or risky for any one alone.

This is what the textbooks mean when they say project finance lets parties redistribute and share the responsibilities found in complex projects. The SPV is the machine that makes that redistribution possible.

When to choose it over corporate finance

Project finance is not the default. It is more expensive in absolute terms: higher interest margins, large legal and advisory fees, slower to arrange. You choose it only when one or more of these conditions hold strongly enough to justify that cost.

• 1The project is large relative to the sponsor. If a single project could sink the whole company on failure, you ring-fence it so failure is survivable.
• 2Cash flows are identifiable and reasonably predictable. The lender needs a cash flow it can model and lend against. A contracted, leased asset gives exactly this; a speculative build-to-sell gives a much weaker version.
• 3Risk-sharing is needed. Multiple sponsors, or a need to push specific risks onto specific parties via contracts, favours the SPV structure.
• 4The sponsor wants to protect its balance sheet: keep debt off, preserve borrowing capacity and rating, avoid breaching existing covenants.
• 5There is a contractual framework that makes risks allocable to creditworthy parties: a strong contractor taking completion risk, a strong off-taker taking demand risk, and so on.

If few of these hold, a plain corporate loan is cheaper and faster, and you should take it. The real skill is recognising which situation you are in. Most people misclassify, and either over-engineer a small deal or under-protect a big one.

Mapping it to your two exit routes

You build for two different exits, and the exit decides what kind of finance the project even is.

Your own business spans both ends of this spectrum, which is exactly why the distinction is worth more to you than to most. We carry both versions through the case study later.

Why the structure is rational, not just clever

It is tempting to read the SPV as financial engineering. It is deeper than that. Project finance exists because it solves real economic problems corporate finance cannot.

The agency problem — free cash flow discipline

In a normal company, managers control a pool of cash and can spend it on weak projects, empire-building, or pet ideas. Project finance strips this out. The SPV's cash is governed by a rigid waterfall (Module 4): money in, then operating costs, then debt service, then reserves, and only what is left, last in line, flows up to sponsors as dividends. Lenders impose a lock-up: no cash leaves to sponsors unless coverage ratios are met. High leverage plus the waterfall forces discipline. There is no slack cash to waste. This is the Jensen free-cash-flow argument, and it is a genuine reason high leverage is a feature here, not a bug.

The information & incentive problem

By isolating one project, lenders analyse one well-defined set of risks instead of an entire diversified company they could never fully understand. And by allocating each risk to the party best able to control it (Module 3), the structure aligns incentives: the contractor bearing completion risk has every reason to finish on time; the operator sharing in performance has every reason to run the asset well.

The risk-redistribution problem

Some projects are simply too large or too risky for one balance sheet. The SPV lets multiple sponsors and lenders pool capital and parcel out risk through contracts, making projects financeable that no single party would dare fund alone. It is why project finance dominates infrastructure, energy and large industrial assets worldwide — and why, in 2026, it is the structure of choice for the data-centre and renewables boom.

Terms introduced here

Recourse

The lender's right to pursue assets beyond the project itself for repayment.

SPV / SPE / ProjectCo

The single-purpose company created to own and operate one project, and nothing else.

Sponsor

The equity owner(s) of the SPV who develop the project and gain from its success.

Ring-fencing

Legal and financial isolation of the project so its risks and the sponsor's other risks do not contaminate each other.

Cash waterfall

The fixed priority order in which the SPV's cash is applied: costs, debt, reserves, then sponsors last. Detailed in Module 4.

Lock-up

A condition preventing cash being paid up to sponsors unless defined coverage ratios are satisfied.

Off-taker

The party contractually committed to buy the project's output — or, in real estate, the tenant paying rent. Central to Module 2.