ÜBER DIESE EPISODE
The architect as developer — stepping out of the consultant's seat and onto the client's side of the table, where you initiate, finance, design, build and own. There are two routes in. One is entrepreneurial: a single practitioner or small firm, the model Jonathan Segal champions, and which I've seen taken up as a retirement plan as readily as a mid-career leap. The other is a mature commercial practice spinning out a development arm. I look at one Malaysian firm that did exactly that — thirty years of landmark work, then a piece of land in the Klang Valley they didn't know what to do with, and eventually a 31-storey tower of 188 units, half sold within a year.
Their reasoning is the interesting part. In thirty years of client work they had never designed for the end user. And they had designed a condominium in Penang, bought a unit in it, and watched water leak from the flat above through theirs into the one below — a plumbing problem. As the developer, they said, you don't punch holes through the floor; you run every service down a wall facing the corridor. That is control, and control is what my own former student was after when he left a very good architecture firm for a developer. But Jared Banks of Shoegnome Architects, on EntreArchitect, is blunt about the cost: development isn't an extra service, it's a second business. No client to guide you. Every delay yours. And collaboration without a leader turned a few months of permitting into nearly a year (for example).
© 2026 Talk Architecture, Author: Naziaty Mohd Yaacob. Photo by Pedro Miranda on Unsplash
Do subscribe for premium content and special features which will help to support and sustain Talk Architecture podcast on a more in-depth explanation on design thesis and processes. These special commentaries and ‘how to’ explanations are valuable insights and knowledge not found elsewhere!