Let me ask you two questions.
If you went to the dentist with a toothache, would you expect a free examination, and agree to pay only once the dentist actually fixed the tooth? Of course not. You pay for the diagnosis. You pay for someone to look at the problem, understand what is happening, draw on years of accumulated knowledge, and tell you what should be done.
That is not something that happens before the work. That is the work.
Now imagine going to a fruit market. You might be offered one grape to taste. But would you expect to eat an entire bunch before deciding whether it was worth buying? Probably not. A sample may be free. The product is not.
So why is the concept phase in architecture so often expected to be cheap? Or worse: free?
Why is the phase that determines almost everything that follows routinely offered as if thinking were not work, as if a decision were not a deliverable, as if architects simply had ideas springing naturally from their minds like water from a spring or lava from a volcano? Even accepting that having an idea can feel effortless in the moment, does anyone stop to ask where that capacity comes from? How long does it take to develop? How many years does it require to look at a site, a brief, a budget, a set of constraints, and possibilities and understand what should happen?
I will tell you why concept design has become so undervalued. And the uncomfortable answer begins with us. With architects.
We Did This to Ourselves
The devaluation of concept design was not simply imposed on architects by unreasonable clients. Architects participated in creating it. For decades, the concept has been used as the flexible part of the fee proposal, the phase that can be reduced, absorbed, partially given away, or quietly included in the hope of winning the rest of the commission.
The logic is easy to understand. Technical work has visible production costs. Drawings take time. Coordination takes time. Compliance takes time. Consultants, documentation, revisions, specifications, construction information. All of it requires measurable hours. It is difficult to fritter away those hours.
Concept feels different. You can sketch something in five minutes. Or, more dangerously, you can take a solution that worked on a previous project, adjust the dimensions, move a few walls, change the materials, and present it again. The client has probably never seen the original. Do that enough times and the business model becomes very efficient. And that is exactly the problem.
Practices operating on volume are naturally incentivized to minimize the time spent thinking about each individual project. Thinking cannot easily be scaled. Repetition can. So the concept became the place where costs were cut: reduce the fee, offer a preliminary sketch, show a few options to win the appointment, then compete with the practice next door, which is willing to do the same thing for slightly less. And then slightly less again.
Eventually, an entire market learns something dangerous: ideas are cheap; drawings are what you pay for. But that is exactly backward. The drawings document decisions. The concept is where those decisions are made.
I once had a conversation with an architect I respect. He made an observation that stayed with me: he had never seen another profession so willing to systematically undermine its own value. Think about how architects talk about each other’s work. The commentary is often more critical than constructive, bridging the gap between reputation and reality, between the image and the building, and between the name and the quality of what was actually delivered. Criticism is fundamental to architecture; we are trained through it. But there is a difference between critical thinking and an industry that competes by devaluing the work of its best practitioners.
Imagine professionals in any other field constantly racing to win clients by demonstrating that the competitor is incompetent and that they can perform the same service for less. It is not a long-term strategy for anyone.
Only established names and larger practices with recognized portfolios can consistently resist this pressure. Their accumulated reputation helps clients see the design process itself as something worth paying for. For everyone else, the temptation to compete on price remains enormous, and concept design was one of the first casualties.
What Does a Cheap Concept Actually Cost the Client?
There are several different conversations about the value of concept design. There is the concept produced by major international studios whose names carry significant commercial weight. There is the concept produced within highly commercial practices where efficiency and volume are central to the business model. And then there is something more important: the value of the concept to the person commissioning and occupying the building.
That is the conversation worth having.
Would you invest hundreds of thousands — or millions — in constructing an idea that took five minutes to produce? Would you knowingly build a solution largely adapted from another project because developing something specific to yours would take too long? Would you assume that a generic idea becomes a great building simply because the technical execution is excellent?
It will not. You can document the wrong decision perfectly. You can detail it beautifully. You can coordinate every engineering system with precision. You can produce impeccable construction drawings. And you will still build the wrong building. Technical competence cannot compensate for a design decision that was never properly considered.
That is what clients should be concerned about. Not whether concept design costs money, but what failing to invest in it may cost them later. An engineer once said something I have never forgotten, not an architect, but an engineer, someone whose work is to solve problems rather than sell ideas: “If you think professional consultancy is expensive, try buying cheap ideas. Then see how much they cost you.”
He was right. Bad ideas rarely remain cheap. They simply send the invoice later.
The Arithmetic Is Almost Embarrassingly Simple
In most architectural fee structures, concept design represents a relatively small portion of the total professional fee. And the professional fee is itself a fraction of the overall investment required to construct a building. The exact percentages vary across countries, project types, and scope. But the principle does not.
A very small percentage of the total investment determines a very large percentage of what that investment ultimately becomes. During concept design, it’s easy to reconsider the entrance. Changing circulation is easy. Testing a different orientation is easy. Questioning whether the building should occupy that part of the site at all is still possible.
Later, every one of those decisions becomes progressively harder. First, it affects consultants. Then approvals. Then technical drawings. Then procurement. Then contracts. Then construction. Then money is already spent. The direction is clear: the earlier a decision is corrected, the cheaper it is. Yet concept design, the phase when the greatest number of decisions can still be changed at the lowest cost, is precisely where clients are most often encouraged to economise.
But I Care Less About The Math Than About The Logic.
Architecture is a long game. One of the longest we play.
We are not designing something consumed tomorrow and replaced next week. We are establishing relationships in space that may endure for decades, determining how people move through a building, where light enters, what they see upon arrival, whether rooms feel generous or oppressive, whether a workplace encourages collaboration or isolation, and whether a house can adapt as a family grows and changes.
Architecture designs consequences through time. When those decisions are made carelessly, or not made at all, the failure compounds. Users live with it. Owners pay for it. Investors absorb it. Cities inherit it. The environment carries it.
And when are those fundamental choices made? During the concept phase. Not when someone is drawing the waterproofing detail; by then, the spatial decisions are already fixed. Not when the contractor arrives on site; by then, the budget is already committed. Not when the building is occupied, and people discover that something fundamentally does not work; by then, the concrete is dry.
Can we understand the responsibility contained in that moment? And then ask for it for free?
A Building Without a Concept Is a Bad Bet
I have been asked to produce technical documentation for projects where there was effectively no concept, no tested idea, no clear spatial proposition, and no convincing answer to what the building was trying to achieve. Just: here are the rooms; connect them.
But architecture cannot begin with connecting the rooms.
One of the questions I consistently ask is, “What is this building for?” Not the program; I can read the brief. I know whether it is a house, an office, a school, or a hotel. That tells me what happens inside. It does not yet tell me what the architecture should do.
What does the building give to the people who use it? What experience does it create? What relationships does it encourage? What problem is it actually solving? What does it contribute to its surroundings? Why should this building, on this site, for these people, take this particular form? Those are concept questions. And when the concept has been produced in five minutes or recycled from elsewhere, there is often no meaningful answer.
Without one, the project becomes a sequence of negotiations. The contractor wants one thing. The budget demands another. Planning regulations impose something else. The engineer needs a structural solution. The client changes their mind. A supplier proposes an alternative. Everyone pushes, and there is no central idea strong enough to hold the line.
That is one of the most important functions of a concept: it gives the project something worth protecting. Without it, a building risks becoming the accidental result of other people’s constraints. Technically compliant. Possibly buildable. Perhaps even photogenic. But without a clear reason for being what it is. Considering the land, materials, energy, money, labor, and environmental cost required to construct almost any building, that is an extraordinary gamble.
This Is Not Really a Message for Architects
At least, not primarily.
Architects will read this, and some will disagree. Many will say, “I do not work this way.” My practice values the concept phase. We never simply recycle solutions. Clients force prices down, leaving us with no alternative. Some of those responses will be entirely valid. But I am less interested in an internal argument about professional practice than in speaking directly to clients.
Because clients have more power in this situation than they often realize.
Before approving the next architectural proposal, it is worth asking a few questions. How did this idea develop? What alternatives were considered? What is specific to this site, this program, these constraints? How much time was genuinely invested in developing this concept?
If the concept arrived very quickly, that may be worth understanding. And if the concept is being offered for free, it is reasonable to ask, “Why?”
Perhaps you are receiving a generous introduction to a thoughtful process. Or perhaps you are receiving something that cost very little to produce. Those are not the same thing, and it is worth knowing which one you are being given before the project begins.
Concept Design Is Where Architecture Begins
Architecture does not begin with drawings.
It begins with thinking. By looking carefully. With identifying the real problem beneath the obvious one. By asking why before rushing towards how. With comparing possibilities, discarding poor ones, testing better ones, and making decisions that will shape the experience of a space for years.
That process is not preliminary to architecture. That process is architecture.
Concept design is not a luxury phase. It is not decoration or the attractive presentation produced before moving on to serious technical work. It is the moment when the project’s most consequential decisions are still flexible enough to be made properly.
Later, those decisions can still be changed. Of course they can. Almost anything in construction can be changed.
There is simply a difference.
During concept design, changing your mind costs thought.
Afterward, it will cost a great deal more.