NovDifferent projects can still share one developer exposure
Why a portfolio spread across several projects may still depend on the same developer, operating model and commercial assumptions.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
A portfolio can look diversified long before it actually is. Three contracts, three buildings and three pins on a map create visible separation. What they do not tell me is whether the outcomes depend on three independent sets of facts.
Imagine a hypothetical investor allocating USD 300,000 across three projects from the same developer group, USD 100,000 in each. One project is close to completion, another is mid-construction and the third is at an earlier stage. The addresses differ and the unit types are not identical. Counting properties gives a neat result: no single purchase represents more than one third of the capital.
That calculation is correct, but it answers only a capital-allocation question. Diversification also depends on what can go wrong together. If all three cases rely heavily on the same group completing projects, delivering a promised specification, organising handover and supporting a similar post-completion model, then a material part of the exposure remains shared.
Start with the dependency, not the project count
I separate the visible asset from the mechanism behind the investment case. Local rental demand may genuinely differ between two neighbourhoods. A family-sized apartment and a compact unit may attract different users. Completion dates can place cash requirements in different years. Those distinctions matter.
Other factors may repeat. The same commercial team may set the assumptions used in several presentations. The same operating model may sit behind projected rental figures. A group-level delay in decision-making or procurement could affect more than one development. None of these possibilities proves that a problem will occur. They simply show that “three projects” is not the same statement as “three independent sources of outcome.”
This is where I find a dependency map more useful than a property count. I want to know which parts of each case are project-specific and which parts are common.
A shared brand and a shared legal counterparty are not the same thing
The contract matters. A group may use different project companies, and the name marketed to buyers may not be the entity signing every agreement. The opposite mistake is also possible: seeing separate legal entities and assuming that the commercial risks are therefore independent.
I do not infer either conclusion from branding. The actual documents need to identify the seller, the obligations and any relevant relationships for the selected transaction. Legal separation can matter greatly, but it does not automatically separate operating capability, management arrangements, reputation, target demand or the assumptions used to justify the purchase.
That distinction prevents two common analytical shortcuts. One says, “It is the same developer, so all projects are one risk.” The other says, “The contracts use different companies, so the risk is diversified.” Both are too broad.
Put numbers on the concentration you can actually identify
The hypothetical USD 300,000 portfolio can illustrate this. By project value, each position is 33.3% of the capital. Suppose, however, that all three investment cases require one unverified management promise to work after handover. For that particular assumption, the concentration is effectively close to the whole portfolio.
This does not mean the portfolio has “100% risk” in any meaningful universal sense. Risk cannot be reduced to one percentage so casually. It means one named dependency appears in all three positions.
Now change the facts. Project A is completed and used by long-term residents. Project B targets a different user group and has a separate operator. Project C is a different asset type, with its own cash-flow logic and a different contractual counterparty. The common developer brand still exists, yet the important economic dependencies may be far less aligned. The conclusion changes because the underlying mechanisms changed, not because the number of addresses did.
Diversification should survive a sentence beginning with “if”
A practical test is to finish several sentences.
If the developer’s construction timetable slips, which positions are affected? If the proposed operator does not perform as expected, which positions depend on that operator? If one tenant segment becomes weaker, are all three assets competing for the same demand? If the original market narrative proves too optimistic, do all three purchases lose their main justification at once?
The purpose is not to manufacture negative scenarios. It is to identify whether several purchases are independent enough to deserve the language of diversification.
An investor may consciously prefer concentration. Familiarity with a developer, confidence built from completed projects or operational simplicity can all be legitimate reasons to allocate more capital to one group. I would simply name that choice accurately. “I am comfortable taking a larger developer exposure” is clearer than “I am diversified because I own three units.”
For an investment brief, I would therefore record the contract party, project stage, operating model, target demand, management dependency and the critical assumption behind each asset. Repeated elements are marked as shared. The document does not produce a magic diversification score, and it does not replace legal or valuation work. It shows whether the portfolio rests on several independent pillars or on one pillar decorated with several project names.
That distinction matters before the fourth purchase, not after it.