Does a project need its own brand, or should it borrow the strength of the parent brand?

When a developer launches a second or third project, the design question is no longer “what should the logo look like.” The real question is: who carries the credibility in front of the buyer, the project name or the developer name? The answer shapes how the entire brand system is organized, not just one project.

Why credibility doesn't add up on its own

Many developers launch projects this way: each project has its own name, its own identity, its own sales team. Project A sells out and ends. Project B launches and starts from zero again. Buyers of project B don't know project A ever existed, and have no reason to trust the developer any faster than they would any other unfamiliar name on the market.

This is the pain point Sinh Vũ meets most often when working with developers who have three or more projects: credibility doesn't accumulate because there is no anchor to accumulate on. Each project spends a budget introducing itself, when the parent brand could be doing that work instead.

The two figures above say the same thing: buyers ask "who built it" before they ask "where is it." If the answer to "who built it" is different for every project, with no link between them, then the developer is erasing itself.

Three brand architecture models developers commonly use

In brand theory, Wally Olins divides brand architecture into three main types. In the real estate sector, these three types show up clearly in how large developers organize their project portfolios.

• Branded house, meaning a unified brand house: every project carries the parent brand name up front. Vinhomes Grand Park and Vinhomes Ocean Park are typical examples. Credibility accumulates in one place, and so does risk. If one project runs behind schedule, the whole portfolio comes under pressure.
• Endorsed brand, meaning a sub-brand endorsed by its parent: the project has its own name and identity, but always sits next to the developer's name according to a fixed rule, usually a small line such as “a project by [developer name]” or the parent logo placed in a fixed corner. This model balances building credibility for the parent with giving the project room to breathe.
• House of brands, meaning a house of many brands: each project is an independent brand, and the parent brand is nearly invisible to the end buyer. This model suits cases where projects differ so much in segment or location that linking them would cause more confusion than help.

Brand architecture is not a way of arranging names. It is a way of allocating reputation.

Compiled from Wally Olins, On Brand, and Jean-Noël Kapferer, The New Strategic Brand Management

When a project should borrow the strength of the parent brand

The question is not "is this project special." The right question is: do buyers of this project trust the developer's name more than the project's name?

If the developer has delivered at least one project on time, with residents living in it and information that is easy to look up, then the developer's name carries real value. Attaching that name to a new project is the fastest way for buyers to shorten the vetting process in their heads.

A project should borrow the strength of the parent brand when:

• Same segment as the previous project, with the same group of buyers.
• The parent brand already has a clear identity in the local market.
• The budget for building a new identity for a project is not enough to create a brand that can stand on its own.
• The sales window is short and trust is needed fast.

When a project needs its own brand

There are situations where attaching the parent brand name to a project does not help, and may even do harm. This is not theory, but a real business risk.

A project needs its own brand when:

• The segment is far from the parent brand's. A developer used to building affordable housing now launches a high-end resort project: sharing the same name will pull perception down rather than lift it up.
• In a new location, buyers do not know the developer's name. Here the parent brand's reputation does not transfer, while investing in a dedicated project brand can build a local foothold.
• The project has a strategic partner, an international architect, or a distinct positioning element strong enough to stand alone. The parent brand can take an endorsing role, without needing to take over the project name.
• The developer is in a phase of recovering its reputation after an incident. The new project needs enough distance to prove itself before bringing the parent brand back into the light.

Savills' figure shows that a clear brand is not just a question of recognition. It is a question of pricing. But to earn that premium, the brand has to be strong enough, meaning it is built consistently across many projects, not put together in a rush for a single launch.

Naming rules: three things must be consistent from the start

Whichever model you choose, there are three things to decide and write down as rules before your first project launches.

One: naming rules. Where the project name sits relative to the developer name, what size the type is, and whether they share a color palette. This decision affects all printed materials, construction site signage, the website, and contracts with design partners later on.

Two: the documentation rule. Every project introduction document must include a section on the developer: which projects it has delivered, and where its public legal information can be found. The Law on Real Estate Business No. 29/2023/QH15, Article 6, requires project information to be made public before the project goes to market, on the national information system and on the company's website. Following the law and building a good brand are one task here, not two.

Three: the on-site touchpoint rule. Site hoardings, show units, sales counters, and sales staff uniforms must be recognizable at a glance as coming from the same house. When a buyer visits the site and finds something different from the documents they read, trust breaks right there, not later.

Where to start if you don't have rules yet

If your portfolio already has two or more projects and no rule yet, the starting point is not redesigning the logo. The starting point is an inventory: list every project, past and current, put their names side by side, and ask: looking at this list, would a buyer know these come from the same developer?

If the answer is no, or it takes an explanation to see it, that is when you need to build the axis. Not for the sake of appearance, but because every following project will sell faster and cost less in building trust, once buyers already know who is behind it.

Sinh Vũ approaches this step by step: read the portfolio first, understand the segment and the location, and only then propose a suitable model. There is no single right answer for everyone, but there is a process for finding the right answer for each specific developer.