How to name a development

There is a street in most British cities where four new schemes are called The Foundry, Foundry Works, The Old Foundry and Foundry Yard. One of them was a foundry.

Naming is the cheapest decision on a development programme and one of the most consequential, because everything else inherits it. The mark, the palette, the brochure, the domain, the hoarding, the way an agent says it on the phone. Change it late and you re-render.

What a name is actually doing

Three jobs, in this order.

Making the scheme findable and repeatable. Someone has to be able to hear it once, remember it, and type it correctly into a search box that evening. That is a lower bar than it sounds and a lot of names fail it.

Setting a price expectation before anyone sees a figure. A name does a surprising amount of positioning work. It signals a buyer type and a price bracket in about a second, and it does so whether or not you intended it.

Separating you from the scheme next door. Both commercially and legally. If a buyer searching your scheme lands on a competitor's because the names are near-identical, you have paid for their enquiry.

Notice what is not on the list: being beautiful, being clever, or referencing the site's history. Those are sometimes useful and never the point.

Why everything is called The Old Something

Because heritage naming is the safest-feeling option in the room.

It is defensible in a planning context, it sounds established, it flatters the local audience, and nobody ever got criticised for it. Which is precisely the problem. It is the choice that attracts no objection and no attention, and there are now so many of them that the category has stopped signalling anything at all.

It is also frequently untrue, and that is a genuine risk. Naming a scheme after an industry that was never on the site is the kind of thing a local historian writes to the paper about, and it lands in the same search results as your scheme name for years.

If the building genuinely was a foundry, and the story is good, use it. If it was a car park, do not invent a foundry.

The categories, and what each one costs you

Place. The street, the district, the postcode. Strong for buyers who already want that location and weak for everyone else, and it makes portal listings work harder. The risk is that you are naming yourself after something you do not control. If the area's reputation moves, yours moves with it.

Heritage. As above. Powerful when true and specific, invisible when generic.

Landmark or feature. A view, a bridge, a park, a tree that is actually there. Reliable, checkable, and hard for the scheme next door to copy.

Abstract or invented. Highest risk and highest ceiling. Owns its search results completely, which is worth more than most developers realise, but it starts with zero meaning and needs the identity and the marketing to supply it. Right for a large or long scheme, wasteful for eighteen flats.

Developer-prefixed. Your company name plus the place. Underused in the UK, and it is the only option that compounds. Every scheme feeds the parent brand, which is the asset that outlives all of them.

The ten-minute test

Before anyone designs anything, run a candidate name through these. Most die here, which is the point.

Say it on the phone. Have someone read it aloud to a person who has never seen it written down, and ask them to write it. If they cannot spell it, your agent will spend two years spelling it and your buyers will not find you.

Search it. All of it: the name alone, the name plus the town, the name plus "apartments". If page one is already occupied by another scheme, a pub, or a housing association block from 2011, you are buying a fight.

Check the domain and the handles, but do not let them decide it. A .co.uk you have to hyphenate is a bad sign; a .com you cannot get is usually irrelevant for a UK residential scheme.

Search the Companies House and trade mark registers. Cheap, quick, and it prevents the one genuinely expensive naming failure.

Say the full sales sentence. "Prices at Foundry Yard start from three hundred and twenty thousand." Some names collapse in that sentence. Better to find out now than in a radio ad.

Write it small. Set it at the size it will be on a portal listing, on a phone, in a list of twelve other schemes. Long names and clever punctuation die here.

Ask what it promises. Every name makes a promise. Riverside promises a river. The Gardens promises gardens. Check you are delivering the thing, because buyers arriving at handover will.

The apostrophe problem, and other quiet killers

Avoid apostrophes. They break domains, they get typed inconsistently, and half your assets will end up with a straight quote and half with a curly one.

Avoid "The" as a load-bearing word. The Exchange and Exchange are the same name, and you will use both by accident within a month.

Avoid numbers that look like they might be a street number when they are not.

And avoid names that only work in the local accent. It is charming and it fails on the phone.

What we actually do

Naming comes before identity and long before visualisation, because everything downstream inherits it and re-rendering is the expensive part.

We put up a small number of options, each with the argument for it rather than a mood board, and we run the test above in front of the client rather than presenting a winner. Names die more usefully in a room than in a document.

And we will say when the honest answer is the street name. A large share of schemes should be named after where they are, plainly, and the effort should go into the identity instead. A confident plain name beats a strained clever one, every time.

---

Naming, positioning and identity, settled before anything is rendered. See how we work with developers, or tell us about the site and we will come back with names and the reasoning behind them.