Av-Gad's Growth Capital: How Bonds, Phoenix, and Partners Reshape the Economics for Common Shareholders

The main article argued that Av-Gad's pipeline is large enough to support years of activity, but not large enough to answer the more practical question: who actually funds the road to that pipeline. This follow-up isolates the capital layer. Not project quality, but how much value is really left for common shareholders after bonds, bank funding, Phoenix, and project-level partners take their place in the stack.

The short answer is that Av-Gad is building a growth engine that depends on sharing the upside quite deeply. This is not just more expensive debt or theoretical dilution. It is a structure in which the company usually keeps operating control, but gives up part of the project economics upfront, grants an option on the urban-renewal subsidiary itself, and in some cases also funds the partner on the other side. So the question is not whether the projects have value. The question is at which layer the value stops before it reaches the common share.

The most interesting signal in the filing is not only the NIS 197.0 million negative cash flow from operations. The more interesting signal is what the board had to include in its two-year forecast in order to conclude that there is no liquidity problem: NIS 34.1 million of cash, NIS 80.6 million of credit lines, alternative financing offers, potential project partners, planned new bond series, and NIS 707.9 million of project surpluses after repayment of Series B and Series G. That is not a description of a company sitting on excess capital. It is a description of a company that needs its funding machine to keep working.

What The Board Is Really Saying About Liquidity

The sentence "no liquidity problem over the next two years" can sound reassuring on first read. It is reassuring as far as immediate distress is concerned. But it also exposes what the company is relying on in order to remain in that position.

At the end of 2025, the company had NIS 34.1 million in cash. That is not trivial, but it is also not a cushion that can fund a growth year on its own for a developer with a broad pipeline. In the same year, operating cash flow was negative by NIS 197.0 million, mainly because of a rise in buildings under construction and a decline in the liability for construction services. In other words, growth is already consuming cash before it releases surpluses.

The critical point sits in the board discussion from March 25, 2026. There the company reviewed NIS 773.5 million of expected expenses and investments, NIS 420.2 million of current liabilities, and NIS 226.7 million of non-current liabilities, against existing cash, credit lines, alternative financing offers, potential partners, and future project surpluses. The right reading is that the company is not presenting surplus liquidity here. It is presenting a capital-rollover plan. If every layer works, the company should meet its obligations. If one of them weakens, the pressure immediately shifts to the others.

The chart does not say that all of these figures sit on one clean accounting bridge. It does show why the central story is funding, not just backlog. The quantified sources the company discloses are not enough by themselves without new debt raising, partner introductions, and actual release of project surpluses. That is why the right way to read the board's sentence is almost in reverse: there is no liquidity problem, as long as the funding mechanism keeps opening on time.

Debt: Covenant Room Exists, But The Structure Is Fully Connected

The good news is that, at the balance-sheet date, the company was not close to breaching covenants. Equity stood at NIS 132.0 million, comfortably above the NIS 40 million floor in Series B and the NIS 50 million floors in Series G and Series D. Liquidity of NIS 34.1 million remained above the next interest payments. Net financial debt to net CAP in Series G and Series D stood at about 66%, below the 85% ceiling.

That is only half the picture. The other half is a structure that ties all funding layers together. At the end of 2025, the company had NIS 107.9 million of bank and institutional credit, of which NIS 89.5 million was classified as current. At the same time, the bond balances on the books stood at NIS 26.5 million in Series B, NIS 103.8 million in Series G, and NIS 89.9 million in Series D. That means bank debt and listed bonds together already sit above NIS 328 million, before other loans and operating liabilities. The maturity profile is also front-loaded: the first year includes NIS 96.3 million to banks and financial institutions, NIS 20.6 million to Series B, NIS 7.5 million to Series G, and NIS 6.3 million to Series D.

More important than size is the way these layers are connected. If Series B is accelerated, that opens an acceleration trigger for about NIS 197.5 million nominal value in Series G and Series D. If Series G is accelerated, it can pull another roughly NIS 119.4 million nominal value in Series B and Series D. If Series D is accelerated, it can pull another roughly NIS 131.5 million in Series B and Series G. Several smaller project-level loans also include provisions that tie them back to the entire listed bond stack. So the real risk is not a covenant that is broken today. It is high connectivity across the funding structure.

So the correct covenant read is not "there is room, therefore there is no issue." The right read is that covenants provide breathing room, but do not change the fact that the whole debt structure depends on uninterrupted access to markets and financing events. Once one layer gets blocked, the question moves very quickly from funding cost to the resilience of the whole structure.

Phoenix Is Not Just Financing, It Changes The Upside Split

This is the layer that is easiest to misread. At first glance, the Phoenix framework looks like a clean solution: an institutional partner funds 60% of the equity required in a project, with the ability to go up to 75%, and Av-Gad can therefore move more projects at the same time. That is true. But it is only half true. And this is no longer theoretical: in the Balfour 81 project in Bat Yam, Phoenix had already provided NIS 29.5 million by the reporting date.

The other half is that Phoenix is not just a financier. In return, it receives 30% to 37.5% of the equity rights in the project vehicle, on a fully diluted basis. So when Av-Gad activates this framework, it is not only increasing capacity. It is also selling part of the project upside in advance. That makes economic sense when capital is scarce, but it materially changes the capture rate for common shareholders. And there is more: in the project waterfall, Phoenix's excess funding gets repaid first, and only then are distributions made pro rata to the equity each side actually put in.

The company keeps day-to-day control through the general partner, and that general partner is also entitled to a one-time management fee equal to 3% of actual project cost. But even that layer comes with an important caveat: if the project vehicle cannot repay all of Phoenix's excess funding, the general partner must return up to 50% of the gross management fee it received, or lose entitlement to it. So even the management-fee layer is not fully insulated from the funding structure.

The deeper layer is the option at the urban-renewal subsidiary level itself. Phoenix was granted an option to acquire up to 20% of the issued and paid-up capital of Av-Gad Quality Urban Renewal, in exchange for fair value less 25%. At the end of 2025, rights representing 15% had already been granted, and the company recognized a NIS 10.7 million liability for that option. The valuation attached to the filing makes clear that this is the currently exercisable portion, 15% out of a 20% ceiling, which is why it equals 75% of the full option value.

That matters for two separate reasons. First, this is no longer only about profit sharing at the individual-project level, but also about potential dilution at the urban-renewal platform level. Second, from the signing date onward, the group's urban-renewal activity is supposed to be concentrated in that subsidiary. So Phoenix's option is not a side right on a small asset. It is a foothold in the platform through which new activity is meant to flow. And the NIS 10.7 million liability is already on the balance sheet. It is not a footnote about the future, but a real 2025 accounting layer.

Petah Tikva Shows How The Model Works In Practice: The Company Is Not Only A Partner, It Also Funds The Partner

The March 18, 2026 immediate report on the Tselah project in Petah Tikva matters not because it changes the 2025 numbers by itself, but because it shows Av-Gad's operating model when capital is the real bottleneck. This is a project with up to 92 units for sale and expected company investment of about NIS 186.9 million, so it is not a marginal example.

Av-Gad Quality received 62.5% of the project company shares for par value, but the shareholders' agreement goes much further than that. The required project equity was estimated at about NIS 18.6 million, and the third party had contributed only about NIS 4 million as of the report date. Under the agreement, each side is supposed to fund according to its holding, but Av-Gad Quality also committed to fund the balance of the partner's share as a loan carrying interest equal to its own cost of funds plus 1.5%, or the cost of a third-party loan, whichever is lower. And if required project equity rises up to NIS 30 million while project profitability remains at least 13%, Av-Gad Quality will still finance the partner's share of that increase under the same mechanism.

The accounting read is straightforward, but the economic meaning is sharper. On the disclosed numbers, Av-Gad's direct share of the initial equity burden is about NIS 11.6 million, while the partner's share is about NIS 7.0 million. Since the partner had contributed only about NIS 4 million, the implication is that the company is expected to bear about NIS 14.6 million of the initial cash burden, part as its own equity and part as a loan to the partner. This is not a classic risk-sharing partnership. It is a partnership in which Av-Gad provides the capital, the funding, and the execution.

The partner is not arriving empty-handed. It is responsible for managing relations with the landowners, obtaining permits, marketing, and sales, and it is entitled to 1% of the selling price of each apartment sold by the project company, in addition to proportional management fees. Av-Gad Quality is responsible for financing, customer service, and execution, including through a group contractor at cost plus 5% to 10%. That split makes it very clear who is supplying capital, and who is supplying the sourcing and landowner-access layer.

One more point matters here. Av-Gad Quality is allowed to transfer up to 37.5% of the project company shares to Phoenix or another institutional body without the partner's consent, subject to advance notice. So Petah Tikva does not only illustrate the partner-loan mechanism. It also shows how the project layer can connect directly into the Phoenix layer. The company builds operating control, but capital flexibility is bought through a redistribution of economic rights.

What That Leaves For Common Shareholders

The central implication of this whole structure is that Av-Gad is not currently short on projects. It is short on capital that can be deployed without sharing the upside. Public bonds and bank debt buy time. Phoenix buys capacity. Project-level partners open doors. But each of those layers takes a different toll before common shareholders see the value.

Debt sits ahead of equity. Phoenix takes part of the project profits and also an option at the subsidiary level. The project partner receives rights, management fees, and sales economics, and in some cases also funding from Av-Gad itself in order to hold its own share. That means the quality test for Av-Gad over the next few years will not be only how many units enter the pipeline or how many projects reach execution. The real test will be how much of that value can actually pass through all funding layers without being diluted away on the way.

This is also the strongest counter-thesis to the growth story. It is entirely reasonable to argue that Phoenix and project partners are exactly the solution a developer needs in order to accelerate execution without loading even more direct equity onto the balance sheet, and that as long as Av-Gad keeps operating control, it is better to own 62.5% or 70% of a project that moves forward than 100% of a project that stays stuck. That argument is fair. But it is only true if projects do in fact move forward, surpluses are released on time, and the company manages to recycle capital from one project to the next without getting trapped between the funding layers. Right now, that is exactly the test that has not yet been proven.

Bottom line: Av-Gad's capital structure no longer resembles a simple model in which the developer originates, funds, builds, and keeps the full upside. It is a more hybrid model: operating control at the top, shared capital in the middle, and split upside underneath. If the pipeline turns into orderly execution and timely surpluses, that structure can work. If not, common shareholders may discover that the company built a large platform, but kept for itself a narrower layer of clean value in each project.