Stop naming your development like a product category

Half the developments launching in Lisbon this year could swap names with each other and nobody would notice.

Riverside This. Prime That. A location plus an adjective plus the word "Residences." It reads like a spreadsheet column, not a place someone will spend the next twenty years of their life in.

A name like that does one job: it describes the product. It tells a buyer what square footage they're getting before it tells them anything they'll actually remember.

The problem is buyers at this price point aren't choosing between specs. They're choosing between two developments that both have marble counters and floor to ceiling windows, and the only thing left to decide on is the one that feels like it already exists as a place.

We get the instinct. A developer wants the name to work hard, to explain the pitch, to reassure the board that nobody will be confused about what's being sold. But the name isn't where the explaining happens. The brochure does that. The website does that. The name has one job: to sound like it was always going to be called that.

When we take on a naming brief, the first thing we throw out is the map. Not literally, the location still matters, but we stop starting there. We start with the feeling the building gives off when you stand in the unfinished shell before the finishes go in. That's usually where the real name is hiding.

If your development still sounds like a listing description, we should talk before the signage goes up.

‍