One of the greatest frustrations in architecture is this: everyone expects certainty long before the process is actually coordinated enough to deliver it.
Clients want answers early. Builders want numbers early. Architects want to move design forward. Consultants are working from incomplete information. Interior selections happen later. Site conditions introduce complications. Budgets shift. Then construction begins and everyone acts surprised when the field becomes the place where the real coordination happens.
That is the broken part.
In my conversation with Adam Katz of Craydl, we explored a problem many architects know well but rarely define this clearly: the pre-construction process is often too fragmented, too reactive, and too dependent on assumptions. Adam’s perspective is especially valuable because he has worked across finance, development, construction, and software, and he sees the disconnect from all sides. He argues that too many teams are still working in silos, and the result is delay, waste, frustration, and lost profit.
For small firm architects, this conversation matters. Not because you need to become a software company or a construction manager, but because this is a leadership opportunity. Architects are in a unique position to improve the way projects begin. And when you improve the beginning, you improve almost everything that follows.
If you want to hear the full conversation, listen to Episode 651 at https://entrearchitect.com/651.
The real problem is not design
Architects are often blamed when projects drift off course, but the issue is usually not design itself. The issue is that design is expected to answer questions the process has not yet properly organized.
Clients come to architects with inspiration images, rough ideas, and emotional goals. Then very quickly they ask the two hardest questions in the business: How much will it cost? How long will it take?
Those questions are often answered too early, with too little information, and then used as the basis for hiring decisions and project expectations.
That is a setup for disappointment.
The architect is trying to balance aesthetics, function, and budget. The builder may not yet be involved deeply enough to contribute practical construction knowledge. Engineers may not yet be coordinated. Interior design decisions may still be unresolved. Yet everyone is speaking as if the project is already defined.
Small firm architects know this pain well. You can create beautiful work, thoughtful work, deeply intentional work, and still get punished if the process is not aligned around that work.
The lesson here is simple: do not confuse early design enthusiasm with project readiness.
Coordination is not a side task
One of the strongest ideas from this conversation is that coordination should not be treated as an afterthought. It is not the administrative burden. It is not the thing you squeeze in after the creative work is done. It is the work that protects the creative vision.
Adam described a common condition in the industry where architects, engineers, and designers all do their work separately, and the conflicts are discovered in the field instead of before construction. He built Craydl around the idea that someone needs to create and manage a single source of truth, so teams can identify clashes, omissions, and misalignments before they become expensive.
That idea is bigger than software.
For architects, it is a reminder that coordination is one of the profession’s most valuable services. It may not be the part clients admire on Pinterest. It may not be the part that wins design awards. But it is the part that prevents trust from collapsing.
When architects elevate coordination, they elevate the entire project.
Clients do not know where to start
This is one of the most important truths in residential architecture, and one the profession has not addressed well enough: most clients do not know where to begin.
They know they want a better home. They know they need more space, more function, more beauty, or more value. But they do not understand the process. They do not understand the sequence of decisions. They do not understand what is driving cost. They do not understand how one choice affects six others.
Homeowners often enter this market by asking friends whether they should start with an architect or a builder. That alone tells us how unclear the process feels from the outside.
This is where architects can lead.
If you are a small firm architect, your role is not only to design the project. Your role is also to frame the journey. The firms that do this best become trusted guides. They educate clients early. They clarify the path. They explain what decisions happen when. They identify the consequences of late changes. They create confidence before they create drawings.
That confidence is valuable. Clients pay for that kind of leadership, even when they do not have the language for it yet.
Better pre-construction protects profit
This is not just a process conversation. It is a business conversation.
When pre-construction is weak, architects lose in several ways. They lose time to revisions that could have been avoided. They lose margin because their teams spend energy correcting preventable problems. They lose trust when expectations were not aligned early. And too often, they lose the opportunity to demonstrate their true value because the conversation becomes about cost overruns instead of quality of leadership.
Adam made this point clearly when he connected risk mitigation directly to profitability. Every clash avoided, every missing decision identified early, every field surprise prevented means less waste and less financial pain for someone on the team.
Architects should hear this carefully.
Protecting profit is not selfish. It is what allows a small firm to stay healthy, serve clients well, compensate team members fairly, and continue doing meaningful work. If your process consistently absorbs chaos, your business will eventually pay for it.
The better your pre-construction process, the better chance you have to protect both your design and your bottom line.
Technology is not the answer, but it is a tool
A lot of architects resist new technology because they fear it will replace judgment, reduce craft, or force them into a more mechanical way of working. That concern is understandable. But that is not what this conversation suggested.
Adam’s advice was not to adopt every new tool. It was to identify one real problem and explore how technology might help solve it. He also emphasized that firms need to know their numbers and lean into technology in practical ways, especially as complexity continues to rise.
That is smart advice.
Technology should support better decisions, not replace them. It should improve clarity, not add noise. It should give architects more leverage, not more confusion.
For a small firm, this might mean improving budget conversations earlier in the process. It might mean creating better visualization tools for client communication. It might mean standardizing your internal workflows. It might mean building a stronger system for consultant coordination. The point is not to chase innovation for its own sake. The point is to remove friction from the places where your firm is losing time, money, or trust.
That is how better businesses are built. One solved problem at a time.
Architects can reclaim leadership in the process
What I found most encouraging about this conversation is that it points to an opportunity, not just a problem.
Yes, the pre-construction process is broken. Yes, homeowners are confused. Yes, builders and architects are often forced to make promises too early. Yes, fragmented information still causes too many costly mistakes.
But architects are uniquely positioned to help fix it.
You understand the vision. You understand how decisions connect. You understand that design is never just about appearance. It is about systems, assemblies, experiences, budgets, and consequences. That perspective is powerful.
The firms that will thrive in the future will not simply produce drawings. They will lead process. They will build trust by creating clarity. They will reduce risk by structuring better collaboration. They will educate clients instead of reacting to them. And they will create businesses that are stronger because their projects are stronger from the start.
That is the real takeaway from this episode.
The opportunity is not only to design better buildings. The opportunity is to design a better way of getting there.
And when architects do that well, everyone benefits. The client gets a better experience. The builder gets a better project. The team works with less friction. And the architect earns something too often lost in this profession: the ability to lead with confidence, create with purpose, and build a healthier business in the process.
To hear the full conversation, listen to Episode 651 at https://entrearchitect.com/651.
Leave a Reply