How much unpaid feasibility work is too much?

Feasibility is one of the most interesting stages in practice.

It is also one of the most vulnerable to being undervalued.

At this stage, the architect may be reading the site, testing constraints, considering planning implications, sensing likely massing, identifying risks, commenting on access, parking, services, or levels, and helping the client understand what kind of project may or may not be possible. It may not look like “design” yet in the conventional sense. But it is often the point at which the project becomes commercially intelligible.

That is precisely why the stage matters.

It is not merely preliminary. It is often where the most consequential early judgment lives.

And yet feasibility is still frequently treated as something that can be partly given away.

Perhaps that happens because it appears light. No detailed drawings, no visible package, no polished output. Just advice, thoughts, options, professional reading. But this is exactly the problem. The less visible the output, the easier it becomes for the market to misread the value.

The architect sees risk, possibility, limitation, and sequence.
The client may experience that as “helpful early guidance.”

The difference between those two perceptions is where scope leakage begins.

Small amounts of unpaid feasibility can seem harmless in isolation. A short review, a quick comment, an early sense-check. But stacked together, they can amount to significant professional work performed before commitment. And because feasibility often reduces uncertainty for the client, it can become the very stage where the client derives major value while the architect carries major ambiguity.

That should prompt a serious question for the profession: should feasibility almost always be a paid first stage?

There will always be some variation by project type, client sophistication, and practice model. But if feasibility is the stage where risk is clarified and commercial direction begins to emerge, then treating it as optional-to-charge may be one of the profession’s quieter self-inflicted wounds.

The reluctance to charge is understandable. Some architects worry that asking for fees too early will scare off the enquiry. Some hope that flexibility at the front end will lead to trust and later appointment. Some feel that feasibility is too “light” to justify formal engagement.

But if the work changes the client’s understanding of the project, reduces uncertainty, or provides a basis for decision-making, it is already professional value.

The profession may need stronger language here.

Not defensive language.
Not legalistic language.
Just clearer language.

What is included in an introductory conversation.
What sits inside a paid feasibility review.
What the client receives from that review.
And why that early step deserves recognition as service rather than goodwill.

Feasibility is not a prelude to value. It is value.

The real question is not whether architects should be generous. It is whether generosity has been allowed to displace structure at exactly the stage where structure matters most.

When did “just a quick opinion” become unpaid scope?

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.