Peak debt vs Site-by-site development finance: A practical guide for multi site growth

If you’re scaling a development pipeline, the way you structure debt can either slow you down, or give you flexibility and capital efficiency. This guide explains (in plain English) how Peak Debt / Revolving Credit Facilities (RCFs) work, how they compare to project-by-project loans, and when each approach tends to fit best.

In this guide:

What ‘Peak Debt’ means and why lenders use it
The difference between site-by-site development finance and an RCF structure
Key benefits and trade-offs (flexibility, fees, reporting, collateral)
A quick checklist to help you decide what fits your business

In development finance, the structure of debt can materially affect cost, flexibility, and execution speed. A common question from growing developers and investors is whether to fund projects one-by-one (site-by-site development loans) or to use a portfolio facility sized to Peak Debt - often delivered through a Revolving Credit Facility (RCF).

Site-by-site finance remains widely used. But for businesses delivering multiple projects at the same time, lenders and borrowers are increasingly moving toward portfolio-based facilities that reflect the borrower’s maximum combined borrowing at any one point in time (their peak exposure), rather than adding up the maximum debt on every individual site.

Below is a straightforward breakdown of both structures, with practical pros/cons and what they typically mean for day-to-day execution.

Option 1: Site-by-site (case-by-case) development finance

Under a traditional approach, each project is financed separately. Every site has its own facility agreement, approval process, and drawdown structure. For a developer delivering several projects in parallel, this often means running multiple debt facilities simultaneously. In simple terms, if a developer plans to build four apartment blocks over three years, they could secure four separate development loans sized to each project’s individual gross development value (GDV).

This structure has some advantages:

Risk is clearly ringfenced at the individual site level
Financial modelling is simpler
Lenders assess each asset independently

However, the drawbacks become clear as scale increases. Each new site requires fresh credit approvals, legal documentation, and fees. Borrowing capacity is often sized to each site’s maximum requirement rather than the developer’s actual peak portfolio exposure.

This can create inefficiencies. Developers may also face sequencing constraints, where lenders require one project to complete or sell down before another can begin.

For smaller or first-time developers this structure can make sense. But for experienced operators with repeatable development pipelines, it can quickly become restrictive.

Option 2: Peak Debt / Revolving Credit Facility (RCF)

A Peak Debt or Revolving Credit Facility (RCF) takes a different approach. Instead of financing projects individually, the lender provides a single facility sized to the borrower’s maximum expected debt exposure across the portfolio.

The developer can then draw and repay funds across multiple projects within the agreed facility limit.

To illustrate, consider a build-to-rent investor planning to deliver three mid-scale urban rental blocks over four years.

Each project requires around £20m of development funding
The projects overlap during construction and lease-up
The maximum combined borrowing at any point is £32m

Under a case-by-case structure, the developer might arrange three separate £20m facilities, meaning lenders underwrite £60m of potential debt.

Under a Peak Debt facility, the lender instead provides a single £32m RCF, reflecting the portfolio’s true peak requirement. The advantages are clear. First, capital efficiency improves. Debt is sized to the borrower’s real exposure rather than the aggregate of individual projects. Second, execution becomes faster. Once the facility is in place, new projects can be funded without restarting the full approval process. Third, developers gain flexibility. Projects can overlap, start earlier, or shift in timing without renegotiating debt each time.

There are trade-offs. Portfolio facilities usually involve cross-collateralisation across assets, and they require stronger financial reporting and integrated portfolio modelling. Lenders also tend to favour experienced developers with a clear track record and repeatable pipeline.

How a Peak Debt / RCF typically works (simplified)

You agree an overall facility limit with a lender (based on the highest combined borrowing you expect across the portfolio).
You draw funds for individual sites as they start (subject to agreed eligibility and reporting).
As units complete, stabilise, or sell down, you repay and recycle that capital into the next site, without needing a brand-new loan each time.
The lender monitors performance at portfolio level (and sometimes at site level), usually with more frequent management information than a one-off loan.

Quick decision guide: which structure tends to fit?

An RCF / Peak Debt facility may be a good fit if you:

Have a repeatable pipeline (multiple sites over time), with overlapping timelines
Want speed and flexibility to start new projects without re-papering debt each time
Can produce portfolio-level reporting and maintain tighter financial controls
Are comfortable with some degree of cross-collateralisation across assets

Site-by-site finance may be a better fit if you:

Are delivering a small number of standalone schemes or a first project
Need clear ringfencing of risk at individual site level
Prefer simpler documentation and lighter ongoing reporting
Don’t expect meaningful overlap between schemes (so peak exposure is close to the sum of the sites anyway)

Why this matters in the current market

In sectors such as build-to-rent and buy-to-rent portfolios, development pipelines are increasingly programmatic rather than one-off.

Operators may be delivering multiple schemes in parallel across different cities, or acquiring blocks sequentially as opportunities arise. In these situations, portfolio-level financing aligns much better with how the business actually operates.

From a lender’s perspective, the structure also improves visibility. Instead of underwriting isolated projects, lenders gain a clearer picture of the overall portfolio performance and pipeline strategy.

We are seeing this particularly among:

Professionalised BTR developers
Institutional residential platforms
Regional developers scaling beyond their first few schemes
Investors combining acquisition and development strategies

For these borrowers, the ability to recycle capital within a single facility can materially accelerate growth.

Heligan View

At Heligan, we increasingly see Peak Debt and RCF structures used where developers have repeatable deal flow and overlapping project timelines.

They reduce friction in the financing process and allow lenders to support a developer’s broader growth strategy rather than simply underwriting individual assets.

That said, they are not always the right solution. Smaller developers or one-off projects may still benefit from traditional site-level financing where ringfencing risk is the priority.

It is also important to note that this concept is not limited to residential development. The same financing logic applies across many sectors where businesses deliver projects on a rolling basis. That could include student accommodation, logistics assets, healthcare facilities, or infrastructure-linked property.

More broadly, the Peak Debt approach is simply about aligning the debt structure with the real cashflow profile of a portfolio.

If you’re planning a multi‑site pipeline and want to understand whether a Peak Debt / RCF structure could reduce cost and increase flexibility, we can help you model your peak exposure and sense-check the most fundable structure. Get in touch to talk through your pipeline, timings, and the financing options available.