by Mauro Moro
I find the first kickoff with clients pretty difficult. Not because they are demanding. But for the opposite reason. They are not demanding. Or to be precise, they are demanding in the wrong directions.
It is remarkable how clients manage to mix everything at once: scope, details, costs, structures, home automation, style, comfort, number of kitchen drawers, distance from the garage, finishes, and light indices. It is exhausting. Most of the time I do not feel like a designer. I feel like a shepherd trying to keep the flock together.
Clients must be demanding. I genuinely prefer working with demanding clients over easy ones.
Demanding in a much more useful way.
That means our thinking is on the same frequency.
The best clients I have worked with were not necessarily the ones who knew exactly what they wanted. Often they did not. What they had was something more valuable: a productive obsession with understanding what they were buying.
They asked questions. They challenged assumptions. They wanted to know why.
And, most importantly, they did not allow the concept phase to become a pleasant little presentation before the “real work” began.
Because the concept is real work.
This is not an article for architects. It is for the people paying for the building.
If you are commissioning a house, an office, a hotel, a development, or any serious architectural project, the concept phase is where many of the decisions that will govern your investment are first made. They are still cheap to question. Cheap to change. Cheap to reject.
Later, they become drawings. Then approvals. Then contracts. Then materials. Then concrete.
So before assumptions start narrowing the possibilities, ask better questions.
Here are five.
1. Is this really my idea, or just what I think I want?
You probably arrived with a vision. Good. You should.
Maybe you have been thinking about this project for years. Maybe you know how you want the house to feel. Maybe you know what is wrong with your office. Maybe you have a strong idea for the hotel, the restaurant, or the development.
That matters.
But it does not mean your first idea is the right solution.
This is where clients sometimes make an expensive mistake: they confuse an instinct with an answer. The brief becomes the first idea, and the first idea is rarely the right one. Some clients arrive so convinced of their own vision that the architect’s job quietly shifts from designer to executor. Someone there to realize what has already been decided. There are architects willing to work that way. That is their choice. But it rarely produces the best building.
The Clients might ask for more light.
Fine. But perhaps you do not actually have a light problem. Perhaps you have a circulation problem, one that keeps the brightest part of the building disconnected from where you spend your time.
The Clients might ask for an open plan.
Maybe. Or perhaps what you really need is flexibility, visibility, and connection, without the smell of frying potatoes filling the entire space.
The Clients might ask for something modern.
This is one of my favorites. What is MODERN? What does that mean? Glass? White walls? Or do you actually mean that you want a building free from the conventions of the one you live in now? Because those are completely different briefs.
Your job as a client is to bring the ambition. The architect’s job is to guide you toward its realization.
If you say I want X and the immediate answer is Sure! No problem! You may not be receiving a service. You may simply be placing an order.
Concept design should uncover the problem beneath the request.
So do not ask: Can you give me what I described?
Ask: What are you finding beneath what I described? Can you give me something better?
If there is no answer, the project may already be moving too quickly.
2. Would you really invest this money in something “more or less” defined?
Stop looking at the render for a moment.
Think about the amount of money you are about to spend.
Land. Construction. Financing. Consultants. Permissions. Engineering. Procurement. Contractors. Furniture. Maintenance. Time. Risk.
Now ask yourself a very simple question: would you make any other investment of this scale based on something that was “more or less” resolved? Or worse — produced in five minutes with a prompt?
Would you invest in a company whose business model was approximately right? Would you manufacture a product whose basic logic was still vague? Would you sign a major contract while saying, we’ll work out the important parts later?
Probably not.
Yet people do exactly this with buildings. They approve an attractive concept that remains fundamentally unresolved because the images look convincing enough to instil confidence.
Do not confuse visual confidence with design resolution.
A concept is not successful because it looks finished. It is successful when the important questions have been answered — and answered intelligently, not superficially.
What is this building trying to achieve? How does it work? Why is it organised this way? What does this decision cost — and what does it save? What happens if the programme changes?
A serious concept gives the project direction. A vague concept does not save money. It simply postpones decisions. And postponed decisions have an irritating habit of returning when changing them costs far more.
Reality always arrives eventually.
And reality invoices.
Ask your architect: Can you show me exactly what this concept solves — and what would change if the concept were different?
If the answer is mostly about aesthetics, keep asking.
3. Aren’t you tired of being sold the same solution?
Look around.
You have seen these buildings before.
I do not know if you have noticed, but something similar happened to cars. When I was a child, cars were wonderfully colourful — my mother drove a bright yellow Ford Fiesta. Look around now: almost everything on the road is grey, white or black. A few brave exceptions aside, the palette collapsed into safety.
Architecture did the same thing.
The same apartment plan with different finishes. The same house reorganised on another plot. The same open-plan living space. The same fashionable façade. The same “luxury” material palette. The same office pretending to be innovative because somebody added plants and informal seating. As if we were all wearing the same outfit, and the only variation was the colour of our phone case.
The same answer, given to a different question.
This is not mysterious. Repetition is efficient. Studios learn what works commercially. Details get reused. Layout logic gets recycled. Familiar solutions reduce risk and save time.
There is nothing inherently wrong with accumulated knowledge. The problem begins when efficiency replaces inquiry.
Your site is not the previous site. Your family is not the previous family. Your business is not the previous business. Your climate, constraints, ambitions and future are not identical to somebody else’s.
So why should your building be?
You may not recognize a recycled solution when it is presented to you. Why would you? You have not seen the previous ten projects from inside the studio.
But you will recognize its consequences eventually.
When a room never quite works the way you expected. When the circulation is annoying every single day. When the supposedly generous space feels strangely ordinary. When the light is wrong. When the thing that looked spectacular in the image becomes merely inconvenient in real life.
And by then, the concrete is dry.
A concept is where a project gets the chance to become specific to this place, this client, this budget, this moment, this problem. Specificity does not come from changing the cladding. It comes from thinking.
Ask: What is genuinely specific about this concept to my site, my brief, and my situation? How are you going to unlock its potential?
Then ask the uncomfortable follow-up question: What would my project’s value be after I’m gone? Does it have a value beyond solving my personal ambition?
The difference between those two answers may tell you exactly what you are paying for.
4. If the world has changed, why are we still building answers to old questions?
Buildings last. Assumptions do not.
The way we live has changed. The way we work has changed. Households have changed. Energy expectations have changed. Our relationship with privacy, mobility and community keeps changing.
And yet architecture has a remarkable ability to continue reproducing solutions long after the conditions that created them have disappeared.
That should concern you as a client.
Because a familiar solution is not necessarily safe. Sometimes it is simply an old assumption that nobody has bothered to question.
A timeless building is not one that refuses to respond to change. It is one whose underlying logic is strong enough to survive it. And that requires asking difficult questions now.
Who will actually use this building, and how might that change? Which spaces are fixed and which should adapt? What are we assuming about how people live or work here? What are we designing because it is genuinely necessary, and what are we repeating because architecture has always done it that way?
A concept built on yesterday’s logic may still look beautiful. It may photograph beautifully. It may win approval.
And it may still be wrong.
Ask your architect: What assumptions about the future are built into this concept, and what happens if those assumptions fail?
That is a much more valuable conversation than whether you prefer stone or timber.
5. You cannot produce your vision alone. Do you know who you are trusting with it?
This may be the most important question.
You have the ambition. The instinct. The investment. The risk. Perhaps even a very clear vision.
But you cannot turn it into architecture on your own. Translating a vision into architecture is the architect’s work, not the client’s.
An architect is not someone who receives your instructions and converts them into drawings. If that is all you need, you are buying technical execution. Concept design requires something else, translation, interrogation, judgment. The ability to hear what you are saying and also notice what you are not saying. The ability to challenge you without hijacking the project.
That relationship is not peripheral to the work. It is part of the work.
So be more demanding about who you choose than simply asking, “Do I like their images?” Can I afford their fee?
Ask instead: Do they listen? Do they ask uncomfortable questions? Can they explain why? Are they genuinely curious about my project or waiting for an opportunity to apply their architecture to it?
Then ask the question that matters most:
Does this person understand what I am actually trying to achieve, and do I trust them enough to let them challenge me?
If the answer is no, keep looking.
Technical competence cannot rescue a project in which the fundamental problem was never properly understood.
The Client Who Asks Nothing Gets What They Are Given
There is a strange fear among clients that asking too many questions will make them difficult.
Forget that.
Demanding is not the same as difficult. A difficult client interferes without understanding. A demanding client insists on understanding. Those are completely different behaviors, and good architects should not be frightened by the second kind. They should welcome it.
Scrutiny does not weaken a good concept. It strengthens it. If an idea cannot survive an intelligent question from the client, imagine how well it will survive a contractor, a budget cut, a planning authority, five years of use, and thirty years of weather.
The project will be questioned eventually. The only choice you have is when.
So before the concept begins, be curious. Be demanding. Ask why. Ask what was rejected. Ask what assumptions were made. Ask what is specific. Ask what the project solves. Ask what it costs you if the architect is wrong.
And be honest about what you do not know.
You are not paying an architect so that you never have to think about the project again. You are paying them so that the two of you can think about it together, and better.
A building is far too expensive a way to discover that nobody asked the right question.
That is not being difficult. That is being a client.
One last thing. This is my personal motto: a great design is not the product of a great architect. It is the product of the collaboration between a great client and a great architect.
Keep it in mind.
Don’t be a mediocre client. Be a great one.
Mauro Moro is an architectural concept designer based in Lisbon. He works at the intersection of strategic design and spatial thinking. Read more about concept design services and what concept design means in practice.