Few phrases in practice sound more harmless than this one:
“Could you just give us a quick opinion?”
It sounds light. Reasonable. Almost too minor to refuse.
And yet many architects know that what follows is rarely
minor.
A quick opinion in architecture is seldom only an opinion.
It draws on judgment shaped by years of training and practice. It may include
planning instinct, code awareness, buildability concerns, site reading, layout
implications, consent risk, and a feel for where a project is likely to
struggle. Even when expressed casually, it is still professional intelligence
at work.
That is why the phrase matters.
It often disguises the first transfer of value from
architect to prospective client before a formal appointment exists.
Of course, every practice needs some form of introductory
conversation. No one is suggesting that every first email or phone call should
trigger an invoice. Clients need a point of access. They need a way to test
fit, ask basic questions, and understand whether the architect is the right
person for the job.
But somewhere along the line, many practices seem to have
lost a clear line between welcoming enquiry and supplying billable professional
thinking.
That line is now blurry in ways that work against the
architect.
A “quick opinion” can become informal feasibility.
Informal feasibility can become design direction.
Design direction can become expectation.
And expectation can become pressure to keep helping before any real commercial
commitment is made.
The problem is not only the time taken. It is the reframing
of expertise as something naturally available in small slices before the
project has earned structured engagement.
That can happen because clients genuinely do not understand
where the boundary lies. It can also happen because architects themselves,
wanting to be helpful and responsive, offer too much too early in the hope of
building trust or winning the work.
But trust should not require the quiet surrender of scope.
The deeper issue is that early-stage architectural judgment
often feels intangible to the market. Because it arrives before drawings,
before formal packages, and before visible outputs, it is easier for others to
misread as conversation rather than service.
Yet in many projects, that early thinking is where the real
value begins.
It is where risk is first identified.
It is where wrong assumptions are interrupted.
It is where feasibility starts to become legible.
It is where the project begins moving from hope toward structure.
That is not peripheral value. It is foundational value.
So perhaps the profession should ask a more direct question:
where exactly does an introductory conversation end and professional input
begin?
Practices will answer that differently. But if the answer is
always vague, scope will continue to leak.
A healthier model may not require less generosity. It may
simply require clearer language: what we can discuss freely, what sits inside a
paid first step, and what kind of judgment is no longer casual once it starts
reducing uncertainty for the client.
A quick opinion is only quick from one side of the
conversation.
